Build 18346.1, 18348.1, 18351.1, 18353.1, 18356.1, 18358.1 64-bit and Skippy Build 18845 64-bit will not install in VMware 15 Workstation. Working in Build 18361.1

This is the first build that will not install in VMware by either total clean install via ISO or upgrading from previous build. It gets to the windows logo and freezes there. No spinning dots, etc. On upgrade, on first reboot it freezes at same windows logo. Confirmed with another Insider on the Insider Forum using VMware.

Something has drastically changed in this build as all previous builds including skippy builds were fine.

This is from Max commenting on my post in FBH:

"Build 18346 installs correctly on a live system and in oracle VM VirtualBox.
Issue is only with VMware WS software. Also tested VMware 14 same issue."

Edit: This issue only occurs with 64-bit versions, the 32-bit will install as usual.

Revised FBH Link

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

here is a fix.. add this to vmx file of your virtual machine:

cpuid.brandstring = "VMware Fix for Windows 10 Build 18346 x64"
cpuid.1.ecx = "0--------------0----------------"
cpuid.1.edx = "-----------0---------0----------"
monitor_control.enable_fullcpuid = "TRUE"

thanks to mkuba50 from MDL forums.

 -andy-

Thanks Andy, I'll give it a try, much apricated.

FYI-- its not just this insider build either, Had VMWare on a W10 Pro, then after an update, all of a sudden the 3 VM's  ALL came up with the same error message, these were Server 2016, CentOS, W10 insider. (I say HAD because its now been replaced with Hyper-V)

Its not good if when MS do some updates and it breaks the VMware and they are not quick to resolve the problem, especially if they are business critical functions. Shouldn't have to inject "fixes" manually each time this happens.

Windows 10 - Never a dull Moment.

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

here is a fix.. add this to vmx file of your virtual machine:

cpuid.brandstring = "VMware Fix for Windows 10 Build 18346 x64"
cpuid.1.ecx = "0--------------0----------------"
cpuid.1.edx = "-----------0---------0----------"
monitor_control.enable_fullcpuid = "TRUE"

thanks to mkuba50 from MDL forums.

 -andy-

Sadly, this did nothing for me.  Still stuck at Windows Logo.  

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

18845 has just installed on my VMware 15 Workstation without any problems. 

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

18845 has just installed on my VMware 15 Workstation without any problems. 

Was that 32-bit because that installed with build 18346.1, the issue was with 64-bit John, haven't tried yet with Skippy, will do that next.

Edit: Installing 32-bit right now, there is no freeze with either Fast or Skippy builds using x86.

Johnny

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

here is a fix.. add this to vmx file of your virtual machine:

cpuid.brandstring = "VMware Fix for Windows 10 Build 18346 x64"
cpuid.1.ecx = "0--------------0----------------"
cpuid.1.edx = "-----------0---------0----------"
monitor_control.enable_fullcpuid = "TRUE"

thanks to mkuba50 from MDL forums.

 -andy-

Sadly, this did nothing for me.  Still stuck at Windows Logo.  

I will give it a try as soon as the 32-bit version of Skippy is installed. 

Edit: Adding these lines to the vmx file is working. The install is going down right now, no freeze. I added these lines to the top of the vmx file. Legsmaniac, did you make sure no vm's are running while editing this file, it won't save properly without. 

I was going to change the cpuid.brandstring for Skippy build but forgot, it is installing without the change anyhow, must just be a rem like command, the next 3 lines do the magic.

Johnny

1 person was helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Tried one more clean install with 18845.1001 with just using the 3 lines and it went through the install.

cpuid.1.ecx = "0--------------0----------------"
cpuid.1.edx = "-----------0---------0----------"
monitor_control.enable_fullcpuid = "TRUE"

Thanks Andy for finding this, and thanks to mkuba50 from MDL forums

As Wayne mentioned above, we should not have to go through this for a program like VMware so I will not mark this as answered till MS resolves this. Maybe their engineers can resolve this with the temp fix, as I have no programming skills.

We do have a temporary fix for now. Roger, can you confirm this is working for you.

Johnny

2 people were helped by this reply

·

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks.

By this method, Windows 10 Build 18346 x64 has been updated successfully!

By the way, this modification should be kept for next updates? Can I delete this part from vmx file?

P.S.

The updates have finished by this post, however the update process takes longer time by repeating "preparing","donloading","installing" many times. Is it by network conjesion or heay updates load?

macchan

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Roger, can you confirm this is working for you.

Confirmed, it works! I posted comments to FB earlier as soon as I saw Andy's reply.

Thanks to Andy and mkuba50

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Legsmaniac, did you make sure no vm's are running while editing this file, it won't save properly without. 

Ah, my bad!  Thanks for that.  I was running Linux.

Checked the file again and you're right, it didn't save.  Never thought to check. Took it for granted.

Saved and double checked and starting again.....

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

Thanks.

By this method, Windows 10 Build 18346 x64 has been updated successfully!

By the way, this modification should be kept for next updates? Can I delete this part from vmx file?

P.S.

The updates have finished by this post, however the update process takes longer time by repeating "preparing","donloading","installing" many times. Is it by network conjesion or heay updates load?

I haven't tried deleting this addition yet, it shouldn't come into play once installed, but at a minimum, I would save this in a text file somewhere as most likely will be needed again.

Not positive if this is an MS or VMware issue, does VMware have to update something now to deal with this or can MS correct this. I will report anything if it comes up in the VMware Forum as I reported this to them, along with this fix, for any other users.

I can not verify your update process as it sounds like you used Windows Update. I used an ISO from UUP dump. You may want to report that in the other thread for this build.

Johnny

Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated July 2, 2020 Views 5,351 Applies to: