Windows 10 Insider Preview Fast Build 19541 - January 8 Insider

@Kari

Thanks, your suggestion was perfect, you nailed it...
Now the Workstation is working again.

JGToy said:

@Kari

Thanks, your suggestion was perfect, you nailed it...
Now the Workstation is working again.

You are welcome. The problem with that error message is that it really is misleading. The problem has nothing to do with Defender, being pure Hypervisor issue.

Kari

RK1997 said:

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.

Yeap, I guess I should start learn how to use this Hype-V thing.

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.

Hadnt tried that option, turned off now and installing now! Lets see if it works

jimbo45 said:

@JGToy

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).

Attachment 262552

cheers
jimbo

Thanks for the explanations!
Actually mine started working just fine after I did what Kari suggested and right now just to make sure (after reading your post) I tested it and it still working.

Kari said:

You are welcome. The problem with that error message is that it really is misleading. The problem has nothing to do with Defender, being pure Hypervisor issue.

Kari

You're 100% right because I followed that link given on the message box and it took me to windows Defender related issue.

New Weekly Windows 10 Insider Program Pulse Survey - January 10

kharder said:

First, stop your virtual machine.
Navigate to the left pane and click Edit virtual machine settings.
Click the Add button at the bottom of the Virtual Machine Settings page.
A new window Add Hardware Wizard will open on your screen.
Select New Hard Disk > SATA and click on Use an existing virtual machine.
Use an existing virtual machine
Now browse your .vmdk file and click the Finish button.

And I managed to "update" all my VMware Workstations to this build (19541) thanks to the above hack.