0x80070002 Error code

Question

File not found when trying to access a file. This error occurs when a user or application attempts to access a file that Windows Server cannot locate at the specified path. The file may have been deleted, moved, renamed, or stored in an unavailable network location.

Answer 1

Hello @Kobi

Welcome to Microsoft Q&A!

Thank you for your patience, and taking the time to elaborate on your concerns.

Error 0x80070002: The system cannot find the file specified

Error 0x80070002 occurs when Windows cannot locate a file or resource required by an operation. This may happen when a file has been deleted, moved, or renamed, when a configured path is incorrect, or when a required file is unavailable.

Recommended troubleshooting steps

1. Verify the file path: Confirm that the file exists at the expected location and that its name and extension are correct.

Check permissions and network access: If the file is on a network share, verify connectivity and ensure the account running the application has the necessary permissions.

Review Event Viewer: Check the relevant Windows logs for additional details about the application or service reporting the error.

If Windows Update is affected: Run the Windows Update troubleshooter, then use the following commands from an elevated Command Prompt:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

1. If the error persists: Identify the operation that fails and inspect its logs to determine the exact file or resource Windows cannot find.

Important: Error 0x80070002 is a general file-not-found error, not a diagnosis of a specific Windows component. The appropriate fix depends on the application, service, or operation that triggers it.

I hope this helps to better understand the diagnostic options available and the risks involved.

If this information was helpful, please click Accept Answer.

Thank you for choosing Microsoft Q&A.

Answer 2

Error 0x80070002 typically means Windows cannot find a required file or path. In Windows Update scenarios, it is commonly caused by missing or corrupt files, incomplete previous updates, or registry entries that point to files or services that no longer exist.

Useful checks:

1. Verify the file or folder path
   • Confirm the file name and full path are correct.
   • If the issue is a general file access error, check whether the file was moved, renamed, or deleted.
2. Check Windows Update logs if the error occurs during updates
   • Review C:\Windows\Logs\CBS\CBS.log.
   • Also check rolled-over logs in the same folder such as CBSpersist*.log or .cab files.
3. Check for known missing folders in update failures
   • Verify that C:\ProgramData\Microsoft\Windows\Start Menu\Programs\System Tools exists.
   • If it is missing, copy the System Tools folder and its shortcuts from a working machine.
4. Check for missing .NET Framework files in monthly rollup failures
   • Verify whether C:\Windows\Microsoft.NET\Framework\v4.0.30319 is empty.
   • If CBS logs indicate related service issues, one documented fix is to back up and delete these registry keys, then try the update again:
     • HKLM\System\CurrentControlSet\services\clr_optimization_v4.0.30319_32
     • HKLM\System\CurrentControlSet\services\clr_optimization_v4.0.30319_64
   • Warning: Registry changes are risky. Back up the registry first.
5. If a cumulative update rolls back after restart
   • Check Event Viewer and CBS logs for missing driver files.
   • If a driver such as flpydisk.inf is identified, export the related registry keys from a working computer and import them on the affected computer. The documented example uses:
     • HKLM\System\CurrentControlSet\Services\flpydisk
     • HKLM\System\CurrentControlSet\Services\sfloppy
   • Warning: Importing registry keys changes system configuration. Back up first.
6. If the error happens during a Windows upgrade
   • Review Setupact.log for WIM mount errors.
   • If WIMMOUNT.sys is missing, export HKLM\System\CCS\Services\Wimmount.sys from a working server and merge it on the affected server.

If the scenario is simply file access outside Windows Update, the supported guidance is to check the spelling and path specification and verify the path exists.

---

• Troubleshoot Windows Update error 0x80070002
• File not found (Visual Basic Run-Time Error)
• Path not found