Category Archives: Cool Tools

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

MS Recasts Printer Driver Requirements

September 8, 2023 Ed Tittel Leave a comment

Very interesting! There’s a September 6 update to MS Learn Windows device drivers docs. Therein, MS recasts its future printer driver requirements (End of servicing plan for third-party printer drivers on Windows.). For those who manage and use Windows printers, it’s worth a read.

Driver Standards Explain How MS Recasts Printer Driver Requirements

The change comes courtesy of the the Internet Printing Protocol (IPP). Originally developed by IBM, IPP is explained in an MS Print support app design guide. Indeed, IPP may be “[u]sed from a client device to interact with the printer to retrieve and set printing preferences and to send the document to be printed.”

Long story short: support for IPP and Mopria standards is a good thing. They make vendor-supplied printer drivers and software unnecessary — at least, for printers that support those standards. And FWIW, IPP and Mopria work on Android, while AirPrint does likewise for iDevices.

That explains the MS timetable in its “end of servicing plan”

September 2023: MS announces end of servicing for third-party printer drivers
2025: No new printer drivers from WU
2026: Printer driver ranking always prefers IPP drivers
2027: Third-party print driver updates disallowed (except for security-related fixes)

IPP Has Been There All Along…

Check out this sub-Window. It comes via Control Panel → Programs and Features → Turn Windows features on or off. It shows built-in IPP support in Windows 10 and 11. See “Internet Printing Client” (box is checked) under”Print and Document Services”

Internet Printing Client checked means IPP is active.
If not, do check it.

Using TCP/IP addresses for networked printers, I’d been unknowingly using IPP for years . Thanks to MS’s updated printer driver architecture, I needn’t use device-specific drivers and software, either. Good stuff.

Indeed, my 2014/2015 Samsung (now HP) and Dell (Brother, actually) printers already use IPP. Most printers made in 2014 or later will do likewise. Good stuff!

Here are additional resources that readers may find helpful.

OpenPrinting Driverless Printers: Vendor makes and models for IPP and/or AirPrint capable printers.
Wikipedia: Mopria Alliance: Info about this trade association. Founded by HP in 2013, it includes global print device makers backing open print initiatives and standards.

Cheers!

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

So Long SUMo & KC Softwares

September 7, 2023 Ed Tittel 6 Comments

Dang! I’ve been through this same situation before with a terrific software update monitor. For the past 3 years or so, a favorite go-to tool in my update arsenal has been KC Softwares Software Update Monitor, better known as SUMo. It looks like it’s time to bid them adieu. As shown in the lead-in graphic’s termination notice, I find myself saying “So long SUMo & KC Softwares.”

After So Long SUMo & KC Softwares, Then…?

Let me tell you how I found out things were shutting down with Kyle Katarn’s operation. I found an oversight in SUMo a few minutes ago. Seems that it’s once again recommending a beta version of DropBox as an update target. The program’s automated “find the highest numbered update” algorithm does that sometimes because beta versions are usually higher-numbered than the most current production ones.

My usual practice for the past year and more has been to send the developer a Twitter (X) message to tell him this needs checking and possibly also fixing. This time, when I attempted to send him a message the application responded “You can no longer send messages to this person.” In turn, this led me to kcsoftwares.com, where I found the termination message you see above. Sigh.

Remembrance of Things Past

Back in 2019, I wrote about an older update monitoring tool, likewise pulled from the market. This was back when Windows Enterprise Desktop was still under the TechTarget umbrella (title: Missing Secunia PSI). Long story short: I used Secunia PSI from 2010 to 2016 with great pleasure and success. When it, too, was withdrawn from the market I had to scramble to find a replacement.

That’s what I’ll do now, too. Stay tuned: both the hunt and its results should be quite interesting.

Cool Tools, Insider stuff, Networking, Recent Activity, WED Blog, Windows 10

Intel Fixes PROSet Problem

September 6, 2023 Ed Tittel Leave a comment

Back on August 18, I reported that version 28.2 of Intel PROSet didn’t support Windows 10 22H2 for some reason. Because I was away from my desk from August 25 through September 4, I only discovered today that Intel fixes PROset problem. According to the properties for the 64-bit executable, it dates back to August 4. That said, today’s download and install works. Indeed, it threw no “version not supported” error message as shown in the earlier post.

When Intel Fixes PROSet Problem, Then What?

This time around, the update worked as expected. The readme.txt file still omits Windows 10 22H2 as a supported version, but the exe file now works properly on my machine. Sigh.

This has me wondering: Did Intel fix something on the sly, or did I simply try to run the wrong exe file last time around? I’ll never know, but I’m glad the update now works as it should. I no longer get nagged when I check updates for something I thought I couldn’t fix on my own.

It’s Still a Mystery to Me…

Looking back at my earlier post, the error message says nothing about which version of Windows it expected to find. I suppose I could have jumped to the conclusion that 22H2 wasn’t supported because it doesn’t appear on the supported version list.

As before, readme.txt calls out Windows 10 21H2 and 1809 but does not mention 22H2. I wonder now if I mistakenly tried to run the 32-bit PROSet executable instead of its 64-bit counterpart. That could provoke the same kind of error message as before. When I try to run that version now, it tells me “Another version is already installed…”

Such surprises can be educational. They teach me that my diagnoses may not always be the correct ones, no matter how plausible the supporting evidence may seem. Indeed, that’s the way things go in Windows-World sometimes, as I know only too well.

Bottom line: I’m glad the update worked this time. Though it may actually have been a self-inflicted problem, PROSet now shows version 28.2.0.2 on my desktop. Call my Windows 10 PC updated, even if I’m not sure exactly what went wrong on August 18.

As you can see at lower left, this running PROSet instance self-describes as 28.2.02 — the latest version.

Cool Tools, Insider stuff, Recent Activity, WED Blog

UUPDump.Net Is MIA

August 24, 2023 Ed Tittel Leave a comment

Well, well, well. I just learned some interesting and useful stuff. But alas, one of my favorite Windows image resource websites is down. That’s right: UUPDump.Net is MIA. According to a handy website I discovered “Is It Down or Just Me?” — the source of the foregoing lead-in graphic — it’s experienced 2 outages that lasted at least 4 hours each in the last 24-hour period. Indeed, it’s currently unavailable. Sigh.

Why UUPDump.Net is MIA Matters…

UUPDump.Net represents a very slick bit of reverse engineering. Essentially, it captures and replays all of the traffic between the WU servers and a client seeking to download some specific Windows image (10 or 11, Home or Pro …, and language). It’s even smart enough to run DISM on a base OS image to add-package in updates and so forth so you can get to specific Build numbers higher than the OS baseline itself (e.g. 22621.2215 on Windows 11 production, or 25831.1010 on Windows 11 Canary Channel Insider Preview). And because it grabs all of its files from Microsoft servers, it’s as safe as they are.

Long story short: I use UUPDump.net when I want to match a Windows image to a specific (and usually pretty recent) Windows 10 or 11 Build on a specific PC or VM. It’s incredibly handy, and serves equally well for in-place upgrade repair installs or clean installs. So when it goes missing, that’s a problem — hopefully, a temporary one.

More Web Status Checks

I also found ip-lookup.org to be helpful in checking on UUPDump.net. As the next screencap shows, it provides an IP address for the website. I can also confirm for myself that the address is not working by typing an “IP URL” into Chrome — namely https://135.181.139.104. This confirms the site is unavailable with a “This site can’t be reached” error message.

Gosh! I hope UUPDump.net comes back up soon. I’ll struggle along without it for now. But I’ll be glad when it comes back to life.

One More Thing: I went to the wayback machine to see if a recent snapshot of the site would work in lieu of the actual site itself. It might! I’m grabbing the stuff for the latest Canary build right now as an experiment. It’s quite a bit slower, and it falls over just after the language selection phase. Doesn’t look like this works. Again: too bad!

Note Added 8/24 ~3PM Central Daylight Time

UUPDump.net is back up. The outage graph at IsItDownOrJustMe says there have been four outages in the last 24 hours, each of 4 hours’ duration. Zounds!

Cool Tools, PowerShell, Recent Activity, Updates, WED Blog, Windows 11

Extra C++ Redistributable Must Go

August 22, 2023 Ed Tittel Leave a comment

Here’s an interesting winget puzzle. Over the past couple of days, I noticed winget was reporting success in upgrading a Visual C++ Redistributable from version 14.36.32532 to 14.38.31919.0. Yet, each time I ran winget after that the same thing would reappear. Good thing I know what’s up with that: it means the new install doesn’t remove the old, now obsolete version. Thus, that extra C++ Redistributable must go.

Accomplishing Extra C++ Redistributable Must Go

In the lead-in graphic I show the two versions side by side inside Revo (bottom of image). I used that same tool to uninstall the other one manually. If you look at the sequence of commands therein, you’ll see I check upgrades. It shows me a new Visual C++ version to install. I install it, and check again: oops! Same old version of the redistributable still needs an update.

Or does it? Actually, it needs to be uninstalled. I could’ve done it with the winget syntax:

winget uninstall Microsoft.VCRedist.2015+.x86 -v 14.36.32532.0

But instead because I had Revo already open I simply right clicked the old version, chose uninstall, and let it do its thing. Gone!

What Happened Next?

As expected, the next time I ran winget upgrade to see if any updates remained pending I got back this mysterious but welcome message. “No installed package found matching input criteria.” In winget-speak, that means it didn’t find anything that needed an update. In other words: removing the obsolete Visual C++ Redistributable took care of my previously persistent version 14.36.32532.0.

Good-oh! Glad I’ve seen this kind of thing before. It told me that I probably had to kill the old version manually, to keep it from provoking a reminder to upgrade to the new. Even though it was present already…

Cool Tools, Device drivers, Insider stuff, Recent Activity, WED Blog

Occam’s Razor Cuts My Intel PROset Problem

August 18, 2023 Ed Tittel Leave a comment

OK, then: let’s take a short trip back to medieval England (14th century) and drop in on philosopher William of Ockham. His original Latin epigram is “Entia non sunt multiplicanda praeter necessitatem.” That’s often translated as “Don’t add more factors to an explanation than are strictly necessary.” Many people take it to mean “The simplest explanation is usually the best (or correct) one.” From a troubleshooting standpoint, I take a different lesson. Eliminate the obvious causes before looking for more exotic ones. And indeed, yesterday Occam’s Razor cuts my Intel PROset problem. I discover it’s the software itself that prevents its installation on Windows 10.

Why Say Occam’s Razor Cuts My Intel PROset Problem?

You can see why I had to haul this old blade out of storage by examining the lead-in graphic. It’s from the Release Notes for the latest version of the Intel PROset and driver software for its wired Ethernet adapters, including for Windows Client OSes. Take a close look at that list. Then consider the version of Windows 10 for which I sought to install this latest 28.2 version — namely Windows 10 22H2.

The installer fired up just fine, but then it took quite a while to do anything. Instead of asking my persmission to commence installation, I got this error message instead:

Despite repeated efforts, I got only this when attempting an install on Windows 10 22H2.

After a couple of failed tries, I figured I’d better check the release notes. And sure enough, I saw what’s missing in the lead-in graphic. This release does NOT support Windows 10 22H2. And that, of course, is why I get that error message. Given that 22H2 is the current Windows 10 version and that 21H2 hit its EOL date on June 13 (a couple of months ago), I have to believe this was a mistake on Intel’s part. But it is what it is, and I have to wait for them to fix it. Until then, I’ll keep running the preceding driver version. Sigh.

FWIW, I just summarized this info in a post to the Intel online forums for their Ethernet adapters and software. I’ll be interested to see what kind of response it evokes, if any. Stay tuned!

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

Inconsequential Windows Errors: Remove or Ignore?

August 17, 2023 Ed Tittel Leave a comment

In refreshing my recollection of what I thought was called “Berkeley’s paradox” — but isn’t — I have to raise the question: If a Windows PC throws an Xbox error and you don’t use an Xbox, does it really matter? In my case, the answer is a resounding “No!” Thus when handling inconsequential Windows errors: remove or ignore are my primary strategies. Let me explain…

Handling Inconsequential Windows Errors: Remove or Ignore?

I repeat: I don’t use an Xbox, so I don’t call on the associated complex of Store apps that offer Xbox connections, controls and capabilities. Interestingly, the Store Library shows only Xbox Game Bar. But if you search Apps on the Store Home page, you’ll find dozens of qualifying hits. Interestingly Xbox Identity Provider isn’t among them.

With a little research, I found a website named “Best Gaming Tips” that directly addresses my issue: Xbox Identity Provider Not Working. It includes a helpful PowerShell command sequence to nix this stubbornly uncooperative beast:

Get-appxpackage Microsoft.XboxIdentityProvider | Remove-AppxPackage

It now seems to be gone, too. If I use winget to search for that package name, it finds nothing. And yet, the entry still shows up in Store. I’m restarting and will try again after that… And indeed, that took care of things. Looks like if you change the underlying app structure (or the packages in which they live) you need to stop/restart the Store to let it continue to reflect current reality correctly. Go figure!

For the nonce, the problem is gone. Should I ever have need of the Xbox Identity Provider, I’ll figure out how to re-install it. That’s a bridge to burn some other day. Here in Windows-World, there are always plenty of such opportunities.

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

Sideload Brings Windows 10 New Photos App

August 16, 2023 Ed Tittel Leave a comment

Here’s something interesting. Thanks to eagle-eyed software maker and reporter Sergey Tkachenko, I’ve just learned you can grab the new Windows 11 version of the Photos app and install it on Windows 10. On 11, it comes from the Windows Store; if you’re left out, a sideload brings Window 10 new Photos app. See the WinAero story Windows 11 Photos app now supports Windows 10 for pointers and such.

How Sideload Brings Windows 10 New Photos App

If you examine the lead-in graphic closely you’ll see the About info for the Windows 11 version of Photos (lower left). Once you download and install that version, the Store offers a renamed version of its predecessor as “Photos Legacy” (right, with about information at bottom). I installed that also to keep my existing (and enormous) trove of meta-data and image info available. Just for grins, I superimposed winver.exe at right center to show it was all indeed running on Windows 10. Good stuff!

One thing: you will visit the mirror of the Microsoft Store downloads to grab the Windows 11 version of Photos for Windows 10. When you do, scroll down to the first Microsoft.Windows.Photos entry that ends with the extension .msixbundle. That’s the one you need to actually perform the install.

It will ask you if you want to update Microsoft Photos? Click the Update button.

Then it will go through the update process and actually install the Windows 11 version on your Windows 10 PC. As soon as it’s done the Store will offer you the Photos Legacy app as well.

So now, I have both the old version (Photos Legacy) and the new version (Photos) running on my Windows 10 PC. As I watch what happens with this new addition to my app stable, I’ll report further if I see anything noteworthy. So far, it all seems pretty routine.

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

Backing Up P16

August 15, 2023 Ed Tittel Leave a comment

I’ve recently swapped out the Lenovo loaner unit for the ThinkPad P16 Mobile workstation here at Chez Tittel. In the same recent period, I’ve written stories for AskWoody about using USB and Thunderbolt versions 3 and 4 for a variety of purposes. When it comes to using any of those technologies with USB-C attached NVMe drives, backup looms large. And boy, are the results for faster storage hookups compelling when it comes to backing up P16. Let me explain…

TB4 Shines When Backing Up P16

The lead-in graphic shows a 1:03 completion time for an image backup on that device inside Macrium Reflect. That’s the fastest I’ve ever seen a full image backup complete on that (or any other) PC, whether to an internal or an external drive. Why doesn’t everybody do it that way?

Let me count the reasons:

Not all PCs or Laptops have fast Thunderbolt4 ports.
TB4 NVMe enclosures are expensive: US$130 and up. Count on spending at least another US$70 or so for a 1 TB NVMe to put inside same. In contrast, you can buy a portable 1 TB NVMe right now for about US$70 (but it’s not TB4, nor even TB3).
One *MUST* use TB4 cables to get those results. Nothing else will do.
USB-C ports can be scarce, so it may be necessary to acquire a TB4 dock. That’ll set you back another US$200-400 depending on ports and features.

But Hey! Look at Them Snappers…

All those caveats said and understood, 1:03 remains a remarkable timeframe for a full image backup. WizTree reports that the P16’s C: drive currently stores 82.8 GB’s worth of stuff. If I’m doing the math correctly that’s 10.48 Gbps as a backup speed. I’ll take it!

I spent over US$200 to put the NVMe enclosure to work, and another US$25 for a year’s worth of access to Macrium Reflect. Is is worth it? IMO, it is. IYO perhaps not…

Cool Tools, PowerShell, Recent Activity, WED Blog, Windows 10, Windows 11

Using Get-WUHistory Requires Finesse

August 14, 2023 Ed Tittel Leave a comment

I’m a big fan of PowerShell. That’s why I was excited to learn about a collection of cmdlets from the PowerShell Gallery named PSWindowsUpdate. Chief among its constituents is a cmdlet named Get-WUHistory that I’ve been finding both helpful and vexing. I say that using Get-WUHistory requires finesse because it works well on Windows 10, but hangs on PCs with longer “history trails” in Windows 11. Let me explain and illustrate what that means…

Why Using Get-WUHistory Requires Finesse

I’m only running Windows 10 on one actual PC (not counting VMs). By chance, that’s where I started working with the PSWindowsUpdate cmdlets. To begin with, you’ll need to install this collection, using this command:

Install-Module -Name PSWindowsUpdate -Force

If you haven’t visited the PowerShell Gallery before, you’ll be asked to grant various permissions so your PC (or VM) can access and use its contents. If necessary, please do so. Then, your installation will complete. After it’s done, you can use the Get-WUHistory command (among others — see a complete list of all 25 cmdlets from this package).

There’s something going on in Windows 11 that will sometimes cause Get-WUHistory to “hang.” How can you tell? The output won’t complete, you won’t get a prompt back, and the cursor keeps blinking. Indeed, it doesn’t even respond to CTRL-C to terminate the command. You must close the open PowerShell window (or tab) to regain control over Windows Terminal.

What’s the Trick to Make Things Work?

For some odd reason limiting the scope of output keeps the Get-WUHistory cmdlet working. Thus, in Windows 11 instead of simply entering Get-WUHistory at the command line, try this version instead:

Get-WUHistory -last 1000

This tells the cmdlet to limit its output to only the first 1000 entries it finds in the update history. Notice that on one of my test PCs, the actual number of entries in the update history is only 157 items, yet the command hangs anyway — except when it’s scoped. Go figure!

Unless scoped [-last 1000] Get-WUHistory hangs on Windows 11.

The lead-in graphic shows the first screen of output from a scoped version of the Get-WUHistory cmdlet. Notice that most of the updates relate to Windows Security (Windows Defender intelligence updates, antimalware platform updates, and so forth). Too much chaff, not enough wheat, IMO. Here’s a way to turn down the volume…

Reducing Get-WUHistory Output Volume

One can, of course, filter Get-WUHistory Output — in addition to limiting its scope — to reduce the output volume. Here’s a command string I found to be incredibly helpful in seeing what’s there, sans security-related stuff:

Get-WUHistory -last 1000 | Where-Object {$_.Title -notlike "*Security*"}

What you see broken across two lines (or more) in the preceding is actually a single (if complex) PowerShell command string. Be sure to remove or ignore any internal line breaks when running this inside Windows Terminal. You’ll get back a mercifully much shorter list of items, mostly cumulative updates (CUs), MSRTs, Update Stack Packages, and the odd antimalware platform update. As you can see, this cuts 157 items down to a more manageable 12. Good stuff!

Eliminating the word security in the “Title” field filters out most of the dross. [Click image for full-sized view.]