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.
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. . .
In looking over my production PC’s Reliability Monitor output I see errors that ring a distant bell somewhere. Turns out lots of people are experiencing them in the wake of installing KB4579311 on their Windows 2004 PCs. Sigh.
It’s true one has to wait a while for OEMs to obtain, test and sometimes tweak device drivers, firmware, and BIOS/UEFI updates before making them available to users of their laptops and PCs. But some such offerings go on for a surprisingly long time, and are of exceptionally good quality. Read the deets…
For the past six months, each new Dev Channel release has me asking “Will RDP work for this release on my Lenovo X220 Tablet?” Sometimes it does, and sometimes it doesn’t. Let me explain (and share a quick fix)…
Weird! Though Reliability Monitor tells me my first two update attempts with KB4586238 succeeded, the minor build number fails to increment. Only after running the Update Troubleshooter and trying again, does the build increase to 20231.1005. Truly, third time’s the charm!
When it comes to swapping an older (usually smaller) NVMe boot/system drive for a newer (usually bigger and faster) one, you can either clone the old drive, or restore an image backup from the old drive to the new one. Deets on pros and cons and choices in this story.
When Windows Update offers Optional updates, those are most often categorized as “Driver updates.” Unless a related device isn’t working well or has a definite problem, the proper response to such offers is to ignore them.
When mysterious command windows appearing at startup tie into repeated failures to upgrade Thunderbolt firmware for bogus reasons, I start looking for answers. When I find them, they fit nicely my usual strategy for misbehaving exe files: delete them!
Good news! While the “Reset this PC” option in Windows 10 version 2004 was broken for some time after its May 27 release, on or after September 8 it’s working properly once again. Glad to see it’s been fixed.