Go to ...

RSS Feed

July 11, 2020

Troubleshooting

Red text reading "could not be run" is NOT a problem, appearances notwithstanding.

Misleading Troubleshooting History in Version 2004

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…

UASP results left, BOT results right

UASP Outperforms BOT Significantly

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…

Warning: There may be some impediments to installation of new PowerToys versions.

Thoughts on Updating PowerToys (Preview)

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.

Network status should likely say "private"

Typical Post-Upgrade Networking Checks and Repairs

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.

SP3 doc (front view)

USB Drive Dropouts = Sign of Failing Dock

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.