How to fix Windows update error 0x80070302?

Install error 0x80070302 means a Windows 11 cumulative update downloaded and installed, then failed and rolled back during the restart. The code is Win32 error 770, and Microsoft gives it no Windows Update meaning, so the real cause sits in CBS.log. Restart, check which build you are on, then install the newest update, not the one from the old message.

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

What install error 0x80070302 means

0x80070302 is an ordinary Windows system error in the eight-digit form that Windows Update prints. The first half, 0x8007, marks a plain Win32 error that was wrapped for the update components. The second half, 0302, is 770 in hexadecimal. Microsoft's list of system error codes names 770 ERROR_CANTFETCHBACKWARDS, with the text "The data provider cannot fetch backwards through a result set."

That text does not describe an update at all. Errors 770 to 775 in Microsoft's list all speak of a "data provider" and a "result set", the language of components that read rows from a database. Microsoft has not published what 770 means when the servicing stack returns it, so treat the code as a signal that the installation failed late, not as a description of why.

Which Windows updates readers report with 0x80070302

We read the questions about this code on Microsoft Q&A, Microsoft's own forum. Each line below is a report by a user, not a statement by Microsoft. Together they show a clear pattern: all are cumulative updates for Windows 11 version 24H2 or 25H2, both regular monthly updates and optional previews.

• Microsoft's release health pages. We read the known issues of Windows 11 24H2 and 25H2 on 14 October 2026. Neither page mentions 0x80070302.
• Press reports. Windows Latest listed 0x80070302 among the codes users saw with KB5065426 in September 2025, next to 0x800F0991, 0x800F0922 and others. It did not quote a Microsoft statement about this code.
• Windows 11 24H2 Home and Pro. Microsoft's release health page says these editions reached the end of updates on 13 October 2026. A 24H2 Home or Pro PC that fails with this code needs a move to 25H2 or 26H2 anyway, which Fix 7 does in one step. Enterprise and Education editions of 24H2 are supported until 12 October 2027.

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

Microsoft has not described a cause for this code. The ranking below comes from what Microsoft documents about how 24H2 updates are built and from the log findings that volunteers and users posted in the cases above. Each cause points to the fix that matches it.

The first cause is the finding in the October 2025 case: a volunteer moderator read the CBS logs and wrote that files were missing in the component store. The second is the finding in the March 2026 case, where the user read dism.log and CBS.log and found an old Windows 10 package blocking security updates.

How to fix install error 0x80070302 in Windows Update

Fix 1 takes ten minutes and changes nothing, so everybody starts there. Fix 2 tells you which of the next fixes is yours. Fixes 3 to 6 repair one cause each. Fix 7 is the repair install: it takes longest, but it is the fix that ended the two cases above where the user reported back.

Fix 1. Restart, check which build you are on, and install the newest update

10 minutesNo riskAlways first, and above all when the message names an update that is a month or more old.

Cumulative updates replace each other every month, so the update in an old message may no longer be the one Windows needs. In one Q&A case the update was reported as already installed while the error stayed on screen. The build number shows what really happened.

1. Restart the PC once with Start > Power > Restart, not with Shut down, so that pending update work can finish.
2. Press Win + R, type winver and press Enter. Note the version (24H2, 25H2 or 26H2) and the OS Build, for example 26200.8037.
3. Open Settings > Windows Update > Update history and note the KB number of the failed update and the date of the last failure.
4. Search the KB number on Microsoft Support. The title of its page gives the build it installs, for example "KB5079473 (OS Builds 26200.8037 and 26100.8037)".
5. Compare the two builds. If your build in winver is the same or higher, the update is in place and the old message can be ignored.
6. If your build is lower, go back to Settings > Windows Update and select Check for updates. Install whatever is offered now, which may be a newer KB than the one that failed.
7. Restart when asked and run winver again.

Fix 2. Find the failing package in CBS.log and dism.log

15 minutesNo riskThe newest update still fails with 0x80070302 and you want to know which of the next fixes is yours.

The Windows Update page shows only the code. Microsoft describes CBS.log as the log of the update installation part of the servicing stack, and it names the package or file that failed. Both solved cases above were solved from these logs.

1. Right-click Start and select Terminal (Admin). On Windows 10, search for cmd and select Run as administrator.
2. Copy both logs to the desktop, so that you read copies and Windows keeps writing the originals.

   copy %windir%\Logs\CBS\CBS.log %USERPROFILE%\Desktop\CBS-copy.log
   copy %windir%\Logs\DISM\dism.log %USERPROFILE%\Desktop\dism-copy.log

3. List the lines that carry the code. Note the date and time of the last hit.

   findstr /i /c:"80070302" %USERPROFILE%\Desktop\CBS-copy.log

4. 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. This is the search Microsoft gives for reading CBS.log.
5. Read 20 to 40 lines above the error line. Note every package name, file name and version number there.
6. Do the same in dism-copy.log if you installed the update by hand. Look for Error and for 770 near the time of your command.

PowerShell (administrator): pack all CBS logs into one file to share with a helper

Compress-Archive C:\Windows\Logs\CBS -f (Join-Path ([Environment]::GetFolderPath('Desktop')) 'CBS.zip')

Fix 3. Repair the component store with DISM, using a Windows image as the source when needed

30 to 45 minutesLow riskThe log names missing or damaged files, DISM reports the store as repairable, or you have no clear cause yet.

The cumulative update builds new system files from what is already in the component store. If store files are missing, the build fails at the restart. DISM RestoreHealth puts the missing files back. When it cannot download them, Microsoft documents how to give it a Windows image as the source.

1. In an administrator terminal, check the store first. Microsoft says DISM reports the image as healthy, repairable or non-repairable.

   DISM /Online /Cleanup-Image /ScanHealth

2. Run the repair and then System File Checker with the library steps below. Restart and try the update.

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

If RestoreHealth stops and says that the source files could not be found, it could not get clean copies from Windows Update. Give it a Windows image instead. Microsoft's documentation of repair sources requires the Wim: prefix and the index of the image inside the file.

1. Download the Windows 11 ISO file from Microsoft's software download page. Use only that page.
2. Right-click the ISO file and select Mount. Note the drive letter it gets in File Explorer, for example E:.
3. Check which image file the ISO holds.

   dir E:\sources\install.*

4. If it is install.wim, list the editions inside and note the index of your edition (Home or Pro).

   DISM /Get-ImageInfo /ImageFile:E:\sources\install.wim

5. Run the repair from that image. Replace 6 with your index. /LimitAccess keeps DISM from going to Windows Update.

   DISM /Online /Cleanup-Image /RestoreHealth /Source:Wim:E:\sources\install.wim:6 /LimitAccess

6. Run sfc /scannow, restart, and select Check for updates.

Fix 4. List the installed packages and look for an old one left by an upgrade

10 minutesNo riskThe PC was upgraded to Windows 11 24H2 or 25H2 from Windows 10 or an older Windows 11, or the log named an old package.

In the March 2026 case CBS.log showed an old Windows 10 package that blocked security updates, and only a repair install cleared it. In June 2026 Microsoft confirmed a similar case for upgraded PCs, reported with 0x800f0993 and 0x80073712. This fix finds out whether your PC has such a package.

1. Right-click Start and select Terminal (Admin).
2. List the cumulative update packages. Microsoft documents /Format:Table for a readable list.

   dism /online /get-packages /format:table | findstr /i RollupFix

3. List all packages into a text file on the desktop, so that you can search it.

   dism /online /get-packages /format:table > %USERPROFILE%\Desktop\packages.txt

4. Open packages.txt in Notepad and search for the package name that CBS.log gave you in Fix 2. Note its state.
5. Search also for 19041 and 19045. These numbers begin the versions of Windows 10 packages. A Windows 11 24H2 or 25H2 PC has 26100 packages.
6. Search for 26100.1742.1.10. A RollupFix package with this version is the one from Microsoft's known issue for upgraded PCs.

Microsoft's service alert of June 2026, as BleepingComputer quoted it, says some PCs upgraded from Windows 10 22H2 or 21H2, or from Windows 11 23H2, to 24H2 or 25H2 might fail to install the latest cumulative update. The alert names the codes 0x800f0993 and 0x80073712, not 0x80070302, so treat it as a lead to check, not as proof.

Fix 5. Install the update by hand with its checkpoint update

20 to 40 minutesLow riskYou install updates from the Microsoft Update Catalog yourself, or the log says a prerequisite is missing.

Since 24H2, Microsoft builds monthly updates as differences against a checkpoint update. Its documentation says a device must have all prior checkpoints before it can take the target update. Windows Update handles this by itself, but a manual install needs the files in the right order.

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

• The checkpoint. The first checkpoint for 24H2 is KB5043080 of September 2024, OS build 26100.1742. Microsoft's own example uses KB5048667, one of the updates readers report with 0x80070302, which needs that checkpoint first.
• "Not applicable to your computer." In the March 2026 case the catalog asked for KB5043080 first, and that file said it did not apply. The user found that Windows Update already carried the right servicing stack update. The message does not mean the PC is broken.
• The same error by hand. If DISM ends with error 770 or 0x80070302 for the .msu file, the store or a package is the cause, not the download. Go back to Fix 3 or Fix 4.

Fix 6. Reset the Windows Update components and run the troubleshooter

15 minutesLow riskThe logs point at the download or the update services, or you want the standard reset before a repair install.

A reset gives Windows Update an empty download cache and restarts its services. That clears a damaged download, which is a rare cause of this code. Every reader in the cases above who tried it still had the error, so it comes late here.

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

1. Restart the PC.
2. Open Settings > System > Troubleshoot > Other troubleshooters and select Run next to Windows Update.
3. Follow the steps in Get Help, then select Check for updates.

Full steps for both versions of Windows: Run the Windows Update troubleshooter. If the drive is nearly full, free space first, because a cumulative update needs room to stage its files: Free up disk space and delete temporary files

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

1 to 2 hoursLow riskEvery other fix failed, an old package blocks updates, or the PC runs Windows 11 24H2 Home or Pro.

A repair install writes a fresh copy of Windows with a new component store and package list, and keeps apps, files and settings. In the March 2026 case it brought the PC fully up to date after every other step failed. With current media it also moves 24H2 to a supported version.

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

In the March 2026 case Reinstall now stopped with "Repair version of Windows not found, please try again later". The route with installation media below does not depend on that download, and it is the one Microsoft gives for Windows 10 too.

1. Download the Windows 11 ISO from Microsoft's software download page, or use the one from Fix 3.
2. Right-click the ISO and select Mount, then open setup.exe from the new drive. Select Yes when Windows asks for permission.
3. Follow the screens until Ready to install. Check that it says Keep personal files and apps. If not, select Change what to keep and pick that option.
4. Select Install. The PC restarts several times. Do not turn it off.
5. When Windows is back, run winver, then open Settings > Windows Update and select Check for updates.

• If setup fails too. In the October 2025 case the repair upgrade ended with 0x8007042B - 0x2000D. 0x42B is Win32 error 1067, "The process terminated unexpectedly". Read setupact.log in C:\$Windows.~BT\Sources\Panther, which Microsoft calls the most useful setup log.
• Windows 10. Microsoft ended support for Windows 10 on 14 October 2025. The repair install works there with Windows 10 media, but Windows Update no longer brings free security updates.
• All reset options, including the ones that remove apps: Reinstall Windows without losing files

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

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

• What to send to support or to Microsoft Q&A: the CBS.zip from Fix 2, the output of winver, the KB number, the dates from Update history and what you already tried. Add dism.log if you installed the update by hand.
• One test with the antivirus paused. Microsoft's support staff often ask users to make sure that only Microsoft Defender is active. If you use another antivirus, 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 and run on its schedule. Send the logs to the administrator before you try a repair install.
• Is it hardware? Nothing in the cases we read pointed at hardware. A failing drive can damage the component store, though. If DISM finds new damage after every repair, check the drive.

How to keep install error 0x80070302 from coming back

Each point follows from how these updates are built. Microsoft documents that a 24H2 or later update is a set of differences against the files already in the component store and the last checkpoint. Anything that removes or damages those files leaves the next update with nothing to build on, and it fails at the restart.

Frequently asked questions

What does install error 0x80070302 mean?

It means a Windows 11 cumulative update failed during installation, usually at the restart, and Windows rolled it back. The code is Win32 error 770 in the notation Windows Update uses. Microsoft names 770 ERROR_CANTFETCHBACKWARDS, "The data provider cannot fetch backwards through a result set". That text belongs to database components and does not describe updates, and Microsoft has not published a Windows Update meaning for it. In practice the update could not be finished with the files in the component store, and CBS.log names the part that failed.

Which updates fail with error 0x80070302?

Readers on Microsoft Q&A report it with cumulative updates for Windows 11 24H2 and 25H2: KB5048667 (December 2024), KB5051987 (February 2025), KB5053598 (March 2025), the preview KB5055627 for ARM PCs (April 2025) and KB5079473 (March 2026), among others. Windows Latest also listed it with KB5065426 in September 2025. The list keeps growing because the code follows the PC, not one update. If your PC fails one month, it will likely fail the next month too, until the cause on the PC is repaired.

Why does the update reach 100 % and then fail with 0x80070302?

Because the hard part of a cumulative update runs during the restart. The download and the first install phase only prepare the files. During the restart the servicing stack builds the new system files from the component store and switches to them. If a file or package it needs is missing, it cannot finish and rolls everything back. That is why winver still shows the old build afterwards, and why resetting the download cache rarely helps with this code.

Is 0x80070302 a known issue that Microsoft is fixing?

No. We read the release health pages of Windows 11 24H2 and 25H2 on 14 October 2026, and neither lists this code. It is also missing from Microsoft's list of common Windows Update errors and from its Windows Update error reference. The closest known issue is the one Microsoft confirmed for 0x800f0993 and 0x80073712 on upgraded PCs, and Fix 4 checks for the package behind it. For everything else the fix is on your PC.

What does "Windows update could not be installed because of error 2359302" mean?

It is a different code from 0x80070302, and a harmless one. 2359302 written in hexadecimal is 0x00240006. Microsoft's Windows Update error reference names it WU_S_ALREADY_INSTALLED: "The update to be installed is already installed on the system." It usually appears when you run an .msu file for an update that is already in place. Check the build with winver as in Fix 1. If the build matches, there is nothing to install.

Will a repair install delete my files or programs?

Not when you choose Keep personal files and apps. Microsoft designs both routes in Fix 7, Reinstall now in Settings and setup.exe from installation media, to keep your files, apps and settings. Check the Ready to install screen before you select Install: it must say Keep personal files and apps. Back up your important files anyway, because a repair install is a large operation. Some apps may ask you to sign in again afterwards.

I see "Erro de instalação - 0x80070302" or "Ошибка установки - 0x80070302". Is it the same error?

Yes. Windows prints the same code in every language, only the words in front of it change. "Erro de instalação" is Portuguese, "Ошибка установки" is Russian, "Installationsfehler" is German and "インストール エラー" is Japanese, and all of them mean install error. The cause and every fix on this page are the same. The menu names in Settings are translated, but the commands, such as winver, DISM and sfc /scannow, are typed the same way in every language.

Should I turn off my antivirus to fix 0x80070302?

Not for good. No case we read was solved by the antivirus, and Microsoft does not link this code to it. Microsoft's support staff do ask users to check that Microsoft Defender is the active antivirus, because a third-party product can interfere with updates. If you use one, pause it for one attempt and turn it back on right after, whatever the result. If the update still fails, the antivirus is not the cause, so continue with the logs.

Does error 0x80070302 happen on Windows 10?

We found no report from Windows 10. Every case we read was on Windows 11 24H2 or 25H2, with OS builds 26100 and 26200. These versions build monthly updates on checkpoints, and Windows 10 does not. Microsoft ended support for Windows 10 on 14 October 2025, so a Windows 10 PC gets security updates only through the paid Extended Security Updates programme. If you do see the code on Windows 10, Fix 2, Fix 3 and Fix 7 apply there in the same way.