How to Fix the ERROR_OPLOCK_HANDLE_CLOSED?

The ERROR_OPLOCK_HANDLE_CLOSED with an error code 803 (0x323 and description The handle with which this oplock was associated has been closed. The oplock is now broken, which typically indicates there is an issue with file locking in network file systems, usually in environments that have the SMB (Server Message Block) protocol, like networked drives or file sharing.

To fix it, check the network connection first and ensure both server and client machines are on the same network.

How can I fix ERROR_OPLOCK_HANDLE_CLOSED?

1. Restart the SMB service

1. Press the Windows key, type cmd in the search box, and click Run as administrator from the list of options to launch Command Prompt with elevated rights.
2. To restart the SMB service, copy the following commands one by one and hit Enter after every command:
   net stop server
net start server
3. Close the Command Prompt window.

2. Disable Opportunistic Locking (Oplocks)

1. Press Windows + R to open the Run dialog box.
2. Type regedit and click OK to open the Registry Editor app.
3. Click Yes on the UAC prompt.
4. First, go to File>Export. Save the .reg file at the desired location.
5. Navigate to this path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
6. Right-click the empty space, select New, then click DWORD(32-bit) value.
7. Name the DWORD as OplocksDisabled, then double-click it and set the Value data as 1.
8. Click OK, then restart your computer to confirm the changes.

3. Check for Windows updates

1. Press Windows + I to open the Settings app.
2. Go to Windows Updates, then click Check for updates.
3. If available, click Download & Install.
4. Select Advanced options.
5. Under Additional options, select Optional updates.
6. If there are updates available, select them and click Download & install.

4. Run the Check disk utility

1. Press the Windows key, type cmd in the search box, select Command Prompt, and choose Run as administrator from the list of options to launch Command Prompt with admin rights.
2. Type the following command to check the integrity of your file system and fix logical disk errors and press Enter: chkdsk C: /f /r
3. If the drive is in use, you will be prompted to schedule the scan after a restart. Type Y and press Enter.
4. Reboot your PC to initiate the scan and fix any corruption on the disk.

5. Disable antivirus temporarily

1. Press the Windows key, type Windows security in the search box, and click Open from the list of options.
2. Click Virus & threat protection.
3. Under the Virus & threat protection settings, click Manage settings.
4. Locate Real-time protection, and click the toggle to turn it off.

If you have third-party antivirus software, you can turn it off for a shorter period and check if the BSoD error still occurs.

6. Update/reinstall network drivers

1. Press Windows + R to open the Run window.
2. Type devmgmt.msc and click OK to launch Device Manager.
3. Locate Network adapters, click it to expand the category, right-click the network driver, and choose Update driver from the context menu.
4. Click Search automatically for drivers.

Windows will search for the best driver version for your device. If it is not able to do so, you can manually install the latest driver version from the device manufacturer’s website. Alternatively, you can get a third-party driver updater tool to ensure all the device drivers are up to date.

If you still get the ERROR_OPLOCK_HANDLE_CLOSED, follow these steps to reinstall the driver:

1. Launch the Device Manager app, locate & click Network adapters, right-click the driver, and choose Uninstall device from the context menu.
2. Select Uninstall again.
3. Go to Action, select Scan for hardware changes to reinstall the driver.

In conclusion, to fix the ERROR_OPLOCK_HANDLE_CLOSED, you can restart the SMB service, disable opportunistic locking, check for Windows updates, run the CHKDSK utility, disable the antivirus, or update/reinstall network drivers.

Recently, we also covered some other BSoD errors, such as ERROR_ACCESS_DISABLED_NO_SAFER_UI_BY_POLICY and ERROR_CORRUPT_LOG_OVERFULL

If you have any questions or suggestions about the BSoD error, feel free to mention them in the comments section below. We will be happy to help you!