All Posts

@jyang2012 wrote: No fix for this? I am getting the same issue on my W11 ARM VM operating on the Fusion 2023 Tech Preview with anything that has to do with any graphics acceleration. There seems to be something very very unstable with the VM Tools graphics drivers. You should have no expectation that fixes will be released for any issues found in this public beta software until the formal release of the next GA version of Fusion. VMware is aware of some issues in their 3d driver for some workloads. I’d suggest dropping an email to fusion-beta@vmware.com with as much detailed information about where you are seeing this error. Don’t wait for the team to watch this forum if you want to make sure you get their attention.  You might want to try to download VMware Tools 12.3.0 https://customerconnect.vmware.com/downloads/info/slug/datacenter_cloud_infrastructure/vmware_tools/12_x%23drivers_tools#product_downloads which appears to have a later date than the Tech preview and see if they fixed the issues there. Otherwise you’ll have to wait. . 

No fix for this? I am getting the same issue on my W11 ARM VM operating on the Fusion 2023 Tech Preview with anything that has to do with any graphics acceleration. There seems to be something very very unstable with the VM Tools graphics drivers.

I just tried this out. Start with a working Windows 11 ARM VM - otherwise you might have to mess around with the EFI boot strings and that isn't going to be pretty. Make a backup copy of the working Windows 11 VM by copying it elsewhere. On this working VM: Remove the TPM device (unless you're using BitLocker, you won't have a problem with removing and re-adding a TPM device). Decrypt the VM. Now go to the VM's settings and click "Add Device...". From there, select "Existing virtual disk".  Navigate to the old VM and select its virtual disk, and specify that you want to make a copy. Leave the original alone. Re-encrypt the VM Add the TPM device back into the configuration On your next boot, Windows may ask you to reset your PIN if you've configured Windows Hello. That's an artifact of losing the TPM device, (I had to reset my PIN - thank heavens that Microsoft Authenticator on my iPhone tied to my Microsoft account made that super easy.) Upon login, my other VM's hard drive is now seen as the E drive.  It does seem a bit strange that the VM won't allow you to add a disk that doesn't have any component of it encrypted. Perhaps that's a remnant of the older fully encrypted disks worked. Paradoxically, Fusion allowed me to remove that second virtual disk without decrypting the VM. Go figure.  

Hello, Another user from the German part of Europe  Is there a solution how I can use the numeric keypad under VMware? So far I have not managed to activate it. Do you have a solution? Greetings from Switzerland Hans

I did a bit more experimenting and here is something interesting: I got my hands on an official Microsoft ISO of Windows 11 Pro ARM 22H2 Build 22621.2283. Here the keyboard worked as expected. The install with the issue was from the same Build, but created using the w11arm_esd2iso method. So there must be some problem there. Looks like neither VMware nor Microsoft need to do something ... There are a few other posts, so I'm not alone with the problem.  

Both: Win10 & Win11. There was never problem with that, any case. But on vmware, When I started using vmware, I noticed that searching in Outlook gave no results. Initially I thought it needed time for indexing. But after about a week I started digging and noticed this inconsistency and the lack of Outlook in the Windows indexing settings. Believe me, I read probably everything that was available on the Internet, I tested everything that was available: and nothing. Please see any common PC/laptop, there is no problem. I would suspect Win & arm....

I did not see Outlook on the list of sources when opened from Windows settings. It was there if I opened from Outlook. I still would suspect a Windows issue as there’s nothing here that seems in any way related to Fusion. You say this is working on physical PCs. What version of Windows is running on them? 

Indexing was in progress, but now is completed (screens are form the 3rd vm, nevertheless on 2 others vms is also completed). It doesn't matter unfortunately But when you open Windows -> settings ......-> indexing, do you see Outlook on the list ? Window opened from windows settings, not from Outlook

Ahh, the differences are that I'm using "new outlook". The Classic Outlook client has the File ->Options selection. I switched back to old outlook and now see the menus you've posted in English.  I'm also seeing in your output that Windows indexing is suspended. My indexing is complete - although I suspect I have nowhere near the number of documents as you. Is indexing supposed to be suspended, or did you manually suspend it?  I tend to agree with @ColoradoMarmot that this looks like a Windows issue. I've seen other complaints on the Microsoft and Parallels forums about indexing issues with Classic Outlook and Windows 11 (not necessarily limited to Windows 11 ARM)  - so I have to think it's more on Microsoft's problem than VMware's. 

I would investigate another theory. This could be is a Microsoft issue, not a Fusion issue. Fusion should be doing nothing to make this search not work.  Apologies but I'm not conversant what appears to be Polish that these screen shots are showing.  What version of Outlook are you running? Are you running classic Outlook My Outlook version (latest Microsoft 365 version which I assume is "New Outlook") does not have a File -> Options menu.

great tutorial, can be useful for all But I have one unsolved problem with Outlook (inside the Windows installed): 1) open Outlook -> File -> Options -> Search -> index options. You can find system window (indexing) WITH Outlook present 2) now, I open Windows settings -> Privacy -> .... (the same system window opens) -> Outlook is NOT present         1) and 2) are attached in screens (pdf-s).  Modifying, "show all localizations", sfs/scannow. DISM/....../restorehealth, rebuilding index - nothing helps (tried all given in all google forums, read thousands of pages....) The only workaround is to exclude (prevent Outlook searching) thru Regedit by adding the key. In my couple of mailboxes I have about 100 k of emails each, which I work with on daily basis (I am a lawyer), I have to search them often, therefore I need using Windows search in Outlook (not native searching in Outlook with workaround by Regedit key because it lasts centuries). I am confused and desperate, because it is my 3rd attempt: 1) with clean install vhdx converted to vmdk (Win11 DEV) downloaded form MS official (insider_preview) 2) with clean install from UUPDUMP.net (Win11 DEV) (insider_preview) (ISO prepared in Windows) 3) and now - according to this tutorial, Win11 ISO downloaded thru CrystalFetch (official release, not insider) Currently I have simultaneously 3 vm's - the same problem on each [vmware fusion techpreview Professional Version e.x.p (22068932), Macbook Pro M1/16/1TB, Sonoma but under Ventura it was the same] The conclusion would be, that Win-guest on Mac-ARM not handling windows search in Oultook. In normal PC there is always no problem. Thank you anybody to check, to confirm the problem, and to solve the problem (hint) which I fight with since February.... 

The 2H22 Tech preview pre-dates Fusion 13 and the (July) 2023 Tech Preview version you had installed. As @palter stated, it became obsolete immediately after Fusion 13 was released last year. And it is not an “upgrade” to either Fusion 13 or the 2023 Tech Preview build you were using; it’s a downgrade.   The 2023 Tech Preview you had installed changed the algorithm for encrypted virtual machines and introduced a new virtual hardware version. A virtual machine that uses the new encryption or has a virtual hardware version of 21 can’t be opened with any other Fusion version. Reinstall the (July) 2023 Tech Preview build you had before you erroneously “upgraded” and all will be fine   Those virtual:machines will be able to be opened by the next “official” version of Fusion, when VMware releases it later this year..(and no, they haven’t said when).