Update Windows to 24H2 on Arm

You might want to read that information a bit closer:
Creating a new registry key "Windowsupdate" in Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows with the three value as shown here seems to have worked for me...
If you look carefully, you will see that it says CREATE A NEW REGISTRY KEY. If you have never used REGEDIT, before, if you attempt this, make sure you back up the Registry before attempting to edit.

 

Hi,

Thanks.

I managed to get it working (Parallels Desktop 20.2.2 / MacBookPro M1 Pro / macOS 15.4 / Windows 11 24H2).
But it took me a lot of effort and retries.

The ISO method does not work!

The RegEdit hack worked after restarting Windows 11 22H2 5 times. Before I could not get a new key inserted.
After I managed to set all the key parameters (listed in the beginning of this threat) I could indeed update to 24H2.

This took 30 minutes. Many, many restarts and stupid waiting screens.
Halfway through though Parallels VM froze solid. Only a very large movable mouse pointer was visible in a black screen.
No action, no reaction.

So I hard booted the VM again after another 15 minutes of waiting.
Than finally the Windows update installer continued again.

And after 15 more minutes and stupid message screens, I got a working install of Windows 11 Pro 24H2 with my old genuine W11 license.

The only issue I have is trackpad scrolling not working in Edge.
But no problem. Edge is frustration-ware anyway... ;-)
Scrolling in every other app. and the finder (haha) is fine.

 

Hi LeRoi,

Thanks for your reply and help.

I did create a new registry key. But REGEDIT reported a key with that name already existed. But it was not shown, nor in any other list.

But (see my other post) after restarting Windows a few times I could create a new key and was able to set all values.
After that the update to 24H2 worked. But it took a long time, many restarts and a complete freeze-up of the installer program.

I never had these kind of problems with REGEDIT before. But all set now.

KR, Mike.

 

Glad to hear you got it resolved. MS Updates can be really frustrating at times (ask me about sitting at 30% on an upgrade for over 30 minutes).