Category Archives: Cool Tools

Build 25158 Camera App Reworked

The latest Dev Channel build includes a new iteration of the venerable Camera app. Indeed, in Build25158 Camera app reworked includes a brand-new, much sparser interface with simplified controls. No settings at all, in fact, as far as I can tell.

If Build 25158 Camera App Reworked, Then What?

Contrast that look and feel from the lead-in image with the Windows 10 version (from higher up in the same baker’s rack in my office). Settings are shown this time at left in the following screencap.

Build 25158 Camera App Reworked.win10-compare

Am I wrong to see the lack of more detailed controls as a loss of capability? [Click image for full-sized view.]

Indeed, most image manipulation is a post-processing task. But I occasionally found it useful to use some of the various controls that the old Camera app made available but which — as far as I can tell — the new Camera app does not. Particularly, the framing grid for image selection and layout help, and the photo quality and aspect ratio controls. To me, this turns the new camera into a more limited, image grab only, kind of function. It’s OK, but it’s not as flexible as the older version.

Running Against the Grain

This is kind of interesting, because most of the new-version or reworked apps showing up in Windows 11 include added functionality and capability, rather than a reduction in same. Favorite example: the sometimes elusive tab feature in File Explorer. Although it has turned into something of a now-you-see-it, now-you-don’t phenom in recent Dev and Beta Channel builds, I do like it and think it represents a useful (if not long overdue) extension to what that tool can do.

The camera changed are described in a a July 13 Windows Blog. It does apparently gain improved QR and barcode scanning. The biggest accolade reads “match the beautiful new look and feel of Windows 11.” It says nothing about the banishment of Settings and related controls. Go figure!

Facebooklinkedin
Facebooklinkedin

Choose Reflect Backup Drives Carefully

I’m a HUGE fan of Macrium Reflect. Available in both free and for-a-fee forms, I’m convinced it’s the best Windows image backup tool available today. Disclosure: I run both free and fee-based versions, and own a Home 4-Pack license that I upgrade as new versions are released. I was reminded to choose Reflect backup drives carefully yesterday, when I targeted an older USB 3 drive with mSATA SSD devices under its hood. Let me explain…

Why Say: Choose Reflect Backup Drives Carefully?

Because the read and write speeds of the underlying device and the speed of the channel (USB 3.1 in my case here) matter. In fact, they strongly affect the time it takes to complete a whole-image backup. In targeting an mSATA device that backup took nearly 40 minutes to complete.

I’m making the same backup right now, and targeting a PCIe x3 NVMe SSD in a Sabrent USB-C enclosure right now. As you can see from the lead-in graphic, Macrium Reflect currently guesstimates it will take 19 minutes to complete. That’s just over 50% faster than the mSATA number, or about 20 minutes overall.

If such a task is running in the background, and can complete whenever it’s done, that doesn’t matter much. But if, as in my case, I was waiting on completion to do something else, it matters a lot.

And There’s More…

While watching the NVMe and mSATA image backups proceed, I noticed another difference. The transfer rate for the two backups not only differed but so did their variability. The NVMe device kept getting faster as it proceeded. It ranged from a low of 1.1 Gbps to a high of 1.8 Gbps. The mSATA device started out at around 600 Mbps, It dropped as low as 220 Mbps, and as high as 1.0 Gbps during the course of the backup process.

Upon completion, Reflect also shared other stats worth noting. The overall read rate for the mSATA device was reported at 1.6 Gbps, while its write rate came in at a less stellar 550 Mbps. On the NVMe device, the overall read rate was 6.6 Gbps, and the write rate 1.9 Gbps. That’s a BIG difference, and explains the title for this story. Yes, these numbers appear inflated because they take compression into account. But those are the numbers that Reflect reports, and they do underscore the importance of device read/write speeds.

Note: Actual time for the NVMe backup was 19:31, while actual time for the mSATA backup was 39:52.

Facebooklinkedin
Facebooklinkedin

Windows Terminal PowerShell Selection

I have to laugh. Yesterday, I noticed version 5 of PowerShell  running inside Windows Terminal. So I naturally wondered: “How do I upgrade this?” Turns out, in fact, that no upgrade is needed. It all comes down to the current Windows Terminal PowerShell selection. I’ll explain shortly, but first: look at the window in the lead-in graphic.

Managing Windows Terminal PowerShell Selection

By default, version 5.1.xxx… appears when you open Windows Terminal. But it’s easy to get to a newer PowerShell version. No upgrading is necessary: you need only know how to do this. If you click on the down-caret at the far right of the title bar, a menu appears, like this:

Windows Terminal PowerShell Selection.choose shell

The down-caret menu lets you choose among shells you can run in a Windows Terminal tab. [Click image for full-sized view.]

The trick — if you can call it that — is to choose the right version of PowerShell (and corresponding default) to run. The top item in the menu corresponds to version 5.1.xxx. The fourth item down brings up the latest 7.x PowerShell version (specifically, 7.2.5). If you click Settings, you can also choose this version as the “Default Profile” which makes the new version (rather than the 5.1.xxx version) appear whenever you open Windows Terminal, or click the “Plus” sign to open a new default Terminal tab.

As with many other things in Windows World, foreknowledge and understanding are key to doing things right. In my case, I had no need to update PowerShell. I only needed to pick the right version to run inside Windows Terminal. Now I know how. If you didn’t know how already, this should make things equally simple for you. Cheers!

Facebooklinkedin
Facebooklinkedin

Change Dev Channel Task Manager Default View

Here’s a nice little addition that’s popped up in the Dev Channel version of Task Manager. If you visit its Settings page, you will see a “Default Start Page” pull-down menu there. This makes it easy to change Dev Channel Task Manager default view. My preference is Details, as shown here:

Change Dev Channel Task Manager Default View.details

Because it’s my go-to view, I set “Details” as the default in Task Manager.

Why Change Dev Channel Task Manager Default View?

For convenience, mostly. It’s not a huge deal in terms of added functionality. But anything that saves a mouse click is helpful, when it comes to getting down to work, eh? In general, MS seems to be moving to a move open, less cluttered layout for Task Manager in the Dev Channel version. It takes a little getting used to, but I like it.

My eyeballs are still better trained to make sense of the old-fashioned Task Manager that’s still visible in Windows 10 and other Windows 11 versions (for me that mostly means production version, Build 22000.778). The contrasting yellow shades for data cells are still more recognizable to me.

But, as with all things Windows, changes spur us on to learn and appreciate new things. That’s how I’m going to play the evolution of Task Manager. We’ll probably have side-by-side versions for Windows 10 and 11 for some time anyway, what with Windows 10 EOL not until October 2025.

But Wait, There’s More…

Turns out you can change the default tab for older Task Manager versions, too. The menu fiddling is a bit different though, as shown in the next screencap:

A different sequence of menu picks changes the default view in old Task Manager iterations.

As you can see in the preceding screenshot, click Options → Set default tab → and then any of the items shown (Processes, Performance, App history, Startup, Users, Details, Services) to make your selection. Good stuff!

[Note] Here’s a shout-out to Mauro Huculak at Windows Central, whose July 8 story clued me into this new wrinkle on an old favorite Windows tool. Thanks, Mauro!

Facebooklinkedin
Facebooklinkedin

More WingetUI Interactions

OK, then. I’m using WingetUI as an element of my Windows PC update toolbox. Along the way, I’m finding some areas where it shines, and others where it doesn’t. But as I gain familiarity with this tool, more WingetUI interactions convince me it’s worth using. That said, it’s no silver bullet for Windows updates, either. Let me explain…

After More WingetUI Interactions, Another Status Report

If you look at the lead-in graphic, I can point to elements where WingetUI shines, and those where it doesn’t. It handles most third-party apps perfectly (e.g. 7-Zip, Kindle, SUMo, Python 2, and Spacedesk). Not so for MS components, except for C++ runtime elements. It failed (or I didn’t try based on prior failures) with Edge WebView2, Teams, and the WADK. This is not a huge problem for me.

SUMo also catches the follow items that did not show up on the WingetUI radar: Chrome, Firefox, CrystalDiskInfo, Intel PROSet utility, MyLANViewer, Nitro Pro, Notepad++ (a false positive, IMHO), Snagit and Winaero Tweaker. Thus I must continue to use a collection of tools to get through my entire update roster. But I knew that already.

All’s Well That Ends Well

I was able to use PatchMyPC to handle the routine updates that WingetUI didn’t see. SUMo led me to fix everything except Intel PROSet, Nitro Pro, and Snagit. I got the first and last myself, and skipped Nitro Pro for the moment (though I did find install syntax for the latest version using winget itself, which I’ll try again later…).

[Note added 1 Day later…] Eventually, I jumped to the Nitro Pro download page (Product Updates) to grab and install the latest version (13.67.0.45). That got me completely caught up. What I now can’t understand is why winget will sometimes update Nitro Pro for me, but why I must do it manually at other times. I’m guessing it depends on package prep and info…

 

Facebooklinkedin
Facebooklinkedin

25145 Gets File Explorer Tabs

OK, then. It’s been a gradual roll-out, so I can’t know if everyone running Dev Channel can see this. But once I got it running, Build 25145 gets File Explorer tabs on both of my test PCs. It’s pretty cool, too, as I hope to show in the ensuing discussion.

To get this party started, you can see File Explorer in the lead-in graphic. It’s got the default tab (“Home”) open at left, the UUPdump folder from my D: drive open at right. The latter shows the various files left over after an .ISO file is created (~4GB item, 6th from top).

When 25145 Gets File Explorer Tabs, Then What?

Why, you mess around with them to see what they can do. So far I’ve discovered multiple techniques to open such tabs, including:

  1. Click the Plus sign (“+”) to the right of the rightmost open tab, and an open tab set to the default appears. Navigate anywhere you want from there.
  2. Right-click a folder inside the main File Explorer pane, and a new option labeled “Open in new tab” appears. I *like* this one! Here’s what it looks like (annotated for easy recognition).

3. I remember reading about a keyboard shortcut to open such a tab, but I can’t find the reference. Winkey+E still opens a new File Explorer window, and WinKey+T doesn’t do anything. I’ll keep poking about on this front, and see what I can learn. So far, the best third-party coverage of the feature I’ve found is at WindowsLatest.

This is a cool and helpful new feature. As I learn (and find out) more about it, I’ll either update this post, or write a new one. Stay tuned!

Facebooklinkedin
Facebooklinkedin

WingetUI Offers Useful Update Capability

Lately, I’ve been using the Winget PowerShell applet to assist with updating my Windows 10 and 11 PCs. Thanks to Martin Brinkmann at Ghacks, I’ve found a GUI front end for that tool. Indeed, the aptly-named WingetUI offers useful update capability.

Winget.UI does other things, too. It let you explore all 3460 packages under its purview (“Discover Software” tab). It also shows a complete list of all packages already installed on your PC (“Installed applications”). On first blush, Winget.UI looks like a good tool. Its GitHub page provides the lead-in graphic for this story.

Winget.UI Offers Useful Update Capability.updates

“Available updates” quickly identifies and provides ready access to item-by-item update launch. [Click image for full-size view.]

What WingetUI Offers Useful Update Capability Means

To update an item from the Software Updates tab in Winget.UI (shown above), simply double-click its corresponding Winget entry under the “Installation source” heading. Personally, I find this prefereable to the winget upgrade --all command. Why? Because it provides item-by-item control. That lets me skip elements (such as MS Teams), which experience has taught me isn’t really amenable to winget updates.

The double-clicking takes a little getting used to, but by and large the update function works well. It worked well for third-party packages, including Kindle, Python 2, and Revo Uninstaller. It hit errors on some built-in MS components, such as the WADK and Edge Runtime. Based on prior history, I didn’t even try the Teams components.

Good, But Not Perfect

I’ll need to spend more time with WingetUI to fully understand and appreciate its foibles and strengths. For now, it’s much like other update tools I use: good — indeed, pretty helpful — but by no means either great or perfect. Perhaps that’s just the way that update tools work here in Windows World!

[Note: Nochmals Danke schoen to Mr. Brinkmann for an interesting find.]

Facebooklinkedin
Facebooklinkedin

Windows Docking Rules Legal Computing

OK, then. I just spent the last week in Waco, at the courthouse for the US Western District of Texas. A few blocks away, the law firms I worked with rented office space at Legal Lawfts on 4th street. In both locations I noticed (and used) a key technology for computing. When I say “Windows docking rules legal computing” I mean that 90-plus percent of the PCs in use ran Windows (10 mostly). And even the lone Macintosh I saw also used a dock for extended functionality.

What Windows Docking Rules Legal Computing Means

When lawyers, witnesses and support staff go to trial, that’s essentially an “away team” exercise. But nowadays when they rent office space, desks come with one or two monitors, external keyboard and mouse, and — you guessed it — a USB-C/Thunderbolt dock of some kind. Thus, I too was able to benefit from a 27″ monitor along with a decent Logitech keyboard and wired mouse, while keeping on working on my trusty and powerful Lenovo X1 Extreme laptop. It rocked!

I also noticed in the courtroom that the “mobile clerk” — that is, the person who is in and out of the courtroom on the judge’s orders — also used a docking station. When he left he would disconnect a single USB-C/Thunderbolt cable and take his laptop with him. Upon his return to his desk, one plug reconnected and he had access to two 27″ screens, plus his own external keyboard and mouse. Good stuff.

Productivity Benefits Power Through

At the offices, we all mostly used cheapo, unpowered hubs with a single HDMI/DP port for video, two USB-C ports, and two or three USB3 Type A ports. That’s where the wired Logitech keyboard and mouse already consumed two of the latter. I actually had to plug the HDMI cable into my laptop because the underpowered hub in the office didn’t work with my X1 Extreme. I did see others using them for video without issues, so something odd was up with my rig.

Thing is: it all worked. We were all much more productive with 2 (and in some cases, 3) screens at work with our laptops. And even on a conventional bar-shaped keyboard (not ergonomic as I use at home) I’m still a lot more productive typing on same rather than the more condensed and taller layout on my laptop’s keyboard deck.

I also have to hand it to my office-mate Jeff, an appellate specialist from Austin.He came prepared with his own, externally powered high-end USB-C/Thunderbolt 4 dock, plus wireless ergonomic keyboard and mouse combo. Heck, he even brought a seat cushion for the comfortable Herman Miller Aeron chairs with which the desks were also endowed. Good stuff, and a valuable learning experience.

Facebooklinkedin
Facebooklinkedin

Kindle Update Problem Solved

Huh! In past discussions of update handling tools such as PatchMyPC and SuMO, I’ve complained about the difficulties that keeping Kindle up-to-date posed for me. Ha! Ha! The joke’s on me this time, because there really is NO such problem. There are a few wrinkles, however, even though I now find my Kindle update problem solved. Let me explain…

How I Got My Kindle Update Problem Solved

As it turns out, Kindle will happily update itself for you. But you have to go about it the right way. And you must keep at it until you get to the latest version. This requires understanding how Kindle update works, which is something it took me some experimenting to learn. Let me share:

1. As you can see from the lead-in graphic for this story, Kindle includes an automatic update feature amidst its various options. That said: YOU MUST LAUNCH the Kindle for PC application before the update function will run. Duh!

2. Kindle does not automatically or necessarily update to the latest and greatest version. It seems to update incrementally from the current installed version to the next available version. That just happened on my X12 Hybrid Tablet, where it took me from version 1.34.63103 (Jan 2022) to 1.35.64251 (Apr 2022), even though version 1.36.65107 (May 2022) was also available.

3. If you find yourself trailing behind the latest and greatest version after an auto-update, open and close the Kindle for PC application again. This will repeat the auto-update process. In my case that got me caught up. My guess is that this could take multiple iterations for those running more seriously out-of-date Kindle for PC versions.

This sure beats my previous approach, which had me visiting the Amazon store to “buy” (it’s free) whatever version was current then, and then to install it over the older version on my target PC. This is a whole lot easier…

The Secret: Run the App!

All this said, the secret to keeping Kindle for PC updated is to run the app as part of your update check cycle. Because the default setting is to “Automatically install…” as it shows in the lead-in screencap, the software does the rest. Wish I’d known this sooner, but glad to know it now. Case closed!

Now, if only Nitro Pro worked the same way I’d be free of my last hold-out “must update manually” program. Sigh.

Note Added One Day Later

As the following screencap shows, the PowerShell winget command is “smart” enough to update Kindle without opening the app. Check this out!

Another great reason to use winget for updating Windows PCs: it will update Kindle without opening the app!
[Click image for full-size view.]

Facebooklinkedin
Facebooklinkedin

Checking Windows DotNET Versions Installed

A recent Windows news story reports that “KB5012643 for Windows 11 breaks .NET Framework 3.5 apps” (WindowsReport). This raises some interesting questions for Windows 11 users. For some, it apparently renders certain apps inoperable. Indeed, the bug highlights the value of checking Windows DotNET versions installed on a given PC.

So I did a little research, and learned there are at least two methods to run this info down. In fact, MS offers a multi-page Docs item that explains how to do it using PowerShell. Belgian-based software developer (and former MVP) Nick Asseloos’ ASoft company goes another way. It offers a free download named .NET Version Detector. Its output provides the lead-in graphic for this story.

What Checking Windows DotNET Versions Installed Tells You

As you can see by examining the lead-in graphic. the detector provides information of several kinds, conveniently listed in order from top to bottom by row:

Row1: Versions of the MIcrosoft .NET Framework Installed. In my example, it shows older versions to the left (2.0, 3.0, and 3.5, with SP levels),and current versions to the right (4.8, with latest update level).

Row2: Extra Details show the folder locations for the various frameworks installed. It also shows names and levels for frameworks installed as well (mostly relevant to 4.x versions), plus languages and updates (mostly a bunch of KB article identifiers).

Row3: .NET Core versions installed for 64-bit (left) and 32-bit (right) enviornments. Given my machines all run Windows 10 or 11, 32-bit is mostly MIA.

How ‘Bout Going the Other Way ‘Round?

OK, we know now how to determine what .NET versions are installed on a Windows PC. What about figuring out which applications use some specific .NET framework? That’s a bit trickier. The only sure-fire method I could find was to fire up SysInternals Process Explorer. There’s a tab named “.NET Assemblies” that shows up whenever a process that includes same gets highlighted.

This means you can find out which .NET versions are in use primarily by observation and inspection. Stack Overflow has an article that explains how to automate this process for managed processes using C# or PowerShell. I’ll leave that as an “exercise for the reader” for those inclined to work out to that extent!

[Note: this story gives a shout out to the redoubtable Martin Brinkmann at Ghacks, whose 2014 story (updated 2018) introduced me to ASoft .NET Version Detector. Nochmals vielen Dank! (Thanks very much again!)]

Facebooklinkedin
Facebooklinkedin