Cool Tools, Insider stuff, Recent Activity, WED Blog

Winget Solves Self-Update Issue

February 29, 2024 Ed Tittel Leave a comment

Once upon a time, not so very long ago, Winget would hiccup when updating itself. No longer. The latest leap to 1.7.10582 solves that, and adds a bunch of cool new functionality as well (e.g. repair command, enable Windows Features as dependency, access URL instead of local file, and more). As Winget solves self-update issue, it’s becoming even more of a go-to tool for admins and power users.

How Winget Solves Self-Update Issue

It’s taking the same approach that Windows Terminal has for a while now: it’s maintaining the existing process, and instructing users to “Restart the application to complete the upgrade.” Closing, then re-opening Windows Terminal does the trick nicely. Glad to see it.

Indeed, this is by any metrics a “big update” for Winget. Take a look at the release page and you’ll see 6 entries under the “Features” heading, with dozens more under “What’s Changed.” Good stuff!

Here’s the complete –info block for this latest incarnation, for the record:

Winget –info for v1.7.10582
[Click image for full-size view.]

These days, I’m about as big a fan of this tool as you can find. I highly recommend it for updating apps and applications in Windows. I also recommend that you send feedback to developers whose apps and applications you use, but who don’t yet submit package manifests to make their updates installable via winget. The winget Windows Package Manager Manifest Creator toolset also got a recent and major set of enhancements designed to persuade those not already using this tool to jump on board. Let them know!

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

Exploring New NVIDIA Beta App

February 28, 2024 Ed Tittel 2 Comments

OK, then. Through what I can only describe as a bitter irony, the only desktop that I own with enough space in the case for a GeForce RTX 3070 Ti is my aging i7-6700 Skylake build. It’s too old to meet Windows 11 system requirements so it’s running Windows 10. Even so, I put it through its paces just now, while exploring new NVIDIA beta app (NVIDIA App.exe). Its home page, with the exe file properties page overlaid, provides the lead-in graphic above.

What Exploring New NVIDIA Beta App Tells Me

If you visit NVIDIA’s “Test Drive” page for this beta software you’ll find a concise summary right next to the download link for same. It reads:

The NVIDIA app beta is a first step in our journey to modernize and unify the NVIDIA Control Panel, GeForce Experience, and RTX Experience apps.

Indeed, the driver update and subsequent desktop behavior is unchanged. I used the beta sofware to update my RTX 3070 Ti to version 551.61 (Rls 2/21/24). Just like GeForce Experience did, it changed all RDP windows from maximized to “fill entire pane.” It also moved all open windows from my (secondary) left-hand screen to the (primary) right-hand screen. Easily cleaned-up but I wish they’d change the code to capture home screen info and restore it at or near the conclusion of the driver install.

The NVIDIA Control Panel is indeed gone from Control Panel, though. Its functions are now integrated into the Beta app. I believe that’s a positive step. NVIDIA also mentions

a redesigned in-game overlay for convenient access to powerful gameplay recording tools, performance monitoring overlays, and game enhancing filters, including innovative new AI-powered filters for GeForce RTX users.”

I’ll have to turn this rig over to my gamer son when he’s home for Spring Break next week and see what he thinks of the gaming stuff. I’m no gamer myself (except for card and board games which exercise none of these advanced capabilities).

What About That New Software?

The beta software kicks off with a new version number of 10.0.0.499/p. So far it seems mostly like a stitched-together version of GeForce Experience and the Control Panel Item. But then, I can’t appreciate the game stuff. We’ll see how it all plays out. It’s undoubtedly more convenient to find everything together, though, so I’ll give NVIDIA brownie points for consolidation. The rest is still TBD. Stay tuned…

Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 10

SearchApp.Exe Sets Windows 10 Crash Record

February 27, 2024 Ed Tittel 2 Comments

It took me a while to count them up, but my Windows 10 production PC hit some rocks yesterday. As SearchApp.exe sets Windows 10 crash record on that PC — 49 Critical “Stopped working” events in one day — I find myself wondering if it’s time to move onto a new production PC here in the office. As you can see in the lead-in graphic, the reliability index dropped like a stone!

Cringing As SearchApp.Exe Sets Windows 10 Crash Record

Frankly, I’m not sure what to make of this. As I dig into similar reports online — as in this TenForums.com thread — I see my problem is neither unique nor necessarily pathological. But gosh! It sure it disconcerting to see so many crashes in a single day.

I know why it happened, too: my Start menu stopped working properly about mid-day yesterday. Thus, I found myself using the Windows Search box a LOT more than usual. Then I figured out I could scroll through “All apps” and get to what I needed alphabetically. Eventually, I went into Task Manager and clicked the “Restart” option in the right-click menu for File Explorer. That restored Start to normal behavior and stopped the weird search bomb from going off, apparently.

Another Brick in the Wall?

I keep thinking that the time is coming ever closer when I’m going to have to switch my production work over to a new desktop. I built one last year (an AMD 5800x, B550 mobo, 64 GB RAM, etc. etc.). Could this be Windows’ way of telling me “time to go!” Perhaps… Let me procrastinate a bit longer, please?

But as Pink Floyd put it “You can’t have any pudding if you don’t eat your meat…” So I’d best get moving in the next month or two. The beast must be fed!

Device drivers, Insider stuff, Networking, Recent Activity, USB devices, WED Blog

Windows 11 Wi-Fi 7 & USB4v2: What’s Up?

February 26, 2024 Ed Tittel Leave a comment

On January 8, 2024 Wi-Fi 7 went public. That’s the same day the Wi-Fi Alliance introduced its Wi-Fi Certified 7 program. USB4 version 2.0 goes all the way back to October 18, 2022. But only with the release of Insider Preview Canary Channel Build 26063 in February 2022 did MS start testing support for related Wi-Fi 7 drivers. (USB4 version 2.0 has been baked in since Build 23615 in the Dev Channel, released January 11, 2024.) Neither has appeared in a production version of the OS. Thus, a valid question for Windows 11 Wi-Fi 7 & USB4v2 has to be: What’s going on? TLDR answer right now is “Not much just yet.” There are lots of good reasons why so please let me explain…

What’s Afoot with Windows 11 Wi-Fi 7 & USB4v2?

One way to look at this is from a market availability standpoint. Precious few devices for sale right now support either or both of these standards. As I write this item, I see exactly 2 network adapters (one USB, the other PCIe x4) that support Wi-Fi 7.Ditto for Wi-Fi 7 routers. I can’t find any laptops that offer built-in support for either standard just yet. Many new models are promised later in 2024, and could change that.

Though it’s being proclaimed as something of an oversight it’s really just a function of supply and demand. (See this Tom’s Hardware news item by way of illustration.) Basic economics and recent history with Wi-Fi 6 and USB4 version 1.0 show that it takes about two years for these new standards to make their way from introduction and into more general adoption. I don’t see this latest iteration as terribly different.

Shoot! I didn’t lay hands on my first PC with built-in USB4 capability until the Panasonic Toughbook FZ-55 showed up here at Chez Tittel late last year. Just before Christmas, in fact. If it takes that long to hit my hot little hands again, I’m looking into late 2025 before a personal encounter might happen.

Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11, Windows Update

Canary 26063 Throws Install Error

February 23, 2024 Ed Tittel Leave a comment

Oh well: it happens sometimes. One of my two test PCs on the Insider Preview Canary 26063 throws install error right near the end of the install process. It’s one I’ve seen before –namely:

Failed to install on ‎2/‎22/‎2024 - 0xc1900101

It’s something of a grab-bag error in that it can come from insufficient disk space, driver conflicts (esp. from external USB devices), an out-of-date driver on the target PC, AV conflicts, and more (see this MTPW Backup Tips note for all the deets).

When Canary 26063 Throws Install Error, Then What?

I’m trying a two-pronged strategy this morning. First thing is a simple retry. And when I ran that option in WU, it thought for a while, then jumped from the download phase to the GUI install phase. So obviously, it checked over yesterday’s UUP downloads and found them satisfactory. Right now, WU is 49% into installling 26063. Here’s hoping that works.

But on the other prong, I’m downloading the 26062 ISO from UUPDump.net. I’ve observed that when a WU-based install fails, sometimes a local install using setup.exe from a mounted ISO will work. It may also provide more useful error messages in local logs should it fall over near the end of the process yet again.

FWIW, this seems to be a pretty substantial update, too. And indeed on the other test PC — the one where the upgrade worked –it says 24H2 in the Winver window. I guess that means MS is floating Windows vNext to Insiders right now.

Lookit that! 26063.1 says “Version 24H2.” It’s arrived…

More to Follow…

Now, the WU install is at 64% and UUP is building images and stuff for the upcoming ISO file. Based on yesterday’s experience, this will still take a while. I’ll jump back in and update when it gets wherever its going. Stay tuned!

Insider stuff, Networking, Remote Desktop (RDP), WED Blog

RDP Absence P16 Fixed

February 22, 2024 Ed Tittel Leave a comment

It’s been weird. I had trouble accessing my Lenovo ThinkPad P16 Mobile Workstation for an attorney call last Friday. I couldn’t see it while it was hooked up on Ethernet but it worked OK in Wi-Fi. Today, i finally figure out why that was happening and RDP absence P16 fixed as a result. Deets follow…

How to Get RDP Absence P16 Fixed…

The ever typical error message that shows up when RDP can’t find a PC by desigation (computer name in this case) appears in the lead-in graphic above. Because I already fixed my P16 problem, I used “P15” as the machine name. Since there ain’t no such beast on my LAN, of course it provokes the old familiar “can’t find the computer…” error message shown. But that’s what I was seeing for the P16.

Took me a while to figure out why. If you follow this blog you know I had a Panasonic Toughbook FZ-55 on loan here for some time (unboxing post). While it was hooked up to the LAN it used the Ethernet port my P16 normally uses. On the P16 I switched to Wi-Fi.

That was the problem: with a new NIC for Wi-Fi the P16 also got a new set of IPv4 and v6 addresses. When I hooked back into Ethernet, RDP knew nothing about this. So when I accessed the P16 by name it went looking for it on its Wi-Fi associated IP address. No go!

Fixing the Mix-up

Removing info from RDP requires deleting associated keys in the Registry. I had to visit the key named

HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default

to reset the RDP roster. With the old (and incorrect) entry removed I had to go through initial RDP connection set-up again for the P16. But that was easy (provide a password for the Windows login I use) and done. Now things are working again on the Ethernet connection. Only problem is, I’ll have to remember to do this again if I switch back to Wi-Fi (or just use the IPv4 address, which is how I got back in and ultimately how I figured things out).

And isn’t that just the way things go in Windows-World sometimes. If it ain’t one thing, it’s another!

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

CNF Conundrum Gets Some Love

February 21, 2024 Ed Tittel Leave a comment

OK, then. I’ve been trying to figure out why, on some of my test PCs, I get an error message when PowerShell loads my profile and tries to import the PowerToys WingetCommandNotFound (CNF) module. You can see that error message in the lead-in graphic above (from my ThinkPad P16 Mobile workstation). Thanks to some fiddling around, this CNF conundrum gets some love — finally!

I haven’t figured out how to fix the problem properly just yet. But for the nonce, if I go into PowerToys, visit CNF, uninstall and then resinstall same, it returns to work. This happens every time I open a fresh PowerShell session, so it’s at least mildly bothersome. But I’m starting to make progress on figuring things out.

How CNF Conundrum Gets Some Love

The error message keeps changing on me as I add things to the folder where the profile resides — namely %user%\documents\PowerShell. First, it complains about not being able to find the module itself. I copy it into that folder. Then it complains about a .DLL. I copy that, too. Finally, it complains about an error handler not being able to field a thrown exception.

It’s not fixed yet, but I now know that this issue comes from my PowerShell modules path set-up. Something is wonky between those search paths (there’s one for the system, and one for my login account) and PowerToys. This happens for one of my Microsoft Accounts (MSAs) every time I use it to log into Windows, because this information is shared across those instances through OneDrive.

What’s Next?

I’ve got to research how I should be setting things up in the OneDrive environment to get PowerShell and PowerToys to get along with each other properly. I’ll be contacting the WinGet crew (Demitrius Nelon’s team at MS) to request additional info and guidance. That’s because my online searches have only clued me into what’s going on, but not how to fix it properly.

Stay tuned: I’ll keep this one up-to-date. And I’ll probably post again, when a resolution is formulated. This just in: OneDrive is reporting multiple copies of the PS profile in its file store. Could this be related? I have to think so. Again: stay tuned…

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

Repair Install Fixes Instability

February 20, 2024 Ed Tittel 2 Comments

At the beginning of this month, I performed an in-place upgrade repair install on my Windows 10 production PC. It’s now running Build 19045.4046. You can see that this repair install fixes instability on the PC in the lead-in graphic. Over the past 20 days I’ve had only one critical event — mostly self-inflicted when testing winget Chrome update behavior (see last Friday’s post for details). Otherwise, this 2016-vintage system has been rock solid of late.

When in Doubt, Repair Install Fixes Instability

Gosh! I’ve long been a believer that an in-place upgrade repair install (IPURI) is something of a Windows cure-all. Reminder: an IPURI runs setup.exe from a mounted ISO for the same version of Windows that’s currently running on a PC. Thus, it requires the host OS to be running well enough to replace itself. See these terrrific TenForums.com and ElevenForum.com tutorials for all the details…

Thus, you can’t use this technique if you’re having boot problems, or the OS isn’t running well enough to get through the GUI phase of a Windows upgrade. But for situations where the OS is running (but most likely, not as well as you might like) this technique works extremely well. My earlier Reliability Monitor trace, before the February 1 IPURI, looked something like a sawtooth wave on an oscilloscope. Ouch!

How to Get the Right ISO

I still use UUPDump.net to match build numbers between what’s running and the ISO I have it build for me. Then, I mount that ISO, and run setup.exe from the virtual DVD drive ID Explorer puts out there for me. Lately it’s been showing up as the E: drive; but this morning it comes up as P:. But you’ll most likely see it labeled with the initial characters of the image label like this:

Here’s what Explorer shows me when I mount the ISO I used on February 1 for an IPURI: Virtual DVD Drive P:

For the record, I also use the excellent Ventoy project software to boot into my various ISOs when an IPURI won’t do. Admins and power users will want to keep a USB handy with their fave ISOs for repair and recovery scenarios. I do that on a 1 TB NVMe SSD inside a USB3.2 drive enclosure. Lets me keep dozens of ISOs around, ready to boot into any of them on a moment’s notice. Good stuff!

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

Winget Browser Updates May Be Curious

February 16, 2024 Ed Tittel Leave a comment

As far as I can tell, I’ve been blogging here about the Windows Package Manager — Winget, that is — since May 2022. Indeed it’s received regular mention ever since (nearly a third of all posts). I finally observed the other day that winget won’t update a browser with any of its processes running on the target PC. Also the browsers I use (Chrome, Firefox, Edge) still make you “Relaunch” to complete any update. This includes instances when Winget updates them successfully. Hence my assertion: Winget browser updates may be curious. And I mean both in terms of effect and outcome.

If Winget Browser Updates May Be Curious, Then?

It doesn’t stop me from trying, but the update doesn’t happen at all when any related process is running. Thus, for example, if any chrome.exe items show up in Task Manager>Details view, winget breezes past the update package and does nothing. Ditto for Firefox and Edge. But it’s a good flag for me to jump into each one’s Help>About facililty which is usually more than happy to update from insider the browser itself. And again, to request a “Relaunch” when that process comes to its conclusion.

It’s all part of the learning process in working with winget to keep Windows up-to-date. Sometimes — indeed nearly all the time — winget handles update packages quite nicely on its own. At other times (less often) winget acts as a sentinel to warn me that an update is available, which I then must figure out how to install.

Here’s a short list of such programs above and beyond the browsers already mentioned: Kindle for Windows, Discord, certain EA game executables, Teams Classic, Windows Terminal (now fixed), and even Winget itself from time to time. But gosh, it’s always fun to see what’s out there and what happens when winget wrangles update packages. It’s made my life ever so much more interesting (and updates easier) since it emerged in 2022.

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

Build 26058 Explorer Brings Button Labels Back

February 15, 2024 Ed Tittel Leave a comment

It’s a small change but a helpful one. In Canary Channel Build 26058 Explorer brings button labels back. That is, instead of simply showing labels and forcing you to do one of these:

Remember what they are and what they do
Mouse over the label icon and read the text tip
Pick one and hope for the best

Explorer once again shows text to accompany the icons so users know what they’re doing. These show up at middle in the lead-in graphic, with icon buttons above and text below. To wit: Scissors button/Cut, overlaid pages/Copy, Text “A”/Rename, Block with pointer/Share, and Trashcan/Delete. Good stuff!

You can see what the old way looks like in the production Windows version (Build 22631) below where the icons appear at the bottom of the Explorer right-click context menu for files inside a folder. Much less intelligible, IMO.

Notice the line of icons at the bottom of the content menu. Mouseover will show tip text.

Rejoice When Build 26058 Explorer Brings Button Labels Back

It’s not a huge change to see text show up with a button, unprompted. But it is a comforting usability improvement. I’d always wondered why MS adopted this ultra-compact approach. But given the presence of tip text on mouseover, I’d always been able to suss things out if I wasn’t 100% what was what.

This latest improvement saves the time and effort involved in mousing over. I definitely appreciate it. On the one hand: thanks! On the other: Why’d it take so long?

And if those aren’t among the major dueling dualities here in Windows-World, I haven’t been paying attention for the past 30-plus years. Yeah, right…