eskimo682's Posts

Also stumbled upon this which holds the interesting idea of disabling the ecores in your vmx: https://communities.vmware.com/t5/VMware-Workstation-Pro/E-Core-and-P-core-support-in-VmWare-Workstation-Pro-17/td-p/2964121 When compiling, I haven't seen any throttling or parking issues myself.

Of course I had to run some benchmarks to test things out. Single thread/All.   14 pcores 2/8 14 pcores + 2 ecores Geekbench6 2249/11104 2246/9372 2277/11138 Passmark 3696/24357 3914/19043 3579/25343   So assuming pcores are used first, using only the amount of pcores seems pretty good (numvcpus = "X" and cpuid.coresPerSocket = "X"). 2 sockets and 8 logical which is what vmware uses by default if you select the maximum 16, either gets a massive hit from switching or then we are not using 16 at all, maybe only 8 (numbers would indicate we do use 16 though). Still surprised by the massive hit though, could also be benchmark related of course. Going for 16 using 2 ecores raises the full score marginally, each ecore=30%*pcore in Passmark, almost no effect in Geekbench. Going to stay at 16=14+2 then. Not for the marginal increase but it seems to work and if vmware someday would upgrade so that the virtual machine would understand ecores, maybe having 2 ecores in there would make sense. Now, if someone could prove using only 12 pcores and leaving 2 pcores and 6 ecores for the main machine because of Teams recordings or something, that would be an interesting read.

Solved (thanks to vmware support). Short recap: Originally Apparently installed some other old softwares as well as I have the 2008 and 2012 redists as well Installed 64-bit redist first Then when it did not work, 32-bit Still didn't work Note: didn't want to uninstall all older versions not to break anything even if supposed to be backwards compatible and then forgot about trying that New try Uninstalled ALL redist versions Then installed 32-bit first, then 64-bit, then rebooted (and vmware was complaining already during boot as it should) Vmware now starts Rebooted again just to get all the vmware services correct Now everything seems fine   Basically this but you really have to uninstall ALL older versions: https://answers.microsoft.com/en-us/windows/forum/all/msvcp140dll-and-vcruntime140dll-missing-error-only/6eeb77ea-3ed3-4b2b-ab8a-26fa6a0fc121

I wish, EU but have Media player (and also have it in Windows Features). Even tried with the Directplay there in case it would be old enough to have the other stuff as well. There must be something I can install to get the required files... might try installing Visual Studio 2015 or something when I get desperate enough

Same problem here but with player. Same two files and a bunch of others as well. Also WIN11 Home 22H2 and run as administrator and with every update I could find. Also redists. Didn't go as far as to install Visual Studio to fix it . Did some trials copying the missing files to syswow64 which did get rid of the not founds but then ended with a version mismatch 0xc000007b instead. This just because I could see the files on Windows10 existing both under system32 and syswow64 so just in case... manual copying might of course skip some necessary dependencies. Vmware runs fine on three other Win11 recently set up in the last month. All Win11 Pro though. Also tried vmware15 pro but that failed installing with a error and no text -> rollback.  Didn't find a sensible error in vminst.log that could explain things (but when it's 15K long...).

Finally had some time to look at this again during the holidays which means taking a full backup and finally allowing Windows to update itself (since this thread has been here a while, better mention I was running Windows 8.1 on the server). Hey presto, someone has fixed something somewhere (not sure when I tried last so fixed sometimes in the last 3-4 months). Since I didn't update Avast at this point yet, apparently this was a Windows issue. Vmware now stays up properly again after rebooting.

I have my server on a weekly reboot/backup/restart cycle and apparently the starting up now just doesn't work with vmware. Sooner or later the server ends up in a BSOD cycle. On vacation for 8 days so disabled my maintenance and will just hope the server stays up otherwise. Don't really want to toss Avast, have it on every other computer so having something different on the server... hmmm. I already have the vmware directories as exceptions but will test having the rootkit shield off as well. Doesn't really matter if it's vmware, Avast or some new Windows component that causes this. Unless someone already has opened a ticket, it's about time (won't myself because on vacation so will not be helpful). If nothing else, I will either report more here and/or test without Avast once I'm back.

I had a similar issue but didn't touch Avast while attempting fixes. Stable for 6h now so I'll post my findings for future reference. How I got into the mess: I run Windows Update which installed KB4507004 KB4507449 KB4506997 After this I performed a disc cleanup while copying 200-300G at the same time (100M/s disk speed glowing red). Since this is my server I often let it handle heavy tasks regardless of how inefficient it is to run much disc activity at once. At some point I realized the copying from my main machine had stopped and lo and behold, the server had booted. While investigating it booted again... and again... and again. At this point I shut down vmware autorunning my sql server virtual machine not to destroy it. And no more BSOD. Huh? I doubt system stress was the reason although the first crashes were all MULTIPLE_IRP_COMPLETE_REQUESTS (and it's over 10 years since vmware had these problems before - quick check of the forum). I just haven't had crashes before even when copying terabytes between ssd's and normal HDD's. Also, everything is just fine, until I start a virtual machine (no, I didn't start another just to check if the important one had become corrupt). Run the virtual machine and within minutes, BSOD. Tried this a few times. Ok, vmware (player) is causing a serious problem at least with this virtual machine. Uninstalled the KB's Windows Update added. Start the virtual machine and BSOD. Downloaded the newest version of Vmware Player, rebooted, start vm... bang. At this point BSOD's are not even getting to the login screen in the vm anymore, from the logs I can see vmware restoring at 1%...5%...93% and bang. Uhum. Run sfc /scannnow and disk checking on the server. Virtual machine on... bang. NOT GOOD. Since it was around midnight at this point I called it a day. Since I spent like 8h resolving this with long breaks I doubt just waiting would have helped. Just mentioning it since I took a longer break going to sleep. Next day I copied the virtual machine to my main machine, where it started nicely. Run sfc and disk checking and rebooted a few times with shutdowns, everything just run fine. Transferred the vm back to my server, started it... crossed my fingers... and it has stayed up since. Guess I'm not installing those Windows updates again in a while although removing them didn't help. Here are the 3 BSOD's that were occurring (IRP's was most common at the start), just copied some here: On Wed 17/07/2019 18:32:33 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x1E (0x0, 0x0, 0x0, 0x0) Error: KMODE_EXCEPTION_NOT_HANDLED Dump file: C:\Windows\Minidump\071719-47673-01.dmp file path: C:\Windows\system32\ntoskrnl.exe On Wed 17/07/2019 16:34:58 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x44 (0xFFFFFA800DCA09D0, 0xEC0, 0x0, 0x0) Error: MULTIPLE_IRP_COMPLETE_REQUESTS Dump file: C:\Windows\Minidump\071719-46550-01.dmp file path: C:\Windows\system32\ntoskrnl.exe On Wed 17/07/2019 16:24:01 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x44 (0xFFFFFA800726C010, 0xEC0, 0x0, 0x0) Error: MULTIPLE_IRP_COMPLETE_REQUESTS Dump file: C:\Windows\Minidump\071719-50903-01.dmp file path: C:\Windows\system32\ntoskrnl.exe On Wed 17/07/2019 16:05:48 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x44 (0xFFFFFA800A32B010, 0xEC0, 0x0, 0x0) Error: MULTIPLE_IRP_COMPLETE_REQUESTS Dump file: C:\Windows\Minidump\071719-50279-01.dmp file path: C:\Windows\system32\ntoskrnl.exe On Wed 17/07/2019 15:34:53 your computer crashed This was likely caused by the following module: ntoskrnl.exe Bugcheck code: 0x3B (0x80000004, 0xFFFFF80003255008, 0xFFFFF880037B0F10, 0x0) Error: SYSTEM_SERVICE_EXCEPTION Dump file: C:\Windows\Minidump\071719-56955-01.dmp file path: C:\Windows\system32\ntoskrnl.exe I have a copy of the original vm that was causing all this. I probably should try to start it once to see if it still bsods but I kinda don't want to end up in a mess again. In case vmware support sends me a request to "do this, then this to make sure you get everything possible logged" I might do it just to find a root cause for this. After taking full partition backups of the entire server so not a small operation. But eventually I will toss the "faulty" vm. Knowing me that might be 5 years from now. Ok, pretty lengthy and somewhat detailed. But as other people have had problems, avast or not, it's better to have more info if this is something new and common.

Finally had time to do some testing (and then realized it might be moot). Didn't find anything conclusive anyway but will list my steps. All this on the secondary Win10 system where I switched back to 12.1 to get anything working three weeks ago. Upgraded (again) to 12.5 (note not 12.5.1 yet as I was curious what eventually fixed the issue for me). The interesting thing here is that the virtual machine crashed once bluescreen style/VMware caught, then actually worked. Maybe going back to 12.5 after using 12.1 kept the network on for this test. No idea. The vm was working in tar mode though, dead slow. Updated the Intel chipset and Realtek drivers (which I imagined fixed things last time). Still works, still tar. Upgraded to 12.15.1, tar disappeared. Good enough for me for now. Hate not knowing the exact fix earlier and definitely not feeling confident at the moment but no point spending more time on this. Time for a backup of one vm followed by a VMware tools update hoping that won't break things :smileygrin: .

Ok, now I actually have some good info. Decided to have one last go today and now all the problems went away. Went through all the Asus/Intel drivers and installed (new) versions of them (not necessarily the newest on the net but from the installation CD - thinking those on the CD are least likely to be broken). And no, I did not record each version number as I was grasping at straws at this point. Possibly the latest Windows updates "upgraded" (or downgraded knowing MS )  one of these and that's the culprit (for me)? So these are for Asus Z170-K but I imagine some of the Intel/Realtek drivers are "generic". Intel chipset 10.1.1.7  (pretty much guessing it is either this one) Realtek Lan Driver 10.1.505.2015 (or this one) Management Engine Interface 11.0.0.1157 (which I selected but it did NOT install - not shown as installed at least) ...and the less likely ones... (listing everything for reference) Intel Rapid Storage 14.5.0.1081 Asmedia usb3.1 1.16.26.1 Asus AI suite 3 1.01.24 Hopefully this helps someone. As for the really good news, since I have this exact same problem and plenty of copies of "bad" vm's to test with I can probably come up with the exact driver which helped by doing one by one on my backup WIN10. Well, helped me at least... Now I need to get some work done... maybe in 1-2 days. Or maybe someone else can verify my hunch about the chipset/realtek drivers meanwhile?

Ok, now things got really bad . I tried VMware-player-12.1.1-3770994 (on my backup Win10 partition) last night (skipped enchanced keyboard if it asked, don't remember). Then reinstalled 12.5 on the main win10 (skipping enchanced keyboard). Now I'm getting the following if I try to use 12.1 (on a vm that has the bridged problem). And the 12.5 gets the same so I cannot even start without a bridged network anymore: "This virtual machine is configured for 64-bit guest operating systems. However, 64-bit operation is not possible. This host supports Intel VT-x, but Intel VT-x is disabled." and "Binary translation is incompatible with long mode on this platform. Long mode will be disabled in this virtual environment and applications requiring long mode will not function properly as a result. See http://vmware.com/info?id=152 for more details." Running a 64-bit host and a 64-bit vm. Haven't changed anything in the bios. Ok, time for hands off until I can read about everything. Restored an old vm which runs ok on 12.1. Unfortunately I don't have time for all this mess right now so I'll have a look in a few days. Clearly need to do this systematically and without deadlines. Even if it means installing Windows 7 somewhere temporarily...

The dreaded "The network bridge on device 'VMnet0' is not running.  The virtual machine will not be able to communicate with the host or with other machines on your network.". Apparently this has not been solved yet? Can provide logs&al if needed. Some info: 1. No solutions have worked yet. 2. Nothing running. 3. "Enhanced Keyboard Driver" on VMnetUserif regedit, no effect. VMware NAT Service, no effect. Rebuilding my entire network right now so this doesn't have high priority but I think I know when this went bad so I'll give some quick info in case it would be helpful: MB: Asus Z170-K (Intel) Windows 10 Pro, installed 2016.10.06 + updates Installed VmPlayer 12.5.0.4352439 on 2016.10.11 (and at that point bridged networking was working fine) 2016.10.14 Windows update did some major lengthy update (Feature update, version 1607) 2016.10.15 Update for Windows 10 Version 1607 for x64-based Systems (KB3176936) - worked past midnight 2016.10.15 Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3194343) Bang - no more bridged network Do not have a physical DVD player installed on this machine yet (will try that one out tomorrow, vmtools hunch -> edit: was a longshot, no effect) Since people have had this issue a month ago it's not "only" the Windows update that is the culprit but that apparently was the deciding factor for me.

Things work better with Player 12 but there are still issues like intermittent sound choking or graphics bottlenecks. But I can live with it as it's not something mission critical. As for licensing, maybe there is some offer some day that will have me return as a paying customer. Not giving up on VMware yet :smileygrin: .

Ok, this explains it somewhat so ty very much for pointing me in the correct direction. http://www.pcworld.com/article/2970075/windows/why-you-cant-find-your-product-key-after-upgrading-to-windows-10.html A real horror for me though as I will have no change of verifying whether my Digital Entitlements actually will work or not later on. Guess I will at least do a clean install on some dummy partition on all real computers for at least one license each.