How to fix Windows update error 0x80070050?

Error 0x80070050 means Windows tried to create a file that was already there: Win32 error 80, "The file exists." With Windows Update it usually means files from an earlier, unfinished attempt are still in the way. Restart the PC and try once more, then reset the update cache.

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

What Windows update error 0x80070050 means

0x80070050 is an ordinary Windows system error in the eight-digit form that Windows Update prints. The first half, 0x8007, marks a Win32 error passed on by the update components. The second half, 0050, is 80 in decimal. Microsoft's list of system error codes gives 80 the text "The file exists." and the constant ERROR_FILE_EXISTS.

So the message is about a name clash, not about a missing or broken download. Something in the chain tried to create a file or folder, and the name was taken. With updates, the usual owner of that name is an earlier attempt that stopped halfway and left its files behind. The fixes below clear those places one by one.

Why error 0x80070050 happens, from most to least likely

Microsoft has not published a cause for this code in Windows Update. The ranking below follows what the code says, a file that already exists, and where Windows Update writes its files. Each cause points to the fix that matches it.

How to fix Windows update error 0x80070050

Fix 1 takes ten minutes and changes nothing, so everybody starts there. Fixes 2 and 3 clear the folders where leftover update files sit. Fixes 4 and 5 repair the disk and system files. Fix 6 installs the update by hand. Fix 7 rebuilds Windows and keeps your files and apps.

Fix 1. Restart the PC to finish the waiting update, then try again

10 minutesLow riskAlways first, and above all when Windows Update shows Restart now or the PC has not been restarted for days.

An update that waits for a restart keeps its files in place until Windows starts again. A new attempt that tries to write the same names meets those files and stops with "The file exists". The restart lets the first update finish and clear its files.

1. Save your work and close open programs.
2. Press Win + I and open Windows Update (on Windows 10: Update & Security > Windows Update).
3. If you see Restart now, select it. If not, open Start, select the power button and choose Restart, not Shut down.
4. After the restart, sign in and wait two or three minutes while Windows finishes its work.
5. Open Windows Update again and select Check for updates, then Download & install if it is offered.
6. If the update asks for another restart, restart again before you judge the result.

Fix 2. Reset the Windows Update cache so the update downloads fresh

15 minutesLow riskFix 1 did not help, or you see Download error - 0x80070050.

Windows Update keeps its downloads and its working files in C:\Windows\SoftwareDistribution. A failed attempt leaves half-written files there, and the next attempt trips over them. Renaming the folder gives Windows an empty cache, so every file is written new.

The steps stop the update services, rename SoftwareDistribution and catroot2 to .old, and start the services again. Renaming keeps the old folders, so nothing is lost if you want to look at them later.

1. 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.
2. 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

3. 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"

4. 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

5. 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

6. 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

Then run the built-in troubleshooter once, which checks the same components: Run the Windows Update troubleshooter

Fix 3. Empty C:\Windows\Temp

5 minutesLow riskThe cache reset did not help, or the folder holds a large pile of old files.

Windows Update runs under the system account, which unpacks into C:\Windows\Temp, not into your own TEMP folder. Old files there can carry the same names that a new install wants to create.

1. Restart the PC once, so fewer files are in use.
2. Press Win + R, type %windir%\Temp and press Enter. Select Continue if Windows asks for permission.
3. Press Ctrl + A to select everything, then press Delete.
4. When Windows says a file is in use, tick Do this for all current items and select Skip.
5. Restart the PC and try the update again from Settings > Windows Update.

Delete only the contents, never the Temp folder itself. A few files stay because they are in use, which is normal. For the general clean-up of temporary files as well: Free up disk space and delete temporary files

Fix 4. Check drive C: for file system errors

15 to 60 minutesLow riskFile Explorer also shows "Error 0x80070050: The file exists." when you move or delete files, or the PC was switched off during an update.

The file system keeps an index of every name on the drive. If that index is damaged, Windows can believe a file exists that is really gone, and any program that wants that name gets error 80. Chkdsk repairs the index.

1. 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.
2. 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:

3. 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

4. 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.
5. 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)

Fix 5. Repair system files with SFC and DISM

30 minutesLow riskThe folders and the disk are clean, or other system errors appear as well.

Damaged files in the update components can make them write the same file twice or misread what is already there. SFC and DISM put back the original files from Windows' own store. This is a general repair, so it comes after the checks that are specific to error 80.

1. 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.
2. 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

3. 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

4. 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

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

20 to 40 minutesLow riskOne KB number keeps failing while other updates install.

A manual install skips the Windows Update download chain and its cache. If the clash was in the cache, the standalone file installs past it.

1. Check your Windows version. Press Windows key + R, type winver and press Enter. Note the version (for example 25H2) and the OS build.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. Install a single file. If there is only one file, double-click it and confirm the installation in the Windows Update Standalone Installer.
8. 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

9. 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

• Save the file to a short local path, such as C:\packages, not to a network share.
• The same error by hand. The cache was not the problem. Run Fixes 3 to 5 if you skipped them, then go to Fix 7.

Fix 7. Reinstall Windows over itself and keep your files and apps

1 to 2 hoursLow riskReaders whose update still fails after Fixes 1 to 6, on any Windows 11 or Windows 10 22H2 PC.

A repair install writes a fresh copy of Windows, with a new update cache and new system files, and keeps apps, files and settings. It clears every leftover that error 80 could be about at once.

1. 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.
2. Start the reinstall. Choose whether the PC may restart on its own 15 minutes after the installation, then select OK.
3. 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.

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

On Windows 10 22H2, or when Reinstall now is missing, use installation media. On Windows 11, download the ISO from Microsoft's software download page, right-click it, select Mount and run setup.exe. Check that Keep personal files and apps is chosen before you select Install.

Windows 10 left support on 14 October 2025. If the PC can run Windows 11, the same repair install is the moment to move to it.

WslRegisterDistribution failed with error: 0x80070050

In the Windows Subsystem for Linux the same code has its own message. The distribution's window first says it is installing and then "WslRegisterDistribution failed with error: 0x80070050" and "Error: 0x80070050 The file exists." Users report it right after a WSL update from the Microsoft Store, on distributions that worked before.

The message suggests the launcher tried to register a distribution whose files were already there. In the reports we read, Microsoft gave no cause and no confirmed fix, so the steps below start with the ones that change nothing.

1. Open Terminal and list the distributions WSL knows.

   wsl --list --verbose

2. If your distribution is listed, start it from here instead of from its Start menu icon.

   wsl -d Ubuntu

3. If that fails, close WSL fully, update it and try again.

   wsl --shutdown
   wsl --update

If 0x80070050 is still there: logs and where to ask

When the error survives every fix, the log shows which file clashed. Collect it right after a failed attempt, so the times match.

PowerShell (administrator): write the Windows Update log to the desktop

Get-WindowsUpdateLog

• What to read: open WindowsUpdate.log, search for 80070050 and note the file path printed nearby. That is the file that already existed.
• What to send: the log, the KB number, the output of winver and what you already tried. Microsoft Q&A takes such cases.
• One test with the antivirus paused. If you use an antivirus other than Microsoft Defender, pause it for one attempt and turn it back on right after: Turn off Microsoft Defender protection for a moment
• A work or school PC. Updates may come from your organization's server, so send the log to your IT team before a repair install.
• Is it hardware? A name clash is not a hardware fault by itself. If chkdsk keeps finding errors or reports bad sectors, the drive may be failing: back up your files first.

How to keep error 0x80070050 from coming back

Each point follows from what the code means. Error 80 appears when a file that Windows wants to create already exists. Anything that leaves an update half done brings the same leftover files, and the same error, back with the next attempt.

Frequently asked questions

What does error 0x80070050 mean?

It means Windows tried to create a file or folder that already exists. The code is Win32 error 80 in the form Windows Update prints. Microsoft's text for 80 reads "The file exists." With updates, the file in the way is usually a leftover from an earlier attempt that stopped halfway, in the update cache or in C:\Windows\Temp. That is why a restart and a cache reset, Fixes 1 and 2, solve most cases.

What is the difference between "Install error - 0x80070050" and "Download error - 0x80070050"?

Both are the same error 80 at different stages. A download error means Windows could not write the downloaded file into its update cache, because a file with that name was already there. An install error means the download finished, but the installer met an existing file while it unpacked or applied the update. For a download error, go straight to the cache reset in Fix 2. For an install error, restart first, then reset the cache.

How do I fix WslRegisterDistribution failed with error: 0x80070050?

Start your distribution from Terminal with wsl -d and its name instead of from the Start menu icon, because the icon may try to register it again. If that fails, run wsl --shutdown and wsl --update and try once more. Users report this error after a WSL update from the Microsoft Store, and we found no cause or fix confirmed by Microsoft. Unregistering deletes the Linux files, so export the distribution first, as the WSL section explains.

Why does File Explorer say "Error 0x80070050: The file exists"?

It is the same error 80 outside Windows Update. Explorer wanted to create a file, often in the Recycle Bin or in the target folder of a move, and found the name taken. Empty the Recycle Bin and try again. If the error keeps coming on that drive, check it for file system errors with chkdsk, as in Fix 4, because a damaged index can show files that are not really there.

Is 80070050 the same as 0x80070050?

Yes. Some tools and logs drop the 0x prefix, others add brackets, as (0x80070050), or write it as HRESULT: 0x80070050. All of them are the same error: Win32 error 80, "The file exists." What differs is the program that reports it. In Windows Update, follow the fixes on this page in order. In WSL or File Explorer, read the section for that case.

Is it safe to reset the Windows Update cache?

Yes. The cache holds downloaded update files and the update history database, not your own files. The steps in Fix 2 rename the folders to .old instead of deleting them, so you can go back if you need to. After the reset Windows downloads pending updates again, which can take a while on a slow connection, and the Update history list may look shorter. Installed updates stay installed.

Do I need the Visual Studio 2005 Service Pack to fix 0x80070050?

No. That advice appears in older guides, but the Visual Studio 2005 Service Pack 1 update was made for Windows Vista and has nothing to do with a file that already exists. Installing it on Windows 10 or Windows 11 does not touch the update cache or the temporary folders. Use the fixes on this page instead, starting with a restart and the cache reset.

Will a repair install delete my files or programs?

Not when you keep personal files and apps. Reinstall now in Settings > System > Recovery on Windows 11 and setup.exe from mounted media are both built to keep your files, apps and settings. With setup.exe, check that Keep personal files and apps is chosen before you select Install. Back up your important files anyway, because a repair install is a large operation, and some apps may ask you to sign in again.

I searched in Hindi or another language. Does this page apply?

Yes, if your screen shows 0x80070050, for example when you wrote "ye error aa rha h" (this error keeps coming). Windows prints the same code in every language, and the commands on this page are typed the same way everywhere, only the menu names are translated. Start with Fix 1, restart the PC and check for updates again, then go on in order.