Tips and Techniques for the Apple Silicon Tech Preview 22H2

Tips and Techniques for the Apple Silicon Tech Preview 22H2

Latest update: Version 7 - 21-September-2022

Changes in this revision

  • The recently released Fedora 37 beta is noted as installing on the Tech Preview with no issues.
  • Instructions on installing Fedora 35/36 have been updated to address a software update failure after the initial installation. The issue is a Fedora issue not related to the Tech Preview, but it prevents necessary Fedora updates from being installed.

This document is designed as an unofficial companion to the 22H2 Tech Preview Testing Guide. It is a collection of issues and solutions reported to the Tech Preview Discussions forum. It's an "all in one place" collection so you don't have to go searching through multiple threads to find common (and not-so-common) helpful hints.

Content in this document is specific to the 22H2 Tech Preview running on Apple Silicon. The 21H1 Tech Preview and 22H2 Tech Preview running on Intel Macs are out of scope for this document.

This document contains hyperlinks to external web sites. It is best viewed with Adobe Reader, but should be readable by any other PDF reader. Of course it can be printed for reference.

Thanks to all of the community members that have contributed their knowledge to the community. Without their contributions, this document would not have been possible or as extensive.

 

Attachments
Comments

 

I'm attempting to install Windows 11 on Fusion on a MACBOOK Pro. Windows is bUnfoooting but tells me that my hardware is incompatible with Windows 11.  Only this I can see that is a potential issue is the Directx 12 support. Any way to get around this? Could it be misleading? I have the Intel processor. I'm on a Multihull boat and need to run a Windows app to see & configure MasterVolt electronics, so important. Unfortunately I bought the OS already.

 

[ image removed by moderator: please re-upload after removing your serial number]

 

@Trim1 

That's regular Fusion for Intel-based Macs, not the Fusion Tech Preview for Macs using Apple processors.

You need to create a post here: https://communities.vmware.com/t5/VMware-Fusion-Discussions/bd-p/3005

 

On another note: do not post a screen shot of your macOS host with the serial number in it. That's sensitive information which should never be shared in public.

--
Wil

This document is fantastic... thank you for contributing!

Excellent work.

Only issue i'd like resolved on my M1 Mac is Shared folders aren't an option

Screen Shot 2022-08-28 at 10.34.34 PM.png

 

Screen Shot 2022-08-28 at 10.34.43 PM.png

@JoshMH the lack of support for shared folders for Windows 11 virtual machines is a documented restriction for the 22H2 Tech Preview. We are all hoping that a complete Tools implementation for Windows 11 for ARM is delivered in the final shipping product which should return the shared folders option to the GUI. 

@Technogeezer Just picked up on this subject again.  Did VMware finally get an arrangement with Microsoft/Qualcomm or whoever it was so they are not breaking legal agreements?  Or are they just forging ahead like Parallels did a year ago?  I've been running the "unsupported" version of Fusion since Windows 11 came out.  For my setup anyway, I don't have any of the issues reported for 22H2 (no problem sharing file folders for example).  It is great that VMware finally got something out that I suppose has more "support," or will eventually be "supported."  I continue to run Parallels on my M1 laptop with zero issues.  Parallels costs a few bucks so it would be nice if Fusion continues to free to non-commercial users if/when they finally release a non-beta product.  I am avoiding 22H2 in the meanwhile as it is beta, and I am not having any problems with my non-beta (but not "supported") version of Fusion on my Intel iMac,

@dminter Your guess is as good as mine about why VMware's lawyers had a change of heart. A comment by @Mikero indicates that they asked Microsoft recently and the answer was that "licensing is between Microsoft and the user". Which to me says that Microsoft won't come after VMware should they build it. Also Microsoft will now allow a retail Windows 11 key to activate Windows 11 for ARM - so there's no more excuse that "you can't license Windows 11 if you're not an OEM".  So I think your latter conclusion that "they are just forging ahead" is probably closer to truth - but that's my opinion.

I've been quite pleased running Windows 11 or ARM on the tech preview. (I run the latest "retail" Windows 11 build from uupdump.net - fully licensed and activated). Only wish that cut/paste/drag/drop was available. 

@Technogeezer Interesting development, and a good one.  I have a lot of confidence in VMware so am glad to see them getting into the pool.  As for Microsoft, the whole relaxing the hardware version TPM requirement may come down to selling more Windows 11 licenses.  I have always purchased and run retail copies - only fair to the people who develop new software like Microsoft.  

@Technogeezer thanks for sharing your personal success anecdote, I don't have an installer build that has worked yet so I'll try the flavour you just mentioned.

@dminter actually the new TPM that VMware has introduced in the 22H2 Tech Preview is heads and shoulders above what you had do with Fusion 12 on Intel Macs. It doesn't incur the penalty of having to encrypt the entire VM, nor does it have all the deficiencies that the experimental vTPM had in Fusion 12 (which means you can actually move the VM from 1 host to another). You don't have to hack around with registry keys in the Windows 11 installer to bypass the TPM check. Much nicer experience than it was in the 21H1 Tech Preview.

@rhaleblianbeta I'd go for the latest Windows 11 ARM public release build from uupdump.net (22000.918). No it's not the release preview, and getting updates from the release channel so you're getting what real Windows 11 for ARM customers are getting. This 22000.918 build is the one I'm currently running (and it was just updated to that build).

I recommend building the ISO from uupdump.net from another Windows system if you have one. It's the easiest option. There's nothing extra you need to install on Windows once you download the build script from uupdump.net. Building on Windows also includes any updates in the ISO making the install process a bit easier. Building on Linux and macOS do not let you include updates in the generated ISO.

Linux is my next choice, because the open source tools needed by the build process are easily installed from most distro's repos.

Unless you are very comfortable using homebrew, I would not recommend you build the ISO on macOS. It's not for the faint of heart. .

@Technogeezer Thanks for the additional info.  When they release the non-beta, I will probably switch to it.  The only question will be undoing what I already have in place with my intel iMac and the previous Fusion work-around. I suppose it will be a matter or uninstalling Windows 11 (copy/product ID protected if I recall correctly).  And uninstalling the Fusion build I am running now.  Perhaps someone will post transition instructions when the time comes.  I am slightly hesitant to mess with the supporting beams as everything works now. 🙂 

"If it ain't broke, don't fix it"

😀

I'll make note of that particular build number.

Yes, I have been using Windows for the uupdump process, as I noted the document also suggests.  Given all of the corner and edge cases of which we are members already, it's insane to add ourselves to another.  😐

Version history
Revision #:
22 of 22
Last update:
‎09-21-2022 11:47 AM
Updated by:
 
Contributors