# Why Windows Shows ERROR_FILE_NOT_FOUND—and What to Do Next?

Windows errors can be confusing, especially when a simple message such as
ERROR_FILE_NOT_FOUND appears without explaining what went wrong. One of the most
common codes associated with this message is 0x80070002.

The error essentially means that Windows or an application tried to access a
file but could not find it at the expected location. The missing file may belong
to Windows, an installed application, an update, a driver, or another system
process.




WHAT DOES ERROR_FILE_NOT_FOUND MEAN?

ERROR_FILE_NOT_FOUND is a Windows error condition indicating that a requested
file could not be found.

A common associated error code is:

Error Code

Meaning

What It Indicates

0x80070002

ERROR_FILE_NOT_FOUND

Windows cannot find a required file

0x80070003

ERROR_PATH_NOT_FOUND

Windows cannot find the specified path




WHY DOES WINDOWS SHOW ERROR_FILE_NOT_FOUND?

Several situations can cause the error.

Possible Cause

What Happens

Missing file

A required file was deleted or moved

Corrupted system files

Windows components are damaged

Failed Windows Update

Update files are incomplete or corrupted

Incorrect file path

Software points to a location that no longer exists

Application corruption

Program files are missing or damaged

Driver problems

A required driver component cannot be located

Scheduled task

A task references a deleted executable

Storage changes

Files were moved between drives or folders

Identifying when the error occurs is one of the most useful ways to narrow down
the cause.

--------------------------------------------------------------------------------

When Does ERROR_FILE_NOT_FOUND Usually Appear?

The error may appear in different circumstances.


DURING WINDOWS UPDATE

If the message appears while Windows is downloading or installing an update, the
problem may involve damaged or incomplete update files.


WHEN OPENING AN APPLICATION

If only one application produces the error, its installation may contain missing
or corrupted files.


DURING STARTUP

An application, service, or scheduled task may be trying to launch a file that
has been removed.


DURING FILE OPERATIONS

Moving, opening, copying, or accessing files can trigger the error if Windows is
given an invalid or unavailable path.

--------------------------------------------------------------------------------

What to Do When ERROR_FILE_NOT_FOUND Appears


1. RESTART WINDOWS

Start with the simplest troubleshooting step.

Save your work, select Start → Power → Restart, and then try the operation
again.

If the error was caused by a temporary process or file-access problem, a restart
may resolve it.

--------------------------------------------------------------------------------


2. IDENTIFY THE MISSING FILE

If the error message provides a filename or path, examine it carefully.

For example, an application might indicate that it cannot find a file inside:

C:\Program Files\ExampleApp\

Open File Explorer and check whether the referenced file exists.

If it does not, determine which application or Windows component owns the file
before attempting to replace it.

Avoid downloading individual DLL or EXE files from random websites. Replacing a
system file with an untrusted copy can create additional security and
compatibility problems.

--------------------------------------------------------------------------------

3. Run System File Checker

If you suspect damaged Windows system files, Microsoft's built-in System File
Checker can scan protected system files.

Open Command Prompt as administrator and run:

sfc /scannow

Wait until the scan completes.

If SFC reports that it repaired files, restart Windows and check whether the
error has disappeared.

--------------------------------------------------------------------------------

4. Use DISM to Repair Windows Components

If SFC cannot resolve the problem, the Windows component store itself may need
repair.

Open an administrator Command Prompt and run:

DISM /Online /Cleanup-Image /RestoreHealth

After DISM finishes, run:

sfc /scannow

Then restart the computer.

This combination can help when Windows system components are damaged.

--------------------------------------------------------------------------------

5. Check Windows Update

If ERROR_FILE_NOT_FOUND appears during an update, open:

Settings → System → Troubleshoot → Other troubleshooters → Windows Update

Run the Windows Update troubleshooter if it is available for your version of
Windows.

Also check that:

 * Windows has enough free storage.

 * Your internet connection is working.

 * The computer has been restarted.

 * The update is not being interrupted by another system process.

--------------------------------------------------------------------------------

6. Repair the Affected Application

If the error occurs only with one program, Windows itself may not be the primary
cause.

Depending on the application, you may be able to repair it through:

Settings → Apps → Installed apps → [Application] → Advanced options

If a Repair option is available, try it first.

If repairing does not work, reinstall the application using its official
installer.

--------------------------------------------------------------------------------

7. Check Scheduled Tasks

A deleted application can sometimes leave behind a scheduled task that still
attempts to run its executable.

Press Windows + R, enter:

taskschd.msc

and press Enter.

Review Task Scheduler Library for tasks associated with the software that is
generating the error.

Look at the Actions section to see which executable or script the task is trying
to launch.

Do not remove system tasks unless you are certain they are unnecessary.

--------------------------------------------------------------------------------

8. Look at Event Viewer

If the error does not clearly identify its source, Event Viewer can provide
additional information.

Open:

Event Viewer → Windows Logs → Application

and:

Event Viewer → Windows Logs → System

Look for errors recorded around the time the problem occurred.

Pay particular attention to:

 * Application names

 * File paths

 * Service names

 * Error codes

 * Timestamps

This information can help identify the component looking for the missing file.

--------------------------------------------------------------------------------

9. Consider Recent Changes

Think about what changed immediately before the error appeared.

Recent Change

What to Investigate

Installed an application

Repair or reinstall it

Uninstalled software

Check for leftover scheduled tasks

Installed a driver

Check the driver installation

Windows Update

Troubleshoot Windows Update

Moved files

Verify the original path

Changed drive letters

Check application paths

Used cleanup software

Check whether required files were removed

This can often point toward the underlying cause more quickly than trying random
fixes.

--------------------------------------------------------------------------------

ERROR_FILE_NOT_FOUND vs. PATH_NOT_FOUND

The two messages are closely related but aren't identical.

Error

Code

Meaning

ERROR_FILE_NOT_FOUND

0x80070002

The requested file cannot be found

ERROR_PATH_NOT_FOUND

0x80070003

The requested directory/path cannot be found

For example, if Windows expects:

C:\Apps\Example\program.exe

but program.exe is missing, the situation can correspond to 0x80070002.

If the Example directory itself cannot be found, the problem may correspond to
0x80070003.

--------------------------------------------------------------------------------

Quick Fix Checklist

Use this checklist when you encounter the error:

Step

Action

1

Restart Windows

2

Read the complete error message

3

Check the referenced file/path

4

Run sfc /scannow

5

Run DISM /Online /Cleanup-Image /RestoreHealth

6

Check Windows Update if the error occurs during updating

7

Repair or reinstall the affected application

8

Check Task Scheduler

9

Review Event Viewer

10

Investigate recent software, driver, or system changes


FINAL THOUGHTS

ERROR_FILE_NOT_FOUND doesn't necessarily mean that Windows itself is broken. It
means that a process expected to find a particular file but couldn't locate it.

The most important first step is therefore to determine which application or
Windows component is requesting the missing file. Once you know that, the
appropriate fix—repairing system files, troubleshooting Windows Update,
repairing an application, or correcting a file path—becomes much clearer.