How to Fix Windows Error ERROR_WAS_LOCKED (Code 717)

In the tech jungle of Windows errors, encountering something cryptic like ERROR_WAS_LOCKED with a code of 717 (0x2CD) might feel like deciphering hieroglyphs. Rest easy—I’m here to guide Windows users through the cause, meaning, and most importantly, reliable fixes for this pesky problem. But let’s start by cracking the code behind this error—what does it even mean?

What is ERROR_WAS_LOCKED (Code 717)?​

The error message reads: "{Page Locked} One of the pages to lock was already locked." While this might sound like a textbook case of computer stubbornness, what it's actually saying is that Windows tried to lock a block of memory and discovered it was already locked. Essentially, it’s a problem with how the system manages memory, and it can stem from:

• Corrupted system files
• Conflicting applications
• RAM (random-access memory) issues
• Malicious activities or embedded malware

In simpler terms, some internal processes are banging heads over access to specific system resources. Now, before you start imagining tiny RAM sticks arguing with your OS, let’s focus on how to fix this and get your system back to smooth sailing.

The Golden Rule: Preliminary Steps​

Before we dive into hardcore fixes, there are a few easy checks to try. Make sure you:

• Reboot your PC (the good ol’ “turn it off and on again” can work wonders).
• Install any pending Windows Updates or software patches.
• Perform a robust malware scan using tools like Windows Defender, Malwarebytes, or your favorite trusted anti-virus software.

If NONE of these simple steps resolve it, it’s time to roll up those sleeves.

---

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

If corrupted Windows system files are steering the ship into chaos, you’ll want to repair them using DISM and SFC tools. These internal tools analyze and repair Windows' resource integrity.

Step-by-Step:​

• Press Windows + S, type "Command Prompt," and select Run as Administrator.
• In the command window, execute these three commands one at a time (press Enter after each):
  

     DISM /Online /Cleanup-Image /CheckHealth
  
     DISM /Online /Cleanup-Image /ScanHealth
  
     DISM /Online /Cleanup-Image /RestoreHealth

• Once completed, follow up with this:
  

     sfc /scannow

• Reboot your computer after the commands finalize.

Why These Work:

• DISM (Deployment Image Servicing and Management): Repairs cached copies of system files stored in a hidden Windows folder.
• SFC (System File Checker): Examines your system for damage and replaces corrupted files with healthy ones. Think of it as housekeeping for Windows.

---

Fix 2: Perform a Clean Boot to Identify Conflicting Apps​

Sometimes the issue isn’t Windows itself but another installed app tugging at the same system resources. A clean boot is like starting Windows in "bare-bones mode," helping you identify which programs are causing trouble.

Step-by-Step:​

• Press Windows + S, type "System Configuration," and hit Enter.
• Navigate to the Services tab.
• Check Hide all Microsoft services.
• Click Disable All (this turns off non-Microsoft apps/services).
• Move to the Startup tab and click Open Task Manager.
• Disable every non-critical startup app (anything that's not directly necessary for your system).
• Reboot.

If the error disappears, enable one service/application at a time to discover the culprit. Once identified, uninstall the problematic app.

---

Fix 3: Uninstall Problematic Programs or Recent Installations​

If this error started shortly after you installed new software, reverting those changes might be the solution.

Step-by-Step:​

• Press Windows + R, type appwiz.cpl, and press Enter.
• Uninstall any recent applications that coincide with the error's timing.
• If simple uninstalls don’t resolve the issue, use a tool like Revo Uninstaller to wipe leftover files, registry entries, and fragments completely.

Pro Tip: Rogue apps often leave behind traces that still cause issues. Tools like Revo or iObit Uninstaller are excellent for cleaning up residual files.

---

Fix 4: Diagnose Faulty RAM with Memory Diagnostic Tools​

If the error traces back to hardware, specifically your RAM, you’ll need to run a diagnostic scan.

Using Built-In Windows Memory Diagnostic:​

• Press Windows + S, type "Windows Memory Diagnostic," and select the option.
• Click Restart now and check for problems.
• After the test completes, investigate the logs using:
• Search for 'mdsched.exe' files in Event Viewer.

Advanced RAM Testing with Memtest86+:​

• Use Memtest86+, an open-source RAM diagnostic tool, which you can boot off a USB stick for a deeper scan.

What to Look For:
If the tool flags errors with a specific RAM module, it’s time to replace that stick. RAM faults can wreak havoc on system performance—but a failing stick is easy to swap out.

---

Fix 5: Perform a System Restore​

If none of the fixes above work, roll your system back to a time before the error appeared. This doesn’t affect personal files but will revert system settings, drivers, and installed apps to the restore point.

Step-by-Step:​

• Press Windows + S, type "Create a Restore Point," and select the result.
• Click System Restore, then Next.
• Choose a restore point dated before the error showed up.
• Follow the prompts, and let Windows do its thing.

Heads Up: The process can take 15-45 minutes, depending on the system size, so ensure your PC is on a stable power source.

---

Why You Shouldn’t Ignore This Error​

If left unresolved, ERROR_WAS_LOCKED 717 can lead to broader stability problems:

• Crashes during critical operations
• Inability to run certain applications
• A grueling performance dip

The memory mismanagement triggering this error, when compounded over time, may indicate deeper hardware faults, so troubleshooting systematically is key!

---

Final Thoughts​

Dealing with ERROR_WAS_LOCKED 717 might feel a bit like untangling holiday lights, but it’s fixable with patience. Most users will find relief through simple file repairs or clean boots, while others may need to take the hardware route. Either way, the solutions here are designed to guide you from "Oh no!" to "Finally fixed!" without losing sleep—or data.
Have a success story resolving this yourself? Let us know to help out our community on WindowsForum.com. Or, if you’ve encountered any twists in handling this error, share your tips to help the next person avoid unneeded frustration.

---

Source: Windows Report How to Fix ERROR_WAS_LOCKED 717 (0x2CD) in Windows