[Fix] 22H2 Windows 11 update fails with error 0x8007001F-0x3000D

Error 0x8007001F - 0x3000D means Windows Setup restarted into the new Windows 11, failed while moving your accounts and files across, and rolled back. Microsoft ties it to invalid user profiles: leftover registry entries, broken folders in C:\Users or old profiles in Windows.old. Start by reading the setup log, which names the profile or file.

Facts checked on 16 October 2026. Steps written for Checked against Microsoft's upgrade documentation for feature upgrades to Windows 11 25H2 and 26H2, started from Windows 10 22H2 or an older Windows 11 version such as 22H2.

What error 0x8007001F - 0x3000D means

Windows Setup reports a failed feature update with two codes. The first, the result code, says what failed. The second, the extend code, says in which phase and during which operation. When the 22H2 update, or any later Windows 11 version, stops with this pair, the rollback screen reads:

Why the Windows 11 update fails with 0x8007001F - 0x3000D

Setup migrates every profile it finds, not only the one you use. If one of them is broken, the whole migration stops and Setup restores your old Windows. Microsoft names the first three causes below for this exact code. The rest are less common and are ranked by how close they come to a data migration failure.

How to fix Windows 11 update error 0x8007001F - 0x3000D

Fix 1 reads which profile or file stopped the migration. Fix 2 to Fix 4 remove the invalid profiles Microsoft names for this code, from the safest place to the most direct. Fix 5 to Fix 7 cover the less common causes. Fix 8 installs Windows without migrating any data, for when nothing else works.

Fix 1. Find the profile or file that stopped the migration in setuperr.log

10 minutesNo riskEveryone, right after the rollback, before the next attempt overwrites the logs.

Microsoft says the specific files and profiles that cause 0x8007001F - 0x3000D are recorded in the Windows Setup log files. Reading them tells you which account or folder to fix instead of trying everything.

1. Press Win + R, type C:\$Windows.~BT\Sources\Rollback and press Enter. Select Continue if Windows asks for permission. If the folder is missing, use C:\$Windows.~BT\Sources\Panther instead.
2. Copy setuperr.log and setupact.log to your Desktop, so a cleanup or the next attempt does not remove them.
3. Open the copy of setuperr.log in Notepad and press Ctrl + End to jump to the last line.
4. Press Ctrl + F, type 8007001F, select Up and then Find Next to reach the last time the code appears.
5. Read the lines just above it. Lines marked MIG come from the migration engine. Look for a profile path under C:\Users, a SID that starts with S-1-5-21, or a file path.
6. Search the same file for Abandoning apply due to error for object. The object named on that line is often the item that failed.
7. Note the time stamp of those lines and look at setupact.log around the same time for more detail.

Fix 2. Delete accounts nobody uses and profiles listed as Account Unknown

10 minutesRead the warningThe PC was shared, came from a previous owner or a workplace, or Fix 1 named a profile that is not yours.

Microsoft says to make sure deleted accounts are not still present on the PC. The User Profiles dialog removes the registry entry and the folder together, which is the cleanest way to take a dead profile out of the migration.

1. Sign in with an administrator account that you will keep.
2. Press Win + I. Open Accounts > Other users in Windows 11, or Accounts > Family & other users in Windows 10.
3. For each account nobody uses any more, select it, then Remove and Delete account and data.
4. Press Win + R, type sysdm.cpl and press Enter.
5. On the Advanced tab, select Settings in the User Profiles area.
6. Select every profile shown as Account Unknown, select Delete and confirm with Yes.
7. Restart the PC and start the Windows 11 update again.

Fix 3. Remove leftover profile keys from ProfileList in the registry

15 minutesRead the warningFix 1 named a SID, or User Profiles looks clean but Microsoft's cause still fits: an account was deleted by hand or by a tool.

Microsoft names corrupt entries under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList as a cause of this exact code. Setup reads every key there and tries to migrate the profile it points to, so a key for a missing folder breaks the migration.

1. Press Win + R, type regedit, press Enter and select Yes.
2. Paste this path into the address bar at the top of Registry Editor and press Enter:

   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

   

3. Select each subkey whose name starts with S-1-5-21 and read its ProfileImagePath value on the right.
4. Compare that path with the folders in C:\Users and with the accounts in Settings. A key whose folder is gone, or whose account was deleted, is a leftover.
5. Leave S-1-5-18, S-1-5-19 and S-1-5-20 alone: they belong to Windows itself.
6. Right-click a leftover key, select Export and save the file. Then right-click it again, select Delete and confirm with Yes.
7. Close Registry Editor, restart the PC and start the update again.

Fix 4. Clear orphaned folders in C:\Users and old profiles in Windows.old

15 minutesRead the warningFix 1 named a folder or a file, C:\Users holds folders for people without an account, or a C:\Windows.old folder exists.

Microsoft names invalid files in the \Users directory as a cause, and adds that an upgrade which did not complete can leave invalid profiles in Windows.old\Users. Removing them leaves Setup only valid profiles to migrate.

1. Open File Explorer and go to C:\Users.
2. Compare the folders with your accounts. Leave Public, your own folder and every folder of an account still in use.
3. For a folder with no account, copy anything worth keeping to another drive, then delete the folder. Select Continue if Windows asks for permission.
4. If Fix 1 named one file, move it out of the user folder to another drive instead of deleting it.
5. If C:\Windows.old exists, press Win + I and open System > Storage > Temporary files. The path is the same in Windows 10.
6. Tick Previous Windows installation(s) and select Remove files.
7. Restart the PC and start the update again.

Do not delete Windows.old by hand in File Explorer: Windows protects parts of it, and a half-deleted copy is exactly the kind of invalid profile this error trips over. More ways to free space safely: Free up disk space and delete temporary files

Fix 5. Unplug extra devices and update the display driver

15 minutesLow riskThe log mentions a driver, or extra devices such as USB drives, docks, card readers or printers were connected during the update.

The text of 0x8007001F is about a device that is not functioning, and Microsoft documents the same FIRST_BOOT and MIGRATE_DATA step failing with a display driver. Removing devices and refreshing the display driver rules that out.

1. Unplug every device you do not need for the update: USB drives, external disks, docks, card readers, printers and game controllers. Keep the mouse, keyboard and display.
2. Update the display adapter driver, or reinstall it if it is already the newest one, as in the steps below.
3. Restart the PC and start the update with only the needed devices connected.

1. Open Device Manager. Right-click Start and select Device Manager.
2. Open the device's Driver tab. Expand the category (for example Display adapters), right-click the device, select Properties and open the Driver tab. Driver Date and Driver Version show what is installed now.
3. Update the driver. Select Update Driver and let Windows search automatically. To use a driver you downloaded from the device maker, select Browse my computer for drivers instead and point to the unpacked folder.
4. Or roll back the driver. If the problem started after a driver update, select Roll Back Driver, choose a reason and select Yes. The button is greyed out when Windows has no earlier driver to return to.
5. Or reinstall the driver. Select Uninstall Device. Tick Attempt to remove the driver for this device only if you want Windows to delete the driver package too, then select Uninstall.
6. Restart. Restart the PC. Windows detects the device again and installs a driver for it.

These steps were written for Windows 11 24H2 and later. The full page with the other versions and what each result means: Update, roll back or reinstall a driver

Fix 6. Reset Windows Update and start a fresh download with the Installation Assistant

20 minutes, plus the upgradeLow riskTwo or more attempts have failed, the update comes through Windows Update, or drive C is nearly full.

Each rollback leaves its work files on drive C. A clean Windows Update cache and a new copy from the Installation Assistant mean the next try does not reuse files written by the failed one.

Copy the setup logs out first, as in Fix 1. Then reset the Windows Update components: Reset Windows Update components. After that:

1. Open Microsoft's Download Windows 11 page and select Download Now under Windows 11 Installation Assistant.
2. Run the downloaded file and select Yes when Windows asks for permission.
3. Select Accept and install and keep the PC on power while it downloads and checks the files.
4. Select Restart now when the Installation Assistant asks, and let the PC restart on its own.

   

Fix 7. Check the disk with CHKDSK and repair system files

30 minutes to 2 hoursLow riskCHKDSK or SFC has found errors before, the PC lost power during an attempt, or other updates fail too.

A profile file on a damaged part of the file system is an invalid file to Setup. CHKDSK repairs the file system under C:\Users, and SFC with DISM repairs the Windows files Setup builds on.

First check drive C for file system errors: Check a disk for errors (chkdsk). Then repair the system files:

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

Fix 8. Install Windows 11 from the ISO without migrating any data

1 to 2 hoursRead the warningFix 1 to Fix 7 did not help, and you are ready to install your apps again and restore your files from a backup.

This error happens while Setup migrates data. If you choose to keep nothing, there is no migration step, so an invalid profile can no longer stop the update. Running the ISO with the default options is still an upgrade and migrates everything.

1. On Microsoft's Download Windows 11 page, download the file under Download Windows 11 Disk Image (ISO) for x64 devices.

   

2. Right-click the ISO file and select Mount. Open the new drive in File Explorer and double-click setup.exe.
3. When Setup shows what it will keep, select Change what to keep.
4. Select Nothing, then Next and Install.
5. After Windows 11 starts, copy your files back from the backup and install your apps again from their makers.

If you would rather keep your files and only refresh Windows itself once the update is done, the keep options are explained here: Reinstall Windows without losing files

If error 0x8007001F - 0x3000D is still there

Each attempt writes new logs, so the answer is in the newest setuperr.log. Copy it out right after the rollback and compare it with the one from the attempt before.

• What to send to Microsoft support or a technician: the full code pair, your current Windows version and build, how you started the update, and the PC model.
• Attach setuperr.log and setupact.log from C:\$Windows.~BT\Sources\Rollback or C:\$Windows.~BT\Sources\Panther.
• List the accounts, keys and folders you already removed.

How to keep 0x8007001F - 0x3000D from coming back

Frequently asked questions

What does 0x8007001F - 0x3000D mean?

It means the Windows 11 update failed in its FIRST_BOOT phase while it migrated your data, and Setup rolled back to your old Windows. Microsoft's upgrade error codes split it in two. 0x8007001F is Win32 error 31, ERROR_GEN_FAILURE. 0x3000D is phase 3, SP_EXECUTION_FIRST_BOOT, with operation 0D, SP_EXECUTION_OP_MIGRATE_DATA. Microsoft's entry for this exact pair says it can be due to a problem with user profiles. The spellings 0x8007001F-0x3000D and 0x8007001F 0x3000D are the same error.

What does 0x3000D mean on its own?

0x3000D is only the extend code: it tells you when the update failed, not why. The first digit, 3, is the FIRST_BOOT phase, the first start of the new Windows during the upgrade. The last two digits, 0D, are the MIGRATE_DATA operation, when Setup moves accounts, files and settings. The why is in the first code. With 0x8007001F it points to user profiles. With 0xC1900101 Microsoft points to a display driver.

Is 0x8007001F a hardware failure?

Usually not in this case. The general text of error 31 says that a device attached to the system is not functioning, which sounds like hardware. But Microsoft's resolution for 8007001F - 0x3000D names invalid user profiles and invalid files in the Users directory, not a device. Start with Fix 1 to Fix 4. Check devices and drivers in Fix 5 only if the profiles are clean, and suspect hardware only if a clean install fails too.

What is 0x8007001F - 0x2000D?

It is the same result code in an earlier phase. The 2 in 0x2000D is the SAFE_OS phase, when the PC runs a small setup environment after the first restart, and 0D is again MIGRATE_DATA. The data migration failed before the new Windows started for the first time. Microsoft does not list this pair separately, but the migration step and the log files are the same, so Fix 1 to Fix 4 are the place to start. A related case is explained in our guide to 0x80070004 - 0x2000D.

What is 0x8007001F - 0x4000D?

It is the same failure one phase later. Windows shows it as "The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation." Microsoft's data migration advice is the same: analyze the log files to find the file or registry entry that blocks the migration. Invalid profiles, leftover ProfileList keys and old folders in Windows.old are the usual suspects, so the fixes on this page apply unchanged.

Is 0xC1900101 - 0x3000D the same error?

No, it fails at the same step for another reason. Microsoft lists 0xC1900101 - 0x3000D as a failure in the FIRST_BOOT phase during MIGRATE_DATA that can occur due to a problem with a display driver. Its mitigation is to disconnect all devices except the mouse, keyboard and display, and to update or uninstall the display driver. That is Fix 5 on this page. With 0x8007001F the first suspect is a user profile instead.

I still get this error on 22H2. Does this page apply to newer versions?

Yes. The reader's question was about the 22H2 update, but every later feature update, up to 25H2 and 26H2, uses the same Setup engine with the same phases, operations and log folders. The code means the same thing and the fixes are the same. Windows 11 22H2 Home and Pro no longer receive updates, so install the current version rather than looking for the 22H2 package.

Do I lose my files when the update rolls back?

No. The rollback returns the PC to the Windows you had before the update, with your files, apps and settings in place. Only the time spent is lost. Your files are at risk only in the fixes that warn you: deleting accounts and profiles in Fix 2 and Fix 4, deleting registry keys in Fix 3, and Fix 8, which installs Windows without keeping anything. Back up before those.

Is it safe to delete keys in ProfileList?

It is safe for a key that belongs to an account which no longer exists, after you back up the registry and export the key. It is not safe for your own key, for the keys of accounts still in use, or for the system keys S-1-5-18, S-1-5-19 and S-1-5-20. Deleting a live key can sign that person into a temporary profile. Check the ProfileImagePath value against C:\Users before you delete anything, as Fix 3 shows.

What is "Intel - System - 9/19/2017 12:00:00 AM - 11.7.0.1000"?

That is how Windows Update names an Intel system driver it offers, with the driver's date and version. It is a driver update, not part of error 0x8007001F - 0x3000D, and this page does not cover it. We could not confirm from Intel which device this exact version is for. If the driver installs and is offered again, or fails, check the device in Device Manager or get the current driver from your PC maker.