Wierd issue with VM Ware

[Master Disaster]

I use VM Ware a lot on my machine and I have had zero issues with it for literally years.

 

Currently I've got a Debian 9 VM running which I use as a sandbox to test out things before I go live with them on my actual install.

 

Yesterday I tried fairly unsuccessfully to get Mint running on my PC, it really doesn't like something and refuses to boot at all (not the issue though) so this morning I decided to do a VM install of Mint so I could try out the Cinnamon desktop but was surprised to see a warning in VM Ware...

 

 

Now I categorically know that 64 bit OSes were working fine a few weeks ago as I did an install on Windows 7 X64, AFAIK nothing has changed on my machine since then (other than updates from MS) so I decided to carry on and see what happened. I finished configuring my VM then pressed Play and was surprised to see this message...

 

 

After doing some investigating it seems that device guard and credential guard are group policies that can be set by businesses to protect devices from end users messing with them. Thing is though, they require manual enabling by the network admin and they also require EFI partition editing. See this link and this link on how to disable it.

 

I know I haven't enabled this policy on my machine so why exactly is it enabled?

 

Anybody got the foggiest idea what is going on please.

 

EDIT

 

The plot thickens, I tried to follow the disable guide and fell at the first hurdle, the policies are not even enabled on my system?

 

 

Now I am really stumped.

[Sack]

Let me guess, windows 10? Their update broke my m.2 wifi card last week, been getting crippled performance since their update, used to get 10MB/s now I get 0.4-2.5 MB/s.

 

On the postive side I got a cable to test my computer and now I'm on a cool 100/100 MB/s connection

[SnipeYa]

9 minutes ago, Sack said:

Let me guess, windows 10?

21 minutes ago, Master Disaster said:

on Windows 7 X64

Reading the full post helps...

 

[Morgan MLGman]

8 minutes ago, SnipeYa said:

Reading the full post helps...

 

He meant he installed Win 7 x64 on VMware, he's on windows 10 according to his profile, so joke's on you.

 

As for @OP, this is what worries me most:

34 minutes ago, Master Disaster said:

 

 

 

Now I categorically know that 64 bit OSes were working fine a few weeks ago as I did an install on Windows 7 X64, AFAIK nothing has changed on my machine since then (other than updates from MS) so I decided to carry on and see what happened.

To install a guest VM in VMware it needs to have the same instruction sets as the host, otherwise it just won't work. Now you do have a 64-bit OS, so why doesn't this work? I do not know.

[SnipeYa]

21 hours ago, Master Disaster said:

*snip*

20 hours ago, Morgan MLGman said:

To install a guest VM in VMware it needs to have the same instruction sets as the host, otherwise it just won't work. Now you do have a 64-bit OS, so why doesn't this work? I do not know.

I'm not sure if this would cause this issue, But... Have any of the bios options for virtualization been magically disabled? I've had problems in the past with VM's from stupid stuff like that.

 

20 hours ago, Morgan MLGman said:

He meant he installed Win 7 x64 on VMware, he's on windows 10 according to his profile, so joke's on you.

I'll give you that one, The egg is on my face now. Seems people hastily blaming windows 10 for things makes me a little grumpier than it should.