Fix it now
0x80070643 is Win32 1603, ERROR_INSTALL_FAILURE, wrapped as an HRESULT: a fatal error during installation. It says a transaction rolled back and nothing more. On a .NET Framework install the usual reason is that the framework already on the machine is damaged, and the real error is in the setup logs rather than in the code.
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
explorer %temp%
- Reboot before anything else. A pending file operation from an earlier update makes every attempt fail identically and costs nothing to rule out.
- Run the three repair commands in the order given: sfc draws its replacement files from the store DISM repairs, so running sfc first wastes a pass.
- Run Microsoft’s .NET Framework Repair Tool and apply what it recommends. It detects the installed versions and repairs the damaged one in place.
- Reboot again and retry. If it still fails, the last command opens the temporary folder – sort by date and read the newest setup logs for the first failure, not the last.
On current Windows builds the 4.x .NET Framework is part of the operating system and is serviced with it. Downloading a standalone installer for a version the OS already includes generally reproduces the same error.
If the installation completes you are finished. If not, the next section explains why one code covers so many different faults and how to find yours.
Why it happens
0x80070643 decodes cleanly and unhelpfully. The 0x8007 prefix marks a Win32 error carried as an HRESULT, and 0x643 is 1603, which Microsoft publishes as ERROR_INSTALL_FAILURE, “Fatal error during installation”. Any MSI transaction that aborts can end this way, so the code tells you an install rolled back and nothing about why.
Framework installs meet it disproportionately because they are chained. A bootstrapper runs several packages in sequence, and a failure in any one of them collapses the whole chain into a single result. The consequence is that the fix depends entirely on which link broke, and the code cannot tell you. A damaged existing framework, a component store that cannot supply a file, a pending restart blocking assembly writes and a Windows Update data store in a bad state all end at the same four bytes.
That is why the logs matter more than usual here. The .NET setup components write a log for the bootstrapper and one per component into the temporary folder. Read them by date, find the first line reporting a failure, and work on that. Everything after it describes the rollback and is noise.
Three other codes travel with this one and none of them has a published meaning. 0x800713EC looks like a wrapped Win32 error, but the number it would wrap, 5100, is not in Microsoft’s published system error code list. 0x81F40001 and 0xC8000222 appear only in user-forum posts. Treat all three the same way: the log line that carries the code says what was happening, and that line is the diagnosis.
A restart is pending and blocking file replacement
You have this one if The machine has an outstanding restart from Windows Update or another install, and the failure is instant and identical every time.
- Restart and let any outstanding servicing finish before doing anything else.
- Retry the installation as the first action after the restart, before other applications load.
- If Windows Update asks for a second restart, take it and try again afterwards.
The installed framework is damaged
You have this one if Repairing the framework from Settings also fails, or several managed applications have started failing at once.
- Run the .NET Framework Repair Tool and apply everything it recommends.
- Follow with
DISM /Online /Cleanup-Image /RestoreHealthand thensfc /scannow. - Reboot and retry the original installation.
- If the application needs .NET Framework 3.5, enable the Windows feature rather than installing a download:
DISM /Online /Enable-Feature /FeatureName:NetFx3 /All.
Community cleanup utilities that strip framework versions can leave a machine unable to service itself. Treat them as a last resort and take a system image first.
The component store cannot supply the files the install needs
You have this one if DISM reports corruption, or sfc /scannow finds violations it cannot repair.
- Run
DISM /Online /Cleanup-Image /ScanHealthto confirm the store is the problem before trying to repair it. - Repair with
DISM /Online /Cleanup-Image /RestoreHealth, adding/Source:and/LimitAccessif the machine cannot reach Windows Update. - Rerun
sfc /scannowand confirm it now completes cleanly. - Retry the framework installation.
The update client is in a bad state
You have this one if The failure happens when the framework arrives through Windows Update, and other updates are failing too.
- Stop the services:
net stop wuauservand, where present,net stop bits. - Rename
C:\Windows\SoftwareDistributiontoSoftwareDistribution.old. - Start the services again and let Windows rebuild the folder.
- Check for updates, install what is offered, reboot, then retry.
Renaming that folder discards the download cache and the update history shown in Settings. Nothing installed is removed and the folder is rebuilt automatically, but the machine re-downloads anything it was part way through.
Full reference
What the codes actually resolve to
| Code | Resolves to | What you can rely on |
|---|---|---|
| 0x80070643 | Win32 1603, ERROR_INSTALL_FAILURE | A transaction rolled back. Nothing about the cause |
| 0x800713EC | 0x13EC is 5100, which is not in Microsoft’s published list | No published meaning. Read the log line that carries it |
| 0x81F40001 | Not published by Microsoft | No published meaning. Read the log line that carries it |
| 0xC8000222 | Not published by Microsoft | No published meaning. Read the log line that carries it |
It is worth being blunt about the last three. There is a great deal written about each of them, and none of it traces back to a Microsoft page. When a code has no published meaning the honest method is to stop treating the number as information and start reading what the installer was doing when it produced it.
Finding the real error in the logs
The chained setup writes into the current user’s temporary folder: one log for the bootstrapper and one for each component it attempted. Open the folder, sort by date, and start with the newest.
explorer %temp%
rem then, for any MSI log you find:
findstr /c:"Return value 3" "%temp%\<logfile>"
- Search each log for the FIRST failure, not the last. The last is almost always the rollback reporting itself.
- In an MSI log, the action named immediately above the first
Return value 3is the one that failed. - The bootstrapper log names which component it was installing when the chain collapsed. Open that component’s own log next.
- If a log names a file or registry key, go and look at it. That is the concrete thing you can act on.
- Keep the logs. If you end up with the vendor or with Microsoft support, they are the first thing asked for.
Repair order for the operating system underneath
| Command | What it does | When to run it |
|---|---|---|
DISM /Online /Cleanup-Image /ScanHealth |
Reports whether the component store is damaged | First, before you repair anything |
DISM /Online /Cleanup-Image /RestoreHealth |
Repairs the store, from Windows Update or a source you supply | When ScanHealth reports damage |
sfc /scannow |
Verifies protected system files and replaces them from the store | After DISM, never before |
DISM ... /Source:<path> /LimitAccess |
Repairs from local media instead of Windows Update | On isolated or tightly filtered machines |
When the framework itself will not repair
- Confirm which version the application actually requires. Installing a newer one does not satisfy a dependency on an older family.
- Check whether the machine is missing servicing updates. A framework several years behind on patches sometimes cannot install over itself.
- Try the installation from a clean boot, with third-party services and startup items disabled, to rule out an endpoint product holding files.
- If DISM cannot repair the store from Windows Update, supply matching installation media with
/Source:and/LimitAccess. - An in-place upgrade using installation media of the same version repairs the operating system while keeping applications and data, and is a much smaller step than a clean install.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80070643 |
Win32 1603, ERROR_INSTALL_FAILURE: a fatal error during installation. The transaction rolled back and the reason is in the setup log | Microsoft Learn |
0x800713EC |
The 0x8007 prefix marks a wrapped Win32 error, but 0x13EC (5100) is not in Microsoft’s published system error code list, so there is no published meaning | not published by the vendor |
0x81F40001 |
No Microsoft page publishes a meaning. Work from the setup log line that carries it | not published by the vendor |
0xC8000222 |
No Microsoft page publishes a meaning. Work from the setup log line that carries it | not published by the vendor |
Confirm the fix worked
- Rerun the installation and confirm it reports success rather than rolling back.
- Run
sfc /scannowand confirm no integrity violations remain. - Run
DISM /Online /Cleanup-Image /ScanHealthand confirm the store reports as healthy. - Launch an application that depends on the framework and confirm it starts and runs normally.
- Check for updates once and confirm Windows Update completes a scan without error, which tells you the update client is healthy too.
Questions people ask about this
Do I have to buy anything to fix this?
No. The .NET Framework is free, the repair tool is free, and DISM and SFC ship with Windows. Nothing here depends on your Windows edition, and an activated machine and an unactivated one fail identically.
What does 0x80070643 actually mean?
It is Win32 1603 wrapped as an HRESULT: ERROR_INSTALL_FAILURE, a fatal error during installation. That is all it means. Any MSI transaction that aborts can end with it, which is why the code alone never identifies the cause.
Can I skip straight to reinstalling Windows?
You should not need to. A DISM repair against a matching source fixes the underlying store in most cases, and an in-place upgrade using media of the same version repairs the system while keeping applications and data.
Why does the standalone .NET installer say it is already part of the operating system?
Because on current Windows builds it is. The 4.x framework is serviced with the OS, so the standalone package declines to install over it. Repair the OS component instead of forcing the download in.
Which log file should I actually read?
Start with the newest files in the temporary folder written by the framework setup, then open the per-component log for whichever package the bootstrapper says failed. Search for the first line reporting a failure, since everything after it describes the rollback.
