Windows 11 upgrade error 0x8007007f: how to fix it

Published Sources checked By helps.wiki editorial team

0x8007007f means "the specified procedure could not be found": Windows Setup needed a DLL or function and could not load it. Microsoft has no dedicated fix, so start with the simple steps (run the installer as administrator, repair system files, remove third-party security software) and move to the ISO or a clean install if they fail.

Applies to:Windows 1121H2, 24H2Windows 10upgrading to Windows 11
On this page

What it means

The code 0x8007007f is the standard Windows error ERROR_PROC_NOT_FOUND, described by Microsoft as "The specified procedure could not be found." During an upgrade it means Setup, or one of the helper components it runs, tried to load a DLL or call a function and could not find it. It tells you what failed, not why.

Because the code is so generic, Microsoft has not published a page with one official fix for it. The steps below combine Microsoft's general upgrade troubleshooting with advice from a Microsoft Q&A thread and a news report, so treat them as commonly useful rather than guaranteed. Don't confuse it with 0x8007007e, which is a different code ("module could not be found").

Sometimes the code appears as a pair, such as 0x8007007F-0x2000A. The first half is the result and the second half tells you which phase and operation Setup was in when it failed.

Symptoms and causes

You are likely dealing with this problem if:

  • The Windows 11 Installation Assistant or Windows Update stops with error 0x8007007f.
  • The upgrade runs for a long time (one reported case reached about 88%) and then rolls back to Windows 10.
  • setuperr.log contains lines such as a failed LoadLibraryExW call for a migration plugin DLL, or a failed sysprep specialize step with hr:0x8007007f.
  • Occasionally the failed attempt ends in a blue screen with a different code, such as 0xC1900101-0x40017.

The usual causes, most common first:

Installer without administrator rights
A 2021 Windows Latest report, written around the Windows 11 launch, names running the Installation Assistant without elevation as a trigger. Whether it still applies on current builds is unconfirmed.
Third-party security software or old drivers
In a Microsoft Q&A case, the moderator had the user remove Avast using its removal tool, and Malwarebytes showed up as a leftover service. Older drivers, including Norton ones, were also part of the clean-up.
Damaged system files or a failing migration plugin
Setup logs in that case showed WSManMigrationPlugin.dll and RasMigPlugin.dll failing to load during the offline specialize phase.
Corrupt Store app (AppX) repository
The same thread's moderator concluded that the AppX Deployment Service crashed while Store app packages were being migrated, and suggested resetting the apps repository.
Low disk space or outdated drivers
Some secondary sources mention these. Microsoft's upgrade guidance also advises keeping enough free space and updating drivers and firmware, but nothing read here proves they cause this specific code.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Run the Installation Assistant as administrator

Easy

The Windows Latest report linked missing elevation to this code. It is a 2021 report, so it may not apply to your build, but it costs nothing to try.

  1. Close the Installation Assistant if it is open, then restart the PC.
  2. Right-click the Installation Assistant file and choose Run as administrator.
  3. Accept the UAC prompt and run the upgrade again.

2.Apply Microsoft's general upgrade quick fixes

Easy

Microsoft's upgrade guidance (written for upgrades started from Windows 10) covers the usual blockers: devices, disk errors, damaged system files and pending updates.

  1. Unplug nonessential USB and external devices, and undock a laptop.
  2. Make sure the system drive has plenty of free space.
  3. Open Settings > Windows Update, install every pending update, and restart.
  4. Run the Windows Update troubleshooter from Settings > System > Troubleshoot > Other troubleshooters.
  5. Open Command Prompt as administrator and run the system file check, then the DISM repair.
    Command Promptrun as administrator
    sfc /scannow
DISM.exe /Online /Cleanup-image /Restorehealth
  6. Still in the elevated Command Prompt, schedule a disk check. Type Y when asked, then restart so it runs.
    Command Promptrun as administrator
    chkdsk /F
  7. Update firmware and drivers from your PC maker's site or Windows Update, then retry the upgrade. If Setup offers Get important updates, accept it.

3.Remove third-party security software and extra programs

ModerateChanges settings

Conflicting security tools were removed in the Q&A case. Microsoft's guidance also suggests removing non-Microsoft antivirus and nonessential software before upgrading.

Before you start: Make sure you have your licence or account details for the security product before removing it, and reinstall it after the upgrade. Windows Security protects the PC in the meantime.

  1. Remove the third-party antivirus using the vendor's own removal tool, which cleans up more than a normal uninstall.
  2. Uninstall other nonessential programs from Settings > Apps > Installed apps.
  3. Restart and run the upgrade again.
  4. After a successful upgrade, reinstall your security software.

4.Upgrade from the Windows 11 ISO instead

Moderate

Running Setup directly from the official ISO avoids the Installation Assistant and is the next step suggested when the Assistant fails.

  1. Download the Windows 11 ISO from Microsoft's official download page.
  2. Right-click the ISO file and choose Mount.
  3. Open the new drive in File Explorer and run setup.exe from inside Windows (not by booting from it).
  4. Follow Setup with its default choices. If it fails again, go to the next solutions rather than changing what Setup keeps.

5.Find the failing component with SetupDiag

Advanced

SetupDiag is Microsoft's tool for reading Setup logs. It reports the likely cause but does not repair anything.

  1. Download Microsoft's SetupDiag tool from Microsoft and run it after a failed upgrade.
  2. Open the SetupDiagResults.log file it creates and read the reported cause.
  3. For manual reading, open setuperr.log and setupact.log. Microsoft lists them in $Windows.~BT\Sources\Panther for the main upgrade phase and $Windows.~BT\Sources\Rollback for rollbacks. After an upgrade that completed they are in Windows\Panther. These folders are hidden by default, so enable hidden items in File Explorer.
  4. Search for 0x8007007f in those logs. A DLL name next to it points to the component that failed, which helps when asking for support.

6.Back up and do a clean install

AdvancedBack up first

If every upgrade path fails, a clean install avoids whatever is damaged in the current system. In the Q&A case the user's clean install succeeded.

Before you start: Choosing Keep personal files only in Setup keeps your personal data but removes all your apps and settings, and Keep nothing erases everything. Back up your files to an external drive or cloud storage first and make sure you have your licences and sign-ins. Resetting the Store app repository, also suggested in that thread, removes all Store apps.

  1. Copy documents, photos and other important data to an external drive or cloud storage.
  2. Run Setup from the Windows 11 ISO. When it asks what to keep, choose Keep personal files only (apps and settings are removed) or the option that keeps nothing, or boot from official install media and perform a clean install.
  3. Reinstall your apps and restore your files afterwards.

Check that it worked

  • The upgrade completes and the PC boots into Windows 11 without rolling back.
  • Open Settings > System > About and confirm the Windows 11 edition and version.
  • Open Settings > Windows Update and confirm it shows no failed update with 0x8007007f.

If it still fails

  • Run SetupDiag and note the exact DLL or phase named in the logs, plus the full code pair if one is shown (for example 0x8007007F-0x2000A).
  • Post those details on Microsoft Q&A or contact Microsoft Support rather than following machine-specific cleanup scripts from other people's threads. One reported registry restore attempt caused a boot loop.
  • If the PC shows a different code such as 0xC1900101, treat that as a separate problem and search for that code.

Questions

Is 0x8007007f the same as 0x8007007e?

No. 0x8007007f means a procedure (function) could not be found, while 0x8007007e means a module (DLL) could not be found. They are neighbouring codes with different meanings.

What do the two halves of a code like 0x8007007F-0x2000A mean?

The first part is the result code and the second part is the extend code, which indicates the phase and operation Setup was in. In one reported case 0x2000A matched the Safe OS phase, running sysprep specialization offline.

Sources

  1. System Error Codes (0-499) (WinError.h)Official · Microsoft Learn
  2. Resolve Windows upgrade errorsOfficial · Microsoft Learn
  3. Windows 10 upgrade quick fixesOfficial · Microsoft Learn
  4. Log files and resolving upgrade errorsOfficial · Microsoft Learn
  5. Trouble upgrading to W11 from W10, error 0x8007007f (Q&A thread) · Microsoft Learn Q&A (community)
  6. Windows 11 is failing for some users with 0x8007007f · Windows Latest

Browse