All Posts

First, I love the 2023 Tech Preview. I'm running a Win-11-on-ARM VM on an MBAir (M2) and it's just awesome. Thanks!  Here's my suggestion: some games (or other apps) really want the mouse to be opti... See more...
First, I love the 2023 Tech Preview. I'm running a Win-11-on-ARM VM on an MBAir (M2) and it's just awesome. Thanks!  Here's my suggestion: some games (or other apps) really want the mouse to be optimized for games. Others don't. It'd be cool to be able to determine for each (Windows) app whether the mouse should be optimized for games, or not optimized, or automatically set. UI-wise, this could work as follows: Select the mouse settings from Fusion's "settings" menu. Where you have the pull-down "Games: [always optimize][never optimize][auto]", add a link or button "optimize per app" (or similar) - and a (scrollable) list of apps with their individual mouse setting. This "mouse optimized apps" list is initially empty. When the user has clicked on that link, show a list of all apps installed on Windows, sorted alphabetically. The user selects an app. The app is added to the mouse optimized list, together with three radio buttons (per entry) "optimized", "not opimized" and "auto" (or similar; the "optimized" wording doesn't really feel right). Default is the general setting (e.g. "auto"). The user may now switch the optimization for that app by selecting another option.  Thank you very much and Have a great day,  Karl 
I'm not a VMware employee, so have no visibility to what's happening in the company or the team that develops VMware Workstation. There's doubtless things happening I'm not aware of, but as a VMware ... See more...
I'm not a VMware employee, so have no visibility to what's happening in the company or the team that develops VMware Workstation. There's doubtless things happening I'm not aware of, but as a VMware customer, it's really not a great look that a Technical Preview is launched to solicit customer feedback and there's effectively no engagement by VMware. I've personally surfaced an issue and a feature request, both unaddressed, and the issue is the survey links for this preview are broken. That was two months ago! Presumably it doesn't matter, as if anyone cared about survey responses, they'd have noticed there aren't any and so fixed it by now. The lack of any engagement by VMware seems to be a common experience among posters. What's the point of a Technical Preview if the feedback is just left not merely unresolved but not even acknowledged and responded to? People are taking the time to give constructive feedback and it's simply ignored. Doubtless Workstation Pro 17 will be a paid upgrade, and at least for me it's going to be a bitter feeling if I do fork out the upgrade cost knowing my and others' input has simply been ignored.
no i did not - since i need it for production, not testing...  
Have you tried the Tech Preview version?  It will be working close to the GA version when it is released... so it should answer your questions about your use cases.
i've tried every way that i can find to disable hyperv / VBS / credential guard using  Manage Windows Defender Credential Guard (Windows) - Windows security | Microsoft Learn it simply does not wor... See more...
i've tried every way that i can find to disable hyperv / VBS / credential guard using  Manage Windows Defender Credential Guard (Windows) - Windows security | Microsoft Learn it simply does not work it's not active by group policy, the registry entries do not exist, the bcdedit command fails.... so there is afaics no way to disable it, and my vm's keep running in ULM mode which makes them unreliable and not workable... please Vmware, release v17 asap...
Any updates  on this issue?  or work-around? This bug together with KB5019959 (BSOD of unsupported CPU)  has made my win10 VMs totally useless.  
Windows 10 or Windows 11 may BSOD in a VM on VMware Workstation while using Host VBS Mode (90134)
anyone who went the disable defender guard way?
well v17 may be released asap  cause this is driving me nuts...
The risk of using the Tech Preview in a production environment is that it is technically beta code and 100% unsupported. You can try it in development to see if it solves the issues you are encounter... See more...
The risk of using the Tech Preview in a production environment is that it is technically beta code and 100% unsupported. You can try it in development to see if it solves the issues you are encountering, but I’d wait for the Workststion 17 official release before deploying to production. 
so basically: - does workstation 22H2 solves the hyperv **bleep** i'm encountering now? * monitor mode ULM * very poor vm performance * extremely slow snapshotting * unable to install W10 22H2 u... See more...
so basically: - does workstation 22H2 solves the hyperv **bleep** i'm encountering now? * monitor mode ULM * very poor vm performance * extremely slow snapshotting * unable to install W10 22H2 update in vm's   - how safe is it to use the workstation 22H2 in production environment? - alternatively: how to get rid of ULM mode in workstation? * bcdedit to stop hyperv launch doesn't do the trick * trying to uninstall hyperv using dsim or powershell does not work - i guess cause w11 22H2 installed VBS by default (and uninstalling isn't without risk it seems (Manage Windows Defender Credential Guard (Windows) - Windows security | Microsoft Learn)  
I had the same issue with Win 10 19045 22H2 x86 (10.0.19045.2251) / on VMWare 16 Pro - 16.2.4 build 20089737 I created a VM Windows 8.x (that use scsi instead of nvme) and it worked Many thanks,
Yes, I see errors in the event log like this: Faulting application name: dwm.exe, version: 10.0.17763.831, time stamp: 0xd5c9fdea Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000... See more...
Yes, I see errors in the event log like this: Faulting application name: dwm.exe, version: 10.0.17763.831, time stamp: 0xd5c9fdea Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0x8898009b Fault offset: 0x0000000000000000 Faulting process id: 0x424 Faulting application start time: 0x01d8f6060f16f37b Faulting application path: C:\Windows\system32\dwm.exe Faulting module path: unknown Report Id: af0924aa-f9d3-4fb3-a734-9f82e998b6e4 Faulting package full name: Faulting package-relative application ID: This happens multiple times (9 times in my most recent test), 3 seconds apart, and then the guest changes resolution to 1024x768 and kicks me out to the login screen.
Do any of you see this in the Windows Event Logs of your Guest VM? Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595 Faulting module name: KERNELBASE.dll, version:... See more...
Do any of you see this in the Windows Event Logs of your Guest VM? Faulting application name: dwm.exe, version: 10.0.19041.746, time stamp: 0x6be51595 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1949, time stamp: 0xcb12e58e Exception code: 0x8898009b
I have a little more information on how this fails on my system - VMWare Workstation Pro 16.2.4 build-20089737 Host:  same problem with both Windows 10 and Windows 11 Guest:  same problem with both... See more...
I have a little more information on how this fails on my system - VMWare Workstation Pro 16.2.4 build-20089737 Host:  same problem with both Windows 10 and Windows 11 Guest:  same problem with both Windows 10 and Windows 11 This problem did not happen with an earlier version of VMWare Workstation, though I cannot tell you which specific version broke it. The symptom on my system is that any video activity, including Youtube, VLC, WMP and Unity Editor causes the screen to flicker between a black screen and a normal screen at around 2-second intervals.  This flicker occurs around 5 times and then Windows reports "Display Driver Failed to Start" and reverts to 640x480 VGA mode. If I reboot the host then the guest will run normally and video will function for at least that session.  After some time of the host being up, whether VMWare is running or not, new sessions of the guest O/S will fail.  I have not identified a specific action in the host that causes subsequent runs of the guest to fail.  After the guest fails once, it will fail every time, regardless of whether I restart VMWare Workstation between guest sessions.  The only way to get the guest to run properly again is to reboot the host. I have not seen an instance where the guest successfully plays video and then subsequently starts to fail in the same session.  It either fails from the start or succeeds from the start.  In either case, the guest will run without issue until the first attempt to do something with video.  It does not matter whether 3D acceleration is enabled or disabled.
I assume you're talking about the 22H2 Workstation Tech Preview? Evidently Microsoft's dev channel upgrader thinks there's something up with the Tech Preview. Any indication from the upgrader what i... See more...
I assume you're talking about the 22H2 Workstation Tech Preview? Evidently Microsoft's dev channel upgrader thinks there's something up with the Tech Preview. Any indication from the upgrader what it thinks the issue is? It's strange that the Tech Preview will install OK after the Windows upgrade so I guess it can't be as incompatible as the upgrader thinks it is. Wonky behavior from a beta version of Workstation and an early pre-beta version of Windows that's never been seen before. Whodathunkit?
Today i got an upgrade to Windows pro preview, release 25231. When i tried to install that update while W.T.P. is installed i got the following error message from the windows upgrade module. "VM Wo... See more...
Today i got an upgrade to Windows pro preview, release 25231. When i tried to install that update while W.T.P. is installed i got the following error message from the windows upgrade module. "VM Workstation, uninstall this app now because it isn't compatible with Windows 11"  I can only install the upgrade when I uninstall VMware Workstation T.P. and after the upgrade install VMWare again.      
Where you able to find a timeline or eta for this fox, many thanks in advance 
Do you have a timeline for this?  I'm dead in the water with this same problem.  
Hello, i tested it but the following happens: Error while opening the virtual machine: VMX file is corrupt.   Best regards Greg