New Windows 10 Insider Channels & Changes Fast ring = Dev Channel Slow ring = Beta Channel Release Preview ring = Release Preview Channel
I have tried upgrading from 1909 (18363.900) to the 2004 19041.xxx via the June 20 .iso and also via the Microsoft upgrade assistant, 4 times now. Every time it gets to about 70% then BSOD's with different error messages. The latest was 'System Thread Exception Not Handled'. Others have been Kernel errors. I just updated the Nvidia graphics driver today to 451.48 too. Is this expected behaviour? Is the only way to get updated with a clean install otherwise? Never been offered the update via WU. Thanks for any suggestions.
Upgrades should have reported that the hardware is not yet supported at forehand. Clean install can work because there are no incompatible drivers or software (i.e) already installed.
@Enthousiast I didn't get any warnings before installing. So, it's a driver problem? The graphics card is an Msi GTX1660Ti. Possibly the sound drivers (Realtek HD audio)?
All but one of my computers is currently reporting: "We couldn't connect to the update service. We'll try again later, or you can check now. If it still doesn't work, make sure you're connected to the Internet." There does not seem to be anything consistent. One of them is on 20H1 and on a wireless connection but another in on 20152 and a hard line connection, same exact issues and it was not like this maybe 2 days ago. EDIT: Spoke too soon, now it is all of them.
Can any who got the new channels, share this registry key contents? Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost export to .reg, zip and upload thanks
I only experience this with some MRP option that blocks telemetry, but when i start edge or msie, the globe turns into the correct icon for a working lan connection and it all works. @Carlos Detweiller (iirc) recently posted the url from which windows checks if it is connected.
What I said about the windows hypervisor still holds. If you have the hyper-V feature installed, the windows os hypervisor needs to be turned off with the following command from a dos prompt: bcdedit /set {current} hypervisorlaunchtype off I'm not running an RTX card, but I am running an older Nvidia 2000 in a Dell laptop with a 377.83 Nvidia driver. I've never had trouble with Nvidia drivers. I'm running Windows OS 19042.331 (20H2) and Oracle VB v6.1.10 r138449 is installed with matching guest editions and an XP, Win7, and Win10 VM all running in 3D acceleration mode. I allot 256MB for the Win7 VM. All of the VMs run fine. I'm sorry I can't exactly reproduce your issue without an RTX card installed. Good luck.