Windows 11, version 24H2 won't install

It's ridiculous that end users are forced to jump through these sorry if his just too run the update to the new windows version. Microsoft really need to sort this out

A lot of users are going to be crashed into a wall now they have taken the brakes off again 🤣. I've given it out that I'm not going to give out brother in law support. Microsoft can do that.

I have had the same problem, and tried so many solutions but this is the only thing that worked for me.

Open Note pad and copy and paste this in

SC config trustedinstaller start=auto

net stop bits

net stop wuauserv

net stop msiserver

net stop cryptsvc

net stop appidsvc

Ren %Systemroot%\SoftwareDistribution SoftwareDistribution.old

Ren %Systemroot%\System32\catroot2 catroot2.old

regsvr32.exe /s atl.dll

regsvr32.exe /s urlmon.dll

regsvr32.exe /s mshtml.dll

netsh winsock reset

netsh winsock reset proxy

rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN

dism /Online /Cleanup-image /ScanHealth

dism /Online /Cleanup-image /CheckHealth

dism /Online /Cleanup-image /RestoreHealth

dism /Online /Cleanup-image /StartComponentCleanup

Sfc /ScanNow

net start bits

net start wuauserv

net start msiserver

net start cryptsvc

net start appidsvc

Save as Wufix.bat (to desktop)

change to all files before saving

go to desktop

right click on Wufix on your desktop, run as administrator

restart your computer

Fixed!!!

That type of fix you find on many I did trillions of them. Was the last check on compliant drivers that did the trick and removing them with nothing. Don't reckon that's there.

The added complication is that some revised drivers aren't 24h2 compatible whilst old ones are so if you do an upgrade of a driver and get one of them you are stuck.

Time will tell whether Microsoft can make the 24h2 upgrade work now they are taking the brakes of it again. The second issue they revert drivers, the first one where the user has some software installed that doesn't pass the final boot into 24h2 means they would have to junk those old incompatible drivers or replace then in an automated way. Issue being the enforced secure boot that they put into 24h2.... that which I believe some people turned off at installation in 24h2 to get it installed. Unless that's in the command above.

So yes it was the the "memory integrity readiness Microsoft tool" that finally got it to work after removing one problematic driver. The fixes can generally be done by doing an inplace restore which dusts down the system rather than a long list of start, stop etc. So for me those didn't work and I got tired of doing them and reading them. 🫣 As said I believe some people turn the back end of UEFI security checks off rather than dealing with the issue.

I have had the same problem, and tried so many solutions but this is the only thing that worked for me.

Open Note pad and copy and paste this in

SC config trustedinstaller start=auto

net stop bits

net stop wuauserv

net stop msiserver

net stop cryptsvc

net stop appidsvc

Ren %Systemroot%\SoftwareDistribution SoftwareDistribution.old

Ren %Systemroot%\System32\catroot2 catroot2.old

regsvr32.exe /s atl.dll

regsvr32.exe /s urlmon.dll

regsvr32.exe /s mshtml.dll

netsh winsock reset

netsh winsock reset proxy

rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN

dism /Online /Cleanup-image /ScanHealth

dism /Online /Cleanup-image /CheckHealth

dism /Online /Cleanup-image /RestoreHealth

dism /Online /Cleanup-image /StartComponentCleanup

Sfc /ScanNow

net start bits

net start wuauserv

net start msiserver

net start cryptsvc

net start appidsvc

Save as Wufix.bat (to desktop)

change to all files before saving

go to desktop

right click on Wufix on your desktop, run as administrator

restart your computer

Fixed!!!

HI,

This sounds interesting, since it seems to offer a simple remedy to the update rigmarole.

However, there are several passages and terms that are not clear to me.

• What is a MSI Vector 16, and how do you post-power it?
• Did you start the update after whatever you did with that MSI Vector 16? And then, when you got stuck at 25%, did you just remove all update caches (see also next point about those files)? Or did you start the accursed 24H2 update all over again after that removal?
• Under C:\Windows\SoftwareDistribution\Download, I see 5 folders and 1 log file. If not all, which folder(s) contain(s) the update caches and the AV features you mention?
• What are AV features?

Looking forward to your reply,

HK

They would have deleted everything in that download directory. The 25% is a cue to which reboot it was on, trying for the first. First set of faulty drivers. The final action is after 70% if you are at <30% you are well back.

AV I guess they meant anything to do with audio visual on the kit.

Basically from reading what they did, was not a major hash of the drivers... reckon that one gives people issues if you change to one that isn't compatible with the migration then it won't go beyond 30%. They were probably just lucky.

HI,

This sounds interesting, since it seems to offer a simple remedy to the update rigmarole.

However, there are several passages and terms that are not clear to me.

• What is a MSI Vector 16, and how do you post-power it?
• Did you start the update after whatever you did with that MSI Vector 16? And then, when you got stuck at 25%, did you just remove all update caches (see also next point about those files)? Or did you start the accursed 24H2 update all over again after that removal?
• Under C:\Windows\SoftwareDistribution\Download, I see 5 folders and 1 log file. If not all, which folder(s) contain(s) the update caches and the AV features you mention?
• What are AV features?

Looking forward to your reply,

HK