Windows 11, version 24H2 won't install

Get multiple error codes - telling I have too little space (which was true, but have cleaned up and still not working) - and telling I don't meet the requirements. Your suggested program ran a check first that told I did meet the requirements, so this is also just bullsh*t.

And yes. I am sure I have 23h2. 100%. The suggested solutions on any pages does not work. I resign.

The Microsoft

"memory integrity system readiness scan tool 24h2"

Google it... found the drive which didn't meet the spec. That is hardly mentioned on the help sites. Found it after 9 weeks of going round the loop and reading the same old fixes. Just one driver that wasn't being used was causing the second boot to fail.

Found it being told to be used when I googled a fragment of the error log.

Basically Microsoft tightened up on security on this release so you have to pass a number of hurdles and those people that say its easy didn't have problem drivers, programs etc. I updated four PCs, one fully compliant W11 laptop no issue. Two non compliant tower units using the server method no issues. One fully compliant W11 laptop that through the raspberry for nine weeks.

Microsoft will have their work cut out to make this update work smoothly due to changing the rules for W11 enforcing better security. Their tools don't tell you what you need to do when it fails. Just vague suggestions unless you are a master with the log files.

So, I have updated Motherboard BIOS, and the chipset drivers (AMD B550 Phantom Gaming 4 Motherboard.

Now, when I run the setup for the iso file, I get a message telling me that it couldnt install becasue I dont have sufficient space on my Windows drive.

I check, and it has 112Gb free out of 229GB. Its an SSD.

So I run the HVIscan_amd64 tool which previously reported on incompatible drivers (now all removed) and it tells me:

VbsGetIssues: 0x00006008

IOMMU required 

Failing to meet 52GB minimum required volume size 

System drive SSD required 

VbsIsRecommended: 0

HVCI incompatible driver scan start...

HVCI: Driver scanning complete

HVCI incompatible driver scan passed!

This just gets better and better

I don't know what the IOMMU error refers to. Searches show its something to do with ebabling memory intergrity or virtualisation support.

I am SERIOUSLY considering booting the machine and installing a ~Linux distro. and to hell with this rubbish.

This has to be one of the most shambolic updates microsoft has ever released

So, I have updated Motherboard BIOS, and the chipset drivers (AMD B550 Phantom Gaming 4 Motherboard.

Now, when I run the setup for the iso file, I get a message telling me that it couldnt install becasue I dont have sufficient space on my Windows drive.

I check, and it has 112Gb free out of 229GB. Its an SSD.

So I run the HVIscan_amd64 tool which previously reported on incompatible drivers (now all removed) and it tells me:

VbsGetIssues: 0x00006008

IOMMU required

Failing to meet 52GB minimum required volume size

System drive SSD required

VbsIsRecommended: 0

HVCI incompatible driver scan start...

HVCI: Driver scanning complete

HVCI incompatible driver scan passed!

This just gets better and better

I don't know what the IOMMU error refers to. Searches show its something to do with ebabling memory intergrity or virtualisation support.

I am SERIOUSLY considering booting the machine and installing a ~Linux distro. and to hell with this rubbish.

This has to be one of the most shambolic updates microsoft has ever released

Minitools reckons it's bad when you get it. Probably all microcode and stuff. My Minor in Computer Science comes in handy at times 😉. 8 bit in those days.

The story goes Microsoft reduced their development staff numbers and the Insider programme was suppose to pick up the slack for free. Some Insider people are there for the ride to blab on about it and not do much. It was the Insider programme that picked up the issues which haven't been resolved in the release version. Probably Musky approach, test to when it doesn't explode...

Yes, as I said. I tried this. Didn't work,

What happened? Did you get an error code?

I'm just wondering - why did the 24H2 installation fail with (Microsoft's own, official) Windows 11 Installation Assistant?

Are you SURE you have 23H2 installed on your computer?

Humour ?.

Now I don't understand your comment! What is the "humor" here? Can you explain more?

I installed Dec 15 the big 24H2 update on my computer (HP 470 G9 laptop, Windows 11 Pro).

The update went well, easily and without any problems with this method:

Windows 11 Installation Assistant

I would like to emphasize that this is one of the three Microsoft's own, official installation methods.

Microsoft says: This is the best option for installing Windows 11 on the device you’re currently using.

https://www.microsoft.com/en-us/software-download/windows11/

My laptop has been working flawlessly and stably ever since!

Yes, as I said. I tried this. Didn't work,

What happened? Did you get an error code?

I'm just wondering - why did the 24H2 installation fail with (Microsoft's own, official) Windows 11 Installation Assistant?

Are you SURE you have 23H2 installed on your computer?

Humour ?.

Now I don't understand your comment! What is the "humor" here? Can you explain more?

I installed Dec 15 the big 24H2 update on my computer (HP 470 G9 laptop, Windows 11 Pro).

The update went well, easily and without any problems with this method:

Windows 11 Installation Assistant

I would like to emphasize that this is one of the three Microsoft's own, official installation methods.

Microsoft says: This is the best option for installing Windows 11 on the device you’re currently using.

---

https://www.microsoft.com/en-us/software-download/windows11/

 

My laptop has been working flawlessly and stably ever since!

https://en.m.wikipedia.org/wiki/Humour

4 in the taxonomy.

The assistant doesn't mean fault less installation. Just one of a number of starting points. All starting points will get you to the same end point. The ISO method gives you the same as the assistant if you don't take the suggested update drivers which you shouldn't. (Thats well know).

The issues with the update are well known and Microsoft accepts many. If you end in the treacle thou in the update you can get very stuck with it bombing out. Probably only Microsoft knows the success rate since their systems are monitoring that. Their systems will not remove duff incompatible drivers, apps and the like. It will not say do this or do that but gives you an error code. For these reasons you are told not to nudge the update by running the assistant, ISO or doing anything but from posts the issues are now being created by Microsoft pushing the update.

The system will push the update a few times and leave if for a while and start again unless they identify a specific issue. Duff drivers and programs may very well not be identified since they aren't identifying these in their error codes. Careful informed examination of the log files and running associated utilities will identify the issue but if you haven't got the skills you need professional help.

The increased security in the update design has led to these issues. Its the second boot where the security screening is deployed. The first boot is similar to the Windows 7/8 to 10. Second boot is where the full security is deployed so dubious material doesn't get through. If you have a relatively simplistic set of software installed you are likely to have few issues if you have "legacy" (read as old) or non Microsoft developed programs which do something above and beyond Microsoft software at a systems level then those are the ones that can cause issues.