Tag Archives: featured

Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 10, Windows 11, Windows OS Musings

Zoom Resume Ruminations

January 19, 2022 Ed Tittel Leave a comment

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.

Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 10, Windows 11

Escaping Excess Windows Audio Reverb

January 17, 2022 Ed Tittel Leave a comment

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

Insider stuff, Recent Activity, Updates, WED Blog, Windows 11

No 22533 Dev Channel Flyouts Here … Unless You Push the Right Physical Button

January 14, 2022 Ed Tittel Leave a comment

The latest Dev Channel version of Windows 11 showed up on my test PCs yesterday. That means I was slow on the uptake: its announcement blog is dated January 12 (Tuesday). Be that as it may, that blog post claims that “new flyouts [for volume, brightness, and more] will appear when you press the volume or brightness keys on your laptop.” Alas, I see no 22533 Dev Channel flyouts here on either of my test machines. Instead, I see only the same old “flyout panel at right” shown below. The “new look” appears as the lead-in graphic for this story, courtesy of the afore-linked 22533 announcement.

Alas, I’m still stuck on the old response to clicking the volume icon in taskbar.

If No 22533 Dev Channel Flyouts Here, Then What?

Wait and hope for this to show up on my machines, I guess. MS doesn’t specifically SAY this is a gradual rollout. But the absence of this feature on both PCs certainly suggests that’s the case. I have to laugh: once again I’m on the slow end of the rollout as a nifty new feature shows up. I guess I should be grateful MS shared an image of what I would be able to see, were I lucky enough to have this capability on my own test PCs. All and I can say is, sigh, and sigh again.

That’s the way things go sometimes, here in Windows-World. This is neither the first time I’ve been left out of a gradual rollout — if indeed that’s what it is. And I’m pretty sure it won’t be the last time, either. I’m curious to see what kind of response my experience will engender when I post this info to the WIMVP Teams channel. Maybe I’m doing something wrong, and there’ll be an easy fix. If so, count on me to report back. In the meantime, stay tuned!

The Fix Is In: Push the Physical Button, Doofus!

I heard back pretty much immediately from Brandon LeBlanc on the Insider Team. Seems this flyout REQUIRES a physical corresponding button (volume, brightness, etc) on the PC in use. And presto (pun intended), as soon as I did that, it worked. So much for my “hurt feelings” at not being included. I just had to push the right button and it worked right away. Go figure — and while you’re doing that, indulge in a chuckle at my expense. It was all there in black and white: I just misunderstood.

Uncategorized

DevMgr Now Checks Windows Drive for Updates

January 10, 2022 Ed Tittel Leave a comment

I guess you could say it’s been a long time coming. With the latest Dec Channel release for Windows 11, Device Manager now defaults to the user’s current default drive. That’s instead of the mostly-absent A: drive (usually a Floppy disk) to which it has defaulted since time immemorial. See the new scheme as the lead-in graphic for this story, see the previous default from my Windows 10 production desktop below. Thus, we see that DevMgr now checks Windows drive for updates by default. Woo-hoo!

The old method goes back to earliest Windows, and defaults to drive A:. How quaint!

If DevMgr Now Checks Windows Drive for Updates, Life Gets Easier

As long as you deposit driver files of interest in the same directory as shown in the lead-in graphic on Build 22000 or higher, Device Manager will find them “automagically.” (See this WindowsLatest story for more info, with a shout-out from yours truly.) It’s a minor, minor change but one that could make life easier for admins and power users everywhere. Floppy disks are so … twentieth century. I still have a USB-attachable floppy drive in my “antiques closet” but I can’t remember the last time I used (at least 3 years ago).

From what I can see, the default directory specification may come from MS Office. On my Dev Channel PC it comes up as:

C:\Users\etitt\OneDrive\Documents

But that directory spec doesn’t show up anywhere in my environment variables, so I’m a little curious as to where and whence it originates. From experience, I know that particular Documents folder (the one inside OneDrive) is a default save folder for Office apps. Otherwise, I’m at a loss to explain it. I’ll poke around and see if I can come with a good explanation. Stay tuned for that administrivia and other burning Windows 11 details. Cheers!

Insider stuff, Recent Activity, WED Blog, Windows 11, Windows Update

Substantial First 2022 Dev Channel Build 22526

January 7, 2022 Ed Tittel Leave a comment

I’d hoped that the initial Dev Channel build for Windows 11 would show up this week. I’m glad it did, but it’s something of a doozy. When I say it’s a substantial first 2022 Dev Channel Build 22526 I means it’s big, and it takes a while to download and install. Let me explain…

What Substantial First 2022 Dev Channel Build 22526 Means

First off, I noticed that it took longer than usual to download and install 22526. That means around 15 minutes to download, and another half an hour to install. By contrast, the preceding 22523 Build downloaded in 5 minutes or less, and took about 15 minutes to install. I had the same experience on both test machines, and also had to wait through another 2 minutes or so for OOB experience during the first boot into the OS.

Running WizTree on my two Dev Channel PCs (a Lenovo X12 Hybrid, and aThinkpad X380 Yoga) I see that the size of the Windows folder is 3.2 GB larger for 22526 than Windows.old for 22523. This, too, is kind of unusual. Normally, size doesn’t vary more than 200 MB one way or the other between adjacent versions.

What’s New in 22526?

According to yesterday’s Windows Insider blog post “Announcing Windows 11 Insider Preview Build 22526,” quite a bit is new. The dev team is “experimenting with showing ALT + TAB as windowed instead of full screen for some Insiders.” And whoop! I see that on the X12. Here’s what that looks like, courtesy of SnagIt 2022:

Instead of filling the whole display, ALT+TAB shows up in windowed mode as shown on PCs lucky enough to get this update in 22526.

This is the first time in my personal experience to get selected for a new feature when a limited rollout or A/B test is announced. I’m jazzed.

Other new items in 22526 include:

Support for wideband speed using Apple AirPods to improve voice call quality
Credential Guard now enabled by default on Domain-joined Windows 11 Enterprise (E3 and E5) licensed PCs
File Explorer will index more file locations to make native file search faster and more efficient

Don’t know where the size bump comes into play among all this stuff, but it’s definitely noticeable.

2022 Insider Previews Off to Interesting Start

I’m tickled to see new stuff showing up so soon. I’m even more tickled to be included in the select few who get to see new features under test. It should be interesting to see how things develop, as we work our way deeper into the New Year. Stay tuned: I’ll keep you posted.

Insider stuff, Recent Activity, Tips, Tricks and Tweaks, Troubleshooting, WED Blog, Windows 10, Windows 11

MS Assistant Whacks Word Weirdnesses

January 5, 2022 Ed Tittel Leave a comment

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.

Insider stuff, Recent Activity, Tips, Tricks and Tweaks, WED Blog, Windows 11, Windows gadgets

Windows 11 Hints Third-Party Widgets

January 4, 2022 Ed Tittel Leave a comment

I confess: I’ve been a fan of Windows gadgets ever since they were introduced in Windows Vista 15 or so years ago (January 30, 2007). I still use them today in Windows 10 and 11, thanks to Helmut Buhler’s excellent 8GadgetPack. Recently, I read intimations that MS would open its Windows 11 Widgets to third parties. I was both intrigued and a little apprehensive to learn that Windows 11 hints third-party widgets. A portion of my Widgets from the Dev Channel build (22523.1000) serves as the lead-in graphic above.

How Windows 11 Hints Third-Party Widgets

As explained in this WindowsLatest story dated January 3, widgets are a little less all-encompassing than gadgets. As Mayank Parmar avers “Windows 11 [widgets] cannot be pinned to the desktop and they appear within the widgets board only.” That said, the same source reports they’ve “seen…documents” that indicate “third-party widgets will be included in Windows 11 version 22H2.”

Because I still use gadgets daily, this information is interesting. Given the right third-party support, it could even be exciting. As you can see to the left, I use gadgets for various purposes, even on Windows 11. For one, they help me keep an eye on system and network activities. For another, they provide an alternative way to shutdown, restart, and so on. And finally, the analog clock on my desktop is easier for me to see and read than the default numeric clock in the taskbar.

If I could get the same functionality from widgets, that would be good. But I also hope MS will provide ways to lock certain widgets on constant display, too. To me, the real benefit of gadgets is that, once parked, they remain visible all the time. For monitoring, time, and system controls this is essential. Note also: the “Control System” gadget (2nd from top) even works in RDP sessions, which normally don’t let you restart or shut down a remotely-connected PC or VM. Very helpful!

I believe opening widgets to third parties in Windows 11 could spur all kinds of interesting functionality and capability. I like the idea of getting such things from the store. But I also hope MS will support locking select widgets on permanent view. Otherwise, I’ll keep using gadgets, too.

We’ll know more as MS releases information to developers to open up widgets to third parties. In the meantime, I’ve got my fingers crossed that somebody will read — and heed — my plea for locked or permanent widgets. Stay tuned: I’ll keep you posted as this situation unfolds.

Letters from the Ed, Recent Activity, WED Blog, Windows OS Musings

Happy 2022 After Road Trip Return

January 1, 2022 Ed Tittel Leave a comment

At about 11:50 PM last night, I woke my dozing wife so we could hoist a glass to the incoming year at the stroke of midnight. Here at Chez Tittel, we’re all still recovering from our major Florida road trip, from which we rolled in at 7:30-ish on the night of December 30. Hence, my well-intentioned wishes to readers for a happy 2022 after road trip return. Auld Ang Syne, and all that…

With Happy 2022 After Road Trip Return, Then What?

In what is becoming a family vacation pattern, we covered lots of ground and saw some super sights on a 13-day trip. We started out from Round Rock, Texas, and bookended the trip with a stay at Crestview, FL, across I-10 from the huge naval air station nominally at Pensacola for the first and last nights away from home. Day 2 was our longest drive, from Crestview to Key West, where we stayed until Day 4.

Here’s how the remaining vacation part of our trip played out:
* Miami Beach at the superb beachside hotel, The Palms (Days 4-7)
* West Palm Beach at the West Palm Hilton (Days 7-9)
* Orlando at the Hyatt Regency next to the Convention Center (Days 9-12)

Day 12 also saw us to Crestview (an easy 6-hour jaunt). Day 13 was a booger, with 13 hours in the car on the way home. To my surprise, we sailed over the I-10 Mississippi bridge in Baton Rouge. Then, we got stuck in a 90-minute traffic jam on the eastbound approach into Houston. (From Baytown to I-610 north, for those who know that part of the world.)

Trip Highlights: Part 1

While none of us is eager to return to Key West (Day 2 of the trip was a grueling 14-hour driving day), we did like the place. Though it’s not in downtown, the Margaritaville Beach House/resort proved to be a well-appointed hotel, albeit with leisurely service and an island state of mind. We had an amazing farewell dinner at the A&B Lobster House on the docks the night before our departure (Day 3). The Boss and The Boy tucked into butter-poached lobsters as big as your head, while I made do with a Oscar-style chunk of grouper.

The drive to The Palms in Miami Beach took less than 2.5 hours. The GPS ran us up Route 1, which I let stand so the family could get a good taste of Miami on our way. Ordinarily, I’d have over-ridden the route and gone up the Florida Turnpike. It was a slow but interesting drive to help see the southern approach to downtown.

In Miami Beach (MB), everybody agreed it was the best vacation spot on our itinerary. We had an amazing Cuban meal at Havana 1957 on Lincoln Street. We got to try a killer Cubano, great ropa vieja and terrific tostones. We also walked 6-8 miles a day during the whole stay, because MB is so walk-friendly. The car stayed in the hotel garage for our entire stay. We took a tour of Miami by bus, and the bay between Miami and the barrier island by boat. Great fun!

Trip Highlights: Part 2

Our next stop was a sentimental destination. My mom lived in Palm Beach Gardens (PBG) from 1991 until 2006, and West Palm is the nearest tourist spot in that vicinity. We drove by her old house a couple of times, but also saw the grand mansions on Palm Beach island, and explored A1A all the way up to Jupiter beach. That included a stroll through the amazing John D. MacArthur Beach State Park on the barrier island to the east of Palm Beach Gardens. It also featured a great Christmas dinner with my Aunt Millie, her daughter, and three of her grand-kids at her PBG condo. Good times!

We also ate twice at a favorite Jewish Deli with many south and central Florida locations: TooJays. We liked it so much, we had our last meal at its Orlando location on our way to Crestview. All I can say is: Best. Matzo Ball Soup. Ever. I mean it! Good shepard’s pie, great pastrami and corned beef, wonderful baked goods, too.

Otherwise, we decided we prefer south to central Florida. On a next trip, we agreed to drop Orlando and Key West. Instead we’ll concentrate on Miami Beach and Palm Beach. Those thinking about a Florida visit of their own should consider doing the same. Cheers!

Back to Business on January 3

I’ll be resuming my normal blogging on Monday, with the real start of the working year for 2022. My first screed will enumerate the contents of the “technology bag” from our trip. I’ll explain what I took with us, how it worked for us, and provide purchase pointers for those likewise disposed. Stay tuned!

Note Added 2 Hrs Later (January 1)

As I re-read this travelogue, it occurs to me that I’m grateful to my readers and those who’ve hired me to work for them. That includes Microsoft (the WIMVP program), Fish & Richardson plus numerous other law firms, Actual Tech Media, ComputerWorld, TechTarget, and the For Dummies… Custom Publications group, among others.

In fact, 2021 turned out to be a much better year than I expected. I have those parties to thank for what success I’ve enjoyed in this current COVID related world of work. I wish everyone only the best for 2022. I hope the New Year is safe, prosperous and, above all, interesting and educational for all of us. Cheers (and thanks) again! =Ed=

Insider stuff, Recent Activity, WED Blog, Windows 11

Windows 11 Year-end Ruminations

December 16, 2021 Ed Tittel Leave a comment

OK, then. I was MIA on the blog yesterday and the day before. I’m also getting ready to take a much-needed break for the rest of the year. For my final post for 2021, I want to share my Windows 11 year-end ruminations and observations. The new OS made its preview debut on June 24 (Dev Channel) and its public debut on October 4 of this year. There’s been lots of activity, things to learn and understand, and various issues to deal with along the way. Let me share some highlights…

Where My Windows 11 Year-end Ruminations Lead

Since day 1 (June 24) I’ve been mostly pleased and impressed with Windows 11. I like its snazzed-up UI, especially the rounded corners and the snappy iconography it uses. It came as much less of a shock to me than did Windows 8 (or 10, for that matter) because it still remains familiar and comfortable to me despite wearing a new set of clothes and offering some new capabilities.

A few glitches aside — such as the AMD and disk drive performance gotchas that have emerged over the past 6 months — Windows 11 has been an entirely positive user and admin experience for me. All of the image manipulation and management, installation and configuration tricks I’ve learned for Windows 10 over the last 7 years have worked for me on Windows 11 so far. That means my comfort level with the new OS is both welcome and quite high.

I understand the ongoing flap about the Windows 11 hardware requirements. I’m rather more amused than pissed off that my still-capable but now 5-year-old i7-6700 desktop doesn’t make the Windows 11 grade. It’s a relief that I currently own only two systems that don’t meet those requirements (the other one is my 2014 vintage Surface Pro 3). I’m going to keep the Surface running until Windows 10 reaches EOL so I can experience what happens as the preceding desktop generation winds down.

I was also impressed and surprised by the out-of-box experience on the Lenovo 11th-gen Yoga 7 14″ thin&light laptop the company sent me for review. The set-up and configuration is fluid and easy, and the OS has worked flawlessly since that unit showed here in October. It is my first exposure to a system with Windows 11 pre-installed and I must say it’s been everything I hoped it would be.

Where Will 2022 Take Windows 11?

We should see the first “big rev” in the fall — if not sooner than that according to the rumor mill. I’m expecting to see more elements fall out of Control Panel and into Settings. I’m expecting more old and familiar “stock apps” (think Notepad, File Explorer, Task Manager, and so forth) get a new look and feel. Some will no doubt experience feature set changes as well (out with the old and in with the new). The turnover of old and new features is a theme I think we’ll see continuing on for many years to come. When it happens I expect to enjoy learning what’s up and then sharing what I learn. Please stay tuned, and take that ride with me.

Let me also wish my readers a safe, prosperous and enjoyable end-of-year holiday season. Look for my daily blogs to resume on Monday, January 3. Happy trails until then!

Yours truly,
–Ed Tittel–

Insider stuff, Recent Activity, Security, WED Blog, Windows 11

New MS Defender Preview Impediment

December 9, 2021 Ed Tittel Leave a comment

I have to chuckle. At the start of November, I wrote here that “I Get No MS Defender Preview.” Just to check up, I went back to the store to grab the Preview. It was no surprise at all that I can still report the same thing. What’s different now is the error message that comes up, as shown in the lead-in graphic. My latest sticking point represents a new MS Defender Preview impediment. As you can see, my account is now recognized, but I can’t log into the preview. Sigh.

Clueless on Overcoming New MS Defender Preview Impediment

I’ve dug around online, at both Microsoft and third-party Windows sites. I cannot find any info on how to subscribe to the Microsoft Defender Preview. Presumably, that would also provide me with necessary login info. But there’s no enlightenment obtainable on how that might be arranged.

Often, when Windows features go into limited release in the Preview channels, I find myself at the end of the pack in gaining access. That phenomenon seems likely in this case, too. I’ll raise a flag in the WIMVP forums and see if I can provoke any action. Shoot! I’d be happy just to get more information on how to subscribe and start participating in the Microsoft Defender Preview.

But — as is so often the case in my experience — I’m on the outside looking in. I know this Preview is happening. I simply can’t get access to it, to sample its functions and capabilities. Stay tuned: I’ll keep you posted as I try to work my way into that charmed space. Hopefully that will happen sooner rather than later. We’ll see!