Category Archives: Windows 10

Self-inducing Windows 10 keyboard output delays

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…

Facebooklinkedin
Facebooklinkedin

Zoom Resume Ruminations

Last week, I reported that disabling the Video Conference Mute feature in PowerToys fixed constant Zoom crashes. This morning, I participated in a successful Zoom conference on the fixed PC. This has me thinking… Thus, I’ll share Zoom resume ruminations to celebrate a return to more or less normal operations. (Note: the lead-in graphic shows PowerToys Video Conference Mute “Off”.)

Where Do Zoom Resume Ruminations Lead?

Having expunged multiple Windows issues in the past week, I’m pondering best Windows troubleshooting practices. First and foremost, I’m reminded that when actual Windows errors present, the best way to find solutions or workarounds is to start from  error messages or codes that appear on-screen.

Thus, searching on “Zoom quit unexpectedly” and “Windows 10” is what ultimately led me to the PowerToys fix. Ditto, when I found a sizable string (7 in all) of repeated COM Surrogate “stopped working” critical events in Reliability Monitor. That, too, led me to a set of possible causes and related fixes.

Troubleshooting Requires Proper Context

If anything I learned while studying anthropology still works for me as a tech person, it’s the importance of putting things into context to really understand them. Troubleshooting research definitely requires taking error messages and including enough context to filter out irrelevancies and focus in on useful insights.

As I look back on my problem-solving efforts of late, I observe  certain “context data items”  make useful adjuncts to error messages and codes. These include:

  • OS version or application name
  • Build number (where applicable)
  • Filenames that appear in error details
  • Complete error code strings (e.g. 0XC0000005 instead of C05)

When I’m looking for present-day errors, I sometimes find it helpful to restrict the time scope for searches to the “Past week” or “Past month” setting in Google. That focuses on current events, as ’twere, and makes results more likely to apply to whatever issues I’m chasing right now.

Works for me, anyway. Hopefully, that means such techniques might also work for you, too!

Notes Added 1 Hour Later

Two things:

1. I just updated PowerToys on the Production PC to version 0.53.3. I’m pleased to report it preserved my “Off” setting for Video Conference Mute. If I turn it back on, the crashes resume (works fine when set to “Off,” though).

2. I learned yesterday that the WindowsInsider Team renewed my Windows Insider MVP (WIMVP) Award for 2022. I’m pleased and humbled to remain a member of that active and vibrant community.

Facebooklinkedin
Facebooklinkedin

Chronic COM Surrogate Windows 10 Failures

OK, then. I was poking around on my Windows 10 production desktop yesterday. Inside Reliability Monitor, I counted up 7 of 10 recent Application Failures from a single cause. It’s shown in the error detail window that serves as the lead-in graphic for this story. All 7 are more or less the same, where I see chronic COM Surrogate Windows 10 failures at work.

With Chronic COM Surrogate Windows 10 Failures, What to Do?

Look it up on the Internet, of course. Using “COM Surrogate stopped working dllhost.exe” as my search string, I found plenty of data to read and digest. As it turns out, this is a pretty common gotcha.

The COM Surrogate is a host process executable named dllhost.exe (as the error info also indicates). It runs as Explorer or other filesystem-related code works it way through file and folder navigation. The process also handles thumbnails (and viewing same) in Explorer and other similar interfaces.

Most of the renditions I perused, pointed to 4 potential causes:

1. a GPU driver problem
2. interference from Data Execution Prevention (DEP) causing a crash
3. munged DLL file connection (e.g. dllhost.exe)
4. corrupt DLL file

Fixes Follow Causes, Right?

Fixes relate directly to causes. For the first cause, replacing the graphics driver with a known good working version is the trick. This may mean rolling back, to reverse a recent problematic upgrade. Or, it might mean rolling forward, if a new version is available (especially one that mentions fixing thumbnail access issues).

For the second cause, creating an exception for dhllhost.exe in the DEP pane in System Properties, Performance options does the trick. Here’s a partial snapshot of what’s involved (for 32-bit Windows 10, navigate to System32; for 64-bit, navigate to SysWOW64 instead):

Chronic COM Surrogate Windows 10 Failures.DEP-exception

This basically instructs DEP to ignore access to dllhost.exe

For the third cause, re-registering the DLL should ensure that dllhost.exe is properly plumbed into the Windows Registry (for more info, please see this MS Support page). This requires entering a pair of commands in an administrative Command Prompt or PowerShell session:

regsvr32 vbscript.dll
regsvr32 jscript.dll

This should handle anything related to DLL registration.

For the fourth cause, MS recommends first running

dism /online /cleanup-image /restorehealth

Follow that up with sfc /scannow until it comes back with “Windows Resource Protection did not find any integrity violations.”

My Chosen Fix: DEP Exception

Because thumbnails are working OK on my system, I decided that causes 1, 3 and 4 were unlikely. So I implemented a DEP exception, as shown in the preceding screencap. So far, it’s working: no COM surrogate errors since that change. I’ll keep an eye on it, and amend this story if that changes. Stay tuned!

Note: this same approach also works on Windows 11, should the COM surrogate cause problems a PC running that OS instead. Cheers!

Facebooklinkedin
Facebooklinkedin

Escaping Excess Windows Audio Reverb

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…).

 

Facebooklinkedin
Facebooklinkedin

2022 Gets First Windows 10 WUCU Woohoo

I can’t help it. I have to have fun with my headlines occasionally. In this case, WUCU refers to a Cumulative Update (CU) delivered via Windows Update (WU). Hence my proclamation, as 2022 gets first Windows 10 WUCU. The woohoo part is just for grins. I was busy enough with writing and phone calls yesterday that I didn’t notice the download and install part. But when I logged in this morning, I saw a notification that led me to the “Restart required” message in WU. It’s present on all the “regular PCs” in my fleet (those not running an Insider Preview).

When 2022 Gets First Windows 10 WUCU, Then What?

Why, restart all those machines, of course. I just checked the Windows 11 PCs, and they don’t seem to be queued up for Patch Tuesday action. I wonder if this is just a one-off, or if the update cadence for the newest desktop OS might be changing. I guess I’ll have to keep an eye on things, to see what happens.

Closer investigation shows that KB 5009566 hit Windows 11 machines yesterday (January 11) as well. It’s labeled as a Quality Update in Update History, not a CU. So it looks like the cadence continues as always, but that the labels attached to the Patch Tuesday update can be either QU or CU depending on their contents and recent prior preview update activity. Good to know!

Here’s what that looks like on my production-level Lenovo X1 Extreme (8th-gen Intel CPU, vintage 2018).

The update for Windows 11 also arrived on January 11, but it’s a QU not a CU. Go figure!

It seems that Windows 11 is finally starting to diverge from Windows 10. I think we may see some exciting new developments and capabilities in the run-up to this fall’s upcoming equivalent to a feature update. Should be interesting. Stay tuned: I’ll keep you posted.

Facebooklinkedin
Facebooklinkedin

Zoom Mystery Gets Interesting Resolution

For the past month or so, I’ve been unable to run Zoom on my primary desktop PC. That’s actually OK, because it doesn’t have a video camera, so it’s been no major gotcha to switch over to the laptop I keep at the left-hand side of my desk. There, a camera is built-in and it works fine with my Jabra 75 USB plug-in headset. Today, determined to find a solution, I stumbled across a revelation in the Zoom Community forums. There, my Zoom mystery gets interesting resolution: because the PowerToys “Video Conference Mute” is enabled by default, it crashes Zoom. Turn that feature off. Presto! No more crashing.

Flailing About Leads to Zoom Mystery Gets Interesting Resolution

At the same time, I’ve also had to switch from my Jabra 75 headset to the older Logitech H750e headset on the production PC. Though the sound widget in Control Panel shows sound input/output, it’s not audible on the headset itself. That’s working properly now, too.

If it hadn’t been for some inspired Google search, I’d never have found this by myself. Turns out it’s a “known thing” in GitHub (where PowerToys development is run). There a bug report about this there. It’s entitled “Zoom continuously crashes with Video Conference Mute enabled.”

I’m very glad this finally popped up on my radar. I’m even gladder there’s an easy fix. Shoot! I’m just glad to see the Zoom dashboard popping up and working on my production desktop PC. This fix was a long time coming, but I’m glad to see it finally in place. Sigh.

 

Facebooklinkedin
Facebooklinkedin

MS Assistant Whacks Word Weirdnesses

These days, I make a sizable chunk of my living using Microsoft Word on huge documents with complex stylesheets. As anybody who does this kind of thing regularly knows, Word can get wonky. That is especially true when large drafts with “Track Changes” turned on must pass among multiple parties. That’s why I’m happy to report that one particular MS Assistant whacks Word weirdnesses. I’m talking about the Microsoft Support and Recovery Assistant (SaRA) shown in the lead-in graphic here (About, Download).

Because MS Assistant Whacks Word Weirdnesses, Use It!

In this latest case in point, I’d cut out a mid-sized section of a large (~200 pg) Word document to work on independently. But when I tried to interact with that document fragment, I started seeing a spray of different errors:

  • Document is too large to save; remove some text or graphics
  • Disk is full; save document to a different drive
  • Permissions error; unable to save document

Normally, when there’s something wrong with the document itself, the errors will remain the same. Also, Word itself is pretty good at repairing corrupted or damaged documents. Thus, this ever-changing panoply of errors got me thinking: “Hmmm. Looks like Word is going wonky.”

Enumerating Office Repairs

I remembered a story I wrote for ComputerWorld last August (4 Steps to Repair Microsoft Office). One of them involved the SaRA. Naturally, I ran the tool (thankfully, it always updates itself first if the version being run is not the most current one available). I had it perform its  Office repairs, then tried the previously problematic file fragment I’d been fighting with. Problem solved!

As mechanics sometimes say: “Get the right tool for the job.” In this case, I was glad that SaRA turned out to be that very tool. I was even gladder to get back to work on writing, and exit Word troubleshooting mode. Sigh.

 

Facebooklinkedin
Facebooklinkedin

Ventoy 1.0.62 Gets Plug-in Manager

I’ve been a huge fan of the Ventoy bootable image tool for several years now. The developers have recently released a new 1.0.62 version at GitHub. It includes a GUI plugin configurator that immediately explained to me why I have issues with my current version on some of my laptops. The partition style on the ventoy drive is MBR and some of my newer laptops are GPT/UEFI only. Thus, when Ventoy 1.0.62 gets plug-in manager, I get ready information to helpful details right away. Cool!

If you’re not already familiar with Ventoy, it includes two partitions on USB attached storage media. The bulk of the device is exFAT formatted, and provides storage for ISO, WIM, VHDX, and other mountable cabinet or image formats. The VTOYEFI partition (32 MB FAT) has just enough smarts to get the PC running, mount an image, and then pass boot control over to that image. The result is a way to store all of your Windows (and other OS) images in one place, along withe repair tools, and boot into them as and when you need to.

If Ventoy 1.0.62 Gets Plug-in Manager, Then What?

Why, download and install if you’re not already using the tool. Or download and update if you already are. The Plugson GUI manager is a major step forward in functionality, visibility and insight, and improved control over the program. I’m not sure I understand all the wrinkles just yet. Thus, I plan on writing about it again after some more time spend fooling round … err … experimenting with its features and functions.

The more I look at plugson the more things I find to like about it. This program has evolved considerably over the three years or so it’s been available. And it just keeps improving and extending what it can do. Good stuff, and a great tool for Windows admins and enthusiasts.

Facebooklinkedin
Facebooklinkedin

Windows 11 Build 22509 Control Panel Changes

It’s been a long time coming, and it could still be some time coming yet. But Windows 11 Build 22509 Control Panel changes show the shape — if not the ultimate destination — of things to come. The lead-in graphic for this story shows Control Panel (CP) from Windows 11 left, and Windows 10 right. (Right-click the image and select “Open image in new tab” or equivalent to see it in its full glory.) Careful examination of the image shows items missing from 11 include Administrative Tools and Windows Tools. The new look includes more modern icons and rounded corners, too.

What Windows 11 Build 22509 Control Panel Changes Presage

The loss of Administrative Tools and Windows Tools is no big thing. Administrative Tools is a portmanteau in File Explorer that leads to a bunch of stuff easily accessible through other means. It includes:

Windows 11 Build 22509 Control Panel Changes.admin-tools

A lot of this stuff is seldom used, and all of it is easily accessible by name, through God Mode, and other means…

Same thing goes for Windows tools, which provides access to 36 items ranging from Character Map to WordPad (in alphabetical order), with considerable overlap with the previous Administrative Tools item. IMHO, neither of these leaving CP is a loss, let alone a great one.

Look for Increasing Vanishment Ahead

Long term the impetus seems clear. MS will move more stuff out of CP and under Settings. Ultimately, CP might disappear completely. But that’s probably a long-term phenomenon at least a few years into the future, if not further out that that. According to WindowsLatest, the next Windows 11 Insider Preview Dev Channel update will do away with still more CP elements. It should be interesting to see which ones go away, and in what order.

As this stuff starts falling out of CP, count on me to keep you informed. I thrive on this kind of administrivia, and revel in sharing it with my readers — that means you! Stay tuned, and we’ll all keep up with the incredible shrinking collection of Control Panel elements.

Facebooklinkedin
Facebooklinkedin

Update Fixes Nitro Pro OCR Issue

The old saying goes “If it ain’t broke, don’t fix it.” I was reminded yesterday that the converse is also sometimes true. I’d been struggling with an OCR issue in Nitro Pro v13. Each time I ran the process on a particular patent PDF (downloaded from the USPTO), the program would crash. Then I remembered that SUMo (Software Update Monitor) had reported a new NP13 update was available on my latest scan. “Hmmm,” I thought to myself, “maybe an update will help…” You could say I clutched at the hope that the update fixes Nitro Pro OCR issue. “Here goes nothing…,” i continued, as I started looking for the latest version download.

Indeed, Update Fixes Nitro Pro OCR Issue

I had to go and download a new version of the Nitro Pro exe. That version number was 13.50.4.1013. Because NP13 lacks a built-in update facility, one must download the exe and manually install it to perform an upgrade. I usually avoid that except in cases of difficulty. But this time, it did the trick. After the update, my next OCR attempt succeeded, as shown in the lead-in graphic.

There’s a “trick” to grabbing Nitro Pro updates. I’ll share it because it will help me remember what I  need to do for my next upgrade, too. You must scroll to the footer (bottom) of the gonitro.com web page, and access the “Downloads” link under the “Support” heading. Here’s what that looks like right now:

Update Fixes Nitro Pro OCR Issue.dl-page

The latest version always shows up at the top of the downloads page.

A link to the latest version always shows up on that page, but is nearly impossible to find otherwise.  I can’t  understand why it doesn’t come up first in a Google search for “Download Nitro Pro.”
It does not: Go figure!

 

Facebooklinkedin
Facebooklinkedin