Category Archives: Cool Tools

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

File Explorer Restart Fixes Start Menu

June 20, 2023 Ed Tittel Leave a comment

I don’t know what I — or Windows itself — did. But I do know for sure that when I logged into my production PC this morning, Start Menu search was broken. I could type anything I wanted into the search bar. But each search came up empty. I could still navigate to apps alphabetically, so I knew something odd or interesting was up. Fortunately, among its many other good qualities, a File Explorer restart fixes Start Menu, too.

How File Explorer Restart Fixes Start Menu

The lead-in graphic shows how it’s done. Fire up Task Manager (I like to use the CTRL-Shift-Esc shortcut, but you can right-click on the Taskbar to get at it through a pop-up menu, too). Find Windows Explorer (I still think of it by its older name as in the title for this blog post), right-click, and select “Restart” from the pop-up menu.

As the term indicates, this basically kills the runtime environment for Windows/File Explorer, which includes the Start Menu, the taskbar, and other stuff, as well as any and all open Explorer windows. All this gets restarted afresh. And when that happens, the new and pristine runtime usually works as it should.

Case in point this morning: my broken Start Menu search function started working again. I cheerfully confess I simply wanted to play Solitaire. But typing “Sol” into the search box did nothing for me. The fix took less than 10 seconds to complete, though. And when it was done it was back to “Windows business as usual.”

Good! That’s just what I wanted… Keep this in your hat: it’s sure to come in handy someday here in Windows-World.

Backup/Restore, Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 11

Windows 11 Restore Point Pros&Cons

June 19, 2023 Ed Tittel 2 Comments

I’ve got to admit it: I’m of two minds about restore points in modern Windows versions — especially Windows 11. I found myself chewing over Windows 11 restore point pros&cons this morning, as I used WizTree to check my boot/system drive on some test PCs. Let me explain…

Exploring Windows 11 Restore Point Pros&Cons

Let’s start with a basic definition courtesy of Gavin Wright/TechTarget:

A system restore point is a backup copy of important Windows operating system (OS) files and settings that can be used to recover the system to an earlier point of time in the event of system failure or instability. It is a part of Windows XP, Vista, 7, 8, 10, 11 and Windows Server. They are created automatically or manually. System restore points only affect OS and application files, but not user data.

I confess: up through and including versions of Windows 8, I used to use Restore Points a LOT. But since the introduction of Windows 10 in 2014/2015 — quite some time now — I’ve been using daily or weekly image backups on my production and test PCs almost exclusively. These protect user preferences, settings, and data as well as the “important OS files” mentioned in the preceding definition. For me, it’s also faster and easier to restore an image backup than it is to do likewise with a restore point (and with less certain results). FWIW, I still use Macrium Reflect Free as my primary backup and restore tool. (I use the paid-for version on production PCs.)

Restore Point Pros

If, as shown in the lead-in graphic, you have restore points turned on, Windows will make them for you automatically or manually. They’re created automatically when you apply Windows updates. Likewise, many application installers are built to make a restore point early on in their operation, so they can roll back to a point in time prior to their actions in case something goes wrong. Also, you can create a manual store point by clicking the “Create” button shown at the lower right in the lead-in graphic. If you do choose to use restore points, I also recommend grabbing and trying out Nic Bedford’s System Restore Explorer as well. IMO, it’s easier to use and more comprehensive than the built-in Windows facility.

Restore points are easy, somewhat automated and cover many OS or runtime issues. This makes them easy and convenient to use, especially for less savvy and sophisticated Windows users. In a nutshell, those are the pros for restore points.

Restore Point Cons

In using WizTree to explore a couple of my test machines this morning, I was reminded of one of the cons for restore points — namely, they can soak up a fair amount of disk space. When I use the “Delete all restore points…” option on one of my Lenovo ThinkPad X380 Yoga PCs this morning, here’s what WizTree showed as deleted immediately afterward:

All in all I recovered almost 6 GB of disk space by deleting all restore points.
[Click image for full-sized view.]

The impact of restore points can be up to the size limit you set aside for such use. As shown in the lead-in graphic, that’s 19.05 GB for my “other” X380 Yoga test PC. If you’re making image backups and restore points, it’s a good idea to allocate no more than 1% or 10GB (whichever is less) for such use.

Besides space issues, I’ve observed that restore points don’t protect you from unwanted registry changes (including preferences, settings, use of tweak tools and so forth). Nor do they restore user or application data files and such, either. In general, I favor image files because they include absolutely everything that might get changed — or go wrong.

That said, if you use an image restore, you will lose any new files or changes you’ve made since the time at which that image was captured. Thus, it may be necessary for you to run a “mini-backup” to save that stuff to a flash drive or other external media before restoring the most recent image so you lose less (or nothing). Because Reflect lets me mount an image as a virtual drive, I often make another image of my broken system just in case I need something from that set-up after I revert to my most recent saved image.

What’s Your Preference?

On your Windows PCs, you can do as you like with backups and restores (including restore points). I don’t use them anymore because they don’t bail me out of all the trouble I often get myself into. If your usage patterns are less experimental or extreme, restore points may indeed meet all your needs. Even so, I’d still recommend periodic image backups just in case they don’t work to get you of some of the jams you may occasionally get into. But again: that’s up to you!

Cool Tools, Insider stuff, WED Blog, Windows 11

Chasing Canary Focus Sessions

June 16, 2023 Ed Tittel Leave a comment

I have to laugh — or, at least, chuckle. After reading about a new Focus sessions widget at MSPowerUser I went chasing after same. I should have known it might not be as available as one might hope. It’s on gradual release. Indeed, it shows up only in one of two of its possible haunts. After chasing Canary Focus sessions for a while, let me explain how I figured this out.

Chasing Canary Focus Sessions
May Yield Mixed Results

The first key to focus sessions is an update to the Clock app. It needs to get to version 11.2305.6.0 (or higher). That should come easily, courtesy of a quick hop into the Microsoft Store’s Library tab, where clicking the “Get updates” button should true up a Canary PC or VM. Indeed, as you can see in the app window from Clock that appears at the head of this blog post, “Focus sessions” is the first element in its left-hand menu (also expanded to fill the right-hand pane as shown).

But a pane in a Windows 11 app is not a widget. So I went to both places where one might expect to find such a thing with mixed results:

1. To the Dev Home (Preview) app, where one can click the “+Add widget” button on its Dashboard pane to pin another widget thereto. But alas, the list of available widgets does not include “Focus session” amidst its still-limited set of offerings.

2. To the news/weather bug on the Canary task bar, where clicking on same opens a larger panel that includes this entry:

After clicking “Add them now” I *DO* see “Focus session” as an available item. Clicking same produces the Focus session widget at the top of the expanded news/weather bug window. Goody!

What Did I Just Learn?

Only some widgets make it onto the Dev Home (Preview) dashboard. Many more are available through the expanded news/weather bug pane. For the time being, it looks like the Focus session widget is one of the latter, but not one of the former. That’s one specific lesson learned.

The bigger implication is that not all new widgets that MS announces will pop up in both places. Only some will make it into the Dev Home dashboard, while all should indeed appear through the expanded news/weather bug. Consider yourself so informed.

Cool Tools, Insider stuff, Recent Activity, Updates, WED Blog

Tracking Minor Updates Poses Diminishing Returns

June 13, 2023 Ed Tittel Leave a comment

Here’s a question whose best practices answer may save admins time and effort. While indeed many developers now push regular updates for their software, not all are equally urgent. Why? Because whereas some updates add valuable new functionality or plug serious security gaps, others may not introduce much of note. That’s why, IMO, tracking minor updates poses diminishing returns against the time and effort required to find, download, and install them.

A case in point appears in the lead-in graphic. Antibody’s WizTree is a tree graph oriented disk space layout visualization and management tool. You’ll notice that winget doesn’t track release numbers past the first sub version level (e.g. 4.14 is what its “show” sub-command displays, and what its “list” sub-command finds on the target PC).

Why Say: Tracking Minor Updates Poses Diminishing Returns?

Simply put, if winget doesn’t track it and package labels don’t include it, not even the developer thinks it’s noteworthy. I’ve had other development teams confirm this approach to me. Thus, for example, when I contacted IObit to ask about minor revisions to their Driver Booster tool (example version number 10.4.0.127) they’ve told me that they don’t advise users to update unless something new or security-related is changed in a new version. If so, their policy is to increment version numbers more significantly, and to use the tool’s auto-update function to recommend and flog the update process forward.

Long story short: if the developer doesn’t recommend installing every minor update that comes along, I can’t do otherwise. For one thing: life’s too short to keep up with absolutely everything. For another, working toward scheduled update windows for most corporate software means choosing only “worthwhile updates” for inclusion. This reduces the amount of change — and its attendant risk — during such windows, and keeps the time and effort required to survive them as manageable as possible.

The old saw: “If it ain’t broke, don’t fix it” somehow seems apt. Don’t let OCD tendencies to keep up with all change put you in a bind. Relax, and watch the blinking lights instead…

Cool Tools, Insider stuff, Recent Activity, WED Blog

Chrome Signals Busy During 114 Update

June 8, 2023 Ed Tittel Leave a comment

Here’s something I’d never run into before. Yesterday, while attempting to upgrade Chrome from a 113.x to the latest 114.y version, I got a “servers busy, try again later” error message. That’s why I’m saying Chrome signals busy during 114 update. Interestingly, this meant that even downloading and running the installer didn’t work. It couldn’t get anything from the servers, either.

If Chrome Signals Busy During 114 Update,
Then What?

Wait for the condition to clear, of course. The denial of service lasted for under half and hour as far as I could tell. But that made me chuckle at the slogan from the download page that appears in the lead graphic. Indeed, there was no place like Chrome yesterday at all. You couldn’t get there from here — at least, not for a while.

Once the servers started responding to download requests as usual, the update went through without difficulty. I guess that’s just the way things sometimes go, here in Windows World. The old saw that begins “If at first you don’t succeed…” somehow comes to mind in this context.

Poking Around Inside Chrome Settings…

While waiting for the DoS to clear, I started poking around inside Chrome settings to see what was new. In turn, this led me to the “chrome web store” where I found some interesting themes and extensions to look at and play with. Given the prevalence of JSON in Windows Terminal, PowerShell, WinGet and other tools, I’m definitely going to take the JSON Formatter for a spin.

Sounds like fun, in fact. So yesterday’s dithering and delay was by no means a total wast of time. And now, the latest Chrome version has made its way onto all of my Windows PCs. Cheers!

Cool Tools, Insider stuff, Recent Activity, Troubleshooting, WED Blog

Winget Zip Support Is Uncertain Right Now

June 5, 2023 Ed Tittel Leave a comment

I have to laugh, because that beats crying. Upon reading about built-in support for ZIP files added to winget v1.4.0.1071, I had to try it (note: it works in some Preview 1.5.1081 installs as well). I ran into issues on various PCs,owing to a missing dependency item. You can see what that error looks like in the lead-in graphic. It worked on some of my PCs but not all of them. Hence I say: Winget Zip support is uncertain right now. It works in some cases, in others it doesn’t.

Exploring Winget Zip Support Is Uncertain Right Now

If you look at the winget output in the lead-in figure, you’ll see the problem isn’t really with the unZIP process. That completes OK as the output line “Successfully extracted archive…” indicates. It blows up after that as it attempts to use the extracted files to drive actual installation. I’ve reported this to team lead Demitrius Nelson, and he suspects some additional framework package is needed. Seems likely given that “dependency missing” is explicitly cited in the last line of the error message.

I did succeed on a few of my systems whereas several others failed with the error message shown above. Here’s how success looks:

When things work, it simply installs from the (temporarily) unzipped archive’s contents. Good-oh!

The Store Version Works Around the Issue

If you don’t want to wait for MS to fix this particular — and quite minor — gotcha, download and install the MS Store version instead. I already know that works just fine because I blogged about it last Thursday: Exploring Windows 11 Dev Home. As a member of the “I have to see it working” club, I’m glad I tried winget to take an alternate install path this morning. That gave me the opportunity to report an interesting gotcha to the dev team. And indeed I got a response back within minutes when I reported my findings to them.

Further, I’m pleased to report that I just tried the MS Store technique on one of my affected PCs, and it worked. The Preview version of Dev Home is now running on that machine. Good stuff!

Note Added June 5 Late Afternoon: Fixed?

I reported the issue this morning and got an immediate response with an explanation and a workaround. Just now, I successfully installed DevHome on two more PCs, with no issues. My sample size is waaaaaaaaay too small for me to say “Fixed” But I can say that perhaps it has been addressed. Thus, fixed? No further direct from the WinGet team means I cany guess, but my guess is — I hope — a good one.

Cool Tools, Insider stuff, Recent Activity, Updates, Windows 10, Windows 11

Winget Upgrade May Require Cleanup

June 2, 2023 Ed Tittel 7 Comments

OK, then: yesterday dev lead Demetrius Nelson and his Winget team pushed an upgrade to winget. This comes courtesy of the Microsoft Store, and shows up as part of the App Installer and/or Windows Terminal packages. I noticed also that winget would occasionally throw the error “Failed in attempting to update the source: winget” as you can see in the lead-in screencap. What made it interesting was that it happens on some, but not all, of my Windows PCs. Now, let me explain why this post says that the “Winget upgrade may require cleanup.”

Why Say: Winget Upgrade May Require Cleanup?

When I saw this pop up in the wake of the new release, I figured the changes involved in pushing it out the door might have been involved. So I contacted Mr. Nelson and sent him (among other info) the screencap that leads this piece off. He responded this morning and explained how I could fix the issue, using the commands:
winget uninstall Microsoft.Winget.Source_8wekyb3d8bbwe winget source reset --force
The first string removes the winget package from the PC. The second resets the winget environment, which is why the user must agree to Terms again before winget will run. After that it shows no upgrades are available (“No installed package found matching input criteria” with no accompanying error message (“Failed in attempting to update the source: winget”).

Problem solved; case closed. It’s always good to get the fix right from the source. Had to laugh about the “It won’t break while the engineer is watching” comment he sent me, too. Isn’t that just the way things go in Windows-World (and elsewhere in life)? LOL

See the whole thing here:

The fix is in — and working! Good stuff…

Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 11

Exploring Windows 11 Dev Home

June 1, 2023 Ed Tittel Leave a comment

Last week, MS released Windows 11 Dev Channel Build 25375.1 (May 25). Having finally gotten a little ahead of my workflow, I visited the MS Store to download Dev Home (Preview). This afternoon, I’ve been exploring Windows 11 Dev Home (Preview) to see what’s what. So far, it’s pretty interesting…

When Exploring Windows 11 Dev Home, Try These…

In the Dashboard, the “+Add Widget” button lets one add widgets for things that include Memory, Network, CPU and GPU. Of course, as a long-time 8GadgetPack fan, I had to try them out. Here’s what they look like:

The various hardware subsystem widgets aren’t too bad — but not equal to gadget counterparts, either.
[Click image for full-sized view.]

Other elements of Dev Home — as you should expect from the name — are distinctly developer focused. You can interact with GitHub and other development platforms, and configure devices for development using XAML or YAML configuration files (just like the newly-added winget capabilities, through no coincidence whatsoever).

The Official (Store) Word Sez…

MS describes Dev Home (Preview) as follows:

Dev Home is a control center providing the ability to track all of your workflows and coding tasks in one place. It features a streamlined setup tool that enables you to install apps and packages in a centralized location, extensions that allow you to connect to your developer accounts (such as GitHub), and a customizable dashboard with a variety of developer-focused widgets, to give you the information you need right at your fingertips.

This is an open source project and we welcome community participation. To participate, please visit https://github.com/microsoft/devhome

This makes for some interesting and potentially useful capability under a single umbrella. So far, I’m having fun looking around and messing with the widgets. Later on, I’ll get more serious about the dev side of things, and bring Visual Studio and other elements into play. Stay tuned!

Backup/Restore, Cool Tools, Recent Activity, WED Blog, Windows 11

Windows 11 Beta Shows OneDrive Holdings

May 31, 2023 Ed Tittel Leave a comment

OK, then. Here’s a minor –but nice — addition to Windows 11 that shows up in Build 22631.1825. That’s right, Windows 11 Beta shows OneDrive Holdings, as you can see in the lead-in graphic. Start → Settings → Accounts takes you where you need to go. It’s right up top, under a heading named “Microsoft storage” as shown in the image.

If Windows 11 Beta Shows OneDrive Holdings, Then What?

I’ve been wary of using OneDrive as a shared file store across multiple PCs. Why? Mostly because things sometimes show up in OneDrive without my specific knowledge or intent. I’ve learned, for example, to explicitly target screencaps in the Pictures folder under my user account folder hierarchy rather than defaulting to the Pictures folder in OneDrive. I shoot tens to hundreds of MB of screencaps monthly (mostly to write about them). I don’t necessarily want them to follow me around to all of my PCs. Ditto for other common Windows File Explorer library folders (Documents, Downloads, Videos, etc.).

But now, I may have to rethink how and when I use OneDrive. It’s now much easier to see when things grow (or worse, mushroom out of control) in that shared store. It occurs to me, for example, when updating apps across my mini-fleet (about a dozen PCs) it might just be easier to download once, stick it in OneDrive, then use it where needed. Just a thought…

Managing OneDrive … Carefully

Searching Google for “OneDrive Manager,” I see numerous third-party tools — and lots of tutorials — aimed at keeping this unruly beast tamed. Methinks I need to spend some time digging, learning, and thinking. I already use Google Drive, Box, and DropBox to good effect (particularly with legal clients). I believe I can and now, should, learn to do likewise with OneDrive. Stay tuned!

Cool Tools, Insider stuff, Recent Activity, WED Blog, Windows 11

RingCentral Requires In-app Upgrade

May 30, 2023 Ed Tittel Leave a comment

In checking over my mini-fleet (1 dozen) of Windows PCs this morning, I came across an interesting winget gotcha. The tool cheerfully informed me RingCentral needed an upgrade. But neither a general upgrade (winget upgrade –all …) nor a targeted upgrade (winget upgrade RingCentral.RingCentral-v …) did the trick. Today, at least, it seems that RingCentral requires an in-app upgrade to bring itself up to snuff.

Why RingCentral Requires In-App Upgrade Is Anybody’s Guess

The whole story plays out in the lead-in screencap. It shows winget upgrade, as it includes RingCentral in its list of item in need of same. Then it shows the general upgrade (winget upgrade –all –include-unknown) updating 2 of those 3 items (excluding RingCentral). Then it shows a general RingCentral command (winget upgrade RingCentral.RingCentral), and a version specific invocation both failing with “No applicable upgrade found.” (If you can’t see it as-is, open the lead-in graphic in its own tab, please.)

So I opened the app and — guess what? — it cheerfully updated itself as part of its startup behavior. I searched the RingCentral knowledge base for insight, but found none.

Installed Apps Tells a More Nuanced Story…

In checking the target PC (one of my road laptops: a Lenovo ThinkPad P16 Mobile Workstation) I found not one — but TWO — instances of RingCentral installed on that machine.

In addition to version 23.1.31.7242 — which winget told me I needed — I also found version 23.2.21.7380. Interesting!

I uninstalled the older version, and RingCentral no longer needs an upgrade but still launches. But alas, it no longer shows up in winget, either. Even more interesting. So I just went into the app and made sure it is working (it is) and that it’s running the advertised most current version 23.2.21.7280 (it is).

But winget still shows “No installed package found matching input criteria.” Looks like this version does not register with winget. It doesn’t show up in SUMo, either. But the 23.1.31.7242 version DID show up in “winget list ringcentral” in the earlier screencap. So I think we’re dealing with something new from the developer for which a winget package is not yet defined. Again: interesting! My first time to see something like this.