Go to ...

RSS Feed

July 12, 2020

Windows Update

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…

New channel names for Insider Settings appear

New Insider Release Names Appear in WU

Earlier this month, MS announced new terminology for levels of participation in its Insider program — namely, Dev Channel, Beta Channel and Release Preview Channel. As of June 29, those Channels are now visible, ready for you to tune in!

Strange Local Security Authority bug forces restart (Source: BleepingComputer.com)

Windows 10 2004 Gotcha Forces System Reboot

A fair number of Windows 10 2004 users are reporting that some PC’s are experiencing an LSASS (Local Security Authority Subsystem Service crash. It forces a reboot within 60 seconds of its occurrence. Ouch!

MS BrightSpot image: fading foliage

Windows 10 2004 Deprecations and Removals

With each new Feature Upgrade, MS retires some features (called removals). It also signals features scheduled for later removal (called deprecations). Here are the lists for both kinds of items for Windows 10 Version 2004, released earlier this week.

2004 starts out with 10 known issues

For Win10 2004, A Big List of Known Issues Appears

Windows 10 Version 2004 gets off to an interesting start with 10 (yes, that’s TEN) issues on its “Known Issues” list. This will explain why many people won’t get an offer to upgrade from WU for a while. That’s OK: you have multiple ways to force the upgrade, if you want to.

Older Posts››