How to Resolve “Amsdk.sys Driver Can’t Load” Error

The file named “amsdk.sys” is a driver associated with Zemana AntiMalware, a security tool designed to detect and remove threats such as malware, adware, spyware, and potentially unwanted programs (PUPs). The “Amsdk.sys driver can’t load on this device” error typically occurs when Windows’ Memory Integrity feature blocks the driver, considering it untrustworthy.

This issue is often caused by security restrictions imposed by the Memory Integrity feature, which prevents drivers that don’t meet Windows compatibility standards from running. Since the Amsdk.sys driver is part of a third-party program, Memory Integrity may block it from loading on your system.

To resolve this issue, you can either stop Windows from blocking the driver or uninstall Zemana AntiMalware entirely, especially if you no longer wish to use the software. Below, we’ll explore the steps to fix the issue.

1. Reinstall Zemana AntiMalware Program

The Amsdk.sys driver may be corrupted or outdated, causing it to be blocked by Windows. A problematic driver, especially one with missing or corrupted files, can trigger this issue. To resolve this, you can either update or reinstall the program to ensure it’s functioning correctly.

1. Press the Windows + R keys to open the Run Dialog.
2. Type appwiz.cpl in the input box and click OK. This will open the Programs and Features window in the Control Panel.
3. Locate Zemana AntiMalware in the list, then double-click it to begin the uninstallation process.
4. Once the uninstallation is complete, you can either reinstall the application to restore the driver or avoid reinstalling it to resolve the error.

2. Disable Memory Integrity

Windows blocks certain drivers that do not meet its compatibility standards. One key feature responsible for blocking unauthorized or unsigned drivers is Memory Integrity (Core Isolation), which is found in Windows Security. Disabling the Memory Integrity feature will allow Amsdk.sys to run on the system. To do so, follow these steps:

1. Open the Start Menu by pressing the Win key.
2. Type Windows Security and hit Enter to open Windows Security.
   
3. Select Device Security from the left-hand sidebar.
4. Under Core Isolation, click Core Isolation Details.
   
5. Turn off the Memory Integrity feature and check the issue.
   

3. Temporarily Disable Driver Signature Enforcement

Driver Signature Enforcement is a feature that prevents unauthorized or unsigned drivers from being loaded in Windows. Since Amsdk.sys is an unsigned driver, we can try temporarily disabling Driver Signature Enforcement to check if it is blocking the driver or not.

1. Click the Start Menu and type Command Prompt.
2. Right-click on it and select Run as administrator.
   
3. In the command prompt, enter the following command.

   bcdedit /set nointegritychecks on

   

4. This should disable the driver signature enforcement, allowing unsigned drivers to be installed on the system.

4. Update Windows Including All Optional Updates

Recent versions of Windows enforce stricter driver validation to enhance system security. As a result, outdated or unsigned drivers, such as Amsdk.sys, are often blocked from loading. Microsoft regularly addresses driver compatibility issues through cumulative updates and optional updates. These updates may include:

• A newer, digitally signed version of the Amsdk.sys driver.
• System-level improvements to enhance compatibility with Windows security features like Memory Integrity and Core Isolation.

Many users reported that after installing all updates (including the optional updates), their issue was completely resolved.

1. Press the Windows + S keys together to open Windows Search.
2. Type Check for updates in the search bar and press Enter.
3. Go to Windows Update > Advanced Options > Optional Updates.
4. Expand the Driver Updates and Other Updates sections, then select all available updates to install both driver and Windows updates.
5. Once the updates are installed, restart your computer and check if the issue is resolved.

By following the solutions above, Amsdk.sys should load properly.

However, if it fails to load and it is not necessary for you to run it, you can disable it permanently by running the commands:

sc stop amsdk
sc config amsdk start=disabled

in the command prompt as an administrator.

This should fix the error message.