VMware Communities
LordKiRon
Contributor
Contributor
Jump to solution

Windows 10 Pro guest wan't load on Windows 10 Pro Host after update to 12.5.7

Well , just as title says, updated from 12.something (not really sure but like a half year ago) to latest 12.5.7 and since then can't start any Windows 10 guests.

The Windows freezes with round thing stopped rotating and that's it.

frozen.jpg

Next time (after power off) it tries to recover and freezes again.

Tried to start from installation ISO image - freezes too, tried to install new Windows 10 VM on new disk - freeze again both custom and "Easy mode".

Windows XP VM starts fine.

Uninstalled VMWare Workstation Pro , removed everything , even cleaned folders and registry manually and installed again - same problem.

Here is a log created (this one from failed installation attempt):

moderate note by wila: Moved the copy&paste version of vmware.log to an attachment. Please do not copy&paste log contents into a post here as it makes the thread very difficult to navigate and read. You can find an attach link at the bottom right area when posting. Note that this is only available in the discussion thread, not in the inbox.

Any ideas ?

(besides reverting to 12.0 and attempting to install one by one or reinstalling host Smiley Happy ?)

0 Kudos
1 Solution

Accepted Solutions
wila
Immortal
Immortal
Jump to solution

Hi,

Are you running AVG or Avast antivirus at the host OS?


If so then see:

XP VM suddenly slow, Win 7 fine


for a solution on using both antivirus products along with VMware


If you are running BitDefender 2017 at the host then the only solution that I am aware about is to uninstall and revert to an older version of BitDefender.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva

View solution in original post

0 Kudos
5 Replies
bluefirestorm
Champion
Champion
Jump to solution

It is a bit difficult to browse through the log you pasted. It would have made things slightly easier if it were attached as file.

Based on what I see so far, you have allocated 6656MB RAM to 8vCPUs with both "Virtualize Intel VT-x/EPT pr AMD-V/RVI" and "Virtualize Performance Counters" checked. The memory/vCPU ratio makes each 8vCPU starved for memory.

2017-07-16T23:19:15.252+03:00| vmx| I125: DICT                  numvcpus = "8"

2017-07-16T23:19:15.252+03:00| vmx| I125: DICT      cpuid.coresPerSocket = "8"

2017-07-16T23:19:15.252+03:00| vmx| I125: DICT                   memsize = "6656"

2017-07-16T23:19:15.252+03:00| vmx| I125: DICT                vhv.enable = "TRUE"

2017-07-16T23:19:15.252+03:00| vmx| I125: DICT               vpmc.enable = "TRUE"

Try with 2 vCPUs (either 2 cores per processor with 1 processor or 1 core per processor with 2 processors) with 4096MB RAM allocation. Disable the Virtualize Intel VT-x as this is only needed if you want to run another VM inside the VM. Uncheck the "Virtualize Performance Counters" as well.

0 Kudos
LordKiRon
Contributor
Contributor
Jump to solution

Thanks, I will try, but this worked before.

I more tend to blame either 12.5.7 version or somethinmg with my hardware. Since last VMware update I added Oculus Rift VR glasses  new USB 3.0 controller for them and updated Daemon Tools software, so might be something related to this. Will do a "research" on weekend.

0 Kudos
wila
Immortal
Immortal
Jump to solution

Hi,

Are you running AVG or Avast antivirus at the host OS?


If so then see:

XP VM suddenly slow, Win 7 fine


for a solution on using both antivirus products along with VMware


If you are running BitDefender 2017 at the host then the only solution that I am aware about is to uninstall and revert to an older version of BitDefender.

--

Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
0 Kudos
LordKiRon
Contributor
Contributor
Jump to solution

Yes, Avast , thank you - I will try this course as well.

0 Kudos
LordKiRon
Contributor
Contributor
Jump to solution

Thank you, indeed - disabling "Hardware assisted virtualization" in Avast settings did the trick. All starts now. Opened ticked with Avast.

0 Kudos