Compatibility VMWare

On 27/06/2020 10:56, Fokke Nauta wrote:
Hi all,

Running W10 Pro x64. Today I started with the 2004 update. During the
update I got the message that VMWare had to be uninstalled as it is not
compatible with Windows 10. I thought this was nonsense as it has
allways been working well and still does. I purchased it and I use it,
so uninstalling was no option. I wasn't able to continue the update
process without uninstalling VMWare, so I quitted the update.
So the 2004 update is no option for me.
I hope I can skip this one and receive other updates. Let's wait and see.

Any of you had the same problem?

Fokke Nauta

Thanks all for your responses. I got the advice to look at the VMWare
forum, and I posted my problem there. The answere was that the version
that I uses (Pro 12) was not compatible with Windows 64 2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(

Fokke

On 6/28/2020 3:53 AM, Fokke Nauta wrote:
Thanks all for your responses. I got the advice to look at the VMWare
forum, and I posted my problem there. The answere was that the version
that I uses (Pro 12) was not compatible with Windows 64 2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(

Fokke

Oh well, but at least you got the answer directly from VMWare, so it's
official.

Yousuf Khan

On 28/06/2020 11:43, Yousuf Khan wrote:
On 6/28/2020 3:53 AM, Fokke Nauta wrote:
Thanks all for your responses. I got the advice to look at the VMWare
forum, and I posted my problem there. The answere was that the version
that I uses (Pro 12) was not compatible with Windows 64 2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(

Fokke

Oh well, but at least you got the answer directly from VMWare, so it's
official.

Â*Â*Â*Â*Yousuf Khan

That's true.
But weird that W10 2004 no longer supports an onder version of an
application. In the previous W10 version it worked well.

Fokke

In article , Fokke Nauta
wrote:

Thanks all for your responses. I got the advice to look at the VMWare
forum, and I posted my problem there. The answere was that the version
that I uses (Pro 12) was not compatible with Windows 64 2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(


Oh well, but at least you got the answer directly from VMWare, so it's
official.


That's true.
But weird that W10 2004 no longer supports an onder version of an
application. In the previous W10 version it worked well.

you were lucky that you didn't run into problems earlier, given that
vmware pro 12 does not support win10 1703 or later.

https://kb.vmware.com/s/article/2129859

Fokke Nauta wrote:
On 28/06/2020 11:43, Yousuf Khan wrote:
On 6/28/2020 3:53 AM, Fokke Nauta wrote:
Thanks all for your responses. I got the advice to look at the VMWare
forum, and I posted my problem there. The answere was that the
version that I uses (Pro 12) was not compatible with Windows 64 2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(

Fokke

Oh well, but at least you got the answer directly from VMWare, so it's
official.

Yousuf Khan

That's true.
But weird that W10 2004 no longer supports an onder version of an
application. In the previous W10 version it worked well.

Fokke

This is because virtual machine hosting softwares "fiddle"
the host.

You'll notice for example, that in Linux, the VirtualBox there
uses DKMS to add something to the kernel. It's interfering in
Ring0.

In the case of Windows 10 2004, Microsoft is attempting to transition
to an era where, in effect, Hyper-V is always running. And then
they can add various bad ideas to the OS, things to further
slow it down.

The various hosting softwares have to "play ball" or get "kicked to the curb".

Microsoft doesn't even allow their own stuff (VPC2007 or Windows Virtual PC)
be installed on Windows 10.

And the thing is, while new CPUs have SLAT/EPT to help Microsoft
on their Hyper-V conquest, older equipment doesn't have it. Which means
at some point, they'll be kicking old kit to the curb too. They'll
eventually realize supporting two solutions, one to keep non-SLAT
machines going, as well as SLAT machines, isn't worth it. So this
seems to be their intention in terms of "forking the hardware universe".

It all depends on how much resistance to stupid container
solutions there is.

Paul

On 28/06/2020 18:48, Paul wrote:
Fokke Nauta wrote:
On 28/06/2020 11:43, Yousuf Khan wrote:
On 6/28/2020 3:53 AM, Fokke Nauta wrote:
Thanks all for your responses. I got the advice to look at the
VMWare forum, and I posted my problem there. The answere was that
the version that I uses (Pro 12) was not compatible with Windows 64
2004.
In order to update Windows, there was no other possibility than
upgrading VMWare pro to 15.6. Unfortunately that costed me $ 180,
including tax.
That's a way to earn money :-(

Fokke

Oh well, but at least you got the answer directly from VMWare, so
it's official.

Â*Â*Â*Â* Yousuf Khan

That's true.
But weird that W10 2004 no longer supports an onder version of an
application. In the previous W10 version it worked well.

Fokke

This is because virtual machine hosting softwares "fiddle"
the host.

You'll notice for example, that in Linux, the VirtualBox there
uses DKMS to add something to the kernel. It's interfering in
Ring0.

In the case of Windows 10 2004, Microsoft is attempting to transition
to an era where, in effect, Hyper-V is always running. And then
they can add various bad ideas to the OS, things to further
slow it down.

The various hosting softwares have to "play ball" or get "kicked to the
curb".

Microsoft doesn't even allow their own stuff (VPC2007 or Windows Virtual
PC)
be installed on Windows 10.

And the thing is, while new CPUs have SLAT/EPT to help Microsoft
on their Hyper-V conquest, older equipment doesn't have it. Which means
at some point, they'll be kicking old kit to the curb too. They'll
eventually realize supporting two solutions, one to keep non-SLAT
machines going, as well as SLAT machines, isn't worth it. So this
seems to be their intention in terms of "forking the hardware universe".

It all depends on how much resistance to stupid container
solutions there is.

Â*Â* Paul

This is a sad story, Paul.
The only reason I stick to Windows is that I have so many applications
that only run on Windows.

We have an 10 years old laptop, running W7. I emptied the hard disk and
installed Linux, Zorin. It looks very familiar to W10. I'm happy with
it, it works well. We have internet and mail. So Linux has become a
proper OS, in many ways better than Windows. But I can't run my Windows
applications on it. Unless I start W10 in a virtual machine, which I
won't do in this laptop.

Fokke

Fokke Nauta wrote:
On 28/06/2020 00:31, Ant wrote:
Fokke Nauta wrote:
...
Fokke, are you using the (lat/new)est VMware version?

No, I'm using 12 Pro. 15.5 Pro is the latest. But I don't want to
upgrade as my current version works OK and an upgrade will cost me $
150,-

Yeah, that's a problem. VMware always want its users to upgrade for new
OSes to be compatible. I have gone through that over a decade when I
used its Workstation and Fusion for work (I didn't have to pay for
them).

Have you ever tried VirtualBox.org? It's free since I use that at home.



No, I haven't. And I stick to VMWare as I have quite a lot of virtual
systems.
But I got an answer from the forum. Windows 10 2004 is only compatible
with version 15. So - If I want Windows to udate to 2004, I'll have to
upgrade VMWare.



Just an option you can import VMWare to Virtualbox, pretty simple. Since
Virtualbox is 0$ won't hurt to try.

https://www.maketecheasier.com/convert-virtual-machines-vmware-virtualbox/

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On 28/06/2020 19:46, Jonathan N. Little wrote:
Fokke Nauta wrote:
On 28/06/2020 00:31, Ant wrote:
Fokke Nauta wrote:
...
Fokke, are you using the (lat/new)est VMware version?

No, I'm using 12 Pro. 15.5 Pro is the latest. But I don't want to
upgrade as my current version works OK and an upgrade will cost me $
150,-

Yeah, that's a problem. VMware always want its users to upgrade for new
OSes to be compatible. I have gone through that over a decade when I
used its Workstation and Fusion for work (I didn't have to pay for
them).

Have you ever tried VirtualBox.org? It's free since I use that at home.



No, I haven't. And I stick to VMWare as I have quite a lot of virtual
systems.
But I got an answer from the forum. Windows 10 2004 is only compatible
with version 15. So - If I want Windows to udate to 2004, I'll have to
upgrade VMWare.



Just an option you can import VMWare to Virtualbox, pretty simple. Since
Virtualbox is 0$ won't hurt to try.

https://www.maketecheasier.com/convert-virtual-machines-vmware-virtualbox/


Thanks.
I wasn't aware of that.
I already upgraded my version of VMWare this morning.

Fokke

Fokke Nauta wrote:

Thanks.
I wasn't aware of that.
I already upgraded my version of VMWare this morning.

Too bad might have saved you some $$. You might want to test
anyway...remember every 6 months we get our click-and-pray feature updates.

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Sun, 28 Jun 2020 08:49:33 +1200, Ralph Fox wrote:

On Sat, 27 Jun 2020 10:56:27 +0200, Fokke Nauta wrote:

Hi all,

Running W10 Pro x64. Today I started with the 2004 update. During the
update I got the message that VMWare had to be uninstalled as it is not
compatible with Windows 10. I thought this was nonsense as it has
allways been working well and still does. I purchased it and I use it,
so uninstalling was no option. I wasn't able to continue the update
process without uninstalling VMWare, so I quitted the update.
So the 2004 update is no option for me.
I hope I can skip this one and receive other updates. Let's wait and see.

Any of you had the same problem?

Fokke Nauta


One of the Windows 10 upgrades required me last year to upgrade VMware from
version 14 to version 15.

VMware issued an update to 14.1.8 to overcome last year's Windows updates,
so that people running v14 could continue without requiring an upgrade to
v15. I was running v14 here on Win 10 1809, so I upgraded to VMware 14.1.8
before I upgraded Win 10 to 1909. No issues. Those two upgrades, VMware and
Win 10, both went well.

Forums are reporting that VMware versions before 15.5 are blocked by MS
Software Compatibility policy. Several fixes have been discussed, with the
two most common being simply renaming the VMware executable (vmware1.exe,
for example), or by downloading the MS Compatibility Administrator and
using it to remove the block.

https://docs.microsoft.com/it-it/win...ed/adk-install

Related info:
https://www.tenforums.com/virtualization/141820-vmware-workstation-pro-cant-run-windows-message.html


I am running VMware 15.5.2 on Windows 10 1909. I see there are now VMware
versions 15.5.5 and 15.5.6 for Windows 10 20H1 build 19041.264 or newer.

I cannot see in your post which version of VMware you are running.

On Sat, 27 Jun 2020 21:28:25 +0200, Fokke Nauta wrote:

On 27/06/2020 21:00, Ant wrote:
Fokke Nauta wrote:
On 27/06/2020 17:10, Yousuf Khan wrote:
On 6/27/2020 7:26 AM, Fokke Nauta wrote:
On the VMWare site it says that concidering host operating systems
Windows 7 and above are supported. So - yet nothing about this problem.
I use Workstation Pro 12 on my system and it works well. I can upgrade
it to version 15, but that will cost me $ 150,-. And why would I as my
current version works well? Only to enable the 2004 upgrade from
Windows? I don't think so.

Fokke

I'm sure there is a solution posted on the VMWare forums on that site.
It may be something as simple as uninstall VMWare while the Win 10 v2004
is being installed, and then reinstall VMWare after Win 10 is upgraded.
Just be careful not to delete your VMWare settings during the uninstall.

****Yousuf Khan

VMWare forum. Haven't thought of that yet. I'm going to search for it.

Fokke, are you using the (lat/new)est VMware version?


No, I'm using 12 Pro. 15.5 Pro is the latest. But I don't want to
upgrade as my current version works OK and an upgrade will cost me $ 150,-

I've read forum postings that say v12 still works if you rename the
vmware.exe executable, also updating any shortcuts you might have, or by
using the Microsoft Compatibility Administrator tool to unblock VMware.
There's also a reg file floating around, but I didn't check it out.

Bottom line, your v12 should still work, but you have to jump through a
hoop.

On Sun, 28 Jun 2020 09:13:35 +0200, Fokke Nauta wrote:

On 27/06/2020 22:49, Ralph Fox wrote:
On Sat, 27 Jun 2020 10:56:27 +0200, Fokke Nauta wrote:

Hi all,

Running W10 Pro x64. Today I started with the 2004 update. During the
update I got the message that VMWare had to be uninstalled as it is not
compatible with Windows 10. I thought this was nonsense as it has
allways been working well and still does. I purchased it and I use it,
so uninstalling was no option. I wasn't able to continue the update
process without uninstalling VMWare, so I quitted the update.
So the 2004 update is no option for me.
I hope I can skip this one and receive other updates. Let's wait and see.

Any of you had the same problem?

Fokke Nauta


One of the Windows 10 upgrades required me last year to upgrade VMware from
version 14 to version 15.

I am running VMware 15.5.2 on Windows 10 1909. I see there are now VMware
versions 15.5.5 and 15.5.6 for Windows 10 20H1 build 19041.264 or newer.

I cannot see in your post which version of VMware you are running.



I am running VMWare workstation pro 12.
But I just got an answer of the VMWare forum, where I also posted this
problem. I'll have to upgrade to 15.6.

According to the good folks at VMware, I also have to upgrade to 15.5+.
However, various non-VMware forums have been posting solutions to avoid
that upgrade so I'm sticking with v14 for now. It does everything I need.

My advice is to ignore the advice you've received from VMware.

On 6/28/2020 1:57 PM, Fokke Nauta wrote:
On 28/06/2020 19:46, Jonathan N. Little wrote:
Just an option you can import VMWare to Virtualbox, pretty simple. Since
Virtualbox is 0$ won't hurt to try.

https://www.maketecheasier.com/convert-virtual-machines-vmware-virtualbox/



Thanks.
I wasn't aware of that.
I already upgraded my version of VMWare this morning.

Fokke

It wouldn't have worked, VirtualBox is having its own problems with
Windows 10's latest versions.

Yousuf Khan

Yousuf Khan wrote:
On 6/28/2020 1:57 PM, Fokke Nauta wrote:
On 28/06/2020 19:46, Jonathan N. Little wrote:
Just an option you can import VMWare to Virtualbox, pretty simple. Since
Virtualbox is 0$ won't hurt to try.

https://www.maketecheasier.com/convert-virtual-machines-vmware-virtualbox/



Thanks.
I wasn't aware of that.
I already upgraded my version of VMWare this morning.

Fokke

It wouldn't have worked, VirtualBox is having its own problems with
Windows 10's latest versions.

Yousuf Khan

What kind of symptoms should we look for ?

Paul

On 28/06/2020 23:56, Char Jackson wrote:
On Sat, 27 Jun 2020 21:28:25 +0200, Fokke Nauta wrote:

On 27/06/2020 21:00, Ant wrote:
Fokke Nauta wrote:
On 27/06/2020 17:10, Yousuf Khan wrote:
On 6/27/2020 7:26 AM, Fokke Nauta wrote:
On the VMWare site it says that concidering host operating systems
Windows 7 and above are supported. So - yet nothing about this problem.
I use Workstation Pro 12 on my system and it works well. I can upgrade
it to version 15, but that will cost me $ 150,-. And why would I as my
current version works well? Only to enable the 2004 upgrade from
Windows? I don't think so.

Fokke

I'm sure there is a solution posted on the VMWare forums on that site.
It may be something as simple as uninstall VMWare while the Win 10 v2004
is being installed, and then reinstall VMWare after Win 10 is upgraded.
Just be careful not to delete your VMWare settings during the uninstall.

Â*Â*Â*Â*Yousuf Khan

VMWare forum. Haven't thought of that yet. I'm going to search for it.

Fokke, are you using the (lat/new)est VMware version?


No, I'm using 12 Pro. 15.5 Pro is the latest. But I don't want to
upgrade as my current version works OK and an upgrade will cost me $ 150,-

I've read forum postings that say v12 still works if you rename the
vmware.exe executable, also updating any shortcuts you might have, or by
using the Microsoft Compatibility Administrator tool to unblock VMware.
There's also a reg file floating around, but I didn't check it out.

Bottom line, your v12 should still work, but you have to jump through a
hoop.


I wish I should have known.

Fokke