Ed Tittel announces his departure from Win10.guru. Thanks for all the eyeballs past and present. See you around the Internet.
Following upgrades to Windows 10 2004 or 20H2 on PCs with Thunderbolt-attached NVMe drives, users may experience a Driver_Verifier_DMA_Violation BSOD. Probably best to avoid such hardware (or roll back Windows) until they get it fixed.
Last Friday, FedEx dropped off a Dell Precision 5500 Mobile workstation with 8-core i7, Quadro T2000 graphics, 32 GB RAM and a 1 TB NVMe SSD. I’m still setting it up and getting to know this machine, but what I’ve seen so far, I like. Check it out!
Every now and then, I’ll send a print job off on my production desktop that goes to an application (today, it was Snagit) instead of target printer. When that happens, I know it’s time to reset the default printer using its new IP address. Let me explain. . .
First thing this morning, I observe on my Lenovo X390 Yoga that WU has finally extended an offer of KB4580364. After accepting that offer, I document my experiences and reactions with download, install, and post-install cleanup. It’s all good — and surprisingly interesting — stuff. Check it out!
OK then, it’s official. According to the MS 20H2 Release Info/Status page, the company is ramping up offers of the upgrade only slowly. You can see their statement on this topic outlined in red in the lead-in graphic for this story. I’m not sure what this has to do with ensuring “a reliable download experience,”
With the release of 20H2, MS points what used to produce the System applet in Control Panel to Settings/System/About instead. I provide some bittersweet commentary, and an explorer shell string that produces the old CPA if that’s what’s really wanted.
MS has a banner for the Setting apps in A/B test right now, which means some users see it, and other users don’t. I provide details on an OS tweaking tool that lets enterprising users change this feature’s status (turn it off it it’s on; turn it on if it’s off).
Having tried and failed to upgrade my 2012 vintage mini-ITX PC (Jetway NF9G-QM77 mobo, intel i7 2630QM CPU, etc.) from 1909 to 2004, I expected a forced upgrade to 20H2 to fail. To my surprise and delight, it worked! Here’s the story…
When news emerges that the official 20H2 release is available through Windows Update, I figure that at least ONE of my 5 version 2004 PCs will get the update offer. None of them qualify, to my great frustration. For me, it’s now a waiting game…