Windows 10 Insider Preview Fast Build 19541 - January 8 Insider

JGToy said:

On this build VMware Workstation 15 Pro doesn't even start saying that:
Attachment 262533
And I am not using Defender and nothing of this is enabled.

I had this same issue of VMware not starting on Windows 10, 1909. That's why I am using Hyper-V for my Insider build.

JGToy said:

On this build VMware Workstation 15 Pro doesn't even start saying that:
Attachment 262533
And I am not using Defender and nothing of this is enabled.

@JGToy and @RK1997

Hi there G'morning !!!

That happens if you enable HYPER-V you don't have to even use it !!!! e.g you might have enabled HYPER-V to use the WSL (you need to enable HYPER-V to use the WSL).

Problem is after disabling say HYPER-V again it doesn't stop the error == a restore where HYPER-V hasn't been enabled was the only way I got round that problem. There might be less drastic solutions but I never found any.

I have more or less given up on VMWare since my main HOST is now Linux and I'm extremely happy with Windows VM's running on the KVM/QEMU Hypervisor now that I've sorted out 99.5% of the niggles -- and it's totally free, blows VMWare's performance out of the water. pass thru works perfectly on pci hardware etc, brilliant paravirtualised virt-winio drivers for Windows guests and can approach almost "Bare Metal Speed".

(Incidentally why VMWare and HYPER-V can't run concurrently seems a bit bonkers -- KVM/QEMU VM's and VMWare WKS VM's can run quite happily side by side as screenshot shows two windows VM's running concurrently here -- one on VMWare the other on KVM -- As two indpendent VM's -- not a nested one -- i.e not a VM running within a VM).



cheers
jimbo

CountMike said:

What doesn't work ?

Hi there
I think the OP couldn't get VMWare to work after enabling (not necessarily starting) HYPER-V on this build of Windows as a HOST. I concur with that problem when I tested this build on a Windows Laptop (with UEFI).

Could be that it's specific to just some machines (UEFI vs BIOS), the VM using UEFI or some of the more eseoteric parameters like setting iommax on in the Virtual BIOS etc -- who knows !!!

We've seen on these boards seemingly identical machines not even being able to install this or some previous builds (Of Windows). !!!

Well "The Wonder of Windows" -- gives us things to do on dark Winter mornings -- light snow currently, 1 deg C and sunrise is at 11.05 today !!!!!!!

Cheers
jimbo

scoopjeff said:

After install I still get the same error as 19536 0xC1900101 -0x30017 first boot phase error. Lesson learnt from 36 and havent bothered doing anymore re stall tests as its a waste of time, obviously something isnt right with these new builds as its not just my machine.

I am having the same problem, can't update from build 19041.1: updating to all the most recent builds up to 19541.1000 (rs_prerelease) always fails with error code 0xc1900101, using Windows 10 Pro Insider Preview 2004, fast ring.

I have both Hyper-V at the OS level and SVM CPU Virtualization at BIOS level enabled: I have read that disabling either of them might help solving the issue, but I really can't because I need them for Docker and WSL.

Every time a new update comes out I eagerly install it hoping the issue to have been fixed but I always end up with the same error. Not sure I can do anything besides waiting for a fix from Microsoft.

Krige said:

I am having the same problem, can't update from build 19041.1: updating to all the most recent builds up to 19541.1000 (rs_prerelease) always fails with error code 0xc1900101, using Windows 10 Pro Insider Preview 2004, fast ring.

I have both Hyper-V at the OS level and SVM CPU Virtualization at BIOS level enabled: I have read that disabling either of them might help solving the issue, but I really can't because I need them for Docker and WSL.

Every time a new update comes out I eagerly install it hoping the issue to have been fixed but I always end up with the same error. Not sure I can do anything besides waiting for a fix from Microsoft.

Hi there

try a NEW install and THEN enable HYPER-V etc.

Cheers
jimbo

jimbo45 said:

try a NEW install and THEN enable HYPER-V etc.

Thanks but I installed the system less than a month ago (WindowsInstallDateFromRegistry: 11/12/2019 10:23:43). That would not really feasible anyway because it would take a few days to have my current setup up and running again and I can't really afford to loose that many days.