If Windows 10 shows 0x80070643 while installing a Windows Recovery Environment (WinRE) or related update, install the latest available Windows updates and restart first. Microsoft says the known WinRE issue was fixed in KB5063523 and later. If the message really says 0x0070643, do not assume it has the same cause: that code is not the code Microsoft documents for this failure, so copy the complete message and identify the exact update before changing anything.
First confirm the code and the failed update
The two strings look similar but are not interchangeable. Microsoft documents 0x80070643 as ERROR_INSTALL_FAILURE in this servicing context. The literal 0x0070643 was not found in the Microsoft documentation reviewed for this problem. A missing digit, an extra zero, or a transcription error can send you toward the wrong repair.
As an Amazon Associate I earn from qualifying purchases.
- Open Settings > Update & Security > Windows Update.
- Select View update history and note the complete error code, the update’s KB number, and whether the entry mentions Windows Recovery Environment, WinRE, Microsoft Defender, or another component.
- Copy the code from the Windows Update details rather than relying on a screenshot or memory. If it is exactly
0x0070643, use Microsoft’s Error Lookup Tool and the full update text instead of applying the WinRE partition procedure below.
The instructions in this article apply to the documented 0x80070643 WinRE servicing failure. They can also help when the same code appears during a Defender-related update, but the failed KB and component still matter.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWhat 0x80070643 means in this Windows 10 case
0x80070643 is a general installation-failure code, not a diagnosis by itself. In the WinRE incident, the update cannot write the recovery files because the recovery partition does not have enough free space. Microsoft states that the WinRE update requires 250 MB of free space in the recovery partition. Some computers have a recovery partition that is smaller than that requirement, while others have a suitable-sized partition in the wrong location or with an unexpected layout.
#1 Best Overall
- Dual USB-A & USB-C Bootable Drive – compatible with nearly all Windows PCs, laptops, and tablets (UEFI & Legacy BIOS). Works with Surface devices and all major brands.
- Fully Customizable USB – easily Add, Replace, or Upgrade any compatible bootable ISO app, installer, or utility (clear step-by-step instructions included).
- Complete Windows Repair Toolkit – includes tools to remove viruses, reset passwords, recover lost files, and fix boot errors like BOOTMGR or NTLDR missing.
- Reinstall or Upgrade Windows – perform a clean reinstall of Windows 7 (32bit and 64bit), 10, or 11 (amd64 + arm64) to restore performance and stability. (Windows license not included.). Includes Full Driver Pack – ensures hardware compatibility after installation. Automatically detects and installs drivers for most PCs.
- Premium Hardware & Reliable Support – built with high-quality flash chips for speed and longevity. TECH STORE ON provides responsive customer support within 24 hours.
Microsoft also documented a confusing error-message behavior: when disk space is insufficient, an error-code handling problem can display 0x80070643 - ERROR_INSTALL_FAILURE instead of the more specific message users would otherwise receive. That is why the code alone cannot prove that the partition is the cause.
- Most likely in the WinRE scenario: insufficient free space in the recovery partition.
- Also possible: a damaged or disabled WinRE configuration, a different update failure, or an update that is unrelated to recovery tools.
- Not established by this code alone: malware, a failing hard drive, or a need to reinstall Windows.
Do these low-risk checks before editing partitions
Partition work can make the recovery environment unavailable if it is performed on the wrong disk or partition. Complete the non-destructive steps first and make sure you can recover your personal files if something goes wrong.
- Back up important documents, game saves, and other data to a separate drive or trusted cloud location.
- Disconnect nonessential USB drives, docks, printers, and other external hardware while Windows Update runs. Leave the keyboard, mouse, network adapter, and any device required to operate the computer connected.
- Confirm that the system drive has ordinary free space. The 250 MB requirement applies to the recovery partition, not merely to free space on
C:. - If device encryption or BitLocker is enabled, make sure you have the recovery key before making partition changes.
- Use an administrator account. The commands later in this guide change boot-recovery configuration and cannot be run from a standard Command Prompt.
Fix 1: install the current update and restart
This is the supported first move because Microsoft says the known WinRE 0x80070643 issue was fixed in KB5063523 or later. Windows 10 support status varies by edition and servicing arrangement, so Windows Update may offer a different final update or no longer offer a free update at all.
Recommended Free Tools
- Go to Settings > Update & Security > Windows Update.
- Select Check for updates and install every available cumulative, servicing-stack, and WinRE-related update.
- Restart when prompted. Do not just close Settings; the recovery update may complete only during the reboot sequence.
- After Windows starts, return to Windows Update and select Check for updates again. Reopen View update history to see whether the same KB still fails.
If the update installs successfully after the restart, no partition change is needed. If the same KB continues to fail and the code is confirmed as 0x80070643, continue with the checks below.
Fix 2: run Windows Update’s built-in checks
Microsoft’s general Windows Update guidance recommends removing nonessential external hardware, running the Windows Update troubleshooter, checking that the account has appropriate permissions, and resetting Windows Update components when normal servicing does not recover. These checks are appropriate when the failed update is not clearly a WinRE update or when the recovery partition already appears adequate.
- Open Settings > Update & Security > Troubleshoot > Additional troubleshooters.
- Select Windows Update, choose Run the troubleshooter, and apply any proposed repair.
- Restart Windows, then check for updates again.
- If the troubleshooter reports that update components are damaged or stuck, follow Microsoft’s Windows Update component-reset procedure for your Windows 10 build. Component reset is different from deleting a recovery partition; do not substitute DiskPart commands for it.
A troubleshooter cannot create space inside a recovery partition. If it reports that the update service is healthy but the WinRE update still fails, inspect WinRE before considering the manual 250 MB procedure.
Inspect WinRE with reagentc /info
Microsoft’s KB5028997 procedure starts by determining where WinRE is installed and how the disk is arranged. Use an elevated Command Prompt so you do not accidentally inspect a different user context.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →- Open Start, type Command Prompt, right-click it, and select Run as administrator.
- Run:
reagentc /infoRead the output and record whether Windows RE status is enabled, the Windows RE location, and the disk and partition indexes shown there. The recovery partition must be after the Windows operating-system partition for the documented rebuild sequence. If WinRE is on another disk, if the location is missing, or if the partition order does not match the procedure, stop instead of guessing.
The output is also useful after any repair: a successful reconfiguration should show WinRE enabled and a valid Windows RE location.
Fix 3: Microsoft’s 250 MB WinRE partition procedure
Use this procedure only when all of these conditions are true:
- The code is confirmed as
0x80070643and the failure is associated with WinRE servicing. - You have backed up important data and, where applicable, have the BitLocker recovery key.
reagentc /infoidentifies the WinRE location and the recovery partition is after the OS partition.- You can identify the correct OS disk, OS partition, and existing WinRE partition in DiskPart.
The following sequence follows the Microsoft KB5028997 approach. DiskPart does not provide a safety net: selecting the wrong partition can remove personal data or the wrong boot volume. If your screen does not match the documented layout, exit DiskPart and obtain qualified help or use Windows recovery options instead.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- High-speed USB 3.0 performance of up to 150MB/s(1) [(1) Write to drive up to 15x faster than standard USB 2.0 drives (4MB/s); varies by drive capacity. Up to 150MB/s read speed. USB 3.0 port required. Based on internal testing; performance may be lower depending on host device, usage conditions, and other factors; 1MB=1,000,000 bytes]
- Transfer a full-length movie in less than 30 seconds(2) [(2) Based on 1.2GB MPEG-4 video transfer with USB 3.0 host device. Results may vary based on host device, file attributes and other factors]
- Transfer to drive up to 15 times faster than standard USB 2.0 drives(1)
- Sleek, durable metal casing
- Easy-to-use password protection for your private files(3) [(3)Password protection uses 128-bit AES encryption and is supported by Windows 7, Windows 8, Windows 10, and Mac OS X v10.9 plus; Software download required for Mac, visit the SanDisk SecureAccess support page]
1. Disable WinRE before changing its partition
reagentc /disableConfirm that the command reports that Windows RE was disabled. If it fails, do not continue to delete or recreate a partition; resolve the configuration problem first.
2. Identify the disk and shrink the OS partition
diskpart
list disk
select disk <OS disk number>
list partition
select partition <OS partition number>
shrink desired=250 minimum=250Replace the angle-bracketed values with the numbers shown on your computer. The shrink command removes 250 MB from the end of the selected OS partition, creating space for a larger recovery partition. If DiskPart reports that it cannot shrink by 250 MB, stop and investigate the layout rather than choosing a smaller value for this WinRE requirement.
3. Select and remove the existing WinRE partition
list partition
select partition <WinRE partition number>
delete partition overrideBefore entering the delete command, verify the selected partition against the size, position, and WinRE location recorded earlier. Do not delete the EFI System Partition, the Microsoft Reserved partition, the OS partition, or a vendor recovery partition that is not the WinRE partition identified by reagentc /info.
4. Recreate the recovery partition for the disk’s partition style
Use the command set that matches the disk style shown by list disk. A star in the GPT column indicates a GPT disk. Microsoft supplies separate commands because GPT and MBR recovery partitions use different identifiers.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
For a GPT disk:
create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac
gpt attributes=0x8000000000000001
format quick fs=ntfs label="Windows RE tools"For an MBR disk:
create partition primary id=27
format quick fs=ntfs label="Windows RE tools"Do not use the GPT identifier on an MBR disk or the MBR identifier on a GPT disk. If DiskPart rejects the identifier or the resulting partition is not where the procedure expects it, type exit and stop for assistance.
5. Re-enable and verify WinRE
exit
reagentc /enable
reagentc /infoThe final command should show Windows RE as enabled and point to the recreated recovery partition. Restart Windows, run Windows Update, and retry the failed KB. If reagentc /enable fails, do not repeatedly delete partitions; capture the exact message and restore the configuration using Microsoft’s recovery guidance.
When the computer will not boot
A startup failure is a different branch from a Windows Update failure. If the machine cannot reach the desktop, do not apply the WinRE partition sequence merely because a previous update displayed 0x80070643. Microsoft’s startup guidance uses Windows installation media, Startup Repair, Event Viewer or log review, and boot-repair commands according to the symptom.
- If Windows reaches the recovery screen, choose Troubleshoot > Advanced options > Startup Repair.
- If Startup Repair cannot resolve the problem, use installation media to enter the Windows Recovery Environment and review the available repair options.
- Record whether the failure began immediately after an update, whether the disk is detected, and whether the error names a boot file. Those details determine whether the issue is boot configuration, filesystem damage, or an update rollback.
Do not format the OS disk or delete recovery partitions as a first response to a boot failure. The WinRE-specific procedure is intended for a confirmed servicing-layout problem, not every startup symptom.
Choose the least risky method that matches the evidence
| Approach | Evidence required | Invasiveness | When it fits |
|---|---|---|---|
| Install updates and restart | Confirmed code and a pending update; no partition diagnosis needed | Low | First step for a WinRE issue because Microsoft says KB5063523 and later contain the fix |
| Windows Update troubleshooter and component checks | Update failure may be service-related or the failed component is unclear | Low to moderate | When ordinary update servicing is stuck or permissions and services need checking |
Inspect with reagentc /info |
Confirmed or suspected WinRE servicing failure | Low | Before any partition change; identifies WinRE status and location |
| Rebuild the WinRE partition | Exact code, matching KB, correct partition order, identifiable WinRE partition, and a backup | High | Only when the recovery partition lacks the required 250 MB and the Microsoft layout matches |
| Startup Repair or installation media | Windows does not boot | Varies | Boot failures, not an assumed substitute for the WinRE update diagnosis |
Windows 10 support status matters in 2026
Microsoft states that free Windows 10 software updates through Windows Update, technical assistance, and security fixes ended on October 14, 2025. That date does not make every existing installation stop working, but it changes what updates you can expect. Eligibility depends on the edition, servicing arrangement, and whether the device can move to a supported Windows release.
If Windows Update offers no newer cumulative or WinRE package, check the device’s edition and servicing status before repeatedly attempting the same repair. A business-managed computer may receive updates under an organization-specific program, while a consumer installation may need a supported Windows upgrade or a hardware-compatibility decision. Do not use an unofficial image or a random partition utility to compensate for an unsupported servicing state.
Quick Recap
What success and failure look like
- Successful update repair: the failed KB installs, Windows Update no longer lists the error, and
reagentc /infoshows WinRE enabled when checked. - Successful partition rebuild: WinRE is enabled, its location points to the recreated recovery partition, and the WinRE update completes after a restart.
- Wrong diagnosis likely: the code is exactly
0x0070643, the failed update is unrelated to WinRE, or the problem is activation, a driver, a hardware device, or startup boot files. - Stop and seek assistance: DiskPart shows an unexpected layout, the WinRE partition is on another disk, BitLocker recovery information is unavailable, or any command proposes deleting a partition you cannot identify confidently.
As an optional shortcut after the manual checks, Outbyte PC Repair can address some common Windows issues, broken system elements, invalid redirects, shared DLL problems, settings that contribute to CPU, RAM or disk load, temporary and cache files, privacy warnings, vulnerability checks, and app-crash logging. It runs on Windows 11, 10, 8 and 7; its free trial is category-based for at least two days and then requires a subscription. It complements antivirus software rather than replacing it, results vary, and no tool repairs every crash.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
