VMware Communities
BenMontana
Contributor
Contributor

How I resolved Workstation Pro 17 "dysfunctional" mess

Host Platform: Windows 11
Workstation Pro 17.0+ (including todays update)

Don't want to divert or hijack the Ubuntu thread going on.

My Workstation Pro 17 slogged down to a non responding mess. This will be a "duh" message for some of you, but might help others not overthink their problem like I was. Forest for the trees case.

I got a spiffy fast Windows 11 gaming box on sale. Normally I would go Linux of some sort, but this was something I couldn't pass on core and memory wise.

Workstation Pro would start and then go unresponsive for the first 15 minutes or more. No kidding. My critical Windows 8 vm (with Quickbooks for my biz) would hang up and I'd have to "reown" it. Mint, Rocky, my other server prototypes with docker, would seize up on starting then run.

It was my antivirus, in this case Bitdefender. Other AVs would require a similar procedure. Adding exceptions to viral scanning.

I added exceptions for the entire drive that a couple vms reside on, and some folders elsewhere that had tiny server prototypes (including USB drives) and the base Workstation installation folder (c:\program files\vmware\vmware workstation) Operations vastly perked up. Then added my iso libraries and shared vm data folder and it's very zippy.

Yeah, pretty sure Bitdefender was looking at the installation iso as well.

The scan on access features of the antivirus killed Workstation Pro. I don't use Ubuntu. I don't know if ClamAV or what Ubuntu might use would cause that. This is an MS Windows specific solution. ymmv

Best regards,
Ben

Reply
0 Kudos
0 Replies