How to fix Windows Error Code 0x800706BE?

Error 0x800706BE means "The remote procedure call failed": one part of Windows asked another to do something and got no answer. You see it in Windows 11 Setup as 0x800706BE - 0x4002F, or in Windows Update as an install or download error. In Setup, select Previous version of Setup first; in Windows Update, restart and select Retry.

Facts checked on 16 October 2026. Steps written for Windows 11 26H2 and 25H2 Setup media, Windows 11 25H2 and Windows 10 22H2 Windows Update.

What error code 0x800706BE means

0x800706BE is a Windows error number wrapped in a result code. Microsoft's table of upgrade errors says a result code that starts with 8 holds a Win32 error code. The last four digits, 06BE, are error 1726, which Microsoft's list of system error codes names RPC_S_CALL_FAILED, with the text "The remote procedure call failed."

A remote procedure call (RPC) is how one Windows process asks another one, often a service, to do work. "Remote" does not mean the internet here: most of these calls stay on your own PC. The call failed because the process on the other side stopped, crashed or was cut off before it answered.

Why Windows shows 0x800706BE

Microsoft does not publish a cause for this code in Setup or in Windows Update. The ranking below joins the meaning of the code with what users report on Microsoft Q&A and in videos. Each cause points to a fix.

Where Windows writes the real cause of 0x800706BE

You do not need any log for Fix 1 or Fix 5. Read the logs when the first fixes do not help, because the lines before the code name the component that stopped answering.

How to fix error 0x800706BE in Windows 11 Setup and Windows Update

Fix 1 to Fix 4 are for Windows 11 Setup and the 0x4002F code. Fix 5 and Fix 6 are for Windows Update. Fix 7 is for a program or printer. Fix 8 repairs Windows itself, and Fix 9 checks the hardware when errors show up everywhere.

Fix 1. Install with the previous version of Windows Setup

5 minutes, plus the installNo riskYou booted from a USB stick and the error appeared before or at the drive step.

The 0x4002F codes come from the redesigned Setup that Windows 11 media has used since 24H2. The same media still carries the older Setup, and users report that it gets past failures that the new one shows with 0x4002F.

1. Boot from the USB stick and choose your language, time and keyboard settings.
2. On the Select setup option screen, select Previous version of Setup in the lower left corner. Some older 24H2 media show Launch the legacy experience as an option instead.
3. Select Next. The older Setup opens and asks for the language again.
4. Select Install now, enter or skip the product key, choose the edition and accept the license terms.
5. Choose Custom: Install Windows only (advanced), select the target partition and select Next.

The older Setup installs the same Windows version from the same media. The same route helps with other 0x4002F codes; for the disk code 0x80042444, see our guide to 0x80042444 - 0x4002F in Windows 11 Setup.

Fix 2. Boot the installation stick in UEFI mode

10 minutesLow riskAn older PC, or a PC whose boot menu lists the stick twice.

Users report 0x800706BE - 0x4002F mostly on older laptops, and one report names a laptop without UEFI and Secure Boot. When the stick starts in Legacy BIOS mode, the new Setup runs in a mode Windows 11 is not built for, and a call inside it can fail.

1. If Windows still runs on the PC, press Win + R, type msinfo32 and press Enter. Read BIOS Mode: UEFI or Legacy.
2. Restart and open the boot menu with the key your PC shows at start, often F12, F11, F8 or Esc.
3. If the stick is listed twice, choose the entry that starts with UEFI:.
4. If there is no UEFI entry, open the firmware settings (often F2 or Del) and look for Boot Mode or CSM. Set UEFI, or turn CSM off, if the PC offers it.
5. Save, restart from the stick and run Setup again.

Fix 3. Make a new installation stick with Microsoft's Media Creation Tool

20 to 40 minutesLow riskThe stick was made with a third-party tool, a multi-boot loader or an ISO not from Microsoft.

A modified image or a loader changes how Setup starts and which components it can reach. If one of them is missing or changed, a call to it fails. A stick from Microsoft's own tool rules the media out.

1. On a working PC, open Microsoft's Download Windows 11 page and select Download Now under Create Windows 11 Installation Media.
2. Plug in a USB stick of at least 8 GB. Everything on it is erased.
3. Run the tool, accept the license, keep or change the language and edition, and choose USB flash drive.
4. Select the stick and wait until the tool says it is ready.
5. Boot the PC from the new stick as in Fix 2 and run Setup again.

Fix 4. Run setup.exe from inside Windows to upgrade to 25H2 or 26H2

1 to 2 hoursLow riskA working Windows 10 or Windows 11 is on the PC, or the 26H2 feature update fails in Windows Update.

Started from inside Windows, Setup runs on the installed system with its drivers and services, not from the stick's small boot system. It skips the boot step where the 0x4002F codes appear, and it replaces a feature update that fails in Windows Update.

1. Back up the files you cannot lose: Back up your files (Windows Backup, File History, Time Machine).
2. Download the Windows 11 ISO from Microsoft's Download Windows 11 page, or use the Installation Assistant on the same page.
3. Right-click the ISO and select Mount. A new drive opens in File Explorer.
4. Double-click setup.exe, select Next, and choose to keep your files and apps when Setup asks.
5. Let the PC restart several times and do not turn it off.

If this route fails, the code and the logs move to C:\$WINDOWS.~BT\Sources\Panther. Read the section on logs above, and free space first with Free up disk space and delete temporary files when the log names disk space.

Fix 5. Restart, retry and reset the Windows Update components

10 minutesLow riskSettings shows Install error - 0x800706be or Download error - 0x800706be for an update.

In Windows Update the call fails when a service that installs the update stops in the middle. A restart starts every service again. If the update still fails, renaming the update cache makes Windows download it again from a clean start.

1. Save your work and select Start > Power > Restart. Use Restart, not Shut down, so Windows starts all services fresh.
2. Open Settings > Windows Update and select Retry next to the failed update.
3. If it fails again, note the KB number from Update history.
4. Reset the update components: stop the services, rename the cache folders and start them again.

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

Microsoft's automatic check runs the same idea with fewer steps. Try it before the reset if you prefer: Run the Windows Update troubleshooter.

Fix 6. Install the failed update another way

15 to 30 minutesLow riskOne update keeps failing with 0x800706be after Fix 5.

The standalone installer from the Microsoft Update Catalog runs outside the Windows Update client. If the call that fails belongs to that client, the update can still install by itself.

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

• A monthly cumulative update: download it from the Update Catalog for your version and system type, as above.
• A feature update to 25H2 or 26H2: use the Installation Assistant or the ISO from Fix 4 instead.
• If Microsoft has a newer update for your version, install that one. It contains the older fixes.

Fix 7. Restart the service behind the program or printer, and reinstall the device

10 minutesLow riskA program or a printer installer shows 0x800706BE or "The remote procedure call failed."

Here the other end of the call is a service, such as Print Spooler for printers. When it crashes mid-call, the program reports the RPC failure. Restarting the service and reinstalling the device clears a crash caused by a bad driver.

1. Press Win + R, type services.msc and press Enter.
2. Find the service the program depends on. For printers it is Print Spooler.
3. Right-click it and select Restart. If it is stopped, select Start.
4. For a printer or other device, press Win + X and open Device Manager.
5. Right-click the device, select Uninstall device, confirm, and restart the PC.
6. Install the newest driver from the maker's support page, then add the device again.

We could not confirm a Microsoft article that ties 0x800706BE to one printer or program. If the service stops again right after you restart it, its driver or the program itself is the problem. Ask the maker for an update. More on driver steps: Update, roll back or reinstall a driver.

Fix 8. Repair system files and test in a clean boot

20 to 40 minutesLow riskThe error comes back after the fixes above, or other Windows tools also fail.

A damaged system file can make a service crash every time it is called. DISM and SFC replace damaged files. A clean boot shows whether a third-party service, such as security or tuning software, breaks the call.

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

Then start Windows with only Microsoft services and try the update or program again: How to perform a clean boot in Windows. If the error is gone in a clean boot, turn the services back on in groups until it returns. A scan with Microsoft Defender is a sensible check at the same time: How to scan for malware with Microsoft Defender.

Fix 9. Test the hardware when errors show up everywhere

30 minutes to several hoursLow riskMany errors at once: apps crash, installers close without a message, and the same stick works one time and fails the next.

A process that crashes because the CPU or memory makes a mistake ends the call without warning. On Microsoft Q&A, a user whose update failed with 0x800706be reported that it was an unstable Intel Core 13th generation CPU, and that updates worked after the CPU was replaced.

1. Remove any overclock or memory profile (XMP or EXPO) in the firmware settings and test again.
2. Update the firmware (BIOS) from the PC or motherboard maker's support page.
3. Test the memory: How to test your RAM with Windows Memory Diagnostic.
4. If you have an Intel Core i5, i7 or i9 of the 13th or 14th generation, check the maker's support page for your board's latest BIOS and contact Intel or the seller if the crashes go on.

If error 0x800706BE is still there

When the fixes for your case have not helped, the answer is in the log of the place where you saw the code. Copy it before you restart, because the Setup logs from a USB boot vanish.

• What to send to support: the full code, where it appeared (Setup, Windows Update or a program), the Windows version, and the KB number for an update.
• Attach setuperr.log and setupact.log for Setup, or a screenshot of Update history for Windows Update.
• Say whether the PC has an overclock, and name the CPU model.

How to keep 0x800706BE from coming back

Frequently asked questions

What does error code 0x800706BE mean?

It means "The remote procedure call failed." The code holds the Win32 error 1726, which Microsoft names RPC_S_CALL_FAILED. One part of Windows called another part, usually a service, and the call broke off before an answer came back. It does not say which component failed: that depends on where you saw the code. In Windows 11 Setup it comes with 0x4002F. In Windows Update it shows as Install error or Download error. The fixes on this page follow those places.

How do I fix 0x800706BE - 0x4002F when installing Windows 11?

Select Previous version of Setup on the Select setup option screen and install with the older Setup (Fix 1). If that link is missing or the older Setup also fails, boot the USB stick from its UEFI entry in the boot menu (Fix 2). Then make a fresh stick with Microsoft's Media Creation Tool (Fix 3). If a working Windows is on the PC, mount the ISO and run setup.exe inside Windows instead (Fix 4).

What is 0x4002F?

0x4002F is the extend code of Windows Setup, the second half of the error. Microsoft's table reads the first digit as the phase, and phase 4 is SP_EXECUTION_OOBE_BOOT. The operation 2F is not in the table, which ends at 20 and was written for Windows 10 upgrades. The new Windows 11 Setup shows 0x4002F after many different first codes, so it tells you little by itself. Read the first code: 0x800706BE means a call between components failed.

How do I fix Install error - 0x800706be in Windows Update?

Restart the PC with Restart, not Shut down, and select Retry in Settings > Windows Update. If it fails again, reset the Windows Update components and the update cache (Fix 5). If the same KB still fails, download it from the Microsoft Update Catalog and run it by itself (Fix 6). When the failing update is the upgrade to 25H2 or 26H2, use the Installation Assistant or the ISO instead (Fix 4).

What does Download error - 0x800706be mean?

It is the same code at an earlier step: the Windows Update client lost contact with a component while the update was downloading or being prepared. The cause is usually a stuck update service or a damaged update cache, not your internet connection. Restart, select Retry, and if it fails again, reset the update components with Fix 5. If the download still fails, get the update from the Update Catalog with Fix 6.

Does 0x800706BE appear on Windows 10?

Yes. The code is part of Windows itself, so Windows 10 shows it in Windows Update and in programs the same way as Windows 11. One Microsoft Q&A report is about a Windows 10 22H2 cumulative update that failed with 0x800706be. Windows 10 left support on 14 October 2025, so many PCs now see it when they move to Windows 11. In that case Fix 4, setup.exe inside Windows, is the usual route.

Why does 0x800706BE appear when upgrading to 26H2?

Microsoft has not listed 0x800706BE as a known issue for 26H2. The upgrade runs many services in turn, and the code appears when one of them stops in the middle. Start with a restart and Retry. If the feature update keeps failing in Windows Update, use the Installation Assistant or mount the 26H2 ISO and run setup.exe (Fix 4). If that fails too, read setuperr.log in C:\$WINDOWS.~BT\Sources\Panther for the component named before the code.

Is 0x800706BE caused by a virus?

Not as a rule. The code says a call between two parts of Windows failed, and that happens most often for ordinary reasons: a stuck service, damaged files or the new Setup on an older PC. Malware can damage system files and cause it indirectly, so a full scan with Microsoft Defender is a fair check when other strange things happen. Fix 8 links the scan. Do not turn off your antivirus to get past the error.

Can a faulty CPU or RAM cause error 0x800706BE?

It can. A process that crashes because of a hardware fault ends the call, and Windows reports the RPC failure. On Microsoft Q&A, a user traced repeated 0x800706be update failures to an unstable Intel Core 13th generation CPU, and updates worked after the CPU was replaced. We could not confirm this in a vendor article. If you also see crashes and installers that vanish, remove any overclock, update the BIOS and test the memory (Fix 9).

Is 0x800706BE the same as 0x800706BA?

No. Both are RPC errors, but they mean different things. 0x800706BE, error 1726, says the call started and then failed. 0x800706BA, error 1722, says "The RPC server is unavailable": the other side never answered, often because a service is not running. The first steps overlap, since restarting the services helps both. For 0x800706BA, check first that the needed service starts at all in services.msc.