If you check your Troubleshooting History on PCs running Windows 10 Version 2004, some will report an apparent error that a critical troubleshooter could not be run. It’s not a problem even though it looks like one: let me explain…
When I can’t RDP into either of my two Beta Channel Insider test machines after upgrading to Build 20161, I play a variation on the old “If it doesn’t work reboot” troubleshooting technique to set things back to rights.
When a long-time subscriber points out that my NVMe device throughput results were way under expected values, I realize I took that drive for a ride on the wrong bus. UASP beats BOT every time with fast storage devices. I shoulda known…
If you want to update PowerToys, be warned that some applications may need to let go of files that its installer touches during installation. That means you’ll sometimes be asked to close such applications before the update runs to completion.
With the release of Version 2004, aka 20H1 or the Windows 10 May 2020 Update, the built-in Optimize Drives utility is losing its TRIM and defrag status information. If you run the utility on Day 1, the record of its use is gone on Day 2.
If you work on a (usually small) private network, and RDP, file sharing, or device sharing quits working (or works only intermittently) after a Windows 10 feature upgrade, here are some tried-and-true fixes to restore things to working order.
I can’t help but notice that backing up to an exernal USB 3 drive plugged into my Surface Pro 3 dock fails on a pretty regular basis. Something seems to be wrong with the dock’s USB ports. So I plug into the SP3 USB 3 port instead.