Anyone knows anyway to get rid of the annoying toast messages "No 3D support from Host" and "Click I finished installing to install tools" etc ? I'm sick to death having to put them away from view.
Go to where VM like Windows 10 for example, go click Edit virtual machine settings, then go to "Display" then uncheck "Accerlerate 3D graphics" then click ok, and will stop pop up the problems.. ATGPUD2003
General it was good, if it was work with windows 11 protections turned like core isolations nd any bsod after when putted on vista/7 updates from windows servers. How I told. Or someone find fixing that? But not type to turn off all what to hyperv vbs, etc.
Windows 11 is still not ready for prime time, especially 24H2, but Microsoft wants to push that to everyone on current editions. I use ESXi 6.7 virtual machine compatibility settings for Windows 7 or higher VMs. I'll be trying VMware 16.1 soon on Windows 10 LTSC 2019. Currently all fine with the latest VMware 15. On newer versions they removed many features. My two cents.
So you don't use VMware 17.x ? Why that ESXI compatible? It put some special function? I saw VMware 15.x has some problems on Windows 11. Windows XP, I know, haven't that acceleration 3D supported. About modifications, I test older windows with that tricks with ESUs what people here put on MDL how work and VMware put BSODs when put update from servers for Vista/7. And that I don't know how skip fix
Can be fixed in vmwarecui.dll: B3 01 EB 05 8A 7D DF 32 DB 8B 4D D0 8B 49 20 85 B3 00 EB 05 8A 7D DF 32 DB 8B 4D D0 8B 49 20 85
Windows 11 23 H2 and Windows 7 any problems. Vista and XP will be test soon. Actually who try go in 24 H2 better stay 23H2.
Please, can anyone with NVidia GeForce card confirm this PotPlayer issue? https://forums.mydigitallife.net/threads/update-vmware-products.36557/page-21#post-1857351 Host Windows 10 Pro Guest Windows 10 Pro/11 Pro VMWare Pro, free - latest Thanks. (I had to go back to v17.5.2)
We know since the new amd cpus disaster that administrator account just bypasses vbs / core isolation thing So it's nothing new at all Proper solution is to completely disable vbs in your boot file (hypervisor), which means you can't use hyper-v, wsl and wsa But it doesn't matter, VMware workstation works very bad with active hyper-v anyway if the guest os isn't x64