Category Archives: Cool Tools

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

Hope MS Makes Good on Classic Teams Uninstall

April 25, 2024 Ed Tittel 1 Comment

I’ve got to admit: I’ve lost count. I’ve seen oodles of updates and versions of Teams come and go on my various Windows 10 and 11 PCs lately. Take a look at Monday’s MS Teams article “End of availability for classic Teams client.” Among much other stuff it says “This rollout involves installing the new Teams client for users who still have the classic Teams client, with Microsoft attempting to uninstall the classic Teams client 14 days after the installation of new Teams.” Gosh, I hope MS makes good on Classic Teams uninstall promises.

Why I Hope MS Makes Good on Classic Teams Uninstall

I’ve tried uninstalling Classic Teams on Windows 10 PCs and VMs. (Note: I do NOT have this issue on Windows 11 PCs of any build or version, stable or Insider Preview channels.) But it often returns to those Windows desktops on its own, through means mysterious and marvelous. In short: it’s attaining zombie-like status except it doesn’t relentlessly chant “Brains! Brains! Brains!”

Better (or worse) still, when I try to use Teams on Windows 10 (it’s still my production work environment), Classic tends to come up by default. I know why — it’s because I use MSAs that aren’t part of an AD/Entra domain — but it’s still irksome.

Gosh! I’ll be glad when July 1 comes and goes and I get to see if the zombie that is Classic Teams will finally get exorcized — err, uninstalled — from my Windows 10 PCs and VMs. Stay tuned! I’ll keep you posted. Fingers crossed, in the meantime. . .

Results from Remove/Replace Operation

Just for grins, I used Revo Uninstaller to get rid of all Teams traces on my production PC. Then I went to the MS Store to download and install its latest version. When I launched for the first time, it asked me if I wanted Teams (New) or Teams (Classic). I chose (New) and now it comes up in the Start menu with no Classic companion. I’ll keep an eye out and let you know if Classic lurches back to life!

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

IPRI Hits Production Windows 11

April 24, 2024 Ed Tittel 1 Comment

I’m not sure exactly how long this has been true but Copilot agrees with me that it first appeared in 23H2 Build 22631.3447. Release date for that build: April 9, 2024. It had been available in Insider Previews since earlier this year, but this is when in-place repair install (IPRI) first showed in a production release. Now that IPRI hits production Windows 11, it’s ever so much easier to let WU provide the files to make that happen. Good stuff.

What IPRI Hits Production Windows 11 Means

Before this facility appeared in various Windows 11 versions, the only way to conduct such a repair was to use UUPdump.net to build an ISO that matched the current installed Windows version, then mount same, and run setup.exe from its root-level folder (see red-boxed item in the screencap following):

The old-school IPRI method requires an ISO for the same version.build that’s running, then launching setup.exe from its root-level folder.

Now, with this change you need only navigate to Settings > System > Recovery, then click the “Reinstall now” button as shown in the lead-in graphic. Windows Update does the rest. It does take a while (50-60 minutes in recent test runs for a ComputerWorld story) but that’s because it has to download all the component files, then build and update an ISO. Adding install time to the time UUPDump.net takes to create the ISO, it’s pretty much a wash.

And again: it’s ever so much more convenient and automated. Big win for Windows users everywhere. Thanks, MS!

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

Busy Week Brings 9 WinGet Updates

April 19, 2024 Ed Tittel Leave a comment

It’s been a busy week, so I’ve been doing stuff more, and playing less with Windows. How do I know? I just ran WinGet on my production desktop and it tossed up a new personal high. That’s right: my busy week brings 9 WinGet updates to my Windows Terminal PowerShell session. You can see the intro part in the lead-in graphic. Wow!

When Busy Week Brings 9 WinGet Updates, Install Them

So that’s what I’m doing right now, as I write this blog post. The whole 9 items took about 2 minutes to complete. It brought 8 successes and one failure. Because I have numerous M365 components open right now, the M365 Apps for Enterprise install failed. That’s probably because I’m using a different subscription version tied to a different MSA. The one I’m using cheerfully reports itself all caught up.

It’s the one I’m NOT using that reports itself out-of-date (which is perfectly OK, because I’m not using it. Maybe I should remove it?) Isn’t it funny how using multiple MSAs in a Windows PC can occasionally make life interesting when you login with one such account, and use assets tied to another such account?

It’s All Part of Windows’ Inestimable Charms…

Learning where the eccentricities reside or potholes lie, and steering around them, gives me countless opportunities for learning and enjoyment when it comes to working with Windows. But less so than usual this week: I’m busy. In fact, I need to go do some paying work as soon as I’m done here. Cheers!

Cool Tools, Insider stuff, PowerShell, Updates, WED Blog

PowerShell Install Goes Cancelled to Abandoned

April 18, 2024 Ed Tittel Leave a comment

Here’s a good one. Take a look near the bottom of the lead-in graphic. It shows what happens at the end of a WinGet upgrade sequence with the PowerShell installer. But whereas that installer used to say “Installation cancelled” it now says “Installation abandoned.” Hence my assertion: PowerShell Install Goes Cancelled to Abandoned. In truth, this simply means the Windows Terminal window must be closed and re-opened for a new PowerShell version to take effect.

What PowerShell Install Goes Cancelled to Abandoned Means

Things get interesting when a program that’s currently running gets updated. Generally, for the code to take over from the old, the old must first stop. Then, the new must start up and run, so it can use all of its newly-minted capabilities and capacities. The “cancelled” and “abandoned” stuff is text for an error message that indicates the installer itself had to terminate in some kind of unexpected, unusual, or surprising way.

Look at what comes up when I close Windows Terminal, and then re-open it. Just for grins, I add WinGet list microsoft.PowerShell and another WinGet upgrade … check. The former shows the new version 7.4.2.0 is present (as does the lead-in prompt above it). The latter shows that a new WinGet check no longer reports that PowerShell needs an upgrade. Case closed!

The new PowerShell version is running so it no longer generates an update notification. [Click image full full-size view.]

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

PowerToys Puzzle Locks Together

April 15, 2024 Ed Tittel Leave a comment

Last week I blogged about how two quick back-to-back Powertoys releases seemed to have left WinGet one release behind. No more! What I described as an “interesting PowerToys Puzzle” was indeed a function of lagging manifest updates. This morning,that former PowerToys puzzle locks together as you see WinGet update it from v0.80.0 to the current v0.80.1 in the lead-in graphic.

After PowerToys Puzzle Locks Together, WinGet Gets It Right

If you look at the top block of text in the lead graphic, you’ll see WinGet recognizes the PowerToys version 0.80.0 needs an update to version 0.80.1. And indeed, that’s exactly what WinGet does in the center block of text just below the list of possible/pending updates that WinGet finds.

I did get a reply to the afore-linked April 11 blog tweet from WinGet team lead Demitirus Nelon. As I had guessed there was a lag between the second release and the WinGet manifest definitions. And it was apparently a completely routine fix, too.

So now, when the “What’s new” document shows v0.80.1 in its lead paragraph that actually agrees with the version that’s running on the target PC. Ain’t it great when things work the way they should? Three cheers for the PowerToys and WinGet teams for working quickly and accurately to fix this sooner rather than later.

I continue to be impressed with the dispatch and dedication of these folks. All I can say is “Keep up the good work!” I’m enjoying being part of the process.

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

Teams Versions Running Side-by-Side

April 12, 2024 Ed Tittel Leave a comment

Gosh, it gets confusing sometimes. But it could be mostly a Windows 10 vs Windows 11 thing. On Windows 10 I find myself with multiple Teams versions running side-by-side. That is: Teams (work or school) vs. Teams Classic. The lead-in graphic shows their taskbar icons serious magnified in that order (Modern: left; Classic: right). It’s interesting and a little vexing from time to time. Fortunately, MS will be retiring Teams Classic sometime later this year (no earlier than July 1, 2024 says Copilot).

Issues with Teams Versions Running Side-by-Side

I know I’m in the minority but I don’t have a current, actively administered MSA that’s tied to an AD, Azure AD, or Entra ID based environment. These are the MSAs that work best and most reliably with the new version of Teams (see about info from my ThinkPad P16 Mobile Workstation, running production Windows 11).

The latest version from my Windows 11 production PC (Build 22635.3430)

Here’s what Teams Classic tells me about itself (through an unusually tortuous path to get to its “About” info).

The latest Classic Teams from Windows 10 (Build 19045.4291)

I sometimes have trouble using the new Teams version as an app, though it does work consistently and reliably on the Web. But too often — especially in view of impending retirement — Teams Classic wants to run when I really want to use the new version. MS says the Classic version is supposed to uninstall automatically after switching over to the new version. So far, it’s not going anywhere…

I have to pay close attention to the icons to see which one I’m using at any given moment. Thus I’ve learned to distinguish the white background and blue symbol for new versus the blue background and white “T” for classic as a quick differentiator. Man, will I be glad when classic Teams finally retires into obscurity. But hey, that’s the way things go here in Windows-World from time to time where more versions of Teams may not be better but are seemingly inescapable in Windows 10. Sigh.

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

Interesting v0.80.x PowerToys Puzzle

April 11, 2024 Ed Tittel Leave a comment

I’ve just stumbled upon — and confirmed — and interesting v0.80.x PowerToys puzzle. Given that every picture tells a story, my lead-in graphic attempts to show what’s going on here. Let me explain, in three sections:

1. Top white text shows the info that pops up after Winget upgrades PowerToys to Version 0.80.0. Notice it reads “Release v0.80.1”.

2. Winget clearly shows it’s upgrading PowerToys to version 0.80.0 in the black text section in the middle.

3. Opening settings in that upgraded version of PowerToys, it self-reports as v0.80.0, and offers the “Install now” button to upgrade the program to v0.80.1. Not coincidentally, that install and upgrade actually work, and result in a self-report of v0.80.1.

Note: you may have to show the graphic in its own browser tab or window to see the whole thing. Some important stuff is on the bottom edge (v.0.80.1 update notification and install button).

Interesting v0.80.x PowerToys Puzzle Gets Cracked

The way I see it, there are two possibilities here, and Ockham’s razor leans heavily toward one of them. First, it’s possible that winget is actually installing version 0.80.1 but misreporting same. I doubt it. My best guess is the second one, which is that v0.80.0 is showing the documentation for v0.80.1 when it should be showing a downrev version.

I think I just confirmed this because I did click the “Install now” button in PowerToys > Settings. It ran a tool called “PowerToys (Preview) x64 Setup” complete with progress bar.

And when it was finished it showed me the same “What’s new” document shown above, also labeled Release v.0.80.1. What’s different this time is that PowerToys > Settings > General now self-reports as follows:

Seems pretty conclusive to me. I’m guessing that the development team hasn’t yet updated their manifests for WinGet to switch things over from v0.80.0 to v0.80.1. At the same time the new “What’s new” has probably pushed out the old one, so it’s showing even on the v0.80.0 version. Go figure!

Cool Tools, Recent Activity, Troubleshooting, WED Blog, Windows 10

Recent Windows 10 Uncommonly Reliable

April 9, 2024 Ed Tittel Leave a comment

It’s my habit to drop in on the built-in Reliability Monitor tool in Windows from time to time. That gives me a rough and ready read on how well — or badly — the focus system is doing. I usually launch this tool by typing “Reli” into the search box, but you can launch it from the Run box or the command line by typing perfmon /rel. If you examine recent history from my production PC, it should be obvious why I say “Recent Windows 10 uncommonly reliable.” In other words, nothing to see here, folks. That’s good!

Fingers Crossed: Recent Windows 10 Uncommonly Reliable

Noticing that things are going smoothly is one thing. Talking about it — and risking some kind of jinx — is entirely another. So I’m tempting fate here, but I must also observe that:

I actively run the target system at least 9 hours a day (weekdays) and at least 6 hours on off days
I’m not hesitant about installing or changing stuff around as I’m researching software, tools, scripting, and OS configurations
I take a complete image backup at 9 AM every morning (7 days a week) so I’m always prepared to restore same should I shoot myself (or my PC) in the foot
It’s been a busy 18 days since my last critical error on March 28. I replaced the CyberPower UPS software that day because the old version kept crashing. The replacement has been quiet since.

Gosh, it’s nice to see my trusty old (closing in on 8 years: i7-6700 Skylake, Z170 mobo, 32 GB RAM, NVIDIA RTX 3070Ti GPU) desktop still chugging along so well. I know I’ll need to replace it soon, but I feel little pressure or need to do so immediately, in the face of these recent Relimon results. Jinx factor aside, that is…

Alas, as I know only too well, this could change in a moment. Good thing I’ve got a 2021 vintage B550 mobo with 5800X Ryzen CPU, 64 GB RAM, and so forth, already put together and ready to drop in should the need arise. But I still don’t feel a pressing need to migrate just yet. Stay tuned…that will no doubt change!

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

MS Store 22043 Speeds Things Up

April 8, 2024 Ed Tittel Leave a comment

I just read online that MS is pushing a new and faster version of its Microsoft Store out through the Insider Preview hierarchy. Figuring out which version I was running on my Canary Channel test PCs showed me that (a) I was running the new version, and (b) that indeed, MS Store 22043 speeds things up notably. Good stuff. The lead-in graphic shows the version number after the app restarted itself following that upgrade.

If MS Store 22043 Speeds Things Up, Then What?

On both of my Canary Channel test PCs (Lenovo Thinkpads: X12 Hybrid Tablet/11th Gen i7 and X380 Yoga/8th Gen i7) , the store was uniformly quicker than before the upgrade. Search times were shorter, update downloads and installs quicker, and navigating around the UI snappier. It still takes a while to download app info in the Library view (but not as long a while as before).

There’s even a new “What’s new…” page that explains new features and improvements in the MS Store, to wit:

Interesting stuff! Thanks to Sergey Tkachenko over at WinAero, whose MS Store story this morning clued me into this new regime.

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

Dropbox Drops Gentle Reminder: RTFM

April 5, 2024 Ed Tittel 2 Comments

I have to laugh. I’ve been trying to get a beta version of Dropbox installed on my Windows 10 production desktop this morning. Trying, and failing, with nothing to show in Reliability Monitor, either. Then I decided to read the whole article about the new beta, which appeared on MSPowerUser on April 1 (no joke, alas). In a manner of speaking, Dropbox drops gentle reminder RTFM (read the fabulous manual).

Here’s what it says:

Note: Windows 10 users will need to uninstall earlier Dropbox desktop applications before installing the updated version to ensure optimal performance.

Guess what I didn’t do before trying the install? You got it in one: I did not first remove the old version before overlaying the new one. Sigh.

Heeding When Dropbox Drops Gentle Reminder: RTFM

Creature of habit that I am, I used winget uninstall Dropbox.Dropbox to remove the old version. Worked like a charm. Then I re-tried the Dropbox 196.3.6883 Offline Installer.x64.exe installer file. It too, then did its thing. And it took its sweet time, too.

But when all was said and done Dropbox came up just fine in Windows 10. It was smart enough to keep the old version’s login data, too, so I was able to get in and start working just like the old version. But by looking at the program’s about info I can see I’m running this latest (beta) version. Problem solved. Like I said: RTFM.

It never hurts to know precisely what you’re doing, before you start doing it. Otherwise, like me sometimes, you’ll have to figure it out as you lurch from one step to the next. Sigh again…