Fix it now
These are two different failures wearing the same result code. 0x4000D and 0x3000D are MIGRATE_DATA operations – setup moving your data and settings. 0x2000C is APPLY_IMAGE in the WinPE phase, which happens earlier and has nothing to do with your data. Read the extend code before you decide what to fix.
SetupDiag.exe /Output:C:\SetupDiag\Results.log
- Suspend disk encryption before you retry:
manage-bde -protectors -disable C: -rebootcount 3. Make sure the recovery key is stored somewhere off the machine first. - Disconnect every peripheral except mouse, keyboard and display, and for 0x3000D update or uninstall the display driver – that is Microsoft’s published mitigation for that one.
- For 0x8007001F – 0x3000D, go to the user profiles rather than the disk. Check
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileListfor entries pointing at folders that no longer exist, and look for invalid files under\Users, including anything left inWindows.old\Users. - Uninstall third-party antivirus, backup agents and file sync clients rather than disabling them, and restart.
- For 0x2000C, Microsoft’s published mitigations are to update drivers, accept ‘Download and install updates (recommended)’, and run a disk check to repair the file system – it is an image apply failure, not a migration one.
- Retry from mounted installation media so you can read
%windir%\Panther\setuperr.logdirectly.
Removing profiles or ProfileList entries destroys data that is not backed up elsewhere. Copy anything you need off the machine first, and remove profiles through System Properties, Advanced, User Profiles rather than by deleting folders.
If the upgrade completes, stop here. If not, the next section separates the migration failures from the image apply failure, because they are fixed in different places.
Why it happens
An in-place upgrade lays down a new operating system image and then moves your accounts, settings and files into it. Those are separate operations in separate phases, and the extend code tells you which one gave up. Getting that wrong sends you to the disk when the problem is a profile, which is the single most common way time is wasted on this code.
0x4000D is phase 4, OOBE_BOOT, operation 0x0D, MIGRATE_DATA. Microsoft’s published cause is a rollback due to a driver configuration issue, with the install failing during the second boot phase attempting MIGRATE_DATA, and the published mitigation is to read the rollback log in $Windows.~BT\Sources\Rollback for a setupmem.dmp and a stop code. 0x3000D is the same operation in phase 3, FIRST_BOOT, and Microsoft attributes it to a display driver problem.
0x2000C is different in kind. It decodes as SAFE_OS / APPLY_IMAGE, and Microsoft publishes two rows for it: an unspecified error during Wim apply in the WinPE phase caused by out-of-date drivers, and an unspecified error in the SafeOS phase during WIM apply that can be caused by an outdated driver or disk corruption. Neither mentions data migration. If your extend code is 0x2000C, setup had not reached your data yet.
The result codes paired with 0x3000D matter as much as the extend code. 0x8007001F – 0x3000D has a published mitigation that points at user profiles: corrupt entries under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList or invalid files in the \Users directory, and Microsoft notes that an incomplete previous upgrade can leave invalid profiles in Windows.old\Users. 0x80070004 – 0x3000D is published more modestly as a data migration problem in the first boot phase with multiple possible causes, resolved by reading the logs.
0x800707E7 – 0x3000D is not in Microsoft’s tables at all. The extend half decodes as FIRST_BOOT / MIGRATE_DATA; the result half is Win32 error 2023, whose published text is about a device profile intended for a different type of device, which is not a user profile and offers no upgrade guidance. Treat the pairing as a first-boot migration failure and read the logs, rather than as a documented condition.
A user profile cannot be migrated
You have this one if 0x8007001F – 0x3000D, or a migration failure that names a profile path in the setup log.
- Sign in as a local administrator and inspect
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileListfor entries whose folders no longer exist or that end in.bak. - Back up anything you need from a broken profile before touching it.
- Remove unused profiles through System Properties, Advanced, User Profiles rather than by deleting folders.
- Check
\UsersandWindows.old\Usersfor invalid files and remove them; the setup logs name the specific files and profiles causing the failure.
The volume is encrypted
You have this one if 0x4000D or 0x3000D on a machine with BitLocker or a third-party encryption product enabled.
- Suspend BitLocker with
manage-bde -protectors -disable C: -rebootcount 3; protection resumes automatically after the restarts. - Confirm the state with
manage-bde -status C:before starting the upgrade. - For third-party encryption, follow the vendor’s documented procedure for a Windows feature update. Some require full decryption, which takes time you have to plan for.
Microsoft names non-Microsoft disk encryption software directly as a cause of SafeOS boot failures on the neighbouring extend code, so this is not a precaution invented for the article.
A filter driver is holding files during migration
You have this one if The same stage fails every time on a machine running antivirus, backup or file sync agents.
- Uninstall the products rather than disabling them, and restart before retrying.
- Pause and sign out of file sync clients, and let any pending sync finish first.
- Disable backup schedules for the duration of the upgrade window.
- Confirm with
fltmc filtersthat the driver is gone rather than merely stopped.
The image will not apply in the WinPE phase
You have this one if 0x2000C, before setup has reached your data at all.
- Update drivers and accept ‘Download and install updates (recommended)’ at the start of setup – both are Microsoft’s published mitigations for this extend code.
- Run a file system check. Microsoft’s second published row for 0x2000C names disk corruption and a check disk repair as the remedy;
chkdsk C: /scanis the read-only online scan to start with. - Disconnect peripherals other than mouse, keyboard and display and retry.
A crash rather than a check
You have this one if 0x4000D, and the rollback folder contains a memory dump.
- Look in
$Windows.~BT\Sources\Rollbackforsetupmem.dmpand the event logs; Microsoft’s published mitigation for this pairing is to determine the stop code from the rollback log. - If a driver is named in the bug check, disable it or get an updated build from the manufacturer.
- Check for firmware updates, and disable BIOS memory options such as caching or shadowing if the platform offers them.
- Make sure there is enough free disk space before another attempt.
Full reference
Reading the pairing rather than the code
| Code | Decodes as | What Microsoft publishes |
|---|---|---|
0xC1900101 - 0x4000D |
OOBE_BOOT / MIGRATE_DATA | Rollback from a driver configuration issue; read the rollback log for a dump and stop code |
0xC1900101 - 0x3000D |
FIRST_BOOT / MIGRATE_DATA | Can occur because of a display driver problem |
0xC1900101 - 0x2000C |
SAFE_OS / APPLY_IMAGE | Unspecified error during Wim apply, out-of-date drivers or disk corruption |
0x80070004 - 0x3000D |
FIRST_BOOT / MIGRATE_DATA | A data migration problem with multiple possible causes |
0x8007001F - 0x3000D |
FIRST_BOOT / MIGRATE_DATA | Corrupt ProfileList entries or invalid files under \Users |
0x800707E7 - 0x3000D |
FIRST_BOOT / MIGRATE_DATA | Not published as a pairing |
What migration has to do
Migration copies account definitions, profile folders, application data and a large amount of registry state from the old installation into the new one. It has to open every file it moves, resolve every profile it finds, and complete before the machine reaches the desktop. Anything that holds a file open, hides one behind an encryption layer, or leaves a profile pointing at a folder that does not exist stops the operation. That is why the fixes here are removal and repair rather than configuration.
Working with profiles safely
- Take a copy of anything you care about from the profile folders before you start.
- Sign in as a local administrator, not as the account whose profile is suspect.
- Read
ProfileListand match each SID’sProfileImagePathagainst what is actually on disk. - Remove unwanted profiles through System Properties, Advanced, Settings under User Profiles, which removes both the folder and the registry entry.
- Delete leftover profiles under
Windows.old\Usersonly after confirming nobody needs the data in them. - Retry the upgrade with only the profiles you actually need present.
Checking the disk without making it worse
chkdsk C: /scan runs an online scan on an NTFS volume and does not repair. chkdsk C: /f requires the volume to be locked, so on the system drive it schedules itself for the next restart, and it repairs. Run the read-only scan first and read the result; a repair pass on a drive that is already producing I/O errors can make recovery harder rather than easier.
When every cause has been ruled out
- Run the upgrade from mounted media rather than Windows Update so the logs are readable while it runs and you can pass setup options.
- Use
/MigrateDrivers Noneso the new installation does not inherit the old driver set. - Check free space on the system volume; migration needs working room well beyond the size of the download.
- Disconnect external drives so setup does not choose one as working space and then lose it.
- If a specific application’s data directory is named repeatedly in the logs, uninstall that application, upgrade, and reinstall it.
When a licence is the actual fix
There is no purchase that fixes a migration failure. On a machine that is already activated the in-place upgrade costs nothing and the digital licence survives it. Two things are worth separating from the fault itself. If the machine runs Windows Home and you want Windows 11 Pro – for BitLocker management, domain join or policy-based control – that is a Windows 11 Pro upgrade licence, and it is a decision about capability rather than about this rollback; the same profile or filter driver problem will stop the upgrade on either edition. The other is the case where you decide a clean installation is faster than another migration attempt. That is a legitimate call once you have exhausted the causes above, and it needs no new licence on a device with a valid digital entitlement for the edition you are installing – only if you change edition does a licence enter it. Back up first, because a clean installation does not migrate the profiles you were trying to save.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0xC1900101 - 0x4000D |
A rollback from a driver configuration issue; the install failed during the second boot phase attempting MIGRATE_DATA | Microsoft Learn |
0xC1900101 - 0x3000D |
Failed during the FIRST_BOOT phase attempting MIGRATE_DATA, which can occur because of a display driver problem | Microsoft Learn |
0xC1900101 - 0x2000C |
An unspecified error during Wim apply in the WinPE phase, from out-of-date drivers or disk corruption; SAFE_OS / APPLY_IMAGE, not data migration | Microsoft Learn |
0x80070004 - 0x3000D |
A problem with data migration during the first boot phase, with multiple possible causes; the logs decide which | Microsoft Learn |
0x800707E7 - 0x3000D |
Not published as a pairing; the extend half is FIRST_BOOT / MIGRATE_DATA and the result half is a Win32 device profile mismatch, which carries no upgrade guidance | not published by the vendor |
0x8007001F - 0x3000D |
A FIRST_BOOT MIGRATE_DATA failure that Microsoft attributes to corrupt ProfileList entries or invalid files under \Users, including leftovers in Windows.old\Users | Microsoft Learn |
Confirm the fix worked
winverreports the build you were upgrading to.- Every user account signs in and finds its profile, desktop and documents intact.
manage-bde -status C:shows protection back on if you suspended it.- The
ProfileListkey contains one entry per account that actually exists, with no orphans left behind. - A second restart completes without a rollback, which is where an OOBE_BOOT migration failure would reappear.
Questions people ask about this
Is my data at risk during these failures?
The rollback itself is designed not to lose anything, and it usually does not. The risk in this article comes from the repair steps rather than the failure: deleting profiles or ProfileList entries destroys data. Back up before touching either.
My extend code is 0x2000C. Should I be looking at profiles?
No. 0x2000C decodes as SAFE_OS / APPLY_IMAGE and Microsoft documents it as an error during Wim apply in the WinPE phase. Setup had not reached your data. Look at drivers and at the file system.
Do I have to pay for anything to fix this?
No. Every cause here is removal, repair or a driver update, and an activated machine keeps its licence through the upgrade.
Should I just do a clean installation instead?
It is a reasonable call after you have worked through the causes, and it avoids migration entirely. It also discards the profiles you were trying to preserve, so back up everything first and be sure you have what applications need.
What about 0x800707E7 – 0x3000D?
It is not in Microsoft’s upgrade tables. The extend code says first boot data migration; the Win32 half is about a device profile intended for a different device type, which is not the same thing as a user profile. Diagnose it from the logs as a migration failure and ignore anyone who offers a confident definition.
