Ratfink_'s Posts

Hello All I am confused a a Long time VMware Fusion ( and ESXi ) user as I have been waiting for a long time for Fusion v13.0 As I needed to continue to work , I was forced to pay for a Parallels v18 License to run my Windows11 Arm VM on my M1 MacBook Now all I want to do is import the VM I have been using for then past 12+ Months into VMware Fusion v13 Pro so I can continue Working. This seems to no longer function as the conversion process assumes you are importing an x86 VM ( instead of checking first ) So , I thought , Simple , I will build a new Windows11_Arm VM in Fusion v13 Pro , but this does not work either.  Networking does not function and the Hardware support id Buggy at Best ( and non-existent at worst ) Please VMware , If you are going to release TP 22H2 as a 'Finished Product' , make sure it actually works before charging me US$ 199.00 for the License !! Tony 

Hi All I do actually realise that this is my own fault.  I assumed that because VM Fusion v8.5.8 support APFS that it would be OK in macOS 10.13 BETA I now realise that while VM Fusion v8.5.8 functions 100%, I have lost all BOOTCAMP support (even though the Windows Partiton functions perfectly in BootCamp and its partition is 100% the same (disk0s3) Is there any current workaround for this prior to VM Fusion v10 ??   a Public BETA of Fusion v10 available?? Thanks in Advance