How to fix Windows update error 0x800f0835?

Error 0x800f0835 means a Windows cumulative update failed during installation and Windows rolled it back. All reports we found come from Windows 10 22H2 monthly updates. Restart the PC and run Windows Update again first: in user reports a second try often installs the same update without the error.

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

What Windows update error 0x800f0835 means

0x800f0835 belongs to the 0x800f08xx family of codes that the Windows servicing stack returns, the part of Windows that installs updates. It tells you the update was downloaded but could not be applied, so Windows undid it. Microsoft does not document this exact code, and we could not confirm its internal name.

The message itself is the same one Windows shows for many update failures. Only the number at the end is specific. On Windows 10 it reads like this in Settings > Update & Security > Windows Update:

Why error 0x800f0835 appears

Microsoft has not named a cause for this code, so the order below comes from user reports and from what the 0x800f08xx codes have in common. The most common pattern is a one-off failure that a second attempt clears.

One user on Ten Forums described the first case exactly: KB5048652 stuck at Downloading: 100%, then half an hour on Getting Windows ready, a forced restart, and 0x800f0835. The next run of Windows Update installed it without errors. Another user saw the same with the preview update KB5050081, which stopped at 73% and then installed after a restart.

How to fix Windows update error 0x800f0835

Fix 1 costs nothing and is the one that worked in the reports we read. Fix 2 to Fix 4 repair the update cache and the system files. Fix 5 skips Windows Update, Fix 6 rules out other software, and Fix 7 reinstalls Windows over itself and keeps your files and apps.

Fix 1. Restart the PC and run Windows Update again

10 to 30 minutesNo riskThe update failed for the first time, or it hung on Downloading 100% or Getting Windows ready and you restarted by hand.

The message itself says Windows will try again, and the reports we read show the same KB installing on the next attempt. A full restart ends the stuck installer and lets Windows start the job from a clean state.

1. Save your work and select Start > Power > Restart. Do not use Shut down, which on many PCs does not fully restart Windows.
2. After the restart, wait two or three minutes until the desktop is calm.
3. On Windows 10, open Settings > Update & Security > Windows Update. On Windows 11, open Settings > Windows Update.
4. Select Retry or Check for updates.
5. Let the download and install finish. If a restart is needed, use Restart now and do not turn the PC off during Getting Windows ready.

Fix 2. Run the Windows Update troubleshooter

5 minutesNo riskThe update failed twice, and you want a quick automatic check before using commands.

The troubleshooter checks the update services, the BITS download service and pending restarts, and fixes their settings. Those are the parts that stop an update between download and install.

1. Open Troubleshoot settings. Select Start > Settings > System > Troubleshoot.
2. Open the list of troubleshooters. Select Other troubleshooters.
3. Run the Windows Update troubleshooter. Under Most frequent, select Run next to Windows Update. The Get Help app opens and starts the checks.
4. Read the result. Wait until Get Help finishes. If it found and fixed a problem, it says so and asks whether this solved the problem. Answer the question so it can offer the next step.
5. Restart the PC. Restart when the troubleshooter finishes, even if it does not ask you to.
6. Check for updates again. Select Start > Settings > Windows Update > Check for updates, and install the updates it finds.

These steps were written for Windows 11 (screenshots: 26H2). The full page with the other versions and what each result means: Run the Windows Update troubleshooter

Lines marked with a small i in the report are information only, not errors. One user on Ten Forums worried about lines naming WaaSMedicService and IsPostback_RC_PendingUpdates after the update had already installed. Those did not stop the update.

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

10 minutesLow riskThe same KB fails at the same point every time, or the download hung at 100%.

Windows keeps the downloaded update in the SoftwareDistribution folder and reuses it on every retry. If that copy is damaged, the install fails again in the same way. Renaming the folder and catroot2 forces a fresh download.

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

Fix 4. Repair the component store with DISM and SFC

15 to 40 minutesNo riskThe update still fails after a fresh download, or other updates fail too.

A cumulative update replaces files in the component store. If files it builds on are damaged or missing, the install stops and rolls back. Microsoft's own route for such failures is DISM with RestoreHealth, then SFC, then Windows Update again.

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

Run DISM first and SFC second. DISM downloads clean copies from Windows Update to repair the store, and SFC then uses that store to repair the system files. A clean SFC result alone, as in the Ten Forums report, does not prove the store is healthy.

DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow

Fix 5. Install the update from the Microsoft Update Catalog

15 to 30 minutesLow riskWindows Update keeps failing with the same KB, and you know its number from Update history.

The catalog file is the full update. Installing it by hand skips the Windows Update download and scan steps, so a problem in those steps no longer matters.

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

Fix 6. Install the update in a clean boot

20 minutesLow riskThe PC runs many third-party services: game launchers, VPN clients, tuning or backup tools.

A clean boot starts Windows with only Microsoft services. If the update installs then, a third-party service was holding files the update needed. It does not turn off Microsoft Defender or other Microsoft security.

1. Open System Configuration. Select Search on the taskbar, type msconfig and select System Configuration from the results.
2. Hide Microsoft services. On the Services tab, select the Hide all Microsoft services check box. Only services from other companies stay in the list.

   

3. Disable the remaining services. Select Disable all, then select Apply.
4. Open Task Manager. On the Startup tab of System Configuration, select Open Task Manager.

   

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

   

6. Confirm the changes. Close Task Manager. On the Startup tab of System Configuration, select OK.
7. 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

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

1 to 2 hoursLow riskUpdates have failed for weeks or months, and Fix 1 to Fix 6 did not help.

A repair reinstall replaces all system files and the component store with a clean copy of the current Windows version. That clears damage DISM cannot reach, and apps, files and settings stay. Independent advisors on Microsoft Q&A give it as the last step for 0x800f0835.

On Windows 11, use the built-in reinstall:

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, use the Media Creation Tool:

1. Open the Windows 10 download page at microsoft.com/software-download/windows10 and select Download tool now.
2. Run the tool, accept the license and select Upgrade this PC now.
3. When the Ready to install page appears, check that it says Keep personal files and apps. If not, select Change what to keep and choose it.
4. Select Install and leave the PC alone. It restarts several times.

If error 0x800f0835 is still there

The servicing log names the package or file that failed. Read it before you try anything else, or send it to whoever helps you.

1. Press Win + R, type %windir%\Logs\CBS and press Enter.
2. Copy CBS.log to the Desktop and open the copy in Notepad.
3. Press Ctrl + F and search for 0x800f0835. Note the time of the last hit.
4. Read the lines just above it. A package name and a version such as 10.0.19045.xxxx tell you which update or component was involved.
5. If the log is long, also check CBS.persist.log in the same folder. It holds older entries.

For a related code in the same family on Windows 11, see our guide to error 0x800f0838, which is caused by a missing checkpoint update.

How to keep error 0x800f0835 from coming back

Frequently asked questions

What does error 0x800f0835 mean?

It means a Windows cumulative update was downloaded but failed while it was being installed, so Windows rolled it back. The code belongs to the 0x800f08xx group of servicing errors. Microsoft does not document this exact code, and the reports we found all come from Windows 10 22H2. Your files are not affected. Restart the PC and run Windows Update again, which in user reports often installs the same update.

What does the message with (0x800f0835) in brackets mean?

The full text is: There were some problems installing updates, but we'll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800f0835). The first part is the same for many update failures. Only the code in brackets is specific. It tells you the install step failed, not the download. Windows will offer the update again, so one retry after a restart is the right first step.

Which updates fail with 0x800f0835?

User reports on Microsoft Q&A and Ten Forums name Windows 10 22H2 cumulative updates, for example KB5044273 from October 2024, KB5048652 from December 2024, the preview KB5050081 from January 2025 and KB5060533 from June 2025. The code is not tied to one update. It is a failure of the install step, so any monthly update can show it. The fixes on this page are the same for each KB.

Does 0x800f0835 happen with KB5066791?

We found no report that ties KB5066791 to this code, although people search the two together. If KB5066791 fails with 0x800f0835 on your PC, the same order applies. Restart and retry, run the troubleshooter, reset the update cache, then repair with DISM and SFC. As the last step, install it from the Microsoft Update Catalog by its KB number.

Is 0x800f0835 a Windows 10 or a Windows 11 error?

Every report we found is from Windows 10 22H2, and the Google searches that lead to this page are for Windows 10 too. The servicing stack and the repairs are the same on Windows 11, so the fixes here work there as well. Windows 10 reached end of support on 14 October 2025. A Windows 10 PC without Extended Security Updates no longer receives cumulative updates at all.

Will I lose files if an update fails with 0x800f0835?

No. When the install fails, Windows undoes the update and starts the PC with the version you had before. Your documents, photos and apps stay. None of Fix 1 to Fix 6 touches personal files either. The repair reinstall in Fix 7 is designed to keep files and apps, but back up what you cannot lose before you run it, as with any reinstall.

Should I turn off my antivirus to fix 0x800f0835?

No. No source ties this code to security software, and turning protection off leaves the PC exposed while you look for the real cause. If you suspect another program blocks the update, use the clean boot in Fix 6. It starts Windows with only Microsoft services, Microsoft Defender included, and you restore normal startup afterwards.

How long should I wait on Getting Windows ready before I restart?

Give it at least an hour, longer on an older PC with a hard disk. A cumulative update can sit on that screen with no visible change while it works. In the Ten Forums report that led to 0x800f0835, the user restarted after about half an hour. A forced restart in the middle of an install is the most common start of this error.

I have a German, Italian or French Windows. Is this the same error?

Yes. Fehlercode 0x800f0835, errore 0x800f0835 and erreur 0x800f0835 are the same code. Only the words around it are translated, and the number is identical in every language of Windows. The fixes on this page work on any language edition. The menu names in the steps are the English ones, so follow the position of the items in Settings. The commands are typed the same everywhere.