How to Delete Failed Windows Update Folder Containing Req File

Use PowerShell to manually remove the stubborn Windows Update folder containing a .req file by stopping the Windows Update service, deleting the C:\Windows\SoftwareDistribution\DataStore directory, and restarting the service. This method bypasses GUI limitations that often fail when files are locked or corrupted, ensuring a clean slate for future updates on Windows 11 systems.

Why Manual Deletion Is Necessary

When Windows Update fails repeatedly, it often leaves behind residual files in the C:\Windows\SoftwareDistribution\DataStore directory. These folders can contain .req files, which indicate pending requests that were never processed due to errors. Attempting to delete this folder through the standard File Explorer interface frequently results in access denied errors or infinite loading states because the operating system locks these files while the update service is running. The Graphical User Interface (GUI) for Windows Update does not provide a built-in "clear cache" button that effectively removes these locked components. As noted in previous troubleshooting guides, simply clicking "Retry" often repeats the same failure loop without addressing the underlying corruption. Therefore, administrative intervention via PowerShell is required to gain full control over the directory structure.

Step-by-Step Removal Process

To successfully delete the failed update folder, you must first ensure no background processes are accessing the data. Follow these steps precisely to avoid system instability.

1. Open PowerShell as Administrator: Right-click the Start button and select "Terminal (Admin)" or "Windows PowerShell (Admin)." Running with elevated privileges is mandatory for modifying system directories.
2. Stop the Windows Update Service: Execute the following command to halt the service responsible for managing downloads and installations:

   Stop-Service -Name wuauserv

   Verify the status has changed to Stopped by running Get-Service -Name wuauserv.
3. Delete the DataStore Folder: Navigate to the root of your system drive if necessary, then execute the removal command. Be extremely careful to target only the correct path:

   Remove-Item -Path "C:\Windows\SoftwareDistribution\DataStore" -Recurse -Force

   The -Recurse flag ensures all subdirectories and the .req files within them are deleted. The -Force flag overrides any read-only attributes.
4. Restart the Service: Once the deletion is complete, restart the Windows Update service to allow the system to rebuild its database:

   Start-Service -Name wuauserv

   You should see the status return to Running.

After completing these steps, navigate back to Settings > Windows Update and click "Check for updates." The system will begin downloading fresh metadata, ignoring the previously corrupted local cache. This process effectively resets the update engine's state without requiring a full system reboot in most cases.

Verifying the Cleanup

It is important to confirm that the deletion was successful. Open File Explorer and navigate to C:\Windows\SoftwareDistribution. You will notice that the DataStore folder is missing. Over the next few minutes, as Windows Update runs, you may see the folder reappear. This is normal behavior; the system creates a new, clean database structure automatically upon detecting pending updates. If the folder does not reappear after several hours, check the Event Viewer under Applications and Services Logs > Microsoft > Windows > WindowsUpdate for any error codes. Persistent errors might indicate deeper issues with disk integrity or system file corruption rather than just a stuck update cache.

Related Resources

If you encounter unusual behavior during this process, such as unexpected script outputs or security alerts, refer to our guide on GitHub PowerShell Code Ran - Is Your Windows System Hacked? to rule out malicious interference. Additionally, for users who need to audit their recent administrative actions, the article View PowerShell History Without PSReadline: A Comprehensive Guide provides methods to trace exactly which commands were executed during the cleanup.

Frequently Asked Questions

Is it safe to delete the SoftwareDistribution folder?

Yes, it is safe to delete the contents of the SoftwareDistribution folder, particularly the DataStore subdirectory. Windows will automatically recreate the necessary structures when it next checks for updates. However, you cannot delete the entire SoftwareDistribution folder while the service is active, which is why stopping the service first is critical.

What if the DataStore folder refuses to delete even after stopping the service?

If the folder remains locked, another process might be holding it open. Use the Resource Monitor tool (resmon.exe) to search for handles related to wuauserv or specific .req files. Alternatively, a simple system restart often releases these locks more reliably than trying to identify the specific conflicting process manually.

Does this fix apply to Windows 10 as well?

Absolutely. While the title focuses on Windows 11, the SoftwareDistribution path and the wuauserv service name are identical in Windows 10. The PowerShell commands provided are compatible with both operating systems and require no modification for older versions.

Will deleting this folder uninstall my installed updates?

No, deleting the DataStore folder does not remove installed updates from your system. It only clears the temporary storage used for downloading and verifying new updates. Your existing software and feature updates remain intact and functional after this cleanup operation.

How long does it take for the folder to reappear?

The folder typically begins to reappear within minutes of restarting the Windows Update service, especially if there are pending updates available. If you have no pending updates, the folder may remain empty or absent until the next scheduled check-in time, which usually occurs every 24 hours by default.