


how to fix 'a digitally signed driver is required' on a win 64-bit system
Aug 01, 2025 am 04:47 AMThe "a digitally signed driver is required" error occurs because 64-bit Windows enforces driver signature verification to ensure system security and stability, blocking unsigned or self-signed drivers. 2. To temporarily bypass this for testing or legacy hardware, disable driver signature enforcement by restarting through Settings → Update & Security → Recovery → Advanced startup, then selecting "Disable driver signature enforcement" from Startup Settings after reboot, noting that this setting resets on each restart. 3. The recommended solution is to install a properly signed, WHQL-certified driver by downloading the latest 64-bit version from the manufacturer’s official website or using Windows Update via Device Manager. 4. Developers testing drivers can enable test signing mode by running "bcdedit /set testsigning on" in an elevated Command Prompt, which allows test-signed drivers to load and displays "Test Mode" on the desktop, reversible with "bcdedit /set testsigning off". 5. On UEFI systems with Secure Boot, ensure Secure Boot is enabled in Standard mode, as Custom or User modes may still block unsigned drivers, and avoid disabling Secure Boot to maintain system integrity. In summary, while temporary workarounds exist, the correct and secure fix is to use digitally signed drivers, with bypass methods reserved for specific, controlled scenarios only.
The "a digitally signed driver is required" error on a 64-bit Windows system typically appears when you're trying to install or load a driver that isn't properly signed by a trusted authority. Microsoft enforces driver signature enforcement on 64-bit versions of Windows to improve system stability and security. Here’s how to fix or work around this issue depending on your needs.

1. Understand Why This Happens
On 64-bit Windows (Windows 10, 11, etc.), driver signature enforcement (DSE) is enabled by default. This means only drivers signed with a valid digital certificate from a trusted certification authority can be loaded. Unsigned or self-signed drivers will be blocked, resulting in the error.
This is especially common when:

- Installing older hardware drivers
- Using custom or development drivers
- Testing unsigned drivers for development or legacy devices
2. Temporarily Disable Driver Signature Enforcement (For Testing)
If you need to install an unsigned driver temporarily (e.g., for testing or legacy hardware), you can bypass the requirement without permanently disabling security.
Steps:
-
Open Settings → Update & Security → Recovery
Under Advanced startup, click Restart now
After reboot, choose Troubleshoot → Advanced options → Startup Settings
Click Restart
-
After the system restarts, press F7 or 7 to select:
Disable driver signature enforcement
Windows will boot with enforcement turned off for that session.
Now you can install or load the unsigned driver.
?? Note: This setting resets after reboot. It's meant for temporary use only.
3. Install a Properly Signed Driver (Recommended)
The best and safest fix is to use a digitally signed driver.
How to do it:
- Visit the hardware manufacturer’s official website
- Download the latest 64-bit driver for your specific device and Windows version
- Ensure the driver is WHQL-certified (Windows Hardware Quality Labs)
- Use Device Manager to update the driver manually
If the manufacturer doesn’t provide a signed driver, consider:
- Using a different (compatible) device
- Contacting support to request a signed version
- Checking if Windows Update has a compatible driver
4. Enable Test Signing Mode (For Developers)
If you're a developer testing a signed-but-not-publicly-trusted driver, you can enable test signing.
Steps:
- Run Command Prompt as Administrator
- Type:
bcdedit /set testsigning on
- Press Enter and restart your PC
After reboot, you’ll see "Test Mode" in the corner of your desktop. This allows loading of test-signed drivers.
To disable later:
bcdedit /set testsigning off
? Only use this for development. Test-signed drivers are not secure for daily use.
5. Check Secure Boot and UEFI Settings (If Applicable)
On modern systems with UEFI and Secure Boot enabled, even temporarily disabling signature enforcement may not work unless Secure Boot is configured properly.
What to check:
- Enter BIOS/UEFI during boot (usually by pressing F2, Del, or Esc)
- Ensure Secure Boot is enabled and set to Standard (not Custom) mode
- Some systems block unsigned drivers entirely if in "Custom" or "User Mode"
Note: Disabling Secure Boot is not recommended and may not even allow Windows to boot.
Summary: What Should You Do?
Situation | Recommended Action |
---|---|
Installing old or third-party driver | Use Disable driver signature enforcement (temporary) |
Regular user with missing driver | Get a signed driver from the manufacturer |
Developer testing a driver | Enable test signing mode |
Frequent unsigned driver needs | Consider replacing hardware or using signed alternatives |
Basically, Windows is blocking the driver for security. While workarounds exist, the real fix is using properly signed drivers. Bypassing the check should only be done cautiously and temporarily.
The above is the detailed content of how to fix 'a digitally signed driver is required' on a win 64-bit system. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undress AI Tool
Undress images for free

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

When the Windows Security Center is blank or the function is missing, you can follow the following steps to check: 1. Confirm whether the system version supports full functions, some functions of the Home Edition are limited, and the Professional Edition and above are more complete; 2. Restart the SecurityHealthService service to ensure that its startup type is set to automatic; 3. Check and uninstall third-party security software that may conflict; 4. Run the sfc/scannow and DISM commands to repair system files; 5. Try to reset or reinstall the Windows Security Center application, and contact Microsoft support if necessary.

Players have been experiencing the PEAK voice chat not working issue on PC, impacting their cooperation during climbs. If you are in the same situation, you can read this post from MiniTool to learn how to resolve PEAK voice chat issues.Quick Navigat

The computer is stuck in the "Undo Changes made to the computer" interface, which is a common problem after the Windows update fails. It is usually caused by the stuck rollback process and cannot enter the system normally. 1. First of all, you should wait patiently for a long enough time, especially after restarting, it may take more than 30 minutes to complete the rollback, and observe the hard disk light to determine whether it is still running. 2. If there is no progress for a long time, you can force shut down and enter the recovery environment (WinRE) multiple times, and try to start repair or system restore. 3. After entering safe mode, you can uninstall the most recent update records through the control panel. 4. Use the command prompt to execute the bootrec command in the recovery environment to repair the boot file, or run sfc/scannow to check the system file. 5. The last method is to use the "Reset this computer" function

Encountering something went wrong 657rx can be frustrating when you log in to Microsoft Teams or Outlook. In this article on MiniTool, we will explore how to fix the Outlook/Microsoft Teams error 657rx so you can get your workflow back on track.Quick

When encountering the "RPCserverisunavailable" problem, first confirm whether it is a local service exception or a network configuration problem. 1. Check and start the RPC service to ensure that its startup type is automatic. If it cannot be started, check the event log; 2. Check the network connection and firewall settings, test the firewall to turn off the firewall, check DNS resolution and network connectivity; 3. Run the sfc/scannow and DISM commands to repair the system files; 4. Check the group policy and domain controller status in the domain environment, and contact the IT department to assist in the processing. Gradually check it in sequence to locate and solve the problem.

When you encounter the prompt "This operation requires escalation of permissions", it means that you need administrator permissions to continue. Solutions include: 1. Right-click the "Run as Administrator" program or set the shortcut to always run as an administrator; 2. Check whether the current account is an administrator account, if not, switch or request administrator assistance; 3. Use administrator permissions to open a command prompt or PowerShell to execute relevant commands; 4. Bypass the restrictions by obtaining file ownership or modifying the registry when necessary, but such operations need to be cautious and fully understand the risks. Confirm permission identity and try the above methods usually solve the problem.

When you encounter the "DefaultGatewayisNotAvailable" prompt, it means that the computer cannot connect to the router or does not obtain the network address correctly. 1. First, restart the router and computer, wait for the router to fully start before trying to connect; 2. Check whether the IP address is set to automatically obtain, enter the network attribute to ensure that "Automatically obtain IP address" and "Automatically obtain DNS server address" are selected; 3. Run ipconfig/release and ipconfig/renew through the command prompt to release and re-acquire the IP address, and execute the netsh command to reset the network components if necessary; 4. Check the wireless network card driver, update or reinstall the driver to ensure that it works normally.

When encountering the "SYSTEM_SERVICE_EXCEPTION" blue screen error, you do not need to reinstall the system or replace the hardware immediately. You can follow the following steps to check: 1. Update or roll back hardware drivers such as graphics cards, especially recently updated drivers; 2. Uninstall third-party antivirus software or system tools, and use WindowsDefender or well-known brand products to replace them; 3. Run sfc/scannow and DISM commands as administrator to repair system files; 4. Check memory problems, restore the default frequency and re-plug and unplug the memory stick, and use Windows memory diagnostic tools to detect. In most cases, the driver and software problems can be solved first.
