Jimic0915
Contributor
Contributor

After UPGRADE to VMware 12 cannot boot Win10

Jump to solution

Hi,

I recently upgrade my MAC to Big Sur and also update VMware Fusion from 11 to 12.

After that, when I tried to launch Win10 VM, it stuck at Windows icon always. (Boot Ubuntu OS is fine BTW)

Screen Shot 2021-04-21 at 12.09.19 PM.png

 Also tried boot manager to perform Windows Automatic Repair but also hung.

 

Try to gather info from logs but not sure what went wrong, could someone help?

Spoiler

2021-04-21T12:08:26.710-07:00| VMware Fusion| I005: /Users/tzchou/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Windows 10 x64.vmx: Disconnect check in progress.

2021-04-21T12:08:26.712-07:00| vix-async-pipe| I005: /Users/tzchou/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Windows 10 x64.vmx: Connected to testAutomation-fd, remote end sent pid: 13761

2021-04-21T12:08:26.713-07:00| VMware Fusion| W003: DnDCPTransportMKSControl::SendPacketAborted failed (Operation aborted).

2021-04-21T12:08:26.713-07:00| VMware Fusion| W003: DnDCPTransportMKSControl::SendPacketAborted failed (Operation aborted).

2021-04-21T12:08:26.713-07:00| VMware Fusion| I005: VMMKS::CheckAndAttach: pipe name: mksctrl-0000013761-000-3fe667d3, can attach: false, is remoting: false.

2021-04-21T12:08:26.715-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 4, running status: 1

2021-04-21T12:08:26.715-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: Tools status is OUTDATED

2021-04-21T12:08:26.741-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 4, running status: 1

2021-04-21T12:08:26.741-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: Tools status is OUTDATED

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: cui::VMPolicyVMDB::GetServerUpdates: VM does not use Server, cancel the retrieving and the configuration for callback.

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: OnVMStateChanged: alive = 1

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: VMMKS::CheckAndAttach: pipe name: mksctrl-0000013761-000-3fe667d3, can attach: true, is remoting: false.

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: CUIMKS: cui::MKS::SetAttached (7FD465AFAC00): attach

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: MKSControlClient: New mksControl data (client: 7FD4649D3660).

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: MKSControlClientData: Created mksControl data 7FD464085200.

2021-04-21T12:08:26.746-07:00| VMware Fusion| I005: SOCKET creating new socket, connecting to /tmp/vmware-tzchou/mksctrl/mksctrl-0000013761-000-3fe667d3

2021-04-21T12:08:26.747-07:00| VMware Fusion| I005: UtilMacOS: Found graphics devices

2021-04-21T12:08:26.749-07:00| VMware Fusion| I005: Initialized the Metal renderer.

2021-04-21T12:08:26.749-07:00| VMware Fusion| I005: cui::MKSScreenView::SetRenderTarget: hostWindow and surfaceID are none. id: 0.

2021-04-21T12:08:26.750-07:00| VMware Fusion| I005: cui::MKSScreenView::OnHostWindowChanged, id: 0, unsetting destination and setting is rendering to false

2021-04-21T12:08:26.750-07:00| VMware Fusion| I005: -[UIDrawnMKSController initWithWindowId:view:portName:], starting UIDrawnMKS rendering

2021-04-21T12:08:26.751-07:00| VMware Fusion| I005: UtilMacOS: Found graphics devices

2021-04-21T12:08:26.753-07:00| VMware Fusion| I005: Initialized the Metal renderer.

2021-04-21T12:08:26.765-07:00| VMware Fusion| I005: -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1

2021-04-21T12:08:26.765-07:00| VMware Fusion| I005+ .

2021-04-21T12:08:26.964-07:00| VMware Fusion| I005: -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1

2021-04-21T12:08:26.964-07:00| VMware Fusion| I005+ .

2021-04-21T12:08:26.970-07:00| VMware Fusion| I005: -[DUIVMActionController currentTogglePowerOnSuspendAction] VMCanNotSuspend UI power state 1

2021-04-21T12:08:26.970-07:00| VMware Fusion| I005+ .

2021-04-21T12:08:27.117-07:00| VMware Fusion| I005: CUIMKS: cui::MKS::OnSetAttachedCompleted (7FD465AFAC00)

2021-04-21T12:08:27.123-07:00| VMware Fusion| I005: SOCKET 16 (52) AsyncTCPSocketSetOption: Option layer/level [6], option/name [1]: could not set OS option for TCP socket; error [102: Operation not supported on socket].

2021-04-21T12:08:27.133-07:00| VMware Fusion| I005: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

2021-04-21T12:08:27.136-07:00| VMware Fusion| I005: SnapshotTree: Emitting refresh (/Users/tzchou/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Windows 10 x64.vmx)

2021-04-21T12:08:27.136-07:00| VMware Fusion| I005: SnapshotTree: Populating (/Users/tzchou/Documents/Virtual Machines.localized/Windows 10 x64.vmwarevm/Windows 10 x64.vmx)

2021-04-21T12:08:27.145-07:00| VMware Fusion| I005: UtilMacOS: Found graphics devices

2021-04-21T12:08:27.146-07:00| VMware Fusion| I005: -[UIDrawnMKSController initWithWindowId:view:portName:], starting UIDrawnMKS rendering

2021-04-21T12:08:27.168-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: The guest is a supported version of Windows, checking Tools status. Version status: 4, running status: 0

2021-04-21T12:08:27.168-07:00| VMware Fusion| I005: OnGuestCanRunUnityChanged: Tools status is OUTDATED

2021-04-21T12:08:27.718-07:00| VMware Fusion| I005: VMHSGetDataFileKey: Could not get the dataFileKey from VMDB

2021-04-21T12:08:48.626-07:00| VMware Fusion| I005: -[DUIKeyboardMouseConnection handleGUIKeyState:], valid key up -> lost focus event. asking MKS to drop pending GUI key. timeDeltaMS: 1764, guiKeyDelay: 300

2021-04-21T12:09:33.843-07:00| VMware Fusion| I005: -[DUIKeyboardMouseConnection handleGUIKeyState:], valid key up -> lost focus event. asking MKS to drop pending GUI key. timeDeltaMS: 2083, guiKeyDelay: 300

2021-04-21T12:16:02.224-07:00| VMware Fusion| I005: -[DUIKeyboardMouseConnection handleGUIKeyState:], valid key up -> lost focus event. asking MKS to drop pending GUI key. timeDeltaMS: 3398, guiKeyDelay: 300

2021-04-21T12:16:07.511-07:00| VMware Fusion| W003: Running support tool: /Applications/VMware Fusion.app/Contents/Library/VMware Fusion Problem Reporter.tool -u tzchou

2021-04-21T12:16:07.511-07:00| VMware Fusion| I005: AppleXPC: Connecting to privileged service com.vmware.IDHelper...

2021-04-21T12:16:14.172-07:00| VMware Fusion| I005: AppleXPC: Connection established to service com.vmware.IDHelper

2021-04-21T12:16:14.172-07:00| VMware Fusion| W003: The collect support info process ID: 15055, fd = 55

2021-04-21T12:16:14.172-07:00| host-103342| I005: AppleXPC: Connection lost to service com.vmware.IDHelper.

2021-04-21T12:23:30.666-07:00| VMware Fusion| I005: -[DUIKeyboardMouseConnection handleGUIKeyState:], valid key up -> lost focus event. asking MKS to drop pending GUI key. timeDeltaMS: 1357, guiKeyDelay: 300

 

Moderator note by wila: Moved the log snippet into a spoiler

 

0 Kudos
1 Solution

Accepted Solutions
wila
Leadership
Leadership

Hi,

Ok, thanks for the logs.

Your CPU is an intel i7-9750H, which has no vPro features.
As such, nested virtualization would make it really slow (the checkboxes under settings -> Processors & Memory -> Advanced options -> I suggest to keep any of those checkboxes unchecked

I think that is the case for your VM, but it won't hurt to check.
Also noticed you assigned 4 vCPU's which should be fine, but I personally would not assign more than 2 on a 6 core physical CPU (threads don't count).

Please change the virtual hardware back to something more recent than version 12

For troubleshooting purposes (to see if we can get your VM to boot properly) I suggest to make the following - temporary - changes to the VM's configuration.

You have a bunch of shared folders configured, for now I suggest to disable them (enable them back after you managed to reboot normally).

Also disconnect the CDrom, any USB devices that are connected to your host, disable 3D acceleration for the moment as well (settings -> display), change the CPU's from 4 cores down to 2 cores.

The lines that I see in the log that surprise me are these:

2021-04-22T11:19:06.011-07:00| vcpu-2| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80402c8c470 count=1
2021-04-22T11:19:06.011-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=1
2021-04-22T11:19:06.011-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=2
2021-04-22T11:19:06.012-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f9826f count=3
2021-04-22T11:19:06.013-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f967c4 count=4
2021-04-22T11:19:06.013-07:00| vcpu-2| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80404f967ea count=2
2021-04-22T11:19:06.015-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x1a0]:=0 (sinking): rip=0x126a3 count=1
2021-04-22T11:19:06.015-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x1a0]:=0 (sinking): rip=0xfffff80404f979a0 count=2
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: APIC CMCI LVT write: 0x100d8
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80402c8c470 count=1
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=1
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=2
2021-04-22T11:19:06.017-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f9826f count=3
2021-04-22T11:19:06.017-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f967c4 count=4
2021-04-22T11:19:06.018-07:00| vcpu-3| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80404f967ea count=2
2021-04-22T11:19:07.369-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000100] 0x7e
2021-04-22T11:19:07.369-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000101] 0xffffffffc0000094
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000102] 0xfffff80404a7eebe
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000103] 0xffffd486df6b37c8
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000104] 0xffffd486df6b3000
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+

 I left off a few lines for vCPU0 and vCPU1..

VMware is trying to read/write to special registers in your CPU and it cannot, which then results in the "WinBSOD" from the looks of it.

I was thinking that my suggestion about the shared folders was irrelevant in this case, but then I saw (&remembered this)
https://communities.vmware.com/t5/VMware-Workstation-Pro/Shared-Folders-in-Win-10-guest-triggering-b...

and sure enough you have several overlapping shared folders.... so it looks like you only need do disable your shared folders (remove the overlapping ones) in order to resolve this.

--
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
6 Replies
wila
Leadership
Leadership

Hi,

Please check the following setting, menu -> Virtual Machine -> Settings -> Advanced -> "Disable Side Channel Mitigations

Is it checked?

If so, then try to uncheck it and then see if you can boot.

If that doesn't help then please attach a FULL vmware.log file, not just a snippet.

edit: check/uncheck confusing 🙂

--
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
Jimic0915
Contributor
Contributor

Hi Wila

I have tried check/uncheck "Disable Side Channel Mitigations" but got the same result.

Hung under "Preparing Automatic Repair" Windows screen

Screen Shot 2021-04-21 at 10.54.41 PM.png

Thanks for your help!!

0 Kudos
wila
Leadership
Leadership

Hi,

I notice that you are on VMware Fusion 12.0.0, not on Fusion 12.1.1

So the first thing to do is upgrade to the latest.
The latest VMware Fusion version can be downloaded here: https://vmware.com/go/getfusion

Sadly the attached log file is not the one I need (I guess I should have been more clear), what I need is the vmware.log files, which are specific for the VM, not the vmware-vmfusion.log, which are for the GUI.

The vmware log files to look at are saved in your virtual machine bundle.

You can find them via VMware Fusion Virtual Machine Library screen.

In the Library, select the virtual machine, then right click (or in apple terms: control+click, don't hold down the control key after clicking) and select "Show in Finder". That should open Finder with the current VM bundle selected.

With the VM bundle select right click again, this time select "Show Package Contents".

This will open the virtual machine bundle and show you all the files it is made up of.

Locate the vmware.log files, select them via command+click one by one and right click again, select "Compress n items". That by itself will create an archive.zip file which you can add to the reply down here.

--
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
Jimic0915
Contributor
Contributor

Hi Wila,

Upgraded to 12.1.1 got the same error.

Also tried to adjust hardware version 12, 16 and 18 under compatibility but no help.

vmware.log attached. Thanks.

 

0 Kudos
wila
Leadership
Leadership

Hi,

Ok, thanks for the logs.

Your CPU is an intel i7-9750H, which has no vPro features.
As such, nested virtualization would make it really slow (the checkboxes under settings -> Processors & Memory -> Advanced options -> I suggest to keep any of those checkboxes unchecked

I think that is the case for your VM, but it won't hurt to check.
Also noticed you assigned 4 vCPU's which should be fine, but I personally would not assign more than 2 on a 6 core physical CPU (threads don't count).

Please change the virtual hardware back to something more recent than version 12

For troubleshooting purposes (to see if we can get your VM to boot properly) I suggest to make the following - temporary - changes to the VM's configuration.

You have a bunch of shared folders configured, for now I suggest to disable them (enable them back after you managed to reboot normally).

Also disconnect the CDrom, any USB devices that are connected to your host, disable 3D acceleration for the moment as well (settings -> display), change the CPU's from 4 cores down to 2 cores.

The lines that I see in the log that surprise me are these:

2021-04-22T11:19:06.011-07:00| vcpu-2| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80402c8c470 count=1
2021-04-22T11:19:06.011-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=1
2021-04-22T11:19:06.011-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=2
2021-04-22T11:19:06.012-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f9826f count=3
2021-04-22T11:19:06.013-07:00| vcpu-2| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f967c4 count=4
2021-04-22T11:19:06.013-07:00| vcpu-2| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80404f967ea count=2
2021-04-22T11:19:06.015-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x1a0]:=0 (sinking): rip=0x126a3 count=1
2021-04-22T11:19:06.015-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x1a0]:=0 (sinking): rip=0xfffff80404f979a0 count=2
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: APIC CMCI LVT write: 0x100d8
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80402c8c470 count=1
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=1
2021-04-22T11:19:06.016-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80402c8c657 count=2
2021-04-22T11:19:06.017-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f9826f count=3
2021-04-22T11:19:06.017-07:00| vcpu-3| I005: SetMSR: unknown MSR[0x8b]:=0 (sinking): rip=0xfffff80404f967c4 count=4
2021-04-22T11:19:06.018-07:00| vcpu-3| I005: GetMSR: unknown MSR[0x17] (read as zero): rip=0xfffff80404f967ea count=2
2021-04-22T11:19:07.369-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000100] 0x7e
2021-04-22T11:19:07.369-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000101] 0xffffffffc0000094
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000102] 0xfffff80404a7eebe
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000103] 0xffffd486df6b37c8
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+
2021-04-22T11:19:07.370-07:00| vcpu-1| W003: WinBSOD: Synthetic MSR[0x40000104] 0xffffd486df6b3000
2021-04-22T11:19:07.370-07:00| vcpu-1| W003+

 I left off a few lines for vCPU0 and vCPU1..

VMware is trying to read/write to special registers in your CPU and it cannot, which then results in the "WinBSOD" from the looks of it.

I was thinking that my suggestion about the shared folders was irrelevant in this case, but then I saw (&remembered this)
https://communities.vmware.com/t5/VMware-Workstation-Pro/Shared-Folders-in-Win-10-guest-triggering-b...

and sure enough you have several overlapping shared folders.... so it looks like you only need do disable your shared folders (remove the overlapping ones) in order to resolve this.

--
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
Jimic0915
Contributor
Contributor

Hi Wila,

It worked.

The shared folder already turned off so did not touch them. I changed the processor to 2 and turn off 3D acceleration then able to get through Windows automatic repair page.

I guess it's some display compatibility issue causing freeze screen.

Thanks for your amazing help. Really appreciate.👍

0 Kudos