sodcalculator

10 Tech How-To

How to Fix Error 0x80070643 on Windows 10

Guide 10-55694 · Updated · Step by step

Error 0x80070643 (often paired with “Fatal error during installation”) appears when Windows Update or a program installer fails mid-way. This guide walks you through the most reliable fixes, from clearing the update cache to repairing system files, so you can get updates installing again without a full system reset.

What You’ll Need

  • Administrator access to your Windows 10 PC
  • Stable internet connection
  • At least 10-15 minutes of uninterrupted time
  • Optional: a backup of important files (recommended before major repairs)

Step-by-Step

  1. Run the Windows Update Troubleshooter. Go to Settings > Update & Security > Troubleshoot, select Windows Update, and click Run the troubleshooter. Let it complete and apply any fixes it suggests. Restart your PC and try updating again.
  2. Clear the SoftwareDistribution folder. Open Command Prompt as administrator (press Windows + X and choose Command Prompt (Admin) or Windows PowerShell (Admin)). Type the following commands, pressing Enter after each:
    1. net stop wuauserv
    2. net stop cryptSvc
    3. net stop bits
    4. net stop msiserver
    5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    6. ren C:\Windows\System32\catroot2 catroot2.old
    7. net start wuauserv
    8. net start cryptSvc
    9. net start bits
    10. net start msiserver

    Restart your PC and try Windows Update again.

  3. Run System File Checker (SFC) and DISM. Open Command Prompt as administrator. Run sfc /scannow and wait for it to finish. Then run DISM /Online /Cleanup-Image /RestoreHealth. This can take 15-20 minutes. Restart after both complete.
  4. Check for disk space. Error 0x80070643 can occur if the system drive is low on space. Open This PC, right-click your C: drive, and select Properties. If you have less than 10 GB free, free up space by running Disk Cleanup (cleanmgr) and removing temporary files.
  5. Repair .NET Framework. Some updates require .NET. Download the latest .NET Framework repair tool from Microsoft’s official site (search “Microsoft .NET Framework Repair Tool”) and run it. Follow the on-screen instructions, then restart.
  6. Reset Windows Update components manually. If the above didn’t work, open Command Prompt as admin and run these commands one by one:
    1. net stop wuauserv
    2. net stop cryptSvc
    3. net stop bits
    4. net stop msiserver
    5. regsvr32 /s atl.dll
    6. regsvr32 /s urlmon.dll
    7. regsvr32 /s mshtml.dll
    8. regsvr32 /s shdocvw.dll
    9. regsvr32 /s browseui.dll
    10. regsvr32 /s jscript.dll
    11. regsvr32 /s vbscript.dll
    12. regsvr32 /s scrrun.dll
    13. regsvr32 /s msxml6.dll
    14. regsvr32 /s actxprxy.dll
    15. regsvr32 /s softpub.dll
    16. regsvr32 /s wintrust.dll
    17. regsvr32 /s dssenh.dll
    18. regsvr32 /s rsaenh.dll
    19. regsvr32 /s gpapi.dll
    20. regsvr32 /s cryptdlg.dll
    21. regsvr32 /s schannel.dll
    22. regsvr32 /s msscript.ocx
    23. regsvr32 /s dispex.dll
    24. regsvr32 /s msxml.dll
    25. regsvr32 /s msxml3.dll
    26. regsvr32 /s msxml4.dll
    27. regsvr32 /s msxml5.dll
    28. regsvr32 /s ie4uinit.exe -ClearIconCache
    29. regsvr32 /s ieframe.dll
    30. regsvr32 /s msfeeds.dll
    31. regsvr32 /s msfeedsbs.dll
    32. regsvr32 /s cdfview.dll
    33. regsvr32 /s iepeers.dll
    34. regsvr32 /s wininet.dll
    35. regsvr32 /s urlmon.dll
    36. regsvr32 /s webcheck.dll
    37. regsvr32 /s occache.dll
    38. regsvr32 /s shell32.dll
    39. regsvr32 /s msjava.dll
    40. regsvr32 /s jview.dll
    41. regsvr32 /s mshta.dll
    42. regsvr32 /s mshtmled.dll
    43. regsvr32 /s mshtmler.dll
    44. regsvr32 /s adrot.dll
    45. regsvr32 /s mmefxe.ocx
    46. regsvr32 /s proctexe.ocx
    47. regsvr32 /s corpol.dll
    48. regsvr32 /s jscript9.dll
    49. regsvr32 /s imgutil.dll
    50. regsvr32 /s thumbcache.dll
    51. regsvr32 /s pcwum.dll
    52. regsvr32 /s msrating.dll
    53. regsvr32 /s mlang.dll
    54. regsvr32 /s hlink.dll
    55. regsvr32 /s msieftp.dll
    56. regsvr32 /s url.dll
    57. regsvr32 /s comcat.dll
    58. regsvr32 /s oleaut32.dll
    59. regsvr32 /s ole32.dll
    60. regsvr32 /s msxml2.dll
    61. regsvr32 /s msxml6.dll
    62. regsvr32 /s msxml3.dll
    63. regsvr32 /s msxml4.dll
    64. regsvr32 /s msxml5.dll
    65. regsvr32 /s msxml6.dll
    66. regsvr32 /s msxml3.dll
    67. regsvr32 /s msxml4.dll
    68. regsvr32 /s msxml5.dll
    69. regsvr32 /s msxml6.dll
    70. net start wuauserv
    71. net start cryptSvc
    72. net start bits
    73. net start msiserver

    Restart and try updates again.

  7. Perform a repair upgrade. If all else fails, download the Windows 10 Media Creation Tool from Microsoft’s official website. Run it and choose Upgrade this PC now. This reinstalls Windows while keeping your files and apps. It often fixes stubborn update errors.

Common Mistakes

  • Skipping the restart after each step. Many fixes require a reboot to take effect. Not restarting can leave the system in an inconsistent state.
  • Running commands without admin rights. The commands in this guide need an elevated Command Prompt. If you see “Access denied,” close and reopen as administrator.
  • Deleting the wrong folder. When renaming SoftwareDistribution, make sure you type the path correctly. Deleting the folder entirely (instead of renaming) can cause more issues.
  • Ignoring disk space. Windows needs several gigabytes free for updates. If you’re under 10 GB, the update may fail with this error.
  • Using third-party “fixers.” These often do more harm than good. Stick to built-in tools and official Microsoft utilities.

Tips

  • Check for pending reboots. If Windows is waiting for a restart, updates may fail. Restart your PC before troubleshooting.
  • Disable third-party antivirus temporarily. Security software can interfere with updates. Disable it just during the update, then re-enable it.
  • Use a wired connection. A stable Ethernet connection is more reliable than Wi-Fi for large updates.
  • Keep your system clock accurate. Incorrect date/time can break SSL connections and cause update failures.

Troubleshooting

If the error persists after trying all steps, try the following:

  • Check the Windows Update log. Open Event Viewer (type eventvwr in Start), go to Windows Logs > Setup, and look for errors around the time of the failed update. The details may point to a specific component.
  • Manually download the update. If you know which update is failing, search for it on the Microsoft Update Catalog website, download the .msu file, and install it manually by double-clicking.
  • Create a new user account. Sometimes a corrupted user profile causes update issues. Create a new local admin account and try updating from there.
  • Use System Restore. If the error started recently, restore your PC to a point before it occurred. Search for “Create a restore point” in Start, click System Restore, and choose a restore point.
  • If nothing works, consider a clean install. Back up your files, then use the Media Creation Tool to create a bootable USB and reinstall Windows 10 from scratch. This is the most drastic step but guarantees a fresh system.

Frequently Asked Questions

  1. What causes error 0x80070643? It’s a generic Windows Update or installation failure, often due to corrupted update files, insufficient disk space, or a broken Windows component.
  2. Will I lose my files if I do a repair upgrade? No, a repair upgrade (step 7) keeps your personal files and installed apps. However, it’s always wise to back up important data before any major repair.
  3. How long does the DISM command take? Typically 15-30 minutes, but it can take longer on older hardware. Let it run to completion without interrupting.
  4. Can I fix this error without admin rights? No, most fixes require administrator privileges. If you’re on a work or school PC, contact your IT administrator.
  5. Is error 0x80070643 the same on Windows 11? The error code exists on Windows 11 too, but the fixes may differ slightly. This guide is specific to Windows 10.
  6. Why does the error say “Fatal error during installation”? This is the human-readable part of the error. It means the installer encountered a critical issue and aborted, which the fixes above address.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →