Insider stuff, Recent Activity, USB devices, WED Blog, Windows 11

Sprucing Up My Desktop Peripherals

Leave a comment

If you look back at my recent bloggage, you’ll see that I spent far too much time recently jumping into and rooting around in UEFI. Specifically, I found myself exposed to the oddities of the Asrock UEFI, which turns out to be finicky in many unexpected ways. Among many other bits of techno-trivia, I learned that my keyboard can’t send function key events to UEFI. I also learned that my logitech mouse sometimes is detected as (!) SATA storage during device enumeration at bootup. So, I’m sprucing up my desktop peripherals to steer clear of those issues. Let me explain…

Why I’m Sprucing Up My Desktop Peripherals

Function keys are helpful and even necessary during inital PC start for access to UEFI. They also drive many functions inside UEFI (e.g. F10 to “save & exit”). When the UEFI can’t read them, it’s anywhere from mildly annoying to maddening. My trusty old MS Comfort Curve 4000 (CC) is what’s known as a “composite USB HID device.” Alas, during POST and UEFI handoff, some PC firmware (including Asrock’s) handles only basic HID devices, not composite ones. To make that stuff work, in other words, I have to use a keyboard different from the CC. Sigh #1.

The older Logitech Unifying transceivers that work with mice and keyboards of that era also show another Asrock firmware quirk. They may sometimes (but not always) be recognized as SATA storage devices during first-time device enumeration. This threw me into an endless cycle of A6 POST errors on the B550 when I was trying to get the upstairs machine working last week. Here again, switching to a wired mouse fixed that issue. Sigh #2.

New Secure Boot, New Accoutrement

My fundamental problem is that I’m recycling old gear on a newer system. So it’s time to buy something new to bring it more in synch with the demands of modern UEFI, Secure Boot certificates, TPM 2.0 and suchlike. After walking thru my options with Copilot I’ve chosen a couple of Logitech items (I’m a long-time fan, and reviewed  lot of their peripherals in the 2000s for Tom’s Hardware):

  • Logitech Wavekeys keyboard (PN: YR0096) mostly matches the CC layout and feel, and is a basic HID device. Thus, its Fn keys should work properly in POST and UEFI.
  • In the same box, a Logi Bolt transceiver (xcvr PN: CU0021) which is supposedly superior to the old unifying xcvr, nor subject to mis-detection as a SATA device.
  • Logitech Signature M650 mouse (PN: MR0091) mostly matches the MS Mobile Mouse 4000 downstairs and the Logi mouse upstairs. Also works with Logi Bolt xcvr so I need only one transceiver for both devices.

I used the Bolt xcvr from the keyboard, so it came up instantly. I had to download and install the Logi Options+ app to get it to recognize the mouse through that same xcvr (it shipped with one of its own). But that was fast and easy, and the wireless link is quick and accurate. Alas, I got down on wireless keyboards back in the 2000s when I had a bad experience with transmission lag. If you type reasonably quickly (I’m at least 40 wpm or better) that’s not acceptable. So far, so good, with these Logitech devices.

Change is a watchword here in Windows-World. Like it or not (and I’m still figuring that out) my peripherals are changing. So are lots of others things. Adapt and thrive is the plan…

Facebooklinkedin
Facebooklinkedin
AI, Insider stuff, Recent Activity, WED Blog, Windows 10, Windows 11

Copilot: Driver’s Education

Leave a comment

If you read yesterday’s blog, you already know that I spent most of the weekend with my Flo6 desktop in UEFI, booting, or at the command line in WinRE/WinPE. On the other PC next to my desk chair, I keep a Lenovo P16 Gen1 Thinkpad. I was running Copilot on that PC, looking for insight into making Secure Boot work on the Flo6. Simply put, you can’t ask for help in Windows when that OS isn’t running. During that process I ended up in class for Copilot: driver’s education became quite a concern as I had difficulty scrolling down to read longish replies to my prompts and queries.

What Copilot Driver’s Education Is About

Turns out my scrolling attempts were misguided. I didn’t really understand how the touchpad on the P16 works. As you can see in the prompt window I’m using in this post for a lead-in graphic, the P16 touchpad is  more oriented to gestures than to driving screen controls.

While I was working over the weekend, I simply popped in a wired mouse — complete with scroll wheel — and used that to speed scrolling while interrogating Copilot on the P16. After I had time to dig in a bit deeper, I learned that a two-finger gesture works for scrolling that touchpad quite nicely (two-finger sweep up to scroll down, down to scroll up — shades of Doc in the movie Cars).

Hah! I’ve been using Copilot since it first showed up over two years ago (June 2023) and didn’t know that this till this weekend. Probably because I still mostly drive with a mouse and not a touchpad. Now I know. Here in Windows-World, it’s the little things that sometimes make a big difference…

Facebooklinkedin
Facebooklinkedin
AI, Insider stuff, PowerShell, Recent Activity, Thoughts & concerns, WED Blog, Windows 11

Secure Boot Pursuit Undone

Leave a comment

We’ve been (and still are, I kid you not) snowed in here in Central Texas. With Winter Storm Fern bearing down on us, we started hunkering down here last Friday (1/23). On Saturday we had rain, sleet and snow, and woke up to snowy sights Sunday. Figuring I had time on my hands, I decided to see if I could get Secure Boot working on my Asrock B550 Ryzen 7 5800X Flo6 production desktop. Alas, after much wrestling with hardware and software, I saw my Secure Boot pursuit undone early, early this morning. Let me explain…

Why Is My Secure Boot Pursuit Undone?

Through all kinds of contortions (see list below) I couldn’t get the PC to boot with Secure Boot enabled. Let me enumerate some of them so you can appreciate what I tried and failed to get done this weekend:

  • 2 repair  installs of my current running OS
  • 1 “dirty install” (do not format partitions, but run installer which moves old OS into Windows.old and creates a new one: IDKYDT)
  • At least 2 each dism /restorehealth, sfc /scannow & chkdsk
  • Remove boot/sys drive from its M.2 slot to wipe NVMe config data from UEFI (have to remove GPU to access slot, sigh)
  • Swapped out old, soon-to-be obsolete 1070 Ti for 3070 Ti GPU.
  • spent over 30 hours fiddling with UEFI and Windows configs

After the “dirty install” I realized I’d hosed the primary MSA login on my main work machine. Not acceptable!! This morning, I built a new Macrium Reflect X Rescue disk, extracted the drivers from the Flo6, and restored my most recent backup (Friday afternoon, after I’d reorganized the boot/sys drive partitions).

Back in Business, Back to Work!

I learned a bunch about boot configuration data and related commands. I’m definitely completely up on booting the Flo6 into WinRE, Windows installer media, and the Macrium Rescue Disk. I’m much better acquainted with the Asrock UEFI than I’ve ever been before.

I also learned that my old MS Comfort Curve 4000 keyboard can’t (or won’t) send Fn key data to UEFI. Working on the ThinkPad P16 Gen 1 I soon figured out scrolling Copilot output was MUCH easier with an external mouse with scroll wheel than using the touchpad. Who knew?

And finally, I learned that Copilot will lead you all over the place trying to solve problems, heedless of time involved and consequence entailed. Sure, AI will tell you pretty much anything about Windows you want to know, but I wasn’t happy with the circuitous routes it took me on, and the circles it spun me through. Then it occurred to me: the words mendacious, malicious, utopia, and paradise all include AI, as do the phrases folie a deux and waste of time. Here in snowed-in Windows-World this weekend, I saw all those things play out. It was oddly engaging, but I’m glad it’s over.

Facebooklinkedin
Facebooklinkedin
AI, Insider stuff, Recent Activity, Troubleshooting, WED Blog, Windows 11

Catching Up Can Be Hard to Do

1 Comment

I’ll admit it. I’m lazy. When I hooked up the Lenovo ThinkCentre Neo 50q Tiny PC a couple of weeks ago, I cheated. How? By hooking up the power, networking, video, keyboard, mouse and camera that had previously been driving the ThinkStation P3 Ultra Gen 2 mini-PC. Yesterday, I had some free time so I unhooked the former and reconnected to the latter. Given the hiatus a storm of updates followed (as expected). When I checked Reliability Monitor (ReliMon) this morning, I found a couple of unexpected errors for the Lenovo TSSIOMonitor (aka Super IO Monitor). When I asked Copilot for help reading those tea leaves, its response: “Catching up can be hard, especially after a prolonged idle period.”

Why Catching Up Can Be Hard

As I look at ReliMon for yesterday afternoon, I see a steady stream of updates and installs that start at 3:38PM and run through 4:09PM (60 in all). According to Copilot, TSSIOMonitor.exe is a Lenovo executable that’s constantly monitoring hardware. Its job is to throw errors when things don’t look or work correctly.

One potential cause of the error is when sensor data is invalid. Another is when driver data doesn’t match what the monitor expects. That’s precisely what happens when chipset drivers update, ACPI tables get rebuilt, embedded controllers reinitialize, and Super I/O registers may be unstable. Basically, the monitor was  using stale data to analyze a fresh situation, and erroring because of inevitable mismatches. Good to know.

Copilot Offers Insight, But I Must Assess Same

I’m getting used to asking Copilot to opine on system stuff when I need help understanding what’s going on. It certainly has more access to deep Windows arcana that I do, but I do notice occasional hiccups and hallucinations as it recites specific details. Indeed it sometimes goes off on tangents that don’t relate to my specific situation, but do play into the general circumstances and experiences around it.

This time, Copilot’s explanation makes good sense. And it helps me understand why such errors might occur when they did. It’s even comforting for it to tell me what I already knew: that a one-off or two-off error while a bunch of updates are underway isn’t terribly concerning. But we both agree that if it kept on happening (TSSIOmonitor.exe has been quiet ever since updates finished) there would be cause for concern, and possible action.

What Ronald Reagan said about nuclear arms monitoring apparently also provides to ingesting information from Copilot: “Trust, but verify.” Words to live by, here in a brave new AI-informed Windows-World.

Facebooklinkedin
Facebooklinkedin
Insider stuff, PowerShell, Recent Activity, Troubleshooting, WED Blog, Windows 11

Fixing WinKey+X Menu Change

Leave a comment

The Win+X menu — that little power‑user gem tucked behind the Start button — is a Windows feature you don’t think about much until it breaks. When it does, the symptoms can be maddening: missing entries, wrong icons, dead shortcuts, or menu items that don’t launch. I recently went through a repair of the Win+X system on my production desktop. That process revealed just how many layers contribute to this simple menu. Here’s a recap of how the issue was resolved in fixing WinKey+X menu change.

Getting Started: Fixing WinKey+X Menu Change

The first clue was that the Win+X menu wasn’t launching Windows Terminal correctly. Instead of opening a PowerShell or Terminal instance, it either did nothing or threw an error. That pointed to a problem in the Win+X shortcut groups. These reside beneath the user profile at:
%LOCALAPPDATA%\Microsoft\Windows\WinX

Windows organizes these shortcuts into GroupN folders (N = 1-3). Group3 is where Terminal and PowerShell entries live. When I opened that folder, those shortcuts were either missing or pointing to stale AppX registrations. This can happen after uninstalling or repairing Windows Terminal, or some profile migration wherein AppX package identities change.

Making Shortcuts Happen…

The next step meant rebuilding shortcuts manually. Windows Terminal doesn’t include .lnk files. Hence, I created fresh ones by right‑clicking the desktop and choosing New → Shortcut, and pointing them at the program. It lives under WindowsApps and includes current version info in its actual filename.

Because Windows Terminal’s AppX path changes with every update, hard‑coding its location isn’t smart. Thus, I used the stable execution alias: wt.exe

Once the shortcut was created, I renamed it to match canonical Win+X naming conventions:
Windows Terminal.lnk
Windows Terminal (Admin).lnk

Then I moved them into the Group3 folder. At this point, the shortcuts existed, but they were MIA on the menu. That’s because Win+X system caches entries and doesn’t refresh automatically. I forcibly rebuilt that cache by signing out and back in. After the next login, the menu finally displayed the new Terminal entries — but the icons were wrong.

What About Them Icons?

This led to the next discovery: Windows Terminal’s icon is stored inside its AppX manifest, not in a traditional .ico file. To fix them, I edited each shortcut’s properties and pointed the icon field to the stable Windows Terminal executable under Program Files. That exposed the correct embedded icon. Once updated, Win+X  displayed the proper visuals.

The final step was cleaning up legacy entries. A repaired Microsoft Account caused Windows to resurrect old Win+X shortcuts from a now-defunct installation. Removing stale .lnk files from Group3 eliminated duplicates and restored the menu to a clean state.

By the end of the trail, Win+X worked again: correct icons, correct commands, and a clean set of shortcuts that launch reliably. The repair reinforced something I’ve seen before in Windows troubleshooting . A system often holds onto old paths, old identities, and old assumptions long after underlying components change or go away. Fixing things means understanding where Windows stores its info, and updating each layer one by one.

If your Win+X menu ever starts acting strangely, a careful rebuild of Group3 shortcuts may be exactly what brings it back to life. Here in Windows-World you can always try. It might work. And if it doesn’t, there’s always something else to try instead.

Facebooklinkedin
Facebooklinkedin
Cool Tools, Insider stuff, PowerShell, Recent Activity, Troubleshooting, WED Blog

WinGet Weirdness Finally Whacked

Leave a comment

Every once in a while, Windows throws you a problem so strange, so deep in the plumbing, that you can’t help but treat it like a spelunking adventure. Over the past week, I’ve worked through one of those rare cases. Copilot ultimately helped diagnose it as a completely broken WinGet (aka Microsoft.AppInstaller) stack. Apparently, it came from corruption inside the WindowsApps directory. That’s the protected, TrustedInstaller‑owned home for all MSIX/AppX packages. I worked through a recovery  process that touched ACLs, reparse points, Safe Mode, user‑level activation, and the PATH environment itself. Ultimately and fortunately, it ended with WinGet weirdness finally whacked.

Getting to WinGet Weirdness Finally Whacked

The symptoms were deceptively simple: WinGet wasn’t recognized, App Installer wouldn’t register, and the user‑level WindowsApps folder lacked key shims. Alas, the root cause was far deeper. The system‑level C:\Program Files\WindowsApps directory had partially corrupted ACLs, preventing enumeration that blocked TrustedInstaller from working. Even elevated tools couldn’t see its innards.

The breakthrough came in Safe Mode, where Windows releases some of its usual locks. Using takeown and icacls, I forcibly reclaimed ownership and permissions long enough to inspect the directory. Hundreds of previously invisible entries suddenly appeared — confirmation that the ACL choke point had finally broken open.

From there, I rebuilt the directory’s security model: restoring SYSTEM and TrustedInstaller with full control, removing inheritance, and returning ownership to TrustedInstaller. With the system-level store healthy, I exited Safe Mode (after discovering that msconfig, not BCD, was trapping the machine there) and rebooted into normal Windows.

Repairing WinGet/Microsoft.AppInstaller

Next came the App Installer repair. The system package was still resident, but user-level registration was MIA. I downloaded the official MSIX bundle, reinstalled it, and then manually re‑registered the package using its AppxManifest. That restored the user‑level WindowsApps directory and recreated the shims — including winget.exe.

But one last puzzle remained: even with the shim present, Windows still didn’t recognize the command. The culprit turned out to be the PATH. During the earlier corruption, Windows had silently dropped this critical entry:
%LOCALAPPDATA%\Microsoft\WindowsApps

Without that, no packaged app alias can resolve. Adding it back with setx, signing out, and signing back in finally brought the entire chain back to life. winget -v lit up instantly.

In the end, the repair touched nearly every layer of the Windows package‑servicing stack: NTFS ACLs, TrustedInstaller ownership, AppX registration, user‑level activation, and environment variables. It was a rare, deep, and oddly satisfying recovery — the kind of fix you document not just for others, but for the story it tells.
And now WinGet is fully operational again.

I’m celebrating the occasional “happy ending” that’s so rare in Windows-World. If you’re lucky you’ll never have cause to do likewise. But if this ever happens to you, here’s a trail of breadcrumbs to lead you out of that forest…

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Thoughts & concerns, WED Blog, Windows 11, Windows OS Musings

NVIDIA Enters Windows on ARM Field

Leave a comment

Here’s an interesting bit of news: AI heavyweight NVIDIA enters Windows on ARM field, as discussion of its N1 and N1X SoC offerings proliferate. These stories are popping today (Jan 20) but rumors have apparently been flying since last year. I got my info from WinBuzzer, but other key stories from TechRadar, DigiTimes, Tom’s Hardware, and more, are also worth a peek. Qualcomm’s exclusivity looks ready to expire, and x86/AMD64 CPUs likely to get even more competition soon.

As NVIDIA Enters Windows on ARM Field, Here’s What’s Known

The initial offering involves two “system-on-a-chip” (SoC) architectures known as N1 and N1X. According to WinBuzzer (confirmed at other sources) “the N1 designation likely targets desktops while N1X focuses on notebooks…” Deeper technical details are still emerging but here are some broad possibilities:

  • 20-core ARM CPU designed with MediaTek
  • 10 Cortex-X925 performance cores
  • 10 Cortex-A725 efficiency cores
  • NVIDIA Blackwell GPU
  • Built on TSMC 3mm process
  • NPU delivers up to 1000 TOPS for AI
  • Includes 128GB RAM shared between CPU & GPU

That certain raises the bar from where things stand with either generation of Snapdragon X processors (shipping X1 variant since last year, X2 planned for Q126 delivery).

Things Could Get Interesting…

The big news here, of course, is that NVIDIA is building in GPU capabilities that match their current discrete and laptop 5070 class devices. Qualcomm’s offerings have delivered sufficient computing power and astounding battery life. But their Adreno GPUs are underpowered for serious gaming, 3D modeling, simulations, and other display-intensive workloads.

Looks like NVIDIA is throwing down a gauntlet in the Windows marketplace. This should make life interesting for everybody, including prospective buyers, but also intel, AMD, Qualcomm. The biggest PC OEMs are already on board. Look out Windows-World, here comes another 800lb gorilla!

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

CrapFixer Gives ASUS A14 Low Bloat Rating

Leave a comment

One of the “interesting parts” of new machine intake is the process of removing things the system maker installs that you don’t want. This is often called “debloating” or “degunking.” I’m adding this to my intake process going forward, and reporting on it today, because I’m mostly convinced that the GitHub CrapFixer project does a good job of taking stock and reporting on unwanted apps (among many other things). I just ran it on my newest Copilot+ PC, and I’m pleased to report that CrapFixer Gives ASUS A14 low bloat rating. I’ll explain…

How CrapFixer Gives ASUS A14 Low Bloat Rating

I’m basing my “low bloat rating” on the information that appears in the lead-in graphic. It’s the CrapFixer “Analyze” output that shows up under the “APPS ANALYSIS” heading. Indeed, there are 17 entries there. BUT inspection reveals that none of these items come from third parties: they are items included by default in a normal Windows 11 installation.

That ties into the definition or bloatware or crapware that I think makes most sense. That definition: software apps from third parties that at least some user neither want nor need on their PCs. Frequent examples include:

  • Trial AntiVirus Suites: McAfee, Norton, Trend Micro, etc.
  • Cloud Storage trials: Dropbox, Box, etc.
  • Media/entertainment trials: Netflix, Spotify, etc.
  • Game trials or freemium games: Candy Crush, Hidden City, etc.

The ASUS A14 Zenbook includes none of these, except stuff that Microsoft bundles with the OS. That’s about as low as bloat gets. For the record, my recently-added Lenovo ThinkCentre Neo 50q gets the same rating, for the same reason.

Here in Windows-World bloatware is not uncommon on new PCs and laptops. It’s nice when little or none presents. And both ASUS and Lenovo make third-party offers available for owners thru their update apps (MyASUS and Lenovo Vantage, respectively). But they don’t preinstall them on their PCs. Good -oh!

 

Facebooklinkedin
Facebooklinkedin
Hardware Reviews, Insider stuff, Recent Activity, WED Blog, Windows 11

ARM Desktop: Neo 50q Pros and Cons

2 Comments

OK, then. I’ve been playing and working with the Lenovo ThinkCentre neo 50q for a couple of weeks now (see my Jan 9 first looks post). Now that it’s been in harness for a bit, I can speak more to what this tiny PC can — and can’t — do. I’ll lay out this ARM desktop (Neo 50q) pros and cons for your consideration. Let’s go…

Considering ARM Desktop: Neo 50q Pros and Cons

The lead-in graphic speaks indirectly to one of my profound reservations about this otherwise nifty mini-PC: the CPU is too under-powered for it to qualify as a Copilot+ PC. Note the model appears as X126100. Its NPU is rated at 45 TOPS but it’s neither a Snapdragon X Elite nor X Plus model. Thus, it doesn’t make the grade, and ships without the Copilot AI namespace, and does not appear on the Microsoft Copilot Plus list. This quibble boils down to: why acquire an ARM desktop if it’s not Copilot+ capable? Good question!

Neo 50q Pros

That’s where the pros for this unit come into play — namely:

  • Compact form factor: works well for small footprint workspaces
  • Incredibly quiet operation: I’ve heard the fan come on only a handful of times in two weeks. When it does it’s still pretty quiet.
  • Low power draw: the overall PC sips rather than sucks power (5-9 W at Windows desktop, 10-18 W normal load; 26 W peak)
  • Instant-on startup: ARM works well with Modern Standby so the unit wakes in 2-3 seconds. Boot & restart times are also  speedy.
  • Enough oomph for everyday computing: handles office apps, surfing & email, Teams & Zoom sessions with aplomb
  • Enterprise-friendly security capability: Pluton support, hardened drivers, Secure Boot & Modern Standby make Neo 50q a good fit for managed environments and secure for standalone use
  • First ARM desktop available, and reasonably affordable at US$589 (does need monitor; mouse & keyboard included)

Neo 50q Cons

Let’s contrast this to the Neo 50q’s various cons — to wit:

  • No Copilot+ capability may deter some users, but only 2-5% of PCs sold today meet those requirements
  • USB-C port does not support Thunderbolt 4 or USB4
  • Limited upgradeability: RAM is soldered. only 1 M.2 slot, no PCIe expansion
  • ARM still imposes some compatibility and performance limitations: some apps won’t run while others run more slowly
  • ARM Adreno GPU limits graphics so it won’t handle serious games nor heavy creativity workloads

Net-Net: Good for Students & Office workers

I give the Neo 50q lots of points for cute, quiet, low power and minimal maintenance requirements. But it’s not a powerhouse by any stretch. It fits well into dorm rooms, home offices and business workspaces for people who need basic computing services. The Neo 50q won’t serve well for those who need more horsepower, who write code or create/edit videos. It can’t (and won’t) do much AI stuff of any kind.

All in all, it’s a niche product that fills that niche well but can’t wander outside those narrow boundaries. Given that the Lenovo IdeaCentre Mini X — a real Copilot+ mini-desktop — lists for US$1365, the next step up is a pretty big one. This will make the Neo 50q very appealing for some, and not at all for others. For myself, I like it very much for what it is and can live with what it isn’t.

Facebooklinkedin
Facebooklinkedin
Device drivers, Insider stuff, Recent Activity, Updates, WED Blog, Windows 11

Intel Graphics DSA Update Weirdness

Leave a comment

It’s strange. I just got a notification on the Lenovo ThinkPad X12 Hybrid tablet that Intel DSA had 3 updates pending: Bluetooth, Graphics and Wi-Fi. Of the three, BT and Wi-Fi went swimmingly. The graphics update, however, hung in unexpected ways. That’s how I found myself fixing Intel Graphics DSA update weirdness minutes ago. The trick is fortuitous, as I’ll explain…

Overcoming Intel Graphics DSA Update Weirdness

I have kind of a built-in timer when it comes to waiting for Windows installs to finish up. If an installer shows a progress bar, and I see no progress at all for 5 minutes, I start getting antsy. At 10 minutes, I pull the plug and kill the installer to see what happens.

Killing an installer may take varying degrees of effort. The Intel Graphics installer was well-enough behaved to respond to the “close window” controls at its upper right corner. In other, more stubborn cases, I’ve been known to resort to Task Manager, where I’ll find and kill the installer process itself. Sigh.

Imagine my surprise when the DSA installer reported success in installing the new Graphics driver. Seems that their current installer had finished, but simply neglected to update the UI to report said progress.

As Luck Would Have It…

My impatience spurred me into doing exactly the right thing. I’ve had other Windows installers hang, where killing the installer meant I had to start over and install again. In some more extreme cases, I first had to clean up the leftovers from the hung installer before a new install would work. That’s where a tool like Revo Uninstaller (in “Hunter Mode”) can be helpful: if you can find a UI trace left behind –such as the DSA notification tray icon — you can use it to help you clean up.

All I can say is “Thank goodness no cleanup was needed.” Here in Windows-World, when things get messy, they can really suck up some serious time. I ran into that last Monday, when WinGet in my primary MSA got profoundly bollixed. Go figure!

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness