CharlesGilley
Contributor
Contributor

Are there issues with Windows 10 1909 with Workstation 15.5.0?

I have a number of VMs I use from time to time.  Silly me, I really need to learn to back them up prior to letting Microsoft update Windows 10.  Anyway, I was happily running on 1903 when MS pushed out 1909.  Now the VM is a slug, taking forever to boot with slow UI responses.  Yes, I know I could have reverted, but I missed my 7 day window.

Would an upgrade to 15.5.1 help me out?

I'll add another question - does VMWare post anywhere compatability tests or warnings?

Regards,

C. Gilley

Edit: removed the 1903 reference from the title

Tags (1)
0 Kudos
12 Replies
CharlesGilley
Contributor
Contributor

Well poking around the kb article, I see 1909 is not in the list.  Hopefully there will be an update soon.

0 Kudos
CharlesGilley
Contributor
Contributor

Can anyone point me to a support location that might show predicted 1909 support plans?

0 Kudos
WhiteKnight
Hot Shot
Hot Shot

I can only relate to my personal experience ...

Upgrading Windows 10 is always a mess on my machines, regardless of host or guest OS.

Such upgrade is, in fact, a new installation of Windows 10 + restoring a number of Windows Registry keys. Unfortunately, some drivers (and application software) seem to store (or rely on) registry key paths which are not restored in the course of the new installation.

So, since my installations all exhibit similar bad behavior to yours', I re-install all my hosts and guests every 6 months. *sigh*    



[VMware]: Workstation 16 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
LongRangeSkeet
Contributor
Contributor

I am currently experiencing somewhat of an issue with 15.5.1 on 1909.

vmware-hostd.exe stopped working in Reliability Monitor

Is it really true, like someone said, that the software doesn't support the latest Windows build? It would be really sad that one of the largest VM companies can't make their program run well on an updated Windows machine.

0 Kudos
RDPetruska
Leadership
Leadership

You may have luck trying the Tech Preview on the latest Win 10 builds.

It would be really sad that one of the largest VM companies can't make their program run well on an updated Windows machine.

Blame Microsoft for making major underlying changes to their OS while still calling it the same OS name/version!

0 Kudos
LongRangeSkeet
Contributor
Contributor

1909 has been out since last November though. Shouldn't that be plenty of time for a large company such as vmware to make their software work nicely with an operating system?

0 Kudos
CharlesGilley
Contributor
Contributor

No, it really isn't it.  If I had to criticize VMWare, they just are not proactive about this issue.  But that's a very light criticism, I mean, think about what they are trying to do - match up with Microsoft?  Ponder that for a second, a minute, a bottle of vodka.

VMWare should have a "Windows Compatibility Page" link.  It would not be hard.  But in all fairness, I myself have shot my toes off twice.  so, best practices:

1) ooooo, my Windows 10 VM wants to update.... yellow post-it says bang head against wall.  Check 2nd post-it

2) BACK UP YOUR VM!!!!!

3) proceed with updates.

Anyone running VMWare Windows anything installations should follow this process.  Control C/V will save you from a world of hard ache

0 Kudos
LongRangeSkeet
Contributor
Contributor

I bought vmware because it seems to support USB devices better than virtualbox.

Is there a better VM alternative to run on a Windows host?

0 Kudos
wila
Leadership
Leadership

Hi,

Control C/V will save you from a world of hard ache

Yep true. I also have a product that can help for doing this automatically (see my signature)

Bonus is that you don't even have to shut down your vm.

Though LongRangeSkeet is complaining about having his host updated to Windows 10 1909 and seeing some errors.

I'd say that as long as your VMware works as intended.. you can ignore those errors, but I do agree that they are indeed not supposed to be there.

Hopefully somebody from VMware will jump in on your topic and ask for more details like crash reports and logs.

Without either of those it is pretty hard to say what the problem is and we can't help without more details.

"App Crash" really isn't sufficient info to say something sensible.

--

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

Hi Charles.

I've been facing the same exact problem hence landed here as a result of a Google search.

I have an Intel NUC https://www.amazon.in/Intel-Core-Mini-32GB-Professional/dp/B07K44BSTJ The combination of 15.5.1 + Windows 10 1909 [18363.657] build is perfectly working without any problem! My Guest VMs don't give me any problems whatsoever.

Now I have a Lenovo P520 Workstation with 2 TB SSD from Samsung, Xeon Processor and everything. 15.5.1 + Windows 10 1909 [18363.657] is giving me serious problems when it comes to Guest VMs. Right from installing a brand new guest to normal UI being sluggish and so on.

I agree I can't spot 1909 in their supported list either but seriously, VMWare has to do better here. This is not the first time I've stumbled into a problem like this. I remember the 15.0 > 15.1 transition.

VMWare - a comment please!

Thanks,

Vikas

0 Kudos
Hermod69
Contributor
Contributor

Hi,

Anyone solved this issue?

I have VMware Workstation 15.5.6 build-16341506. After my computer was upgraded to build 1909 of Windows 10, i got messages that my computer is not compatbile.

Se attachment.

I have done alle the things that the link say i should do.

Anyone have a idea?

Regards,

Hermod Svingerud

0 Kudos
Dryne
Enthusiast
Enthusiast

For me, VMWare guest has handled all Windows 10 updates better than my host machine has.  My guest updated to the absolute latest Windows 10 2004 update without any issues.  My host consistently failed Windows 10 updates starting in March of 2020 and has been failing every month after that.  Only after complaining bigtime on Microsoft community forums about how poor Microsoft's quality is did someone on Microsoft's end take action that results in successful Windows 10 1909 updates to the latest version.

I really bad mouthed them telling them that Windows 3.1 was more reliable than this garbage.  I think my words hurt resulting in my updates magically installing next try :smileygrin:

0 Kudos