Windows 11 23H2 update requires DirectX 12?

[ohwell]

I tried in vain to get the 23H2 update on my ARM64 install of Windows 11 Pro. A bit of searching leads me to believe that 23H2 requires DirectX 12, and therefore I will not be able to install or upgrade to 23H2 since Fusion only supports DirectX 11.

Is that correct?

[Technogeezer]

I’m seeing the same thing.

Windows 11 has always had an official system requirement of DX12 but it’s never refused to install because of VMware’s SVGA being DX11. As far as I can tell, Parallels doesn’t support DX12 either.

I’m not sure that it’s because of DX12 though. 22H2 upgraded to 23H2 in a Insider Preview Beta Channel build VM that Inhave. Rather I’m inclined at this point to believe that they are staging the upgrade and haven’t released it yet. I’m going to wait a bit longer before being concerned, since a lot of what was originally supposed to be new in 23H2 has already been released to 22H2.  

Maybe @Mikero can see if VMware can contact Microsoft to see what’s the hold up? 

[ColoradoMarmot]

I thought I read that they pulled it?

[Technogeezer]

@ColoradoMarmot - I had not heard that, any pointers or articles?

I still believe that 23H2 isn't that big a deal yet, since most of the things Microsoft was targeting to be in it were released in 22H2 already. 

[HackaMac]

I had no trouble at all upgrading to 23H2.  I haven't really installed much in the way of 3rd party SW; Firefox and Steam.

Mac Studio M1 Max, MacOS Sonoma

The Windows 11 VM was originally built on Fusion 13.0.  The 23H2 upgrade was done on 13.5.  I never installed any MS Insider Preview releases.

[Technogeezer]

That's good news @HackaMac - I guess I'll just have to be patient until Microsoft decides to offer the update to me. 

[HackaMac]

@Technogeezer ,

Now that I think of it, the VM was built on the Fusion Tech Preview version, according to your Unofficial Guide (Thanks for that!).  And downloaded via CrystalFetch, in case that makes and difference.

[Technogeezer]

No there's nothing different there.  CrystalFetch uses the same technique that I used in my w11arm_esd2iso and I suspect that VMware is using in their tool as well.  Those download the release channel Windows 11 ARM 22H2. 

I have 2 VMs, one running the Insider Beta Channel release (which did update do 23H2 as part of the beta channel) and one running the release channel 22H2. (which has not updated to date). 

Patience is a virtue, I guess.

[SvenGus]

In the meantime, one can optionally install Windows 11 23H2 immediately with the enablement package:

https://www.xda-developers.com/windows-11-version-23h2-manual-install/#how-to-download-the-23h2-enab...

[SvenGus]

… Which essentially only requires an up-to-date Windows 11 22H2 installation (with the latest cumulative update).

[billearl]

The ARM64 MSU did not work for me on an M1 Mac with latest version of Win 11 22H2 with "Get the latest updates..." turned on. It installed something, but did not update to Win 11 23H2. Same result in VMware Fusion and Parallels.

[Technogeezer]

@SvenGus  Thanks for that. I did see article (or something similar to it) that points to the enablement package that's being downloaded via Windows Update. And read the Microsoft KB article on the enablement package that noted the prerequisites.  

I'm in no urgent need to go down that road. Yet  Especially since I have a second, VM running the beta channel builds that already made the leap to 23H2.

[Technogeezer]

The enablement package doesn't do much. It "flip bits" to turn on disabled features that are already present in the latest 22H2 update and then changes the Windows version. Nothing else gets downloaded unlike what you'd see with other Windows cumulative updates or "service pack" releases. 

To verify that it worked, run winver.exe and see what it says for the version.

[ohwell]

The MSU worked a treat, thank you.

[billearl]

Okay. I was expecting a long update process. The version is now 22631.2506, shown as 23H2, installed on May 5, 2023. This applies to VMware Fusion and Parallels. Seems like a stealth upgrade. I'm a bit puzzled why Microsoft would want to slowly roll out such a painless upgrade.

[Technogeezer]

Microsoft did deviate from normal practice with 23H2. What I've read indicated that they decided to release a lot of the features early, but  released the 23H2 enablement package to "rebase the version" and turn on a couple of features they had put in the code, but hadn't enabled (probably needed a bit more time to test them out). 

They look like they've decided to support the "once a year feature releases xxH2" for 2 years from their initial release. See https://learn.microsoft.com/en-us/lifecycle/products/windows-11-home-and-pro

Hence the need to "rebase" the versioning.

[Technogeezer]

Just FYI - Windows Update just offered the 23H2 "upgrade"/enablement package to my 22H2 release channel VM. It installed without issue. 

The reported build is 22631.2506

Patience paid off... at least in my case.