Fix it now
Microsoft’s reading of 0x800F0923 is that a driver or other software on the machine is not compatible with the upgrade. Setup writes the name into its own logs, so get SetupDiag to read them for you rather than working through them by hand.
SetupDiag.exe /Output:C:\setupdiag.log
pnputil /enum-drivers
dism /online /get-drivers /format:table
- Read the SetupDiag output. A DriverMigrationFailure, UnknownDriverMigrationFailure, DriverPackageMissingFileFailure or HardblockDeviceOrDriver result names the package for you.
- If SetupDiag matches no rule, open
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log. It holds errors only, so it is short, then find the same timestamp in setupact.log for the surrounding lines. - Install the manufacturer’s current driver for the package you have identified, or remove it:
pnputil /delete-driver oemNN.inf /uninstall. - Re-run the upgrade from mounted media with
setup.exe /auto upgrade /dynamicupdate nodrivers, so Setup takes its cumulative update but does not fetch the same driver back mid-run.
Match packages on the original name and provider from pnputil /enum-drivers, never on the oemNN number. That number is assigned locally and means nothing on another machine.
If the upgrade completes, you are done. If it fails again in the same place, the next section covers what migration is doing to your drivers and which of the failures you have.
Why it happens
An in-place upgrade does not reinstall your drivers. It inventories the driver store, works out which packages the new build already supplies a better version of, and migrates the rest as they are, on the assumption they will still load. That assumption fails when a package was built against interfaces the new kernel no longer exposes, when it is signed in a way current rules reject, or when it is simply too old for the servicing stack to process. Microsoft’s published reading of 0x800F0923 is exactly that: a driver or other software on the PC is not compatible with the upgrade.
The three codes that travel with it are not variations on the same idea, and treating them as one is how an afternoon disappears. 0x800F020B is SPAPI_E_NO_SUCH_DEVINST, which Microsoft defines as the device instance not existing in the hardware tree: the package refers to hardware the machine cannot see. 0xC1900206 is MOSETUP_E_COMPAT_DEVICEREQ_BLOCK, the system failing the device scan rather than the application scan. 0x80070103 is the odd one out and is dealt with below.
0x80070103 resolves to Win32 error 259, which Microsoft’s system error code list defines as no more data being available. The common reading, that Windows Update is offering a driver that is not a better match than the one already installed, is not something Microsoft publishes, so treat the code as informational and do not let it pull you away from the package the setup logs actually named.
An obsolete third-party driver has no version for the new build
You have this one if SetupDiag reports a driver migration failure, or the setup logs name a package from a hardware vendor whose date is years older than the rest of the driver store.
- Find the package with
pnputil /enum-driversand match on the original name and provider. - Check the manufacturer’s support page for a version that states support for the build you are moving to.
- If one exists, install it and retry. If none exists, remove the package:
pnputil /delete-driver oemNN.inf /uninstall. - Restart, confirm the device still works or fails cleanly, then run the upgrade.
Removing a driver for hardware you still use leaves that device on a generic Microsoft driver, or not working at all, until the vendor publishes something supported. Establish that before you remove it, not after.
Dynamic Update fetches the bad driver back during setup
You have this one if You removed the package, confirmed it had gone, and the identical failure returned on the next attempt.
- Run the upgrade from mounted media with
setup.exe /auto upgrade /dynamicupdate nodrivers, which keeps the cumulative update but skips driver acquisition. - If that is not enough,
/dynamicupdate disableturns the whole mechanism off. - As a last resort,
/migratedrivers nonehas Setup use only the drivers the new build carries. Download the vendor’s network and storage drivers first.
The package points at hardware that is not there
You have this one if 0x800F020B, and the package relates to a printer, scanner, dock or other peripheral that is switched off, unplugged or long retired.
- Connect and power on the device if it is still in use, then retry.
- If it has been retired, remove its driver package with pnputil and clear the phantom device from Device Manager with Show hidden devices enabled.
- Retry the upgrade.
The device scan blocks rather than the application scan
You have this one if 0xC1900206, with nothing flagged among the installed applications.
- Treat it as a hardware and driver problem: MOSETUP_E_COMPAT_DEVICEREQ_BLOCK is the system failing the device scan.
- Update chipset, storage and graphics drivers from the manufacturer’s page for the exact model.
- Disconnect everything the machine does not need to run, and retry.
The component store cannot process the package at all
You have this one if CBS.log carries the failure rather than the setup logs, and DISM reports corruption in the component store.
- Run
DISM /Online /Cleanup-Image /ScanHealth, then/RestoreHealth, supplying media with/Source:WIM:D:\sources\install.wim:1 /LimitAccessif the machine cannot reach an update service. - Follow with
sfc /scannowand confirm it completes cleanly. - Retry the upgrade once both report success.
Full reference
Where to look, in order
| Where | What you get |
|---|---|
| SetupDiag | Microsoft’s own rules applied to your logs, with a named rule where one matches |
C:\$WINDOWS.~BT\Sources\Panther\setuperr.log |
Errors only, from the attempt in progress |
C:\Windows\Panther\setupact.log |
The full narrative, copied here once the machine is back |
C:\Windows\Logs\CBS\CBS.log |
Servicing detail when the failure came from the component store side |
pnputil /enum-drivers |
Every third-party package in the driver store, with published name, provider and date |
dism /online /get-drivers /format:table |
The same inventory, easier to scan |
SetupDiag rules worth recognising
| Rule | What it means |
|---|---|
| DriverMigrationFailure | A fatal failure migrating drivers |
| UnknownDriverMigrationFailure | A bad driver package is preventing the upgrade |
| DriverPackageMissingFileFailure | A file the driver package needs is missing |
| HardblockDeviceOrDriver | An incompatible device driver |
| UserProvidedDriverInjectionFailure | A driver you supplied to Setup failed |
| UnsignedDriverBootFailure | An unsigned driver caused a boot failure |
The Dynamic Update switch has more than two settings
| Value | Effect |
|---|---|
Enable |
Dynamic Update runs normally: updates and drivers are fetched during setup |
Disable |
No Dynamic Update operations at all |
NoDrivers |
Everything except driver acquisition, which is usually what you want here |
NoLCU |
Everything except the latest cumulative update |
NoDriversNoLCU |
Neither drivers nor the cumulative update |
NoDrivers is the setting most of these cases actually need. Disabling Dynamic Update outright also loses the latest cumulative update, which frequently contains the setup fixes you would rather have during an upgrade that is already failing.
Removing a package without breaking the device
- List the store:
pnputil /enum-drivers, and note the published name, original name, provider and date. - Match the failing package on the original name and provider. The oemNN.inf number is local to the machine.
- Remove it with
pnputil /delete-driver oemNN.inf /uninstall, which also uninstalls it from any device using it. /forcewill delete a package that is still in use by a device, and/rebootrestarts if the operation needs it. Both are documented options, and both deserve thought before use.- Restart and confirm in Device Manager that the affected device is either running on an inbox driver or cleanly disabled.
When the blocking device is one you cannot give up
If the package belongs to hardware the business depends on and the vendor publishes nothing for the target build, the upgrade waits or the hardware is replaced. Removing a driver that a critical device needs in order to force the upgrade through just moves the outage to the far side of the reboot. That is a procurement conversation, not a technical one, and it is better had before the maintenance window than during it.
0x80070103 is worth ignoring while you work. It resolves to a documented Win32 error meaning no more data is available, it is not what stopped your upgrade, and chasing it costs time the feature update failure does not give you.
When a licence is the actual fix
Nothing in this article is solved by buying a licence: a blocking driver is a driver problem, and the Windows entitlement the machine already holds covers the upgrade. The one place licensing enters is at the end, when the driver stack is old enough that a clean installation is genuinely the faster route, because that rebuild has to be entitled to the edition you install. Arco supplies Windows 11 Pro upgrade licences and will check the device’s current entitlement first, which on a machine bought with Pro preinstalled usually shows that nothing needs buying.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x800F0923 |
Microsoft Support: this might indicate that a driver or other software on the PC is not compatible with the upgrade | Microsoft Support |
0x800F020B |
SPAPI_E_NO_SUCH_DEVINST: the device instance does not exist in the hardware tree, so the package refers to hardware that is not present | Microsoft Learn |
0x80070103 |
Win32 error 259, no more data is available. The common reading, that a driver on offer is not a better match than the installed one, is not published by Microsoft | not published by the vendor |
0xC1900206 |
MOSETUP_E_COMPAT_DEVICEREQ_BLOCK: the system does not pass the device scan to install the update | Microsoft Learn |
Confirm the fix worked
pnputil /enum-driversno longer lists the package you removed.- SetupDiag reports no driver rule against the logs from the successful run.
- The upgrade completes and
winvershows the build you intended. - Device Manager shows no device in an error state after the upgrade.
- The device whose driver you replaced is working on the version the vendor publishes for the new build.
Questions people ask about this
How do I know which oemNN.inf is the right one?
Run pnputil /enum-drivers and match on the original name and the provider, not the oem number. The numbering is assigned locally, so the same package is a different number on the next machine, and removing the wrong one leaves a device without a driver.
Is /migratedrivers none risky?
It is a supported option that takes All or None, but the machine comes up with only the drivers the new build carries. Download the vendor’s network and storage drivers before you use it, or you may be left on a machine that cannot reach the internet to fetch them.
Do I need to buy anything?
No. This is a driver compatibility problem and the existing Windows licence covers the upgrade. The only cost that ever attaches is hardware, when the device whose driver is blocking has genuinely reached the end of vendor support.
Why does the same driver work on an identical machine?
Identical models rarely have identical driver sets. A different dock, a different storage firmware revision, one extra vendor utility or a driver that came down through Dynamic Update on one machine and not the other is enough to change the outcome.
Should I use a driver updater utility to sort this out?
No. Take drivers from the hardware manufacturer’s support page for the exact model. Third-party updater tools install packages that were never tested on that machine, which is a good way to turn one blocking driver into several.
