In looking over Reliability Monitor on my production PC today — it’s on 2004 because I’d been waiting for the 20H2 update offer from WU, still MIA — I noticed two File Explorer crashes on October 18. Having recently read coverage on this very topic at WindowsLatest, I can’t help but think I’ve been bitten by those bug(s).
For more info read Mayank Parmar’s story Windows 10 update crashes File Explorer, causes black screen. He characterizes KB4579311 as a “disastrous update,” which I think is a little over-the-top. But he does point to both File Explorer crashes and black screens as symptoms (and I’ve had 5 of those on this PC since the update was applied, too). I can’t say I like this kind of behavior from Windows 10, though it hasn’t impacted my ability to use this PC daily and productively.
A Blessing in Disguise?
I’ve got to admit I’m getting tired of waiting for WU to extend the 20H2 offer to my 3 Lenovo laptops and my lone desktop still running 2004. This might be just the excuse I need to force-upgrade at least some of these systems to 2004 sooner rather than waiting on Microsoft’s pleasure.
20H2 has been pretty solid on the 3 Insider Preview/Release Preview Channel machines it’s been running on for weeks (Lenovo T520, Surface Pro 3, and Lenovo X380 Yoga). Because my production PC is one of the machines involved, I think I might just force upgrade it after I finish writing this blog post (I’m working on that very machine right now). Checking Reliability Monitor on those PCs, I see no File Explorer crashes nor any blackscreen events on any of them as far back as their history goes (September 24, 2020 on the X380 Yoga, for example).
This might be just good enough for me. OTOH, others not looking for excuses to climb onto the leading/bleeding edge of Windows 10 releases may want to consider uninstalling this CU instead. Either approach seems like a good way to stop these errors from recurring. And that’s the way things go far too often here in Windows-World. I’m not in agreement with Mr. Parmar that this is a “disaster.” But it’s nothing to look forward to, or tolerate indefinitely, either.
Author: Ed Tittel
Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.