DigitalPersona 5300 driver (patched) — Overview and guidance
Summary
- The DigitalPersona 5300 is a USB fingerprint reader used for biometric authentication; its official drivers are typically provided by the vendor (DigitalPersona / later crossmatch/ HID Global integrations) and by OEMs. “Patched driver” usually refers to a modified driver that adds features, fixes compatibility issues, removes vendor restrictions, or bypasses firmware/OS checks. Using patched drivers may carry security, stability, and legal risks.
Typical reasons people look for a patched driver
- Restore compatibility with modern OS versions (e.g., newer Windows releases where original driver installers fail).
- Re-enable legacy features removed by newer vendor drivers.
- Remove forced enrollment or cloud-lock behavior imposed by vendor software.
- Enable use with third‑party biometric software that doesn’t accept the stock driver.
- Fix bugs (device not recognized, intermittent disconnects, bad image capture).
Common changes in patched drivers
- Modified INF files to allow installation on different hardware IDs or unsigned driver installation.
- Hooking or wrapping vendor DLLs to alter API behavior.
- Replacing or removing telemetry/phone-home components.
- Adjusting USB timeouts, packet sizes, or control transfers to accommodate OS stack changes.
- Removing signature enforcement (unsigned kernel-mode drivers) or re-signing with alternate certificates.
- Patching vendor-supplied middleware to change licensing checks.
Technical considerations
- Driver type: DigitalPersona 5300 typically uses a kernel-mode driver plus user-mode middleware for fingerprint capture and SDK libraries. Kernel components are the most sensitive: unsigned or altered kernel drivers can cause BSODs or be blocked by Windows Driver Signature Enforcement.
- Compatibility: Patched drivers may be intended for a particular Windows build (e.g., 7, 8.1, 10, 11). Mismatched drivers can lead to device malfunction or degrade system biometric stack (Windows Hello, credential providers).
- Middleware/SDK: Third-party apps integrate via DigitalPersona SDKs (e.g., DPFPDev, DPFPDevUSB). A patched driver may also require matching patched middleware to avoid API mismatches.
- Security: Biometric drivers and middleware deal with sensitive data (fingerprint images, templates). Patched drivers can change how data is stored or transmitted—introducing risk of template leakage, local compromise, or weakening of template protection.
- Signing and driver installation: On modern Windows, kernel drivers must be signed; installing unsigned patched drivers often requires disabling driver signature enforcement or using test-signing, which reduces system security.
Legal and policy risks
- Altering proprietary drivers or redistributing patched versions can violate software license agreements or local laws.
- Using patched drivers to bypass licensing or authentication protections may violate terms of service or be unlawful in some jurisdictions.
- Corporate policy: enterprise environments typically prohibit installing unofficial drivers for compliance and audit reasons.
Safe alternatives and recommended approach
- Official support
- First try official drivers from the device OEM or supplier website and contact their support for updated releases or compatibility patches.
- Vendor SDK and updates
- Use the vendor’s SDK (official) and middleware that are kept up to date; vendors sometimes release signed drivers for newer OSes.
- Firmware updates
- Check for firmware updates from the vendor/OEM before seeking patched drivers.
- Virtualization or compatibility mode
- If driver works only on older systems, consider running legacy OS image in a VM and connecting the device via USB passthrough.
- Open-source or community drivers
- Where available and reputable, community drivers with maintained source code (allowing audit) are preferable to opaque patched binaries.
- Test in isolated environment
- If you must test a patched driver, do so on a disposable/test machine or VM snapshot; do not deploy to production systems.
- Verify integrity and origin
- Avoid downloading drivers from untrusted sites. If using community builds, prefer those with source code or reproducible build instructions.
- Endpoint protection and monitoring
- After installation, monitor system behavior, check for unusual network activity, and ensure backups and system restore points exist.
Installation checklist (safe, minimal)
- Obtain driver and verify source/trust.
- Create a full backup or system snapshot.
- Disable automatic Windows updates for drivers (temporarily) to prevent overwriting.
- Use Device Manager to update driver, pointing to extracted files; if unsigned, you may need to enable test-signing (understand the risk).
- Reboot and test enrollment, capture quality, and integration with target applications.
- Revert to backup if instability occurs.
Troubleshooting common problems
- Device not detected: check USB cable/port, power; try different port; check Device Manager for code 10/43.
- Driver shows as unsigned: Windows 10/11 will block—use test-signing only in controlled test environment.
- Low-quality captures: verify firmware, run vendor calibration tools, clean sensor surface.
- Middleware/API errors: ensure SDK versions match driver expectations; check for mismatched DLL versions.
- Blue screens: uninstall patched driver in Safe Mode and restore previous driver or snapshot.
When you might accept risk
- Lab testing or research on device behavior or interoperability.
- Integrating device with legacy systems where no vendor update is available and business need is high—after risk assessment and approval.
When to avoid patched drivers entirely
- On production systems with sensitive biometric data.
- If vendor support or warranty is required.
- If driver comes from unknown/untrusted source or is distributed with unclear licensing.
Short checklist for evaluating a patched driver before use
- Source trustworthiness (owner, repo, signatures)
- Availability of source code or clear changelog
- Target OS/build compatibility
- Whether kernel components are modified/unsigned
- Evidence of community review or vendor acknowledgement
- Rollback plan and backups
Concluding recommendation
- Prefer official, signed drivers or well-audited open-source alternatives. Use patched drivers only for testing in isolated environments, after verifying provenance and accepting the security and legal trade-offs.
If you want, I can:
- Provide step-by-step installation instructions for a specific Windows version (I will assume Windows 10 x64 unless you state otherwise).
- Suggest places to check for official driver updates and SDKs.
- Outline a minimal test plan to validate a patched driver safely.
HID DigitalPersona 5300 (formerly U.are.U 5300) is a high-performance, PIV-certified fingerprint reader used for secure enrollment and authentication in large-scale environments. While specific "patched" driver files are rarely released as standalone downloads by the manufacturer, critical updates are typically delivered through DigitalPersona Lite Client patches or specific library updates. HID Global Core Connectivity & Driver Behavior
The DigitalPersona 5300 operates differently than standard plug-and-play USB devices. Technical support for this reader is often provided by a code library dpfpdd5000.dll ) rather than a traditional Windows driver. HID Global Integrated Installation : Drivers are usually bundled within the DigitalPersona Workstation or Kiosk installation packages. WBF vs. Legacy
: The reader often uses proprietary SDKs and is not natively compatible with Windows Hello
unless a specific Windows Biometric Framework (WBF) driver is used. Manual Reinstallation
: If the device is missing from the Device Manager's "Authentication Devices" section, the driver can often be manually found and reinstalled from the local directory: C:\Windows\DPDrv HID Global Troubleshooting & Common "Patches"
Users seeking a "patched" driver are often attempting to resolve specific installation errors or compatibility issues with newer Windows versions. Remote Patching : Administrators can deploy DigitalPersona Lite Client patches
remotely using MSI technology for 32-bit and 64-bit environments. Error 1310 Fix
: To resolve a common installation "Error 1310," administrators may need to run the setup with elevated privileges through the command prompt after clearing existing policy constraints. Device Visibility : If the reader is powered (indicated by a blue light
behind the sensor) but not recognized, users should check for HID Global Drivers
and verify if the provider is listed as "HID Global" or "Microsoft" in the Device Manager. SDK Availability : For developers, the 5300 is compatible with the latest DigitalPersona Biometric SDKs
, which include the necessary libraries for capture and extraction. Technical Specifications HID DigitalPersona 5300 Fingerprint Reader
The HID DigitalPersona 5300 Go to product viewer dialog for this item.
(formerly U.are.U 5300) is a high-performance, FBI PIV and FAP 30 certified optical fingerprint reader designed for large-scale civil ID and commercial authentication. Obtaining a "patched" or functional driver often involves specific installation steps to ensure compatibility with modern operating systems like Windows 10 and 11. Core Technical Specifications
The device is built for durability and high-volume use in harsh environments.
Resolution: 500 dpi grayscale images in ANSI and ISO/IEC standard formats.
Durability: Features an IP64-rated glass platen that is resistant to chemical and physical damage.
Security: On-board electronics for counterfeit finger rejection and automatic calibration. Interface: USB 2.0 High Speed. Driver Installation & Troubleshooting Standard drivers for the DigitalPersona 5300
are typically included within the DigitalPersona Workstation or Kiosk client packages. Installation Path
Once the client software is installed, the driver files are usually located at C:\Windows\DPDrv.
In the Windows Device Manager, the reader should appear under Authentication Devices. Resolving Common Driver Issues
If the reader is not recognized or fails to initialize, users often employ these "patch" methods:
The DigitalPersona 5300 Patched Driver is a lifesaver for anyone trying to maintain legacy biometric hardware on modern systems. If you've ever dealt with the frustration of a high-quality scanner becoming a "paperweight" due to OS updates, this patch is the bridge you need. The Verdict: Essential for Legacy Support
The DigitalPersona 5300 remains one of the most reliable optical fingerprint readers on the market, but official driver support often lags behind the latest Windows 10/11 security builds. The "patched" version effectively bypasses compatibility hurdles, making it a 5-star utility for system admins and developers. Key Highlights
Seamless Integration: Once applied, the driver allows the hardware to be recognized instantly by the DigitalPersona SDK and standard Windows Biometric Framework.
Improved Stability: The patch addresses common "Device Not Found" errors and initialization hangs that plague the stock drivers on 64-bit systems.
Extended Hardware Life: It saves businesses significant costs by allowing them to keep using their existing 5300 units instead of upgrading to newer, more expensive models. What to Watch Out For
Security Permissions: Because it is a "patched" driver, you may need to disable Driver Signature Enforcement in Windows during installation.
Source Reliability: Always ensure you are sourcing the patch from a reputable developer or internal repository, as unofficial drivers can pose security risks. Final Thoughts
If you are running a high-traffic environment—like a bank or a secure office—this driver patch is the only way to ensure your 5300 scanners keep up with modern software demands. It’s a technical fix that delivers immediate ROI by restoring functionality to trusted hardware.
Method B: Temporary Disable DSE (For One Boot Session)
If you don’t want a permanent Test Mode watermark:
- Restart Windows while holding Shift → Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press 7 (Disable driver signature enforcement).
- Install the patched driver normally.
Note: This must be repeated after every reboot.
The Official Dead End
DigitalPersona (now part of HID Global) officially ended mainstream support for the U.are.U 5300 years ago. Their modern software suite, HID DigitalPersona, focuses on newer readers like the 4500, 5200, and 5500 series. For the 5300, HID’s standard response is: “Please upgrade your hardware.”
For companies with 50+ scanners, that’s a massive capital expense. For hobbyists or small offices, it’s a deal-breaker. Hence, the underground need for a patched driver—a modified version of the original .inf and .sys files that bypass timestamp or signature checks.
Step-by-Step: Installing the DigitalPersona 5300 Patched Driver on Windows 11
Assuming you have downloaded a verified patched driver (let’s call it DP5300_Patch_v2.zip), follow this guide. You must disable Driver Signature Enforcement temporarily.
Key Patch Features
- Digital Signature: The patched driver included a digital signature to ensure the authenticity and integrity of the software.
- Secure Data Storage: The patches introduced secure data storage mechanisms to protect sensitive user data, such as fingerprint templates.
- Compliance with Regulations: The patched driver ensured compliance with relevant regulations, such as GDPR and HIPAA, by implementing robust security measures to protect personal and sensitive data.
Alternative 1: Use the Generic Windows USB Driver
Ironically, the DigitalPersona 5300 is a standard USB HID fingerprint device. Windows 10/11 includes a generic "Windows Biometric Framework" (WBF) driver.
- Uninstall any failed DigitalPersona driver.
- Plug in the 5300. Let Windows automatically search for drivers.
- If it grabs "Microsoft WBF fingerprint driver," you may get basic functionality (Windows Hello only, no proprietary SDK).
Limitation: The generic driver does not support DigitalPersona’s own verification engine (DPAPI).
What Does "Patched" Mean in This Context?
When users encounter a "patched" driver for the DigitalPersona 5300, it generally refers to one of three scenarios. It is crucial to distinguish between them to ensure system stability.
Alternative 3: Cross-Grade to DigitalPersona 4500 or 5200
Used 5200 readers often sell for $15–$30 on eBay, and they have official, signed drivers for Windows 10/11. The sensor quality is identical to the 5300 (the 5300 was mainly a casing refresh). This is the smartest long-term investment.
5300 Driver Patched — Digitalpersona
DigitalPersona 5300 driver (patched) — Overview and guidance
Summary
- The DigitalPersona 5300 is a USB fingerprint reader used for biometric authentication; its official drivers are typically provided by the vendor (DigitalPersona / later crossmatch/ HID Global integrations) and by OEMs. “Patched driver” usually refers to a modified driver that adds features, fixes compatibility issues, removes vendor restrictions, or bypasses firmware/OS checks. Using patched drivers may carry security, stability, and legal risks.
Typical reasons people look for a patched driver
- Restore compatibility with modern OS versions (e.g., newer Windows releases where original driver installers fail).
- Re-enable legacy features removed by newer vendor drivers.
- Remove forced enrollment or cloud-lock behavior imposed by vendor software.
- Enable use with third‑party biometric software that doesn’t accept the stock driver.
- Fix bugs (device not recognized, intermittent disconnects, bad image capture).
Common changes in patched drivers
- Modified INF files to allow installation on different hardware IDs or unsigned driver installation.
- Hooking or wrapping vendor DLLs to alter API behavior.
- Replacing or removing telemetry/phone-home components.
- Adjusting USB timeouts, packet sizes, or control transfers to accommodate OS stack changes.
- Removing signature enforcement (unsigned kernel-mode drivers) or re-signing with alternate certificates.
- Patching vendor-supplied middleware to change licensing checks.
Technical considerations
- Driver type: DigitalPersona 5300 typically uses a kernel-mode driver plus user-mode middleware for fingerprint capture and SDK libraries. Kernel components are the most sensitive: unsigned or altered kernel drivers can cause BSODs or be blocked by Windows Driver Signature Enforcement.
- Compatibility: Patched drivers may be intended for a particular Windows build (e.g., 7, 8.1, 10, 11). Mismatched drivers can lead to device malfunction or degrade system biometric stack (Windows Hello, credential providers).
- Middleware/SDK: Third-party apps integrate via DigitalPersona SDKs (e.g., DPFPDev, DPFPDevUSB). A patched driver may also require matching patched middleware to avoid API mismatches.
- Security: Biometric drivers and middleware deal with sensitive data (fingerprint images, templates). Patched drivers can change how data is stored or transmitted—introducing risk of template leakage, local compromise, or weakening of template protection.
- Signing and driver installation: On modern Windows, kernel drivers must be signed; installing unsigned patched drivers often requires disabling driver signature enforcement or using test-signing, which reduces system security.
Legal and policy risks
- Altering proprietary drivers or redistributing patched versions can violate software license agreements or local laws.
- Using patched drivers to bypass licensing or authentication protections may violate terms of service or be unlawful in some jurisdictions.
- Corporate policy: enterprise environments typically prohibit installing unofficial drivers for compliance and audit reasons.
Safe alternatives and recommended approach
- Official support
- First try official drivers from the device OEM or supplier website and contact their support for updated releases or compatibility patches.
- Vendor SDK and updates
- Use the vendor’s SDK (official) and middleware that are kept up to date; vendors sometimes release signed drivers for newer OSes.
- Firmware updates
- Check for firmware updates from the vendor/OEM before seeking patched drivers.
- Virtualization or compatibility mode
- If driver works only on older systems, consider running legacy OS image in a VM and connecting the device via USB passthrough.
- Open-source or community drivers
- Where available and reputable, community drivers with maintained source code (allowing audit) are preferable to opaque patched binaries.
- Test in isolated environment
- If you must test a patched driver, do so on a disposable/test machine or VM snapshot; do not deploy to production systems.
- Verify integrity and origin
- Avoid downloading drivers from untrusted sites. If using community builds, prefer those with source code or reproducible build instructions.
- Endpoint protection and monitoring
- After installation, monitor system behavior, check for unusual network activity, and ensure backups and system restore points exist.
Installation checklist (safe, minimal)
- Obtain driver and verify source/trust.
- Create a full backup or system snapshot.
- Disable automatic Windows updates for drivers (temporarily) to prevent overwriting.
- Use Device Manager to update driver, pointing to extracted files; if unsigned, you may need to enable test-signing (understand the risk).
- Reboot and test enrollment, capture quality, and integration with target applications.
- Revert to backup if instability occurs.
Troubleshooting common problems
- Device not detected: check USB cable/port, power; try different port; check Device Manager for code 10/43.
- Driver shows as unsigned: Windows 10/11 will block—use test-signing only in controlled test environment.
- Low-quality captures: verify firmware, run vendor calibration tools, clean sensor surface.
- Middleware/API errors: ensure SDK versions match driver expectations; check for mismatched DLL versions.
- Blue screens: uninstall patched driver in Safe Mode and restore previous driver or snapshot.
When you might accept risk
- Lab testing or research on device behavior or interoperability.
- Integrating device with legacy systems where no vendor update is available and business need is high—after risk assessment and approval.
When to avoid patched drivers entirely
- On production systems with sensitive biometric data.
- If vendor support or warranty is required.
- If driver comes from unknown/untrusted source or is distributed with unclear licensing.
Short checklist for evaluating a patched driver before use
- Source trustworthiness (owner, repo, signatures)
- Availability of source code or clear changelog
- Target OS/build compatibility
- Whether kernel components are modified/unsigned
- Evidence of community review or vendor acknowledgement
- Rollback plan and backups
Concluding recommendation
- Prefer official, signed drivers or well-audited open-source alternatives. Use patched drivers only for testing in isolated environments, after verifying provenance and accepting the security and legal trade-offs.
If you want, I can:
- Provide step-by-step installation instructions for a specific Windows version (I will assume Windows 10 x64 unless you state otherwise).
- Suggest places to check for official driver updates and SDKs.
- Outline a minimal test plan to validate a patched driver safely.
HID DigitalPersona 5300 (formerly U.are.U 5300) is a high-performance, PIV-certified fingerprint reader used for secure enrollment and authentication in large-scale environments. While specific "patched" driver files are rarely released as standalone downloads by the manufacturer, critical updates are typically delivered through DigitalPersona Lite Client patches or specific library updates. HID Global Core Connectivity & Driver Behavior
The DigitalPersona 5300 operates differently than standard plug-and-play USB devices. Technical support for this reader is often provided by a code library dpfpdd5000.dll ) rather than a traditional Windows driver. HID Global Integrated Installation : Drivers are usually bundled within the DigitalPersona Workstation or Kiosk installation packages. WBF vs. Legacy
: The reader often uses proprietary SDKs and is not natively compatible with Windows Hello
unless a specific Windows Biometric Framework (WBF) driver is used. Manual Reinstallation
: If the device is missing from the Device Manager's "Authentication Devices" section, the driver can often be manually found and reinstalled from the local directory: C:\Windows\DPDrv HID Global Troubleshooting & Common "Patches"
Users seeking a "patched" driver are often attempting to resolve specific installation errors or compatibility issues with newer Windows versions. Remote Patching : Administrators can deploy DigitalPersona Lite Client patches
remotely using MSI technology for 32-bit and 64-bit environments. Error 1310 Fix
: To resolve a common installation "Error 1310," administrators may need to run the setup with elevated privileges through the command prompt after clearing existing policy constraints. Device Visibility : If the reader is powered (indicated by a blue light
behind the sensor) but not recognized, users should check for HID Global Drivers
and verify if the provider is listed as "HID Global" or "Microsoft" in the Device Manager. SDK Availability : For developers, the 5300 is compatible with the latest DigitalPersona Biometric SDKs
, which include the necessary libraries for capture and extraction. Technical Specifications HID DigitalPersona 5300 Fingerprint Reader
The HID DigitalPersona 5300 Go to product viewer dialog for this item. digitalpersona 5300 driver patched
(formerly U.are.U 5300) is a high-performance, FBI PIV and FAP 30 certified optical fingerprint reader designed for large-scale civil ID and commercial authentication. Obtaining a "patched" or functional driver often involves specific installation steps to ensure compatibility with modern operating systems like Windows 10 and 11. Core Technical Specifications
The device is built for durability and high-volume use in harsh environments.
Resolution: 500 dpi grayscale images in ANSI and ISO/IEC standard formats.
Durability: Features an IP64-rated glass platen that is resistant to chemical and physical damage.
Security: On-board electronics for counterfeit finger rejection and automatic calibration. Interface: USB 2.0 High Speed. Driver Installation & Troubleshooting Standard drivers for the DigitalPersona 5300
are typically included within the DigitalPersona Workstation or Kiosk client packages. Installation Path
Once the client software is installed, the driver files are usually located at C:\Windows\DPDrv.
In the Windows Device Manager, the reader should appear under Authentication Devices. Resolving Common Driver Issues
If the reader is not recognized or fails to initialize, users often employ these "patch" methods:
The DigitalPersona 5300 Patched Driver is a lifesaver for anyone trying to maintain legacy biometric hardware on modern systems. If you've ever dealt with the frustration of a high-quality scanner becoming a "paperweight" due to OS updates, this patch is the bridge you need. The Verdict: Essential for Legacy Support
The DigitalPersona 5300 remains one of the most reliable optical fingerprint readers on the market, but official driver support often lags behind the latest Windows 10/11 security builds. The "patched" version effectively bypasses compatibility hurdles, making it a 5-star utility for system admins and developers. Key Highlights
Seamless Integration: Once applied, the driver allows the hardware to be recognized instantly by the DigitalPersona SDK and standard Windows Biometric Framework. The DigitalPersona 5300 is a USB fingerprint reader
Improved Stability: The patch addresses common "Device Not Found" errors and initialization hangs that plague the stock drivers on 64-bit systems.
Extended Hardware Life: It saves businesses significant costs by allowing them to keep using their existing 5300 units instead of upgrading to newer, more expensive models. What to Watch Out For
Security Permissions: Because it is a "patched" driver, you may need to disable Driver Signature Enforcement in Windows during installation.
Source Reliability: Always ensure you are sourcing the patch from a reputable developer or internal repository, as unofficial drivers can pose security risks. Final Thoughts
If you are running a high-traffic environment—like a bank or a secure office—this driver patch is the only way to ensure your 5300 scanners keep up with modern software demands. It’s a technical fix that delivers immediate ROI by restoring functionality to trusted hardware.
Method B: Temporary Disable DSE (For One Boot Session)
If you don’t want a permanent Test Mode watermark:
- Restart Windows while holding Shift → Troubleshoot → Advanced Options → Startup Settings → Restart.
- Press 7 (Disable driver signature enforcement).
- Install the patched driver normally.
Note: This must be repeated after every reboot.
The Official Dead End
DigitalPersona (now part of HID Global) officially ended mainstream support for the U.are.U 5300 years ago. Their modern software suite, HID DigitalPersona, focuses on newer readers like the 4500, 5200, and 5500 series. For the 5300, HID’s standard response is: “Please upgrade your hardware.”
For companies with 50+ scanners, that’s a massive capital expense. For hobbyists or small offices, it’s a deal-breaker. Hence, the underground need for a patched driver—a modified version of the original .inf and .sys files that bypass timestamp or signature checks.
Step-by-Step: Installing the DigitalPersona 5300 Patched Driver on Windows 11
Assuming you have downloaded a verified patched driver (let’s call it DP5300_Patch_v2.zip), follow this guide. You must disable Driver Signature Enforcement temporarily.
Key Patch Features
- Digital Signature: The patched driver included a digital signature to ensure the authenticity and integrity of the software.
- Secure Data Storage: The patches introduced secure data storage mechanisms to protect sensitive user data, such as fingerprint templates.
- Compliance with Regulations: The patched driver ensured compliance with relevant regulations, such as GDPR and HIPAA, by implementing robust security measures to protect personal and sensitive data.
Alternative 1: Use the Generic Windows USB Driver
Ironically, the DigitalPersona 5300 is a standard USB HID fingerprint device. Windows 10/11 includes a generic "Windows Biometric Framework" (WBF) driver.
- Uninstall any failed DigitalPersona driver.
- Plug in the 5300. Let Windows automatically search for drivers.
- If it grabs "Microsoft WBF fingerprint driver," you may get basic functionality (Windows Hello only, no proprietary SDK).
Limitation: The generic driver does not support DigitalPersona’s own verification engine (DPAPI). Typical reasons people look for a patched driver
What Does "Patched" Mean in This Context?
When users encounter a "patched" driver for the DigitalPersona 5300, it generally refers to one of three scenarios. It is crucial to distinguish between them to ensure system stability.
Alternative 3: Cross-Grade to DigitalPersona 4500 or 5200
Used 5200 readers often sell for $15–$30 on eBay, and they have official, signed drivers for Windows 10/11. The sensor quality is identical to the 5300 (the 5300 was mainly a casing refresh). This is the smartest long-term investment.
