Ouch! Take a look at the error list from one of my two Dev Channel PCs (for January 21). You can’t help but notice 6 of 7 errors relate to backgroundTaskHost.exe. Ditto for how lousy the experience index remains (under 4 all days showing). Indeed, Dev Channel Build 22535 throws regular backgroundTaskHost.exe failures on both of my test PCs. I’ve reported it to Feedback hub, and am hoping somebody’s looking into it.

What to Do When Build 22535 Throws Regular backgroundTaskHost.exe Failures

Looking around online, I don’t see much by way of relief for workarounds or registry hacks. Here’s some representative detail from Reliability Monitor, from which I’ll point out recurrent elements:

Detail on these errors from ReliMon is more alike than different

Common elements include:

• Exception Code: 0XC0000005
• Application path: C:\Windows\System32\backgroundTaskHost.exe
• Faulting module path: C:\Windows\System32\msvcrt.dll
• Faulting…full name: includes ContentDeliveryManager

Understanding the Error

The error code, often abbreviated 0X5, when checked in the MS Error Lookup Tool returns status value: ERROR_ACCESS_DENIED. The same thing comes up in the System Error Codes for values 0-499. According to the WikiFixes Ox5 page, this may be caused by a system component or application malfunction or corruption. In this case, I’m looking at backgroundTaskHost.exe and msvcrt.dll (part of the MS Visual C++ runtime and compiler) as potential culprits.

Having run both disk ... /restorehealth and SFC /scannow on the affected PCs, I don’t think the .exe or the .dll files are damaged or corrupted. My best guess is that something is off with the build itself, and that MS will have to find and fix the problem. Funny thing is, my 22535 builds appear to work well otherwise, and don’t manifest obvious runtime issues or problems. Interesting, eh?

Let’s see what happens when word of this gets out further. I’ll keep you posted as things change.

Recently, while troubleshooting an issue on Windows 10 where Zoom kept crashing unexepectedly, I observed something even more vexing. The cure for that specific issue is to turn Video Conference Mute off in PowerToys (on by default). But as soon as one does that, keyboard input slows to a crawl. Indeed, when self-inducing Windows 10 keyboard output delays that way, it can take seconds for a keystroke to appear on-screen. If you type even modestly fast (like me) that means you can finish a whole sentence before output shows up on screen. When you make occasional typos — as I sometimes do (1 in this sentence so far) — that’s immensely frustrating.

When Self-inducing Windows 10 Keyboard Output Delays, Easy Fix

At first, I tried restarting the Explorer task in Task Manager. That sometimes helps when such symptoms appear. Not this time. The next standard fix is a system restart. And indeed, that did the trick for me.

I know that PowerToys ties into Windows at a pretty deep level. I’m guessing that turning default settings off in the program may change low-level system behaviors. Apparently, the Video Conference Mute change is discombobulating enough to change the delay involved in keyboard echo (the time it takes for a keypress value to show up on screen).

Another “Interesting” Issue Caught and Killed

This happens only on Windows 10, though. I tried the same changes on Windows 11, and it didn’t affect keyboard output at all. On Windows 10, I first noticed it in the WordPress editor. But then, it showed up in Outlook and Word — and even, Notepad — so I assumed it was an across-the-board thing.

Thus, I’m glad that an old standby in whacking Windows weirdnesses — namely, a restart — fixed the issue on my production PC. I use that machine all day long, every day, and mostly enter text on a keyboard for a living. Thus, fixing anything that slows down text entry is of major importance — to me, at least.

Stay tuned. As things are always interesting with Windows in some odd way or another, this is a thread I’ll have no trouble adding to in my daily writing. As Roseanne Roseannadanna often said on SNL: “It’s always something!” Too true…

My first job out of college was in an archival sound studio at the Library of Congress. Believe it or not, they even send me to a summer audio engineering program.  (The Eastman School of Music, Summer, 1974.) In the nearly 4 years I worked there, I’d like to think I learned a little something about quality sound delivery. That’s why I’ve been chafing during recent attempts at escaping excess Windows Audio reverb. This morning, I finally fixed my problem on my production desktop.

Hows and Whys of Escaping Excess Windows Audio Reverb

First: a problem description. Any kind of music playback on my external speakers has sounded weird lately.  (When I play sounds in “the open air,” I use a set of Axiom Audio components. These inlude: L, R, and subwoofer speakers with external amplifier.)  Here’s my best problem description. On playback, music sounded like it was in a concrete stairwell or in a big tiled bathroom. From my years in the studio and subsequent experience, I knew it was a reverb problem.

First, I went poking around in the Realtek Audio Console app. It’s shown as the background for this story’s lead-in graphic. But none of the changes I made in the equalizer, or among its various settings options (Rock is show in the afore-mentioned screencap), made any difference.

Thus, I realized it had to be something in the old Control Panel Sound widget. It was. At one point or another I must have checked the box shown in the screencap foreground red-arrowed “Enable audio enhancements.” As soon as I unchecked that item, my excess reverb disappeared. Everything returned to normal and my various music sources sounded as much like their original recordings as my semi-pro sound chain (external amp and speakers) could deliver.

When in Doubt, Experiment…

I don’t think I would’ve been able to solve the issue if I hadn’t fooled around with the EQ presets in the Realtek Audio Console. As soon as it was obvious that this element in the audio software chain wasn’t responsible (I was sure I’d picked the “Club” or “Party” presets, both of which seem to boost reverb noticeably), I knew it had to be the Sound widget. And sure enough, whatever audio enhancement had kicked in when I checked that box made a BIG difference.

Fortunately, it was easily fixed and my tunes are now back to normal. Now the question becomes: what do I want to listen to today? As I finish out this post, I’m enjoying the alt-pop sounds of 90s British group “The SUNDAYS.” Good stuff (and it sounds like it oughter…).