How to fix KB5057056 fails to install in Windows 10?

KB5057056 is an optional preview update of 22 April 2025 for .NET Framework 3.5, 4.8 and 4.8.1 on Windows 10 version 22H2. It brought no new security fixes, and every later .NET Framework update contains it. Restart the PC and install the newest .NET update Windows Update offers instead.

Facts checked on 15 October 2026. Steps written for Windows 10 22H2.

What Windows 10 update KB5057056 is

KB5057056 is not a Windows update in the usual sense. It updates .NET Framework, the runtime many Windows programs are built on. Microsoft released it on 22 April 2025 as a Cumulative Update Preview for .NET Framework 3.5, 4.8 and 4.8.1 on Windows 10 version 22H2.

Microsoft's page says there are no new security improvements in this release. It carries the earlier security fixes plus quality and reliability fixes. It is made of two packages: KB5056577 for PCs with .NET 3.5 and 4.8, and KB5056578 for PCs with .NET 3.5 and 4.8.1.

Why KB5057056 fails to install

Microsoft says it is not aware of any issues in this update. So the cause sits on the PC, in Windows Update or in the installed .NET Framework. These are the usual causes, ordered by how likely they are.

KB5057056 after the end of Windows 10 support

Support for Windows 10 ended on 14 October 2025. The last .NET Framework update Microsoft released for Windows 10 22H2 before that date is KB5066747. Microsoft's list then continues with .NET updates from April 2026 to KB5128925 of 13 October 2026.

How to check whether the .NET update is installed and where it failed

Before you repair anything, check what the PC already has. A failed KB5057056 entry can stay in the history after a newer .NET update installed well.

1. Open Settings > Update & Security > Windows Update > View update history.
2. Open the group of .NET Framework updates and look for a newer entry than KB5057056 that says Successfully installed. If you find one, nothing from KB5057056 is missing.
3. Note the date, time and code of the failed KB5057056 attempt.
4. Press Win + R, type %windir%\Logs\CBS and press Enter. Copy CBS.log to the Desktop and open the copy in Notepad.
5. Press Ctrl + F and search for KB5056578 or KB5056577. The lines with error or failed near the time of the attempt name the step that broke.

How to fix KB5057056 failing to install

Fix 1 solves most cases, because the update you need today is a newer .NET Framework update. Fix 2 installs the package by hand. Fix 3 repairs .NET Framework itself. Fix 4 to Fix 6 repair Windows Update, the system files and free space.

Fix 1. Restart and install the newest .NET Framework update instead

10 minutesNo riskEveryone, first. Above all if KB5057056 still shows as failed in Update history.

KB5057056 is an optional preview, and every later .NET Framework update for Windows 10 22H2 is cumulative. Installing the newest one gives the PC the same fixes plus the security fixes the preview never had.

1. Save your work and select Start > Power > Restart. Use Restart, not Shut down.
2. Open Settings > Update & Security > Windows Update and select Check for updates.
3. Install the .NET Framework update offered, and any Windows update waiting with it. Do not search for KB5057056 again.
4. Restart when Windows asks.
5. Open View update history and check that the new .NET Framework entry says Successfully installed.

The newest .NET update Microsoft lists for Windows 10 22H2 is KB5128925 of 13 October 2026. If your PC is offered an older one, such as KB5066747 of 14 October 2025, it still contains KB5057056.

Fix 2. Install the right .NET package by hand from the Microsoft Update Catalog

15 minutesLow riskWindows Update fails on the download, stops at the same point, or offers no .NET update at all.

The catalog file is the complete standalone package, so a damaged download in the update cache is no longer used. The catalog lists one file per architecture, and the wrong one will not install.

1. Press Win + R, type winver and press Enter. Check that it says Version 22H2.
2. Open Settings > System > About and read System type: 64-bit (x64), 32-bit (x86) or ARM-based (ARM64).
3. Go to https://www.catalog.update.microsoft.com and search for the newest .NET update, KB5128925. Search for KB5057056 only if you need exactly that package.
4. Select Download on the line for Windows 10 Version 22H2 that ends in your architecture, for example for x64.
5. Run the downloaded file and select Yes when Windows asks for permission.
6. Restart the PC when the installer finishes.

Step by step, with screenshots of the catalog: Install an update from the Microsoft Update Catalog.

Fix 3. Repair .NET Framework with the Microsoft .NET Framework Repair Tool

15 minutesLow riskEvery .NET Framework update fails, or programs built on .NET show errors as well.

KB5057056 patches the .NET Framework already on the PC. When that install is damaged, the patch has nothing sound to build on. The Repair Tool looks for known setup problems and repairs the installed .NET Framework.

1. Run the .NET Framework Repair Tool. Download the Microsoft .NET Framework Repair Tool and run NetFxRepairTool.exe. The wizard looks for setup problems, asks for your consent before it applies fixes, then repairs the installed .NET Framework versions. The tool is in English only.
2. Turn on .NET Framework 3.5 if a program asks for it. Select Start, search for Windows Features and open it. In Turn Windows features on or off, select the .NET Framework 3.5 (includes .NET 2.0 and 3.0) check box and select OK. Windows downloads the files, so stay online.
3. Restart and test. Restart the PC and start the program that showed the error.

These steps were written for Windows 11 25H2 and 26H2, Windows 10 22H2. The full page with the other versions and what each result means: How to repair Microsoft Visual C++ Redistributable and .NET Framework

Fix 4. Reset the Windows Update components

10 minutesLow riskAll updates fail, not only .NET, or the download fails again and again.

A damaged download in the SoftwareDistribution folder is used again at every retry. Stopping the update services and renaming the cache folders makes Windows download the .NET update from scratch.

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 5. Repair the system files with DISM and SFC

15 to 40 minutesNo riskCBS.log names missing or damaged files, or the fixes above did not help.

When every update fails, not only .NET, the damage is often in Windows itself. DISM downloads clean copies of damaged components, and SFC then repairs the system files in use.

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. Run DISM first. Type the command below and press Enter. Wait until it says The operation completed successfully.

   DISM.exe /Online /Cleanup-Image /RestoreHealth

3. Run System File Checker. 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.

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

Fix 6. Free space on drive C: with Disk Cleanup

10 minutesLow riskDrive C: is almost full.

The x64 package is 151.8 MB, and Windows needs more room than that to unpack it and keep old files until it finishes. Windows Update Cleanup removes old update files no longer needed.

1. Type Disk Cleanup in the search box on the taskbar and press Enter.
2. Select drive C: and select OK.
3. Select Clean up system files, then select drive C: and OK again.
4. Tick Windows Update Cleanup, Temporary files and Delivery Optimization Files, and select OK.
5. Restart the PC and check for updates again.

More ways to free space: Free up disk space and delete temporary files.

If KB5057056 still fails

If all six fixes failed, first ask whether you need KB5057056 at all. A newer .NET update that installed well makes the failed preview harmless.

• What to send to support: the KB number, the error code and time from Update history, CBS.log, and your .NET version (4.8 or 4.8.1).
• Which fixes you already ran, and whether other Windows updates install.

How to uninstall KB5057056

If KB5057056 did install and a .NET program broke after it, you can remove it while it is the newest .NET update. Microsoft lists no known issues, so check the program's own updates first.

1. Open Windows Update. Select Start > Settings > Update & Security > Windows Update.
2. Open the update history. Select View update history. Note the KB number and the date of the update you suspect.
3. Open the list of removable updates. Select Uninstall updates.
4. Uninstall the update. Select the update you want to remove in the list, then select Uninstall.

These steps were written for Windows 10 22H2. The full page with the other versions and what each result means: How to uninstall a Windows update

How to keep .NET Framework updates from failing again

Frequently asked questions

Do I need KB5057056?

No, not by name. KB5057056 is an optional preview, and Microsoft says it has no new security improvements. Every later .NET Framework update for Windows 10 22H2 contains its fixes. If View update history shows a newer .NET update as successfully installed, nothing from KB5057056 is missing. A failed KB5057056 entry is then only a record of the attempt, and you can ignore it.

Is KB5057056 a security update?

No. Microsoft's page says there are no new security improvements in this release. It contains the security fixes released before it, plus quality and reliability fixes. In the Microsoft Update Catalog it was listed under the classification Updates, not Security Updates. The monthly .NET updates before and after it, such as KB5055683 and KB5062154, are the ones that carry new security fixes.

What are KB5056577 and KB5056578?

They are the two parts of KB5057056. KB5056577 updates PCs with .NET Framework 3.5 and 4.8. KB5056578 updates PCs with .NET Framework 3.5 and 4.8.1. Windows installs only the one that matches the .NET version on your PC, so you may see that number in logs or in the list of installed updates instead of KB5057056.

What are the known issues of KB5057056?

Microsoft lists none. Its page says Microsoft is not currently aware of any issues in this update. A failure on your PC therefore points to the PC itself: a damaged download in the update cache, a damaged .NET Framework install or damaged system files. Fix 2, Fix 3 and Fix 5 cover these in that order.

Which .NET update should I install instead?

The newest one Windows Update offers. The newest .NET Framework update Microsoft lists for Windows 10 22H2 is KB5128925 of 13 October 2026. Before Windows 10 support ended, the last one was KB5066747 of 14 October 2025. Both contain KB5057056. We could not confirm which PCs outside Extended Security Updates get the 2026 .NET updates, so install whichever newer one your PC is offered.

Why does Windows Update not offer KB5057056 on my work PC?

Because Microsoft did not publish it to those channels. Its page says the preview was not available through Windows Update for Business and not synced to WSUS automatically. An administrator could import it into WSUS by hand. Most companies skip previews and wait for the next monthly .NET update, which contains the same fixes.

Does turning off the antivirus or firewall help KB5057056 install?

No source ties security software to this failure. The old version of this guide suggested turning off the firewall, and we removed that advice, because it leaves the PC open and the firewall does not block Windows Update downloads in a normal setup. If you suspect your third party antivirus, pause it for one test install and turn it back on at once: Turn off Microsoft Defender protection for a moment.

Is KB5057056 for Windows 11?

No. KB5057056 applies only to Windows 10 version 22H2. Windows 11 gets its own .NET Framework updates with other KB numbers. If Windows Update offers another number on your PC, follow that one. To see which Windows you have, press Win + R, type winver and read the version and build.

How do I know which .NET Framework version my PC has?

You do not need to know it to fix KB5057056. Microsoft built the update for PCs with .NET 3.5 and 4.8 and for PCs with .NET 3.5 and 4.8.1. Windows Update and the x64 catalog package pick the right part themselves: KB5056577 for 4.8 or KB5056578 for 4.8.1. The x86 and ARM64 packages are separate files in the catalog.