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).

 

I cannot upgrade to 24H2, still on 23H2 and Parallels 19. What am I missing? Is 19 of Parallels not compatible with 24H2? Thanks

 

between the GPedit and regedit I can't get windows update to 24H2, I have installed all the edits to both and no go. I am at wits end.

any help would be greatly appreciated.

Thanks.

 

I'm running Windows 11 Pro 23H2 (22631.5624) in Parallels 20.4.0 (55980) on macOS 15.5 on an M1 MacBook Pro, and I'm still not seeing the update to 24H2 in Windows Update, despite the fact that Microsoft says it's been "broadly available" since May 2.
Haven't tried adding the Registry key yet, but I'm a little reluctant to force it in case there's some reason why it's intentionally not appearing for my machine? I understand these updates are rolled out in stages, but it sounds like at this point it should be available for everybody. Is there an official explanation from Microsoft or Parallels?

 

Decided to go ahead and try the Registry key trick, since I have plenty of backups. It worked perfectly and the 24H2 update installed no problem!

 

Here we are in September and using Parallels 26.0.1, still cannot get my Windows VM to update to the latest version.
Windows update tells me that it is available as part of my Windows Insider program membership.
The download looks like it's going to happen, but does not proceed beyond 0%
I frequently get the warning about "this build of windows will expire soon - 15/09/2024"
I've tried the registry hack above, doesn't seem to work for me, nor any of the other suggestions.

Did anybody have any luck with anything else?

 

Following the start of this thread, when I, too, had the problem of W11 not updating, I followed some of the advice and got 24H2 installed. That was almost a year ago and I'm struggling to remember the precise route I took, but it didn't involve registry hacks (something I was quite familiar with before I switched from a Windows PC to a Mac with a Windows VM). AFAIR I downloaded a new ISO from MS and upgraded from that.

 

Rather than trying all of these time consuming and ultimately fruitless workarounds, would i be better trying to create a new Windows VM in parallels completely separate from my existing one and then trying to register it to the windows insider program to get ongoing updates?
I would be very nervous about destroying my current functioning Windows 11 VM, so would time machine backup before proceeding.
Just wondering whether that it a feasible workaround for a very frustrating situation?

 

After trying all the hacks and having zero luck, I decided to redownload windows from parallels and now I have the latest 24h2. Since I didn't have a lot of stuff loaded in windows it was not a big deal.

 

I've just tried creating a new Windows 11 VM from parallels on my MacBook Air and succeeded.
Doing so means I'm tight on space and required a USB drive to supplement space available for the updates.
I'm just wondering whether there's a way to transfer windows settings etc from the original VM, as now I'm being asked for an activation code?
Or alternatively can I actually change some of the settings on the original VM which refuses to update through Windows update.
Parallels really should have sorted this issue out!

 

I don't think it's a parallels problem, it's a windows thing. Yea I had to buy a new windows key to activate the the new windows instance and just blew away the old windows since the stuff I had in it could easily be reinstalled. I don't keep any data on the windows VM's.