How to fix Windows update error 0x8007006E?

Q: How do I find which file caused 0x8007006E?

Search CBS.log. Copy C:\Windows\Logs\CBS\CBS.log to the desktop, search the copy for 8007006e , then for , error at the same time, and read the lines above it. The file path there is the file Windows could not open. If CBS.log has nothing, run Get-WindowsUpdateLog in PowerShell and search the log it puts on the desktop. Fix 2 shows each step and a table of what each path points to.

Ugnius Kiguolis

Published Oct 15, 2026

Prefer to fix it yourself? The manual steps follow.

9methods
10 minutes to 2 hours
Intermediate

Start fixing

Applies to Windows 11 and Windows 10: monthly cumulative updates, .NET and driver updates that fail with 0x8007006E in Settings > Windows Update or in Update history

9 methods in this guide

What the error means
Causes, ranked
The fixes
1. Restart and retry
2. Find the file in the log
3. Clear the update cache
4. Clean boot
5. Repair system files
6. Check the disk
7. Install the update by hand
8. Repair install
9. Test your security program
Still there: read the logs
Prevent it
FAQ

Question

I keep getting 0x8007006E whenever I try to update Windows. How do I make it work again? It never happened to me before.

Error 0x8007006E means Windows could not open a file or device that the update needs. The code is Win32 error 110, "The system cannot open the device or file specified", so the fix is to find which file and why it is blocked. Restart and retry first, then read the log and clear the update cache.

Short answer

0x8007006E is not a broken update. It means Windows could not open one file or device while it installed the update. Restart once and retry (Fix 1). If it fails again, search CBS.log for the file it could not open (Fix 2), then clear the update cache (Fix 3). A third-party security program that holds files open is the next suspect (Fix 4). System file and disk repairs follow.

At a glance
Error	0x8007006E: Win32 error 110, `ERROR_OPEN_FAILED`, "The system cannot open the device or file specified."
Where it appears	Settings > Windows Update, next to the update that failed, and in Settings > Windows Update > Update history. The same code also appears outside updates, for example in Certificate Services and in developer tools.
Main cause	A file the update needs cannot be opened: a damaged or locked file in the update cache, or a file held open by a security program. Microsoft does not publish a Windows Update specific cause for this code.
Fastest fix	Restart with Start > Power > Restart and retry the update (Fix 1). If it fails again, read the log (Fix 2) and reset the update cache (Fix 3).
Also written as	8007006E, 0x8007006e, error 110, 0x6E, -2147024786 (the same number as a signed decimal).
Affects	Windows 11 and Windows 10. The code is a general Windows error, so it is not tied to one update or one version.
Microsoft's status	Not on Microsoft's list of common Windows Update errors (read 15 October 2026). No known issue names it.
Sibling code	0x80070020, `ERROR_SHARING_VIOLATION`: a file in use by another process. Microsoft ties it to non-Microsoft filter drivers such as antivirus.
Where the cause is logged	`C:\Windows\Logs\CBS\CBS.log`, and the Windows Update log made with `Get-WindowsUpdateLog`. Search for `8007006e` and `, error`.
Time to fix	10 minutes for Fix 1. About 30 minutes for the log and the cache reset. 1 to 2 hours for a repair install.

Facts checked on 15 October 2026. Steps written for Windows 11 (25H2 and 26H2) and Windows 10 22H2.

What Windows Update error 0x8007006E means

0x8007006E is an ordinary Windows system error in the eight digit form that Windows Update prints. The first half, 0x8007, marks a plain Win32 error wrapped for the update components. The second half, 006E, is 110 in hexadecimal. Microsoft's list of system error codes gives 110 the text "The system cannot open the device or file specified."

Infographic that splits 0x8007006E into 0x8007 and 006E, equal to Win32 error 110 ERROR_OPEN_FAILED, with Microsoft's message text, what it means for an update and the other spellings of the code — The code decoded: Windows Update wraps error 110, a file or device that could not be opened.

So the code does not describe the update. It says that at one moment of the download or the installation, Windows asked for a file or a device and could not open it. Which file is not shown on the Windows Update page. It is written in the logs, which Fix 2 reads.

Where the same code shows up
What you see	Where	What it tells you
The update name with 0x8007006E and a Retry button	Settings > Windows Update	The update failed. The page does not say which file was the problem.
The same update listed as failed, with the date	Settings > Windows Update > Update history	How often it failed. The date tells you where to look in CBS.log.
"The system cannot open the device or file specified."	A command window, for example after `wusa` or `DISM` installs a downloaded file	The same error without Windows Update in between. The message is the text of error 110.
`0x8007006e (WIN32: 110 ERROR_OPEN_FAILED)`	Certificate Services and `certutil`, or developer tools	The same code outside updates. Those cases are not about Windows Update and this page does not cover them.

Why the code keeps coming back

A one time lock, for example a scan that held a file for a second, goes away after a restart. When the same update fails with 0x8007006E every time, the blocked file stays blocked. Then the fix is to find it, not to retry.

Why Windows update error 0x8007006E happens, from most to least likely

Microsoft has not published a cause of 0x8007006E for Windows Update. The ranking below follows what error 110 means, what Microsoft says about its close sibling 0x80070020, and what developers report about the same code in other programs. Each cause points to the fix that matches it.

Cause	How often	How to tell	Fix
A file in the update cache, `C:\Windows\SoftwareDistribution` or `catroot2`, is damaged or still locked from an earlier attempt.	Most often	CBS.log or the Windows Update log names a file in one of these folders.	Fix 3
A security program, an antivirus or a work security agent, holds the file open while Windows tries to replace it.	Often	A third-party antivirus is installed. The log names a file that exists and looks normal.	Fix 4, then Fix 9
A system file or a file in the component store (WinSxS) is damaged.	Sometimes	The log names a file under `C:\Windows`, or DISM reports the store as repairable.	Fix 5
The disk has file system errors, so the file cannot be read at all.	Rarely	Other files fail to open too, or the disk check finds errors.	Fix 6
A one time lock during a busy restart.	Sometimes	It failed once and the next attempt works.	Fix 1

The second cause has the best evidence outside Windows Update. Microsoft writes that 0x80070020, a file used by another process, is caused by non-Microsoft filter drivers such as antivirus. Developers of the uv Python tool traced the same 0x8007006E code to security software that inspects files, in one case a Bitdefender component.

Decision chart for error 0x8007006E with six rows: a single failure, a failure every time, a file in SoftwareDistribution or catroot2, a third-party antivirus, a file under C:\Windows, and other files failing, each with the fix to start with — Find what you see on your PC in the left column and start with the fix on the right.

What older guides get wrong

Disk Cleanup and restarting services are common advice for this code. Neither opens a locked file, and Microsoft does not connect this code with free space. Keep enough space for updates, but start with the file the log names.

How to fix Windows Update error 0x8007006E

Fix 1 takes ten minutes and changes nothing, so everybody starts there. Fix 2 tells you which file failed and which fix is yours. Fixes 3 to 6 each repair one cause. Fixes 7 and 8 get the update on the PC another way. Fix 9 is a short test of your security program, never a permanent change.

What you see or have	Start with
It failed once, or you have not restarted since it appeared.	Fix 1
It fails every time and you do not know why yet.	Fix 2
The log names a file in `SoftwareDistribution` or `catroot2`.	Fix 3
A third-party antivirus or a work security agent is installed.	Fix 4, then Fix 9
The log names a file under `C:\Windows` or `WinSxS`.	Fix 5
Other files fail to open too, or the disk is old.	Fix 6
Only one update fails and everything else is clean.	Fix 7
Every other fix failed.	Fix 8

Fix 1. Restart, retry the update and check what failed

10 minutesNo riskAlways first, and above all when the error appeared once.

Error 110 often means a file was locked at that moment, for example by a pending update step or a scan. A real restart releases every lock, and Update history shows whether the same update keeps failing.

Save your work and select Start > Power > Restart. Use Restart, not Shut down, so that pending update work can finish.
Open Settings > Windows Update and select Check for updates or Retry.
If it fails again, open Settings > Windows Update > Update history.
Note the name and KB number of the failed update, and whether it is a quality update, a driver or a .NET update.
Note the dates of the failures. You need them in Fix 2.

Windows Update page with an update and its KB number: screenshot taken on Windows 11 26H2 — Update history lists each update by its KB number. Note the one that fails with 0x8007006E.

What Update history tells you
You see	Next
The update installed after the restart	Done. The lock was temporary.
A newer update is now offered and installs	Done. The newer update replaces the old one.
The same update fails with 0x8007006E every time	Fix 2
Only a driver update fails	Install the driver from the device maker's site, or use Fix 7.

It worked if: The update installs after the restart, and Windows Update says you are up to date.

If not: If the same update fails again with 0x8007006E, find the file that could not be opened in Fix 2.

Fix 2. Find the file that could not be opened in CBS.log and the Windows Update log

15 minutesNo riskThe update fails every time and you want to know which of the next fixes is yours.

Error 110 always concerns one file or device, and the logs name it. Microsoft's own advice for update errors is to open CBS.log, search for the error and read the lines above it.

Right-click Start and select Terminal (Admin). On Windows 10, search for cmd and select Run as administrator.
Copy CBS.log to the desktop, so that you read a copy and Windows keeps writing the original.
```
copy %windir%\Logs\CBS\CBS.log %USERPROFILE%\Desktop\CBS-copy.log
```
List the lines that carry the code. Note the time of the last hit.
```
findstr /i /c:"8007006e" %USERPROFILE%\Desktop\CBS-copy.log
```
Open CBS-copy.log in Notepad, press Ctrl + F and search for , error. Go to the lines with the same time as the last hit.
Read 20 to 40 lines above the error line. Note every file path you find there.
If CBS.log has no hit, the failure was in the download. In PowerShell as administrator, build the Windows Update log on the desktop and search it the same way.
```
Get-WindowsUpdateLog
```

What the file path points to
The path contains	It points to
`SoftwareDistribution` or `catroot2`	Fix 3: clear the update cache
A file that exists, and a third-party antivirus is installed	Fix 4, then Fix 9
`C:\Windows\System32` or `WinSxS`	Fix 5: repair system files
A file that cannot be read at all, or many paths at once	Fix 6: check the disk
Nothing clear	Fix 3, then Fix 5

Which program holds the file

For the sibling code 0x80070020 Microsoft suggests Process Monitor from Sysinternals. Start it, retry the update, stop the capture and filter for the file name from CBS.log. The process that holds the file is listed next to it.

It worked if: You have a file path and know which of Fix 3 to Fix 6 matches it.

If not: If the log is too long or nothing stands out, go to Fix 3. It is safe on every PC and repairs the most common cause.

Fix 3. Reset Windows Update components and clear the update cache

10 minutesLow riskThe log names a file in SoftwareDistribution or catroot2, or you found no clear cause.

Windows keeps downloaded updates in SoftwareDistribution and update signatures in catroot2. A damaged or locked file there fails every retry. Renaming both folders with the services stopped makes Windows fetch fresh copies.

Open Command Prompt as administrator. Type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
Stop the update services. Type the commands below and press Enter after each one. If Windows says that other services depend on Cryptographic Services, it stops them too. A message that a service is not started is fine.
```
net stop wuauserv
net stop bits
net stop cryptsvc
```
The update services are stopped. Screenshot: Windows 11 26H2.
Delete the download queue files. This clears the list of downloads that the Background Intelligent Transfer Service keeps. If Windows says it cannot find the files, continue.
```
del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
```
Rename the update cache folders. Renaming keeps a copy in case you need it; Windows creates new, empty folders when the services start again. If you get Access is denied, a service is still running: repeat the previous step.
```
ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
ren %systemroot%\System32\catroot2 catroot2.old
```
Both folders now end in .old. Screenshot: Windows 11 26H2.
Start the services again. Type the commands below and press Enter after each one. The requested service has already been started is fine: Windows started it on its own.
```
net start cryptsvc
net start bits
net start wuauserv
```
BITS and Windows Update are running again. Screenshot: Windows 11 26H2.
Restart and check for updates. Restart the PC. Then select Start > Settings > Windows Update > Check for updates. The first check can take longer than usual because everything is downloaded again.

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Reset Windows Update components

It worked if: The services start again, Windows Update downloads the update from the start, and it installs.

If not: If the update downloads again and fails with the same code, something keeps the file blocked. Go to Fix 4.

Fix 4. Retry the update after a clean boot

20 minutesLow riskA third-party antivirus, backup tool, disk tool or work security agent is installed, or the log names a file that looks normal.

A clean boot starts Windows with only Microsoft services. Microsoft gives this step first for its sibling code 0x80070020, which non-Microsoft filter drivers such as antivirus cause. If the update installs now, a third-party program held the file.

Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.
Disable the remaining services. Select Disable all, then select Apply.
Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.
Disable the startup apps. On the Startup apps tab in Task Manager, select each item whose status is Enabled and select Disable. Write down or take a screenshot of the items you disable: you need the list to turn them back on.
Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
Restart and test. Restart the PC. Windows now starts in a clean boot environment: try again the thing that failed (run the app, install the update, uninstall the program).

These steps were written for Windows 11 25H2 and 26H2. The full page with the other versions and what each result means: How to perform a clean boot in Windows

System Configuration, Services tab with Hide all Microsoft services ticked and the Disable all button: screenshot taken on Windows 11 26H2 — Hide all Microsoft services before you select Disable all, so that Windows Update keeps running.

Retry the update in Settings > Windows Update while the PC is in clean boot.
When it installs, undo the clean boot with the same steps and select Enable all.
Turn programs back on in small groups to find the one that blocks updates, then update or replace it.

It worked if: The update installs in clean boot. After you undo it, the PC starts normally.

If not: Some security programs load drivers that a clean boot does not stop. If you have one, try Fix 9 after the repairs below.

Fix 5. Repair system files and the component store with DISM and SFC

30 minutesLow riskThe log names a file under C:\Windows, or Fixes 3 and 4 did not help.

An update builds new system files from the component store in WinSxS. If a file there or in System32 is damaged, Windows cannot open it and stops with error 110. DISM repairs the store, then SFC repairs the files.

Open an elevated command window. Right-click Start and select Terminal (Admin), or type cmd in the search box, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
Run DISM first. Type the command below and press Enter. DISM downloads clean copies of damaged components from Windows Update, so it can take several minutes. Wait until it says The operation completed successfully.
```
DISM.exe /Online /Cleanup-Image /RestoreHealth
```
Run System File Checker. In the same window, type the command below and press Enter. Do not close the window until the verification reaches 100%.
```
sfc /scannow
```
Read the result and restart. Compare the last message with the table below this guide, then restart the PC so that repaired files are loaded.

These steps were written for Windows 11 24H2 and 25H2. The full page with the other versions and what each result means: Run DISM and SFC to repair Windows system files

DISM /RestoreHealth running: screenshot taken on Windows 11 26H2 — Run DISM first, so that SFC can repair system files from a clean component store.

It worked if: DISM says the restore operation completed, SFC finds no integrity violations or repairs them, and the update installs after a restart.

If not: If SFC cannot repair some files, or the update still fails, check the disk in Fix 6.

Fix 6. Check the disk for file system errors

10 minutes to 1 hourLow riskOther files also fail to open, programs crash, or the PC has an old hard drive.

Error 110 also covers files that cannot be read because the file system is damaged. Check Disk finds and repairs such errors, which no update repair can do.

Open Command Prompt as administrator. Type cmd in the search box on the taskbar, right-click Command Prompt and select Run as administrator. Select Yes when Windows asks for permission.
Scan the drive without changing anything. Type the command below and press Enter. Replace C: with another drive letter to check that drive. This scan only reports; it does not fix anything.
```
chkdsk C:
```
If errors were found, run the repair. Run chkdsk with /f to fix file system errors. On the Windows drive (C:) chkdsk cannot lock the drive while Windows is running, so it offers to check it at the next restart.
```
chkdsk C: /f
```
Schedule the check and restart. Type Y and press Enter, then restart the PC. chkdsk runs before Windows starts. Do not turn the PC off while it runs.
Read the result after the restart. The report of a check made at startup is not shown on the desktop. Open PowerShell and run the command below to see it, or open Event Viewer (eventvwr.msc) > Windows Logs > Application and filter by the sources Chkdsk and Wininit.
```
Get-WinEvent -FilterHashtable @{LogName='Application'} | Where-Object { $_.ProviderName -match 'wininit' } | Select-Object -First 1 | Format-List TimeCreated, Message
```

These steps were written for Windows 11 and Windows 10 (the steps are the same). The full page with the other versions and what each result means: Check a disk for errors (chkdsk)

chkdsk report ending with Windows has scanned the file system and found no problems: screenshot taken on Windows 11 26H2 — The read only scan shows whether the drive has errors before anything is changed.

If the disk reports bad sectors

Back up your files before a repair run. Repeated errors on the same drive are a hardware sign, and no update fix will last on that disk.

It worked if: The scan says Windows found no problems, or the repair finishes, and the update installs after a restart.

If not: If the disk is clean and the update still fails, install the update by hand in Fix 7.

Fix 7. Install the update by hand from the Microsoft Update Catalog

15 minutesLow riskOnly one update fails, and the cache reset and repairs are done.

The catalog file does not pass through the Windows Update cache, so a blocked file in the download path is skipped. If it fails with the same error text, the blocked file is on the system side.

Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
Find the KB number. Open Settings > Windows Update. A failed or pending update is listed with its KB number; earlier ones are under Update history.
Check the processor type. Open Settings > System > About and look at System type: an x64-based PC needs the x64 file, an ARM-based PC (for example Snapdragon) needs the arm64 file.
Search the catalog. Open the Microsoft Update Catalog at catalog.update.microsoft.com in your browser, type the KB number (for example KB5124010) in the search box and press Enter.
Pick the right row. Find the row whose title names your Windows version and your processor type (x64-based or arm64-based) and select Download on that row.
Download every file listed. A window lists one or more .msu links. Download all of them into one empty folder, for example C:\packages. On Windows 11 24H2 and later the list can include earlier checkpoint updates that the new one needs.
Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
Install several files with DISM. If there are several files, open an elevated Terminal or Command Prompt and run DISM with the newest file. DISM finds the other files in the same folder and installs them in the right order.
```
DISM /Online /Add-Package /PackagePath:C:\packages\<newest-file>.msu
```
Restart. Restart the PC when the installation finishes, then run winver again: the OS build should have changed.

These steps were written for Windows 11 24H2 and later; Windows 10 22H2. The full page with the other versions and what each result means: Install an update from the Microsoft Update Catalog

Microsoft Update Catalog search results for a KB number, with an x64 and an ARM64 row of the same cumulative update and the Download button — The catalog lists one row for each processor type. Pick the row that matches the system type of your PC.

It worked if: The installer finishes, asks for a restart, and Update history shows the update as installed.

If not: If the installer shows "The system cannot open the device or file specified.", go to Fix 8.

Fix 8. Repair Windows with an in-place reinstall that keeps your files and apps

1 to 2 hoursRead the warningEvery fix above failed, or the logs name many damaged files.

A repair install replaces every Windows file and the component store at once, and brings the PC to the current build. Whatever file the update could not open is replaced with it.

Back up first

The repair keeps your files and apps when you choose to keep them, but a power cut or a full disk can still go wrong. Back up your documents before you start, and plug a laptop in.

Open Recovery in Settings. Open Settings > System > Recovery. Next to Fix problems using Windows Update, select Reinstall now. This keeps your apps, files and settings.
Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
Wait and restart. Windows Update downloads and installs a repair copy of your current Windows version. Keep the PC plugged in and online, and restart it when asked.
If that did not help: Reset PC. Back in Settings > System > Recovery, next to Reset this PC, select Reset PC. This keeps your personal files but removes installed apps and settings.
Choose Keep my files. Select Keep my files. Do not select Remove everything.
Choose where Windows comes from. Select Cloud download to download a fresh copy of Windows, or Local reinstall to use the files already on the PC (faster, but may not include the latest updates).
Reset. Review the summary and select Reset. The PC restarts several times.

These steps were written for Windows 11 22H2 and later. The full page with the other versions and what each result means: Reinstall Windows without losing files

Reset this PC: Keep my files or Remove everything: screenshot taken on Windows 11 26H2 — Choose to keep your files, so that only Windows itself is replaced.

It worked if: Windows starts on the current build, your files and apps are there, and Windows Update installs the next update.

If not: If the repair install itself fails, read the setup logs listed in the next section and ask for help with them.

Fix 9. Pause third-party security for one update attempt, then turn it back on

10 minutesLow riskA third-party antivirus or security agent is installed and a clean boot did not stop it.

Security programs inspect files as Windows opens them, and developers report that this inspection returns 0x8007006E. Pausing protection for one attempt shows whether it is the cause.

Disconnect from untrusted networks and close your browser and email.
Open your security program and use its own option to pause protection for the shortest time it offers, for example 10 or 15 minutes.
Open Settings > Windows Update and select Retry right away.
Turn protection back on as soon as the attempt ends, whether it worked or not.
If the update installed, update the security program or ask its maker about Windows Update exclusions. Do not keep it off.

For Microsoft Defender the steps are here: Turn off Microsoft Defender protection for a moment. Defender is rarely the cause, because it is built to work with Windows Update.

It worked if: The update installs during the short pause, which shows that the security program held the file.

If not: If the update fails even with protection paused, the security program is not the cause. Collect the logs in the next section.

If 0x8007006E is still there: the logs to read and what to send

Each failed attempt leaves a trace. Collect it right after a failure, because CBS.log keeps growing and older parts move into other files in the same folder.

Where each part of the failure is written
Log	Where	What to look for
CBS.log	`%windir%\Logs\CBS`	`8007006e` and `, error`, then the file named above the error
WindowsUpdate.log	On the desktop, made by the PowerShell command `Get-WindowsUpdateLog`	The KB number and the time of the failed attempt
dism.log	`%windir%\Logs\DISM`	`Error` near the time of a DISM command
setupact.log and setuperr.log	`C:\$Windows.~BT\Sources\Panther`	The last error lines of a failed repair install

What to send to support or to Microsoft Q&A: the KB number, the dates from Update history, the file path from CBS.log, the name of your security program and what you already tried.
When it is the disk: if Check Disk keeps finding errors or the drive reports bad sectors, replace the drive. No update fix lasts on a failing disk.
On a work PC: a security agent managed by your company can block files the user cannot unblock. Send the log lines to your IT team.
A similar code after the restart: if the update installs and then rolls back with 0x80070302, see our guide to error 0x80070302.

How to keep 0x8007006E from coming back

Error 110 comes back when the same program or the same damaged file blocks the next update. A few habits keep the path clear for every monthly update.

Restart the PC at least once a week with Start > Power > Restart, so that pending update steps finish and file locks are released.
Keep one security program. Two antivirus programs that scan the same files are a common source of locked files.
Keep your security program updated, and remove one you no longer pay for, with its maker's removal tool.
Do not stop or rename update folders by hand while an update is downloading.
Run DISM /Online /Cleanup-Image /ScanHealth after a crash or a power cut during an update.
Windows 10 left support on 14 October 2025. A Windows 10 PC without Extended Security Updates gets no new monthly updates, so plan the move to Windows 11.

Frequently asked questions

What does error 0x8007006E mean?

It means Windows could not open a file or a device it needed. The code is Win32 error 110 in the form Windows Update uses. Microsoft names it ERROR_OPEN_FAILED, with the text "The system cannot open the device or file specified." In Windows Update it usually means a file in the update cache or a system file was damaged, or another program held it open. The Windows Update page does not say which file it was, but CBS.log does.

Is 0x8007006E a problem with the update itself?

Usually not. The code describes a file that could not be opened on your PC, not a faulty update package. That is why the same PC can fail with it on several updates in a row. When the update itself was faulty, Microsoft lists it on the release health page of your Windows version, and 0x8007006E is not on Microsoft's list of common Windows Update errors. Clear the update cache and look for the blocking program instead of waiting for a new update.

How do I find which file caused 0x8007006E?

Search CBS.log. Copy C:\Windows\Logs\CBS\CBS.log to the desktop, search the copy for 8007006e, then for , error at the same time, and read the lines above it. The file path there is the file Windows could not open. If CBS.log has nothing, run Get-WindowsUpdateLog in PowerShell and search the log it puts on the desktop. Fix 2 shows each step and a table of what each path points to.

Can my antivirus cause error 0x8007006E?

It can. Security programs inspect files as Windows opens them, and while one does, the file may be unavailable. Developers of the uv tool traced this exact code to security software, in one case a Bitdefender component. Microsoft ties the sibling code 0x80070020 to non-Microsoft filter drivers such as antivirus. Test it with a clean boot (Fix 4) or a short pause for one attempt (Fix 9), and always turn protection back on.

Is it safe to delete the SoftwareDistribution folder?

Renaming it is the safer choice, and that is what Fix 3 does. With the update services stopped, Windows creates a new empty folder and downloads the updates again. Your files, apps and installed updates stay. You lose the list of past updates in Update history, which is only a display. Delete the renamed SoftwareDistribution.old folder only after updates work again.

Does Disk Cleanup fix 0x8007006E?

Not on its own. Error 110 means a file could not be opened, not that the disk is full. A full disk shows another code, 0x80070070, which is error 112, "There is not enough space on the disk." Keep enough free space for updates, but start with the file named in the log. Disk Cleanup does not open a locked file or repair a damaged one.

I see 0x8007006E outside Windows Update. Is this the same problem?

It is the same error, a file or device that could not be opened, but the fix depends on the program. Administrators see it in Certificate Services when a certificate revocation list cannot be read, and developers see it when a tool cannot open a file it just wrote. Those cases are not covered here. This page is about Windows Update, where the file belongs to the update or to Windows.

Will a repair install delete my files?

Not when you choose to keep your files and apps. A repair install replaces Windows itself and keeps your documents, apps and most settings. It still runs for an hour or more, and a power cut during it can go wrong, so back up your documents first. Fix 8 links to the full steps for Windows 11 and Windows 10.

What does the error mean in other languages, for example cosa significa or cómo corrijo este error?

The meaning is the same in every language version of Windows: the system could not open a file or a device the update needed. The fix is the same as well. Restart and retry first, then find the file in CBS.log, clear the update cache, and test your security program. This page is in English only, and the commands in it work the same in any language of Windows.

Sources

Microsoft Learn: System Error Codes (0-499), error 110 (0x6E) and 112 (0x70) (learn.microsoft.com)
Microsoft Learn: Common Windows Update errors (0x80070020 and how to read CBS.log) (learn.microsoft.com)
GitHub, astral-sh/uv issue 20567: ERROR_OPEN_FAILED (0x8007006E) caused by a security product (github.com)

Did this fix work?

One click, no account. It tells the next reader which guides are worth their time.

We show the result once 20 readers have answered.

Still broken? Describe your case with the exact error text.

Questions and experiences: fix Windows update error 0x8007006E

Still broken, or found a fix we did not cover? Ask here: members and our editors answer. Reading is open; writing needs a free account.

0 comments

…