Compatibility VMWare

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

Fokke Nauta wrote:

Any of you had the same problem?

Presume the problem is hyper-V related? I remember when win10 sandbox
was introduced it b0rked virtual box ...

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

This is potentially caused by the WSL2 and Sandbox options
in Windows Features. But when I look in there, I see a ton
of stuff that wasn't there before, and might potentially
interact with Hyper-V.

https://i.postimg.cc/pLqnMLSz/lots-of-interference.gif

VirtualBox was supposed to have "acquired" a capability to
"run under HyperV hypervisor". With Microsofts interest in
containers and Russian Dolls, it's inevitable that sooner
or later, virtualization software would "bump heads" with
the company making the OS.

I suspect that's why your VMWare got "bumped off". It didn't
make a version that runs under HyperV, which would prevent
Microsoft from turning on HyperV and using it for everything
under the sun.

Another possibility, is your machine doesn't have SLAT/EPT
(Second level address translation/Extended Page Tables). Check
your CPU feature set for the details. I only have one machine
with EPT here. AMD calls it one thing, Intel calls it the other.

Normally, hypervisors (of different classes) don't allow
nesting. But, the user can manage this, by only *running*
one of them at a time. In the case of WSL2, WSL2 is not
supposed to be a classical VM, and consequently the user
would be forgiven for not realizing they can't run VirtualBox
at the same time as WSL2. What Microsoft wants application
developers to do, is "bow down" and drink the Koolaid,
and make their applications fit into the bigger picture
Microsoft is cooking up. In the case of VirtualBox, they're
supposed to have made a change to Version 6 so that
VirtualBox will run under Hyper-V, as if it was
a Hyper-V Guest or the like.

Even if you untick lots of boxes, as in the above picture,
there's still no guarantee that VMWare will install. I don't
think the "block" would be made in that way, to only trigger
if some enabled features conflicted. I think the block
is more likely to say, "2004? No VMware for you then". And
if VMWare changes their mind, then the block would be
version sensitive, and when it sees a Hyper-V compatible
version, it would allow it.

Microsoft has blocked hosting software before. It blocked
VPC2007 and Windows Virtual PC from running on Windows 10.
You couldn't install them.

Paul

On 27/06/2020 11:34, Paul wrote:
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

This is potentially caused by the WSL2 and Sandbox options
in Windows Features. But when I look in there, I see a ton
of stuff that wasn't there before, and might potentially
interact with Hyper-V.

https://i.postimg.cc/pLqnMLSz/lots-of-interference.gif

Thanks for the picture. However, everything that is marked red, was
turned off on my system. So - that would be allright, I guess.

VirtualBox was supposed to have "acquired" a capability to
"run under HyperV hypervisor". With Microsofts interest in
containers and Russian Dolls, it's inevitable that sooner
or later, virtualization software would "bump heads" with
the company making the OS.

I suspect that's why your VMWare got "bumped off". It didn't
make a version that runs under HyperV, which would prevent
Microsoft from turning on HyperV and using it for everything
under the sun.

I guess you're right.

Another possibility, is your machine doesn't have SLAT/EPT
(Second level address translation/Extended Page Tables). Check
your CPU feature set for the details. I only have one machine
with EPT here. AMD calls it one thing, Intel calls it the other.

Where can I find this? In the BIOS?

Normally, hypervisors (of different classes) don't allow
nesting. But, the user can manage this, by only *running*
one of them at a time. In the case of WSL2, WSL2 is not
supposed to be a classical VM, and consequently the user
would be forgiven for not realizing they can't run VirtualBox
at the same time as WSL2. What Microsoft wants application
developers to do, is "bow down" and drink the Koolaid,
and make their applications fit into the bigger picture
Microsoft is cooking up. In the case of VirtualBox, they're
supposed to have made a change to Version 6 so that
VirtualBox will run under Hyper-V, as if it was
a Hyper-V Guest or the like.

Even if you untick lots of boxes, as in the above picture,
there's still no guarantee that VMWare will install. I don't
think the "block" would be made in that way, to only trigger
if some enabled features conflicted. I think the block
is more likely to say, "2004? No VMware for you then". And
if VMWare changes their mind, then the block would be
version sensitive, and when it sees a Hyper-V compatible
version, it would allow it.

Microsoft has blocked hosting software before. It blocked
VPC2007 and Windows Virtual PC from running on Windows 10.
You couldn't install them.

Â*Â* Paul

Thanks.
So I won't update to 2004. I like to continue to use my VMWare.

Fokke

On 27/06/2020 11:26, Andy Burns wrote:
Fokke Nauta wrote:

Any of you had the same problem?

Presume the problem is hyper-V related? I remember when win10 sandbox
was introduced it b0rked virtual box ...


Likely. See the reaction of Paul and my answer to it.

Fokke

On 6/27/2020 4:56 AM, 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

Go to the VMWare website and they likely have an explanation for it, and
probably an updated version. The incompatibility is likely due to the
fact that Microsoft is now heavily dependent on its own Hyper-X software
for a lot of things to containerize stuff (such as the new Windows
Sandbox feature). I have noticed a similar thing with VirtualBox and
Windows, VirtualBox can no longer startup by itself, it is now supposed
to make use of Hyper-X as its hypervisor, but that feature is completely
broken Virtualbox doesn't work with it.

Yousuf Khan

On 27/06/2020 12:43, Yousuf Khan wrote:
On 6/27/2020 4:56 AM, 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

Go to the VMWare website and they likely have an explanation for it, and
probably an updated version. The incompatibility is likely due to the
fact that Microsoft is now heavily dependent on its own Hyper-X software
for a lot of things to containerize stuff (such as the new Windows
Sandbox feature). I have noticed a similar thing with VirtualBox and
Windows, VirtualBox can no longer startup by itself, it is now supposed
to make use of Hyper-X as its hypervisor, but that feature is completely
broken Virtualbox doesn't work with it.

Â*Â*Â*Â*Yousuf Khan

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

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

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

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?
--
Life is so crazy! ..!.. *isms, sins, hates, (d)evil, illnesses (e.g., COVID-19/2019-nCoV/SARS-CoV-2), deaths, heat waves, fires, out(r)ages, unlucky #4, 2020, etc.
Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

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,-

Fokke

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.


--
Kind regards
Ralph

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.

--
Life is so crazy! ..!.. *isms, sins, hates, (d)evil, illnesses (e.g., COVID-19/2019-nCoV/SARS-CoV-2), deaths, heat waves, fires, out(r)ages, unlucky #4, 2020, etc. Note: A fixed width font (Courier, Monospace, etc.) is required to see this signature correctly.
/\___/\ Ant(Dude) @ http://aqfl.net & http://antfarm.home.dhs.org /
/ /\ /\ \ http://antfarm.ma.cx. Please nuke ANT if replying by e-mail.
| |o o| |
\ _ /
( )

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.

Fokke

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.

Fokke