Error Details
| Fact | Value | Source | Note |
|---|
| Exact error string | 0x80070002 | WindowsUpdate.log | -> ERROR_FILE_NOT_FOUND |
| Affected build range | Windows 11 23H2 | | |
| Registry key involved | HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate | registry | -> Check for relevant policies |
| Relevant service/endpoint URL | https://update.microsoft.com | | |
| Log line signature | Error 0x80070002: The system cannot find the file specified. | WindowsUpdate.log | |
Log Files to Check
C:\Windows\Logs\WindowsUpdate\WindowsUpdate.logC:\Windows\System32\winevt\Logs\Microsoft-Windows-Client-Side-Platform%4Operational.evtx
What This Error Actually Means
The error code 0x80070002, which translates to "ERROR_FILE_NOT_FOUND" in Windows Update logs, is raised when the system encounters a missing or corrupted file during the download or installation of an update. This can occur due to issues with BITS (Background Intelligent Transfer Service) failing to properly transfer files from Microsoft's servers, often because the manifest references a component that has been removed or whose hash has changed since the update was initiated.
The error is typically associated with the SoftwareDistribution folder located at
C:\Windows\SoftwareDistribution, where Windows Update stores downloaded updates before installation. If this folder contains incomplete or corrupted files, BITS will fail to download necessary components for an update, leading to a failure in the update process and triggering the 0x80070002 error.
Affected Versions and Scope
This issue is specifically observed on Windows 11 build 23H2. It does not affect other versions of Windows or earlier builds of Windows 11, such as 21H2. The problem can also occur in enterprise environments where strict update policies are enforced via the
HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate registry key.
The error is less likely to appear on systems that have a more relaxed update policy or those that do not enforce specific update rules through Group Policy Objects (GPOs) or Intune. However, this does not mean it cannot occur in such environments; the root cause often lies with network issues, server-side changes, or client-side corruption.
Where To Look First: Logs and Event IDs
To diagnose this issue effectively, start by examining two specific log files:
C:\Windows\Logs\WindowsUpdate\WindowsUpdate.log
C:\Windows\System32\winevt\Logs\Microsoft-Windows-Client-Side-Platform%4Operational.evtx
Within these logs, look for the exact error string: "Error 0x80070002: The system cannot find the file specified." Additionally, Event IDs 1001 and 1003 are particularly useful in diagnosing this issue. These event IDs can be found by using the
Get-WinEvent cmdlet with the following syntax:
Get-WinEvent -LogName "Microsoft-Windows-Client-Side-Platform/Operational" | Where-Object { $_.Id -eq 1001 -or $_.Id -eq 1003 }
These logs will provide detailed information about the specific update that failed and may indicate which files are missing or corrupted.
Root Causes
The primary causes of this error can be categorized into a few distinct scenarios:
Corrupted SoftwareDistribution Folder
This is often due to incomplete downloads, network interruptions during updates, or server-side changes that invalidate existing download packages. The presence of files with unexpected hashes in the
C:\Windows\SoftwareDistribution folder can indicate this issue.
BITS Service Issues
Problems within BITS itself can prevent it from successfully downloading update components. This might be due to network configuration issues, firewall rules blocking BITS traffic, or server-side changes that affect how updates are delivered.
Manifest Hash Mismatch
This occurs when the manifest file for an update references a component with a hash value that no longer matches the actual content on Microsoft's servers. This can be caused by server maintenance, software rollbacks, or other unexpected changes in the update pipeline.
Fix Procedure
To resolve this issue, follow these steps:
- Stop Windows Update and BITS Services: Use PowerShell to stop both services with the following commands:
Stop-Service -Name wuauserv
Stop-Service -Name bits
- Rename SoftwareDistribution Folder: Rename the folder at
C:\Windows\SoftwareDistribution to .old.
This step can break enrolled devices if they are currently in an update process.
- Rename Catroot2 Folder: Rename the folder at
C:\Windows\System32\catroot2 to .old.
- Restart Services: Restart both services with these commands:
Start-Service -Name wuauserv
Start-Service -Name bits
- Re-run Windows Update: Open the Settings app, go to "Update & Security," and click on "Check for updates."
If the issue recurs, check the CBS.log and WindowsUpdate.log files for specific component hash mismatches. You can use PowerShell cmdlets like
Get-WinEvent -LogName "Windows Update" | Where-Object { $_.Id -eq 1003 } to find relevant entries.
Error Code Variants
| Error Code |
Description |
Distinguishing Factors |
0x80070490 |
The update package is corrupt and cannot be installed. |
This error occurs when the downloaded file is corrupted but not missing. Check for partial downloads in SoftwareDistribution. |
0x80244017 |
The update cannot be installed at this time because the systems event log is full. |
This error indicates a full system event log rather than missing files. Clear logs using Event Viewer or PowerShell cmdlets like wevtutil cl System. |
Verification
To verify that the fix has been successful, check for the following:
- The WindowsUpdate.log should no longer contain entries with error code 0x80070002.
- Windows Update should be able to download and install updates without errors.
You can also use PowerShell cmdlets like
Get-WinEvent -LogName "Microsoft-Windows-Client-Side-Platform/Operational" | Where-Object { $_.Id -eq 1003 } to ensure that no new error entries are being logged.
Prevention
To prevent this issue from recurring, consider implementing the following measures:
- Regularly clear out old update files: Use PowerShell scripts or scheduled tasks to periodically clean up the SoftwareDistribution folder.
- Implement robust network policies: Ensure that BITS traffic is not being blocked by firewalls and that there are no unexpected interruptions during updates.
Additionally, you can use Intune policies to enforce these practices across your organization. Navigate to "Intune admin center > Devices > Configuration profiles" and create a new profile with settings like
./Device/Vendor/MSFT/Policy/AssignedAccess/UpdateCleanup to manage update files more effectively.
A quick diagnostic shortcut is using the command wusa /uninstall /kb:KBxxxxxx /norestart followed by a full system scan with Windows Update, which can often resolve issues without needing to rename folders.
By following these steps and implementing preventive measures, you can ensure that your systems remain up-to-date while minimizing the risk of encountering error 0x80070002.