Windows 10 Insider Preview Fast Build 19541 - January 8  

Hi folks

martyfelker said:

you might have enabled HYPER-V to use the WSL (you need to enable HYPER-V to use the WSL

HyPER-V is only needed for WSL2 which actually runs Linux in a VM (kinda cheating IMHO), It is not needed for WSL1 which still works (just installed Fedora Remix which is worth 5 bucks).

This build is extremely fast but I just installed Fedora Rawhide (KDE Plasma) w/ kernel 5.5rc5 which is like greased lightening.

Hi there

running 6 concurrent Windows VM's on Arch Linux (kernel 5.10) - qemu/KVM -- all run like "greased lightning" - bridging works so they all interconnect with each other and the Host.

One nice thing about this type of HYPERVISOR is that you can totally logoff the Host and the VM's are still running and useable to any authorised users - they don't need accounts on the Host to access the VM's.
You can also run the whole thing "Headless" -- tricky to do if you aren't adept with things like vi editor, XML and bash scripts but with a bit of SSH you can manage the whole kybosh via cmdline !!!.

This makes these VM's ideal for operating from a NAS type server where they can be accessed remotely via a standard Laptop. VM's can also be controlled remotely as well --i.e shut down, restarted, modified etc.


apart from the glitch with Photoshop CC20 (now confirmed it's an adobe not a Windows problem) this release has passed everything I've chucked at it.

So I'm leaving it as a "Working" VM to see if it's useable as an "Everyday" machine.

One thing though I've moaned long about is the problem with long file names - the 266 char limitation of path/folder/filename restriction. Although Internally this has been lifted so many processes / applications still use the drop down "file explorer" api which still has the limitation. It's probably why IE11 is still on the build - so much of the file browsing is still bound into some of IE11's processes so there's probably quite hard work for Ms to do still to "untangle this" from the OS so we can finally be rid of it.

Cheers
jimbo

Still, cannot update from 19041, error 0xC1900101 - 0x2000C. The installation failed in the SAFE_OS phase with an error during APPLY_IMAGE operation.

I have never had any issues updating this laptop from Fast build to Fast builds, any ideas?

AndreTen said:

Did you disable CPU virtualization in BIOS? Like scoopjeff suggested?

i just did, and upgrade installed with no errors. I had to skip previous upgrade, and postponed this one due to the same errors.

Problem is the bios is password protected and I have no idea what the password is. Odd how this never had to be disabled in previous versions. Would a clean install work?

PurSpyk said:

Problem is the bios is password protected

Can you reset the BIOS?

PurSpyk said:

Problem is the bios is password protected and I have no idea what the password is. Odd how this never had to be disabled in previous versions. Would a clean install work?

I am the owner, I password protected the laptop while drunk, I know we do odd things