How to Resolve ERROR_WAS_LOCKED 717 in Windows

The ERROR_WAS_LOCKED error, identified by the code 717, signifies a specific type of memory management issue within the Windows operating system. This error occurs when the system attempts to lock a segment of memory, only to find that this particular memory page is already in a locked state by another process. Essentially, it indicates a conflict in how different applications or system processes are vying for access to the same memory resources, leading to a deadlock or an inability to proceed with the intended operation. This can manifest during various operations, from software installations to everyday application usage, causing disruptions and system instability.

Understanding the underlying cause is the first step toward resolving ERROR_WAS_LOCKED (717). The error message itself, “{Page Locked} One of the pages to lock was already locked,” points directly to a contention over memory access. This contention can arise from several sources, including corrupted system files that disrupt normal memory allocation, conflicting software applications that fail to release memory locks properly, underlying issues with the computer’s Random Access Memory (RAM), or even the presence of malware that interferes with system processes. Each of these potential causes requires a distinct troubleshooting approach to effectively clear the error and restore system stability.

Understanding the Error_Was_Locked 717

The ERROR_WAS_LOCKED error, specifically code 717, is a precise indicator of a memory access conflict within Windows. When a program or the operating system itself needs to secure a portion of memory for its operations—a process known as “locking” a page—it must ensure that no other process is currently using or has locked that same memory segment. The error 717 arises when this check fails, meaning the requested memory page is already locked by another entity. This situation prevents the current operation from proceeding, leading to the error message and potential program or system malfunction.

This memory locking mechanism is crucial for maintaining data integrity and preventing race conditions where multiple processes might try to modify the same data simultaneously, leading to corruption. When this mechanism encounters an already locked page, it signals a problem in resource management. The implications can range from minor application glitches to complete system freezes, depending on the criticality of the memory being accessed and the process attempting to access it.

The error message “{Page Locked} One of the pages to lock was already locked” is a technical description of this memory contention. It’s not a user-friendly explanation, but it accurately describes the state: Windows tried to lock a memory page, but it was already locked. This implies a breakdown in communication or coordination between different parts of the operating system or installed applications regarding memory allocation and usage.

Common Causes of ERROR_WAS_LOCKED 717

Several factors can contribute to the ERROR_WAS_LOCKED 717 error. Corrupted system files are a frequent culprit, as they can interfere with the proper functioning of memory management routines. When these critical files are damaged, Windows may struggle to correctly track or release memory locks, leading to conflicts.

Conflicting applications also play a significant role. Software that is poorly coded, runs in the background, or has resource management issues might fail to release memory locks when it’s supposed to. This can leave memory pages locked indefinitely, causing subsequent attempts to lock them to fail with error 717. Malware infections can similarly disrupt system processes and memory management, leading to this error.

Hardware issues, particularly with RAM, can also be a root cause. Faulty RAM modules can lead to unpredictable memory access errors, including memory page lock conflicts. If the system cannot reliably read from or write to RAM, it can manifest in various errors, including 717. Over time, these issues can degrade system performance and stability.

Preliminary Troubleshooting Steps

Before diving into more complex solutions, it’s wise to perform a few basic troubleshooting steps. A simple reboot of your computer can often resolve temporary glitches in memory management or process conflicts. This is akin to clearing the system’s short-term memory and allowing processes to start fresh.

Ensuring your Windows operating system and all installed software are up-to-date is also crucial. Pending updates often contain bug fixes that can address known issues with memory management or application compatibility. Finally, running a thorough malware scan with a reputable antivirus program can help rule out any malicious software that might be causing system instability and memory-related errors.

Fix 1: Repair Corrupted System Files Using DISM & SFC Commands

Corrupted Windows system files are a common reason for various errors, including ERROR_WAS_LOCKED 717. Fortunately, Windows provides built-in tools to scan for and repair these files: the Deployment Image Servicing and Management (DISM) tool and the System File Checker (SFC). These tools work together to ensure the integrity of your Windows installation.

To begin, you need to open the Command Prompt with administrative privileges. Press the Windows key + S, type “Command Prompt,” right-click on the result, and select “Run as administrator.” Once the elevated Command Prompt window is open, you will execute a series of commands. First, run DISM commands to repair the Windows image itself. These commands are:

DISM /Online /Cleanup-Image /CheckHealth

DISM /Online /Cleanup-Image /ScanHealth

DISM /Online /Cleanup-Image /RestoreHealth

Each of these DISM commands performs a progressively deeper check and repair of the Windows system image. The `/RestoreHealth` command is particularly important as it attempts to fix any detected corruption by downloading necessary files from Windows Update. After the DISM commands have completed their tasks, you will then run the SFC command. This command directly scans and repairs protected Windows system files. Enter the following command and press Enter:

sfc /scannow

This scan may take some time to complete. Once both DISM and SFC scans are finished, it is imperative to restart your computer. This allows the repaired or replaced system files to be properly integrated into the operating system, potentially resolving the ERROR_WAS_LOCKED 717 error.

Fix 2: Perform a Clean Boot to Identify Conflicting Apps

Software conflicts are a frequent cause of system errors, and ERROR_WAS_LOCKED 717 is no exception. A “clean boot” is a diagnostic process that starts Windows with a minimal set of drivers and startup programs. This helps you isolate whether a third-party application or service is causing the conflict.

To perform a clean boot, first, open the System Configuration utility. Press Windows + S, type “System Configuration,” and press Enter. Navigate to the “Services” tab. Here, you must check the box that says “Hide all Microsoft services.” This ensures you are only looking at non-Microsoft applications and services. After hiding the Microsoft services, click the “Disable All” button.

Next, go to the “Startup” tab within System Configuration. Click on “Open Task Manager.” In Task Manager, you will see a list of startup programs. For each non-essential program listed, right-click on it and select “Disable.” Be cautious not to disable critical system drivers or security software if you are unsure. Once all non-critical startup items are disabled, close Task Manager and return to System Configuration. Click “Apply” and then “OK.” You will be prompted to restart your computer. After the restart, if the ERROR_WAS_LOCKED 717 error no longer appears, it indicates that one of the disabled startup programs or services was the cause. You can then re-enable them one by one, restarting after each to pinpoint the exact conflicting application.

Fix 3: Check for RAM Issues with Windows Memory Diagnostic

Random Access Memory (RAM) is fundamental to how your computer operates, and faulty RAM can lead to a wide array of errors, including memory access conflicts like ERROR_WAS_LOCKED 717. Windows includes a built-in tool called Windows Memory Diagnostic that can help identify problems with your RAM.

To initiate this diagnostic, press the Windows key + S, type “Windows Memory Diagnostic,” and select the application from the search results. You will be presented with two options: “Restart now and check for problems (recommended)” or “Check for problems the next time I start my computer.” Choose the recommended option to restart your computer immediately and begin the memory test.

The diagnostic tool will run automatically upon reboot. This process can take a significant amount of time, depending on the amount of RAM you have. Once the test is complete, Windows will restart again, and you can view the results. If the tool detects any errors, it usually indicates that one or more of your RAM modules may be faulty and require replacement. Addressing faulty RAM is critical for overall system stability.

Fix 4: Uninstall Recently Installed Software

Sometimes, the ERROR_WAS_LOCKED 717 error can be triggered by a recently installed application. This is especially true if the software is not fully compatible with your system or has underlying issues with resource management. If the error began appearing shortly after installing new software, that software is a prime suspect.

To address this, you should uninstall the recently installed program. Press Windows + R, type “appwiz.cpl,” and press Enter to open the Programs and Features (or Add/Remove Programs) control panel. Locate the software that was installed most recently, right-click on it, and select “Uninstall.” Follow the on-screen prompts to complete the uninstallation process.

If a simple uninstall doesn’t resolve the issue, consider using a more thorough uninstaller tool, such as Revo Uninstaller. These tools can help remove leftover files, registry entries, and other remnants of the program that a standard uninstall might leave behind, ensuring a cleaner removal. After uninstalling the problematic software, restart your computer and check if the ERROR_WAS_LOCKED 717 error has been resolved.

Fix 5: Restore System to a Previous Point

If the ERROR_WAS_LOCKED 717 error started appearing recently, a System Restore can be an effective solution. System Restore allows you to revert your computer’s system files, installed applications, and registry settings back to a previous state when the error was not occurring. This can undo recent changes that may have caused the conflict.

To access System Restore, press Windows + S, type “Create a Restore Point,” and select the matching result. In the System Properties window that appears, click the “System Restore…” button. Click “Next” to proceed. You will see a list of available restore points. It’s best to choose a restore point that was created on a date before you started experiencing the ERROR_WAS_LOCKED 717 error.

Select the desired restore point and click “Next,” then “Finish.” Windows will warn you that the process cannot be interrupted once started. Confirm to proceed. Your computer will restart and begin the restoration process. If successful, your system will revert to the chosen state, and the error should be resolved. Note that any programs or updates installed after the chosen restore point will be removed.

Fix 6: Reset Network Settings

While less common, network-related issues can sometimes contribute to system errors like ERROR_WAS_LOCKED 717, especially if network processes are involved in memory management or if a network service is misbehaving. Resetting your network settings can resolve underlying network configuration problems that might be indirectly causing the memory conflict.

To reset network settings, open the Settings app by pressing Windows + I. Navigate to “Network & Internet,” then click on “Status.” Scroll down on the Status page and find the “Network reset” option. Click on it, and then click the “Reset now” button. You will be warned that this action will remove and then reinstall all network adapters and reset other networking components to their original settings. You will need to reconnect to your Wi-Fi networks and reconfigure any custom network settings after the reset.

Confirm the reset by clicking “Yes.” Your computer will restart automatically. After the reboot, Windows will attempt to reconfigure your network connections. This process can help clear out any corrupted network configurations or services that might be contributing to the memory lock issue.

Fix 7: Check for Windows Activation Issues

While not a direct cause of memory lock errors, Windows activation problems can sometimes lead to system instability and unusual errors. If your Windows license is not properly activated or has become invalid, it can trigger various system-level warnings or errors. It is worth checking your activation status as part of a comprehensive troubleshooting process.

To check your activation status, go to Settings by pressing Windows + I. Select “Update & Security,” then “Activation.” Here, you will see whether your copy of Windows is activated. If it indicates that Windows is not activated or that there is an activation error, you may need to troubleshoot this issue separately. This could involve entering your product key again, running the Activation Troubleshooter, or contacting Microsoft Support if the problem persists. Ensuring Windows is properly activated can sometimes resolve unexpected system behaviors.

Fix 8: Investigate Network Adapter Driver Issues

Problems with network adapter drivers can lead to a variety of connectivity and system stability issues. If the ERROR_WAS_LOCKED 717 error is occurring during network-intensive operations or if you’ve recently experienced network problems, it’s possible that a faulty or outdated network adapter driver is contributing to the issue.

To check your network adapter drivers, open Device Manager by pressing Windows + S, typing “Device Manager,” and selecting it from the results. Expand the “Network adapters” section. Look for any devices with a yellow exclamation mark or a red X, which indicate a problem. Right-click on your network adapter and select “Update driver.” You can choose to search automatically for updated drivers or browse your computer if you have downloaded a driver manually from the manufacturer’s website.

If updating the driver doesn’t help, consider uninstalling the device. Right-click the network adapter and select “Uninstall device.” Then, restart your computer. Windows will attempt to reinstall the driver automatically upon reboot. If the issue persists, you may need to download the latest driver directly from your network adapter manufacturer’s website and install it manually.

Fix 9: Consider a Corrupted User Profile

A corrupted user profile can lead to a wide range of unpredictable behavior within Windows, including errors like ERROR_WAS_LOCKED 717. When your user profile becomes corrupted, certain settings or data associated with your account may become inaccessible or damaged, leading to system instability.

To address a potentially corrupted user profile, the recommended approach is to create a new user account and then copy your essential data from the old profile to the new one. To create a new account, go to Settings > Accounts > Family & other users. Click “Add someone else to this PC” and follow the prompts to create a new local account. Once the new account is created and set up as an administrator, log in with it. Then, navigate to the C:Users folder, locate your old (corrupted) user profile folder, and copy all your important files (Documents, Desktop, Pictures, etc.) to the corresponding folders in the new user profile.

After transferring your data, you can try logging into your original profile one last time to see if the error is gone, or you can continue using the new profile. If the new profile works without the error, it strongly suggests that the original profile was indeed corrupted. You may need to reconfigure some application settings or re-login to certain services within the new profile.

Fix 10: Advanced Troubleshooting with Safe Mode

If the standard troubleshooting steps haven’t resolved the ERROR_WAS_LOCKED 717 error, booting into Safe Mode can provide a more isolated environment to diagnose the problem. Safe Mode starts Windows with a minimal set of drivers and services, which can help determine if a third-party application or driver is causing the conflict.

To boot into Safe Mode, you can access it through System Configuration (msconfig). Open System Configuration, go to the “Boot” tab, and under “Boot options,” check the “Safe boot” box. You can choose “Minimal” for a basic Safe Mode or “Network” if you need internet access. After applying the changes, restart your computer. If the error does not occur in Safe Mode, it confirms that a non-essential program or driver loaded during a normal boot is the cause.

Once in Safe Mode, you can systematically disable startup programs and services (similar to the clean boot process) to identify the offender. Remember to uncheck the “Safe boot” option in System Configuration once you have finished troubleshooting to return your system to normal startup. If you are stuck in Safe Mode, you may need to use the `msconfig` utility from within Safe Mode to disable the Safe Boot option and restart normally. Some users may need to use advanced recovery options or bootable media to exit Safe Mode if they cannot access `msconfig`.