Terence,
I just wanted to drop into here and thank you for the hvciscan tip. This fully Win11 compliant Lenova Legion laptop I'm typing on would make it all the way through the painfully slow upgrade to 24H2 and would bomb out during the second boot phase with error code: 0xC1900101 - 0x40017 Yep, a device driver problem of some sort. I ran hvciscan and it reported SIX .sys files that were not compatible with the new memory model:
jlinkx64.sys
ssdudfu.sys
VIA_USB_ETS.sys
mbtusbser.sys
wdcsam64_prewin8.sys
PxHlpa64.sys
I researched all six of those and decided, what the heck, it'll run without those and I renamed (*.old) all six to prevent loading. I reran hvciscan and it reported no problems. I reran the 24H2 setup (I used the .iso) and Win11 24H2 installed. Some day when I'm bored I'll clean up the registry.
Thanks again.
Geo.
**First of all - it's really great that you successfully updated to version 24H2!**π
But in my opinion ... this cannot / must not be the case!
If we think in general about ordinary computer users who do not have "deeper" IT skills --> they do not really know how to solve the installation problems of this important update.
However, they are the majority.
Even on this forum, in several discussion threads, there are dozens of "anxious cries for help"π¨about this.
Now Microsoft should offer ALL USERS a well-installable and functional 24H2 - **otherwise things will get out of hand, and will no longer be under anyone's control.**π€π