Tag Archives: featured

Learning About UpdateStar

With the shutdown of the SUMo database on November 1, I’ve been casting about for a new update scanner that covers my bases. I had been considering UpdateHub, UCheck and UpdateStar. Based on the number of items that each program finds, and the ease of working with them (free versions only), I’ve now pretty much settled on UpdateStar freeware (make sure you can down to the button that reads “Download” under the Free of charge heading). It’s not without its foibles, though…mostly, that learning about UpdateStar involves completely do-it-yourself updates.

Learning About UpdateStar Means DIY  Updates

Unless you want to pay US$34.95 (first year)/$19.95 (subsequent upgrades, with discounts for 3 PC packages), working with UpdateStar means it scans only for what’s out of date. It doesn’t help you find or install new stuff. It will, however, uninstall specific versions of software, which can be helpful when updates aren’t smart enough to uninstall their predecessors. That happens pretty regularly.

Most of the time searching for “update splat” where splat is the name of the program you wish to update will tell you what you need to do. It mostly works for me, anyway. And many of the odd and interesting tricks I’ve learned while working with SUMo transfer over to UpdateStar reasonably well, too.

The Current UpdateStar Situation

Right now,  on my production Windows 10 PC (it’s the with the most apps and applications installed: 113 in all) I’m getting reasonable results from the program. It shows me 9 programs in need of updates and I was able to take care of all of them. For 8 of them, that meant finding and installing the necessary updates (2 of them left old versions behind and UpdateStart uninstalled them for me quite happily). For 1 of them, I decided an uninstall was a good idea, because I have a better tool (Micosoft Update Health Check, to which I greatly prefer Brink @ TenForums.com’s Reset_Reregister
_Windows_Update_Components.bat script).

That said, UpdateStar did produce some false positives. These were current programs that were indeed up-to-date, but for which the program incorrectly claimed newer updates were available (Revo Uninstaller and Snagit 2024). Easily checked and ignored, however.

By and large this program works pretty well. I’m still figuring things out, so will probably learn and report more over time. For the moment, I give it “one thumb up” (a positive, but not ringing, endorsement). Let’s see what happens next… I’m still on the upward slope of that learning curve!

 

Facebooklinkedin
Facebooklinkedin

Another Great UUPDump.Net Use Case

Monday-Wednesday I was working on an article for the AskWoody newsletter. Among a variety of tasks, one that I found interesting hinged on working with and taking screenshots of a Windows 10 app around a certain date (late July 2022). This makes for another great UUPDump.net use case. Let me explain…

What Makes For Another Great UUPDump.Net Use Case?

It took me a while to figure out the right date before which I had to stand up Windows 10. And because a Microsoft Store app was involved, I also had make sure the VM didn’t have Internet access. Otherwise, because the Store does auto-updates it would have replaced that point in time’s version of the app with something else. Because I was interested in seeing that specific version (or something older) at work, updates were a no-no.

Another ingredient was also key to my research: An MS Support note entitled “Windows 10 update history.” This handy document lets one see all Windows 10 releases and their dates of issue. Because I knew what date I had to hit, I wanted something as close to but still prior to it to show me what I needed. Ultimately, that worked!

Getting Past a Few Little Details

Setting up the VM also posed a handful of minor challenges. Because I set up a Type 2 VM I had to use the Restart button in the Hyper-V window to forcibly get the ISO I built for my test image to boot. I also had to remember to turn off enhanced mode to login via RDP (a known issue). And finally, I had to do some creative rooting around my file system to find a usable Windows 10 key (I persevered, and succeeded). Other than that, things went off just as I’d hoped.

Using my approach, I was able to run and screencap the target app. Luckily for me the date I picked still had the right (older) version installed. Once I brought it up, it told and showed me what I was looking for.

Great fun — and like the title says — it really is a great use case for UUPDump.net, thanks to its complete historical record of Windows 10 and 11 release, including Insider Previews. Glad my heretofore unsubstantiated theory about using historical versus current Windows versions worked out.

Facebooklinkedin
Facebooklinkedin

Windows 11 Canary Grants Wi-Fi List Refresh

Here’s a good, if subtle, addition to Windows 11’s bag of networking tricks. In Build 29997, Windows11 grants Wi-Fi list refresh capabilities. Let me explain, starting in pictorial form.  Take a look at the lead-in graphic. There’s a refresh button (a circular arrow) at the lower right (cursor is perforce parked on it; you’ll need to right-click the image and show it in its own tab so see what I’m talking about). But the “Refresh network list” button is the real key. That means the Wi-Fi interface is forcibly scanning its locale to rebuild a current list of available Wi-Fi resources. Very handy, to get this right from the Taskbar.

When Windows 11 Canary Grants Wi-Fi List Refresh, What Then?

This is always a good thing to do when searching for networks. MajorGeeks does a good job of explaining the “old regime” — namely: “How to Reset Network Settings In Windows 10 & 11.

That means clicking through the following sequence: Start → Settings; → Network & Internet (Win10) or Advanced network settings (Win11) → Scroll down, then select “Network reset.” I count 5 mouse clicks required.

The new ways take 3 clicks if you’re using wired Ethernet, 2 if already using Wi-Fi. For wired Ethernet, that’s Select Network icon in taskbar → Select Caret to left of Wi-Fi “Available” button in network pop-up → Click on “Refresh list” button at lower left of network list pop-up. For those using Wi-Fi, clicking the Wi-Fi icon on the taskbar skips the first wired step. Easy-peasey.

Does This Change Matter?

To those who switch Wi-Fi networks regularly, it is a nice little touch. For everybody else, it’s mostly nugatory. But hey, improving Windows is most definitely a matter of “little by little, step by step.” FWIW, I really like this change and think it makes Wi-Fi networking more usable on Windows 11. What’s your take?

Here’s a shout-out to Sergey Tkachenko at WinAero. His November 16 story brought this nice but subtle change to my attention. Spacibo, Sergey!

 

Facebooklinkedin
Facebooklinkedin

PowerShell Update Twofer Strikes

Whoa! No sooner had I updated PowerShell from version 7.3.9 to 7.3.10 than came the 7.4.0 in-window notification. You can see all this in the lead-in graphic, as a rare but not unheard-of PowerShell Update twofer strikes my local Windows 10 and 11 desktops.

When PowerShell Update Twofer Strikes, Keep Going

I had to chuckle after I patted myself on the back for updating PowerShell inside Command Prompt (the best way to avoid odd update behavior that can occur when PowerShell attempts to update itself). The very next thing I saw in a new PS window was the “black text against white background” notification shown in the lead-in graphic.

That notification reads:

A new PowerShell stable version is available: v7.4.0
Upgrade now, or check out the release page at
https://aka.ms/PowerShell-Release?tag-v7.4.0

That URL links to the named release page at GitHub, where one can download an installer that matches OS, architecture and so forth. I ran the file named PowerShell-7.4.0-win-x64.msi. It worked like a charm!

And unlike other, earlier attempts at running the MSI installer to move up a PowerShell version, this one successfully cleaned out the just-updated 7.3.10 version without difficulties. Looks like the PowerShell team is getting its act together…

This does raise the question: when will winget update start targeting v7.4.0 instead of v7.3.10? Looks like that’s already taken care of. Look at this output from winget upgrade from a Windows 11 test machine: it literally got fixed while I was writing this blog post. LOL!

PowerShell Update Twofer Strikes.winget-check

Winget now knows it needs to target v7.4.0 as the current PS version. [Click image for full-sized view.]

As you can see, winget upgrade is not recommending 7.3.10 anymore. Now it’s aware of, and ready to upgrade to, 7.4.0. Good-oh!

 

Facebooklinkedin
Facebooklinkedin

PowerToys Needs Specific .NET Runtime

I saw with some interest that Microsoft released .NET 8.0 earlier this week. As I was running winget yesterday, I also noticed that Microsoft Windows Desktop Runtime needed an update from version 6.0.24 to 6.0.25 (see lead-in graphic, where it shows up second from the top). “Hmmm…” I thought “I wonder if something will blow up if I delete this older version.” So I did. And indeed, when I went on to update PowerToys later that afternoon, I noticed it was smart enough to install version 6.0.25 during its own install process. Hence my claim: PowerToys needs specific .NET runtime.

Why PowerToys Needs Specific .NET Runtime…

There’s obviously some dependencies in the code that link to this specific version of .NET. Even though I installed 8.0 (and you can also see a current 7.0 version in the lead-in graphic as well) there’s something in the 6.x versions that PowerToys needs to do its thing properly.

Please take this as an illlustration of why one so commonly finds multiple generations of the various .NET runtimes (Core, Desktop, SDK and Framework) running on a single Windows instance. Different apps, applications, and even OS built-ins need different ,NET runtimes and so forth to do their jobs. And that’s the way things go on desktops and servers here in Windows-World. Get used to it!

Meet the .NET uninstall tool

All this goes to explain why there’s a special tool named dotnet-core-uninstall that lets you get rid of those .NET elements for which no current dependencies exist. See this terrific MS Learn document “.NET uninstall tool” for all the gory details. It runs inside PowerShell or Command Prompt, and helps you find and remove obsolete .NET components. Good stuff!

Facebooklinkedin
Facebooklinkedin

Happy 17th Birthday PowerShell

In reading about the run-up to the MS Ignite conference — getting underway in Seattle — I learned this morning that November 14 is the anniversary date for PowerShell. That’s why I expressed the sentiment in the title — namely “Happy 17th Birthday PowerShell!”

Why Say: Happy 17th Birthday PowerShell?

Since its inception in 2006, PowerShell (PS) has slowly and steadily taken over the lead role at the command line for Windows admins and enthusiasts. Probably more importantly, PS became open-source and cross-platform in August 2016 with the debut of PowerShell Core. According to Wikipedia, as of Windows 10 Build 14971 (November 2016) PS took over the default role as primary command line shell for Windows.

What makes PS worth getting to know? Unlike the Command Prompt (which traces all the way back to DOS days) it’s a fully featured runtime environment. Thus it handles task automation and configuration management. And it does so in an environment that’s got most of the capabilities of a full-blown programming environment. Shoot: you can create interactive scripts using PS, and you can embed PS within other applications. Then, too, PS supports an extensive library of built-in cmdlets (“commandlets”) to support all kinds of specialized, focused operations. It also works both locally and remotely. IMO, it’s more fun than a barrel of monkeys!

The Journey to PS Nerdvana

I’ve been working with PS increasingly since it initially became available around the same time that Windows Vista appeared. But it’s only in the last 3-4 years I’ve really started working with it more extensively. It is very much the case that the more I’ve used it, the more I’ve come to like PowerShell.

Indeed, I’ve got a TekkiGurus story coming sometime soon that provides a PS script to show how I customize Windows Terminal and PS on my PCs. (I’ll link to it when it goes live.) It includes:

  • Download, installing and configuring OhMyPosh, along with a Nerd Font is uses for prompt customization in PowerShell
  • Download, install, and add a ColorTool to the PS environment
  • Install and use Winfetch to show off current WT/PS look and feel

So again: happy birthday, PowerShell. You’ve made my job in setting up and taking care of Windows images and installations much, much easier. Thanks a bunch!

Facebooklinkedin
Facebooklinkedin

OneDrive Quit Flap Flopped Magnificently

I have to laugh. In the past week-plus, a huge to-do has emerged around OneDrive. Seems that MS decided not to let users quit the program without providing a reason. That is, users had to pick from a list of options to explain why they were exercising the “Quit OneDrive” option shown in the lead-in graphic before the program would cease operations. Today, MS removed that requirement as this OneDrive Quit flap flopped magnificently with users. They didn’t buy in!

Why OneDrive Quit Flap Flopped Magnificently

Simply put, the overwhelming consensus from users varied between “WTF!” and “You can’t make me do that!!!” MS was testing this survey and got savaged by respondents. According to Sergey Tkachenko at WinAero “Following negative customer feedback, Microsoft has decided to revert the OneDrive exit confirmation.” Again: LOL!

Here’s the list of options that MS presented to users as they attempted to exit OneDrive (screen-capped from the afore-linked WinAero story, since I missed to the whole shebang):

OneDrive Quit Flap Flopped Magnificently.quitlist

7 Ways to Leave Your OneDrive.(Credit: WinAero)

Now the quit option has reverted to its former less vexing version, as shown here:

So Quit, Already…

Case closed, I guess. Somebody, somewhere is surely thinking: “Let’s not do THAT again for a while, OK?” And boy bowdy, is that ever the way things go in Windows-World from time to time. The last laugh is the best one, they say — so let it rip! Still chuckling…

Facebooklinkedin
Facebooklinkedin

November Windows 11 Deprecation Includes Tips

For some, this may be good news. For others, not so much. MS announced a raft of “Deprecated features for Windows Client” on November 7. Among them is one of my personal pet peeves. That’s right November Windows 11 Deprecation includes tips app amidst its number, along the Computer Browser, WebDAV, and Remote Mailslots, atop a list of older items. See the afore-linked MS Learn item for all the details.

If November Windows 11 Deprecation Includes Tips, Then What?

First of all deprecated doesn’t exactly mean “dead.” Instead, it means something more like “while it’s on its way to oblivion, you’d best learn to live without it.”  Microsoft positions this status as follows:

The features in this article are no longer being actively developed, and might be removed in a future update. Some features have been replaced with other features or functionality and some are now available from other sources.

That’s OK with me, because I was never a huge fan of the Tips app. I seldom, if ever, turned to it explicitly. And when MS fired it in my direction thanks to defaults or settings I didn’t (yet) know about, I would invariably turn them off when they made themselves known.

Tips app info from the Windows 11 Start Menu.

But that’s just me. For all I know, there are plenty of people left in the lurch with the immanent departure of Tips from the scene. All I can say is; I’m glad not to be a member of that no-doubt disconsolate group.

For Me, Opting In Beats Opting Out

In general I’m of the opinion that if MS wants to make information services available to users, they should introduce and explain them. Then, after demonstrating their costs and benefits, they should give interested users an opportunity to opt in. Those who want to use those services can do so, but those who don’t want them need do nothing to keep them at bay.

Indeed, there’s a whole class of emerging Windows built-ins called System Components (see my October 27 post for deets) for which the same treatment makes good sense (Tips is among them, in case you wondered). Ditto for things like the new Windows Backup app, now included in ALL Windows 11 distros, over the vehement and vociferous objections of Enterprise and Education license holders.

Gosh! If MS were to adopt an opt-in philosophy for all stuff that’s not strictly necessary for Windows 11 to function properly, it would make life easier for the admins who handle images and their deployment and the people who use them. Something to consider, eh? Hope somebody high up at MS takes this to heart…

Facebooklinkedin
Facebooklinkedin

SUMo Is Turned Off

I have to laugh, so I don’t cry. Despite rumors that its developer, Kyle Katarn, might republish his dandy Software Update Monitor (S U Mo) utility as Open Source code, the supporting servers shut down on November first. Notice the company slogan for KC Softwares (Katarn’s company, and the program’s maker) reads: “We are here to stay.” Now that SUMo is turned off, there’s some irony there, eh?

When SUMO Is Turned Off, Then What?

I had a general inkling that things might go sideways on November 1. Why? Because the website reads:

KC Softwares activities are to be terminated by end of October 2023.
All products are to be considered as End-Of-Life (EOL) on October 31st 2023.

And indeed, when I tried to run the program on November 1, I got an error message as it tried to scan its database for the first item in its inventory (7-Zip, by virtue of its position at the top of the alph sorting order).

SUMo Is Turned Off.server-error

Trying again later is not going to help. The server is off.

Other, Less Palatable Alternatives

LifeWire has a September 11, 2023 story “11 Best Free Software Updater Programs.” At this point, I’ve tried them all. I’m a big fan of Patch My PC, but it doesn’t cover enough of my installed software base to do the job on its own. And so far, none of the others have really captured my fancy or regard.

Why is that? Most of the free versions have paid-for counterparts. And most of them also qualify as “teaseware” — that is, they tell you about things they could do for you if you purchased the paid-for version. For now, I’m getting by with winget (and WingetUI), Patch My PC, and a bit of elbow grease. Hopefully, a real contender will emerge (and sooner is better than later).

Stay tuned! I’ll keep you posted. But don’t hold your breath, either. This could — and probably will — take a while…

Facebooklinkedin
Facebooklinkedin

Phased Windows 11 23H2 Rollout Bites Hard

It’s another never-ending story. Earlier this week, I found myself wondering why none of my 5 physical Windows 11 production PCs, nor either of my two Windows 11 production VMs, were getting any WU action for the 23H2 eKB (enablement package). Then I read from various sources (see this WindowsLatest item, for example) that it’s arriving as a “phased rollout.” Given my personal experience (0 for7) I must observe that the phased Windows 11 23H2 Rollout bites hard here at Chez Tittel. Go figure!

If Phased Windows 11 23H2 Rollout Bites Hard, Then…?

There are other ways to force the KB5027397 eKB onto a production Windows 11 22H2 system running 22621.2506. This makes the transition to 22631.2506 and changes the version number from 22H2 to 23H2. You can read all those details in Shawn Brink’s helpful ElevenForum post “…Enablement Package for Windows 11 version 23H2..” More important, there’s a link there to an MSU (Microsoft Update, with installer) file for X64 and Arm64 PCs. I’ve used it on three of my production PCs and both VMs now, so I’m convinced it’s legit and I know it works.

But gosh! I always wonder why MS makes us wait for updates to rollout. The official line is they’re being conservative and taking no chances on incurring errors or issues on existing Windows 11 PCs, especially older units. But with two of my population less than a year old, both running pretty beastly workstation grade configurations, I’m puzzled by their hold-backs.

On the two PCs that haven’t yet updated (a 2020 vintage Dell OptiPlex 7080 with 11th-gen i7, and a 2021 vintage Ryzen 5850X) I’m deliberately waiting. I’m checking daily to see when WU will “make the offer.” So far, nada. Stay tuned…

Facebooklinkedin
Facebooklinkedin