Windows 10 Insider Preview Dev Build 21376.1 (co_release) - May 6 Insider

martyfelker · 14 May 2021

It sucks that M$ is not telling us anything. Back to Linux.

Well, I decided to reboot to Windows because MS just wanted to get in the .Net Framework update.

martyfelker · 14 May 2021

Well just imported a QEMU/KVM from my RAID0 storage and created a Gnome Boxex VM from the ISO. Here the 3 are co-existing and waiting for the next build. Virtualbox can't play with them because

irtualBox can't enable the AMD-V extension. Please disable the KVM kernel extension, recompile your kernel and reboot (VERR_SVM_IN_USE).

Not going to disable a kernel service for VB.

Windows 10 Insider Preview Dev Build 21376.1 (co_release) - May 6-screenshot-2021-05-14-04-00-41.jpg

jimbo45 · 14 May 2021

VMWare and KVM/QEMU working perfectly and concurrently on my Linux Host - (current kernel now 5.12.3) with KDE plasma wayland desktop.

No problems at all running a couple of different W10 builds including this one as VM's.

I gave up on VBOX a while ago - I never found it easy or particularly pleasant to use. VMware even though I've had difficulties from time to time makes installing and using VM's a real doddle (remembering of course to install vmware tools on the guests) while KVM/QEMU just blows the rest out of the water for performance (as you can get near native speeds with the correct hardware).

I might try playing around with HYPER-V and some pass thru - I've got an older laptop which should be man enough for the job - or even a 2nd level VM !!!!

Cheers
jimbo

martyfelker · 14 May 2021

VB is not my favorite virtualization program - VMware is even though it cost a bundle to get both 15 (and its free upgrade to 15.5, which has VMware Workstation Server) and 16 which works even on kernel 5.13rc1 on Fedora Rawhide - where I'm hanging out now. I know VB developers are aware of the conflict with libvirt and eventually, they may find a workaround - or not. It is worthwhile for those who do not want to shell out the bucks for VMware which is certainly what I would use if you want/need to have your VMs work on Linux and Windows in a dual boot environment like I am running. I will use ver 16 on my laptop when it gets fixed by Elucktronics. But damn - I should have waited for their AMD Ryzen 64GB with Radeon GPU. Don't know whether they will be able to tell what caused the crash of that damn Intel/Nvidia version - although I must say that the old NVidia card I am using now is performing quite well. It lucks likely that we will have to wait until next week for a build although they have released very rarely on a Friday. Perhaps they are even working on some interesting new feature but I doubt it. Concentrating on 21H1 I guess. We are but mushrooms in the dark, being feed nothing.

Winuser · 14 May 2021

Will the release a new build during a Bug Bash?

OilerNut · 14 May 2021

Tweet
— Twitter API (@user) View on Twitter

CountMike · 14 May 2021

Still an hour to go, we'll se then.

Wynona · 14 May 2021

Winuser said:

I'm surprised that MS hasn't released a fix for the end of service bug. Maybe it will be fixed in the next build.

Yeh . . . I just got the cumulative update, which wasn't much. Didn't change a thing.

Wynona · 14 May 2021

jh30uk said:

Not sure where to put this so Brink can move it:

I am on latest DEV and through WU :Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version Next for x64 (KB5003266)

There, fixed it for ya.

I'm pretty sure you're in the right place, since the CU updated 21376.1 and wasn't offered to me on my production partition.

I was hoping it would take care of the "expiration notice" but it didn't.

kado897 · 14 May 2021

Wynona said:

There, fixed it for ya.

I'm pretty sure you're in the right place, since the CU updated 21376.1 and wasn't offered to me on my production partition.

I was hoping it would take care of the "expiration notice" but it didn't.

It was just a .NET CU Wynona.