24H2 Upgrade Issue

After making an image, if doing an inplace upgrade fails, look at your error logs to see if it points you to what's causing the failure. Depending on where in the install the failure occurs, the log can be in multiple places.

If no error message occurs, the following log files are created when an upgrade fails during installation before the computer restarts for the second time. You have to look at these logs to get an idea of what's causing the failure. Since mine rolled back, I found mine in C:\$Windows.~BT\Sources\Rollback\setupact.err

• C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\Windows\setupapi.log
• [Windows 10:] C:\Windows\Logs\MoSetup\BlueBox.log
• C:\Windows\inf\setupapi.app.log
• C:\Windows\inf\setupapi.dev.log
• C:\Windows\panther\PreGatherPnPList.log
• C:\Windows\panther\PostApplyPnPList.log
• C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and then you restore the desktop:

• C:\$Windows.~BT\Sources\panther\setupact.log
• C:\$Windows.~BT\Sources\panther\miglog.xml
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.dev.log
• C:\$Windows.~BT\sources\panther\setupapi\setupapi.app.log
• C:\Windows\memory.dmp

The following log files are created when an upgrade fails, and the installation rollback is initiated:

• C:\$Windows.~BT\Sources\Rollback\setupact.log
• C:\$Windows.~BT\Sources\Rollback\setupact.err

Mine rolled back so I found mine in the last 2 logs..
If logfiles do not direct you to what caused the error, I advice anyone to not waste his time. Bite the bullet and do a clean install or stay where you are for now. 24h2 will have you chasing your tail for days. There are always some upgrade issues with every version but I don't think any other one MS has released has caused the kind and number of issues being reported with 24h2..
Mine failed and I spent all day messing with it and not getting anywhere. I finally clean installed so I don't have to worry about it. At least I know I have a perfectly clean system now. It had been 2 years since my last clean install so it was time.

antspants said:

Well I “thought” that when Microsoft temporarily stops offering the 24H2 update for devices with known detrimental issues (or whatever) the 24H2 install would only know this by connecting online.
I would doubt these exclusions would be written into the ISO.

So I thought, because I don’t know better, that disconnecting from the net would prevent 24H2 knowing your WD is an issue.

If it were me, i’d disconnect the internet and In-Place with a Rufus v4.6 USB

That screenshot you first posted, is derived from an online check, I am betting.

I am obviously speculating.

Click to expand...

I can confirm it's an online check. I kept getting the block issue due to the installed WD_Black SN770 2TB boot drive on my Asus mini PC. Did the HMBAllocationPolicy reg hack then disabled network and told the installer not to check for updates. Upgraded to 24H2 using latest official iso from Microsoft. Thank you everyone who contributed to this thread,

hexpek

hexpek said:

I can confirm it's an online check. I kept getting the block issue due to the installed WD_Black SN770 2TB boot drive on my Asus mini PC. Did the HMBAllocationPolicy reg hack then disabled network and told the installer not to check for updates. Upgraded to 24H2 using latest official iso from Microsoft. Thank you everyone who contributed to this thread,

hexpek

Click to expand...

Welcome to the forum

Yeah thanks, it seems logically obvious really. No way Microsoft is going to write a block for software or hardware into an ISO as the situation surrounding either could be corrected.

So they block it with an online check

I do believe however, Windows ignores network settings in this situation? This is why I turn OFF the router
I’m not aware of the HMBAllocationPolicy, will look at it

antspants said:

Welcome to the forum

Yeah thanks, it seems logically obvious really. No way Microsoft is going to write a block for software or hardware into an ISO as the situation surrounding either could be corrected.

So they block it with an online check

I do believe however, Windows ignores settings in this situation? This is why I turn OFF the router
I’m not aware of the HMBAllocationPolicy, will look at it

Click to expand...

I forgot to mention I also upgraded the firmware on the WD-Black SN770 with the WD Dashboard utility to version 731130WD. Seems stable for now, I'll report back if there are any issues.

Cheers,
hexpek