Windows 11, version 24H2 won't install

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

Ganesh When you say OEMs and Microsoft have to work together, do you mean hardware or software or both? Reason I ask is some people have Microsoft computers yet had and have problems, so in that case they are the OEM too!

Hello

I never had any problems with my PC .

Windows 11, version 24H2 update is ready to install, I approve the restart, it starts working, stops at 68% for 5 minutes, then restarts and turns off PC. When I booth back, it simply wants to download it and install it again.

Troubleshooter shows Error but offers no solution.

I have downloaded the ISO and followed all instructions, but 26% in, the installer just stops all goes back to windows and says Windows 11 instalation failed.

Any ideas?

Hey, hope you solved your issue by now

I had windows update not downloading issue since 22h2, and I used iso file to update my windows

But finally I found the solution!

If you have 8GB or less ram:

First delete windows update cache

Then do a clean boot and update your windows.

This solution worked for me; I think this error is due to windows update NOT being optimised and therefore it uses a lot of resources especially ram.

By performing a clean boot your system should allocate available resources to windows update.

Hope it helps