Fix it now
Setup failed during partition analysis and validation. Microsoft’s documented cause for this row is more than one system partition being present, most often a second disk that used to be a system drive, so the fix is to take the extra one out of view rather than to repair anything.
reagentc /info
diskpart
- Read the
reagentc /infooutput and note where the recovery environment currently lives. You will want to put it back the same way. - In diskpart, run
list diskand thenlist volume. Look for a second disk carrying an EFI system partition, or a second small partition that a previous installation left behind. - Physically disconnect the extra disk if you can. That is the cleanest test and it changes nothing on the disk itself.
- If you cannot disconnect it, take it offline for the duration:
select disk <n>thenoffline disk. - Where the machine is encrypted, suspend protection before the upgrade rather than decrypting:
manage-bde -protectors -disable C:. - Run the upgrade again, then bring the disk back online and confirm the recovery environment is still enabled.
Do not delete a partition to make this go away. Taking a disk offline is reversible; deleting the wrong small partition is not.
If the upgrade proceeds you can stop here. If not, the next section explains what setup is looking for and why an ambiguous answer stops it.
Why it happens
Before it does anything else, setup has to work out which partitions it is dealing with: which one the firmware boots from, which one holds Windows, and which one carries the recovery environment. That analysis has to produce exactly one answer for each. The extend code 0x20009 marks the failure as happening in that analysis and validation stage, which is why the machine stops so early and so cleanly.
The two main codes describe the two ways the answer can be wrong. 0x80073BC3 is Win32 15299, ERROR_SYSTEM_DEVICE_NOT_FOUND: the requested system device cannot be found. 0x80073B92 is Win32 15250, ERROR_AMBIGUOUS_SYSTEM_DEVICE: the requested system device cannot be identified because multiple indistinguishable devices match the identification criteria. Read together they say what Microsoft’s own mitigation says: setup either found nothing it could call the system partition, or it found more than one and will not guess.
That is the correction worth making, because these codes are widely blamed on a stale or undersized recovery partition. The recovery partition is a real cause of other upgrade failures, and it is worth checking, but it is not what these two codes are reporting. The third code in this family is 0x80070002, Win32 2, ERROR_FILE_NOT_FOUND, which Microsoft publishes as 0x80070002 - 0x20009. The seven-digit form that circulates is a transcription of the same row.
A second disk is presenting a system partition
You have this one if The machine has more than one disk and one of them was previously the boot drive, or came out of another computer.
- Run
list diskandlist volumein diskpart and identify every EFI or system partition on the machine. - Disconnect the extra disk, or take it offline with
select disk <n>thenoffline disk. - Run the upgrade, then bring the disk back online afterwards.
An external drive, a card reader with a card in it and a docked drive all count. Disconnect everything that is not needed for the upgrade.
A drive letter is assigned to a partition that should not have one
You have this one if The EFI system partition or the recovery partition appears in Explorer with a letter.
- In diskpart, select the volume and run
remove letter=<x>. - Confirm with
list volumethat the partition no longer holds a letter. - Retry the upgrade.
The recovery environment is in a state setup cannot work with
You have this one if reagentc /info reports the recovery environment as disabled, or pointing somewhere that no longer exists.
- Record the current configuration from
reagentc /infobefore changing it. - Disable and re-enable it:
reagentc /disable, thenreagentc /enable. Disabling is an online-only operation. - If
reagentc /enablecannot find an image it falls back toWinre.wimin\Windows\System32\Recovery, so make sure that file is present. - Retry the upgrade, then confirm the recovery environment is enabled again afterwards.
Encryption is holding the volume in a state setup will not touch
You have this one if The system drive is encrypted and the failure happens at the same point every time.
- Suspend protection rather than decrypting:
manage-bde -protectors -disable C:. - Run the upgrade to completion.
- Re-enable protection afterwards and confirm the drive reports as protected again.
Suspending is a temporary state that resumes on its own or on command. Decrypting a large volume takes hours and gains you nothing here.
Full reference
Reading the partition layout before you change it
| Command | What it shows |
|---|---|
list disk |
Every disk the machine can see, with size and partition style |
list volume |
Every volume, its letter, label, file system and type |
select disk <n> then detail disk |
What is on one disk specifically |
select volume <n> then remove letter=<x> |
Takes a drive letter off a partition that should not have one |
select disk <n> then offline disk |
Hides a disk from Windows without altering anything on it |
Nothing in that table needs clean, delete partition or format. If you find yourself typing one of them to fix an upgrade, stop: you are about to make a reversible problem permanent.
The recovery environment
| Command | What it does |
|---|---|
reagentc /info |
Reports whether the recovery environment is enabled and where it lives |
reagentc /disable |
Disables it and moves the image back into Windows. Online images only |
reagentc /enable |
Re-enables it, falling back to Winre.wim in \Windows\System32\Recovery |
Take the output of reagentc /info before you touch anything. It is the record of what the machine looked like when it worked, and it is the only easy way to tell afterwards whether you put it back the way you found it.
The codes in this family, read precisely
It is worth separating what each code says, because they get treated as one undifferentiated partition problem and they are not. One says the device could not be found. One says several devices matched and could not be told apart. One says a file was not found. Those point at different checks, and knowing which you have narrows the search considerably.
When the layout is genuinely correct
- Check for firmware settings that expose extra devices, such as a RAID or optional storage controller mode that presents volumes differently to setup than to Windows.
- Look for virtual drives created by backup, disc-imaging or virtual machine software. They can present as disks during analysis.
- Confirm the system disk’s partition style matches how the machine boots, since a mismatch produces confusing analysis results.
- Read the setup logs in
$Windows.~BT\Sources\Pantherand search for the code, then read the lines above it to see which device setup was examining. - Run SetupDiag afterwards. It reads the same logs and will name a matching rule if one applies, which saves reading them by hand.
Licensing has nothing to do with this one
No part of this failure is an entitlement problem. Setup stops before it reaches anything licence-related, and the machine’s activation state is unchanged by the whole episode. Treat any advice to buy a licence to resolve a 0x20009 failure with suspicion.
When a licence is the actual fix
Nothing in this article is fixed by buying anything. Setup stopped during partition analysis, and taking the extra system partition out of view costs nothing. The only reason a licence enters the conversation is the far end of it: if the layout turns out to be so tangled that a clean rebuild is quicker than untangling it, and the machine’s edition or media is no longer to hand. Arco supplies Windows 11 Pro upgrade licences for that case, and will say so plainly when the answer is a diskpart command rather than a purchase.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
0x80073BC3 - 0x20009 |
Win32 15299 ERROR_SYSTEM_DEVICE_NOT_FOUND during partition analysis and validation. Microsoft’s mitigation names multiple system partitions as the cause | Microsoft Learn |
0x80073B92 - 0x20009 |
Win32 15250 ERROR_AMBIGUOUS_SYSTEM_DEVICE: multiple indistinguishable devices match the identification criteria | Microsoft Learn |
0x8007002 - 0x20009 |
Microsoft publishes this row as 0x80070002 – 0x20009, Win32 2 ERROR_FILE_NOT_FOUND. The seven-digit form in circulation is the same row | Microsoft Learn |
Confirm the fix worked
- The upgrade proceeds past partition analysis and reaches the first restart.
reagentc /inforeports the recovery environment as enabled, in the same place it was before.- Any disk you took offline is back online and its volumes are accessible.
- If you suspended encryption, the drive reports as protected again rather than merely encrypted.
Questions people ask about this
Is this the recovery partition being too small?
That is a real cause of other upgrade and update failures, but it is not what these codes say. 0x80073BC3 is ERROR_SYSTEM_DEVICE_NOT_FOUND and 0x80073B92 is ERROR_AMBIGUOUS_SYSTEM_DEVICE, and Microsoft’s mitigation for the row is about multiple system partitions. Check the recovery partition by all means, but check for a second system partition first, because that is what the documentation points at.
Can I just delete the extra EFI partition?
Do not. Taking the disk offline achieves the same result for the duration of the upgrade and is completely reversible. Deleting a system partition on the wrong disk leaves a machine that will not boot, and telling the two apart under time pressure is exactly when mistakes happen.
Why does an external drive matter?
Because setup examines every device it can see. A USB disk that was once someone’s system drive still carries the partition that made it one, and setup has no way to know you do not mean that one. Disconnecting everything non-essential before an upgrade is cheap insurance for this and several other failures.
Do I have to decrypt the drive?
No, and you should not. Suspending protection puts the volume into a state setup can work with while leaving the data encrypted on disk, and it is a command rather than an hours-long operation. Re-enable protection when the upgrade finishes and confirm the drive reports as protected.
