Windows 10 Copilot Limitations

Dang! I’d have to call my desktop experience “a swing and a miss.” I jumped on the KB5023378 Preview update, expecting to get Copilot out of that amendment. Wrong! Among the first words in the afore-linked update Support note, key Windows 10 Copilot limitations emerge. This includes this scoping statment: “This [Copilot addition] only applies to devices that run Home or Pro editions…” (emphasis mine). As you can see from the lead-in graphic for reasons that are too long and tedious to explain, this PC is running Windows 10 Enterprise. Sigh.

Bitten By Windows 10 Copilot Limitations

Sigh. It just goes to show that my personal dark cloud hasn’t quit hovering in the vicinity. I’ve often observed that if MS slides an update out as a gradual release, my PCs are invariably in the rear guard. This is something of a spin on this all-too-familiar situation, but nontheless an amusing one.

Fortunately, my physical desktop is not the only Windows 10 image I can run. I just jumped over to the ThinkPad P16 Mobile Workstation where I have a couple of Win10 images from which to choose. My cleanest one (installed last week for an AskWoody column) is installing same right now. When it reboots, I expect to see a Copilot icon in the Taskbar. Here goes…

Overall, install time on a 4GB Gen2 VM was quick. The whole thing took under 3 minutes to download, install, then cycle through post-reboot update processing. Good stuff. But did I see Copilot on the Taskbar when it was all done? Nope.

I had to turn on and relaunch the VM to come back from the update reboot. And another reboot didn’t bring it up, either. Nor did a right-click in the Taskbar show a Copilot control. No Copilot item under Settings → Personalization, either. Very interesting. I’m obviously going to have to learn more to get Copilot working on my Windows 10 Pro VMs. Should be fun: stay tuned!

That Old Familiar Sensation

I see in the Windows Latest coverage (Mayank Pamar) that “Microsoft has also warned that the feature may not be available on devices with compatibility issues, including devices with an incompatible app.” Why do I get the feeling that includes either my ThinkPad P16 Mobile Workstation or its Hyper-V runtime environment for my 2 Windows 10 VMs on that machine?


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 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, 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.


Winget WT Update Workaround Needed

In going through update maneuvers yesterday, I observed there was a winget WT update workaround needed. That is, my attempt to upgrade Windows Terminal (WT) using winget failed. You can see what happened in the lead-in screencap. It shows that an initial attempt to install a dependency for WT — namely Microsoft.UI.Xaml — failed because a higher-numbered version is already installed. Whoa!

What Is the Winget WT Update Workaround Needed?

What to do? Fortunately, there are always multiple ways to update or upgrade in Windows-World. This time around, I went to the WT GitHub page and checked the version number on the latest release. As you can see in the next screencap, it’s the very same version that winget tried, but failed, to install as shown in the lead-in graphic.

Winget WT Update Workaround Needed.github

Funny thing: latest version matches winget’s target. That means there’s another way…

Given that GitHub has the same version, there should be some kind of Windows installer amidst its list of downloads. When I see it’s named Microsoft.WindowsTerminal…msixbundle, realize it’s targeting a Store version of WT. So off I go to check updates in the Store first. Nothing there, so I download and install the afore-mentioned msixbundle file. It works, as you can see in the About info from WT on that PC.

Winget WT Update Workaround Needed.about

Click the down-caret in the title bar in WT, then select “About” in the drop-down menu. Here ’tis!

As shown, the manual update using the msixbundle file did the trick. I could have waited, and the Store would have (eventually) handled the update automatically. But if I could have waited, I probably wouldn’t be the rabid Windows Insider I’ve always been, since day 2 of that program’s launch. LOL!

Feedback Followup…

I’m pretty sure winget should be smart enough to keep going if it finds a higher-numbered version of a dependency already in place on a target update PC. I’m going to share this blog post with the nice folks on the winget team. I bet they’ll fix this muy pronto! TIA, people…

Just Checked In … And It’s Fixed

I sent feedback to the team yesterday and got a reply that the dependency check should be a “min version check.” That is check to see that version is “greater than or equal to” versus “equal to.” And indeed, it now seems to be fixed. Thanks, guys: hope you all have a marvelous holiday break.


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!



Windows 10 Copilot Is Coming

OK, then. Rumors have been swirling for weeks, but MS made things official on November 16. To see that, please check the “firstPublishedDate” field in this MS Support note: How we are maximizing value in Windows 10. It also tells us that Windows 10 Copilot is coming, initially in the Release Preview channel for Insiders.

What Windows 10 Copilot Is Coming Really Means

MS puts things this way in the afore-linked Support note:

We are hearing great feedback on Copilot in Windows (in preview) and we want to extend that value to more people. For this reason, we are revisiting our approach to Windows 10 and will be making additional investments to make sure everyone can get the maximum value from their Windows PC including Copilot in Windows (in preview).  We are also adding the “Get the latest updates as soon as they’re available” toggle to Windows 10.

Aside from seeking a larger audience (there are 1.0-1.1 B Windows 10 monthly active users, versus around 400 million such users for Windows 11), what else does this change do for Microsoft? Good question! It certainly confirms their commitment to integrating AI into the desktop and its supporting apps and platforms on as many levels as possible.

What Else Does Windows 10 Copilot Tell Us?

Methinks it says MS has learned from history, and does not necessarily expect the world to turn on a dime when Windows 10 EOL comes in October 2025. Taking Windows7 as a case in point, that tide didn’t really turn until 2-3 years after its EOL came along. And in the interim, a lot of customers (especially the US DoD and other government agencies) paid big for “extended support” to keep Windows 7 alive and secure while the migration got underway.

Could it be that MS wants to make the productivity advantages of Copilot available to its largest user base? Definitely. Could they recognize that it is likely to stay in the lead position until 2027. Absolutely. Could this move lower the impetus to migrate, or does it simply acknowledge the most likely outcome in the marketplace? You tell me!


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

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!



Start11 v2 Familiarization Blivets

Among lots of other stuff, I just learned that there are many, many more whimsical definitions for the word “blivet” than I ever imagined. Check out this Google Search to see what I mean. The term popped up in connection to several annoying, ridiculous and useless (or at least, unintelligible) things that just happened to me while working further with Stardock’s mostly terrrific Start 11 utility. I call them Start11 v2 familiarization blivets because they popped up as I continue to work with and get to know this program’s latest incarnation. Let me explain…

Enumerating Start11 v2 Familiarization Blivets

Here are two blivets I’ve just run into:

1. Search for Start11 in the Windows Start menu, and multiple hits appear. One of them is Start11 v2, another is Start11. I had to screw around a bunch to figure out that Start11 is right entry to select to launch the Start11 v2 controls. The only way you can do the latter, actually, is to “Run as administrator” (and it only works sometimes). Suggestion to Stardock: drop the other entries and stick with only Start11. This was both frustrating and vexing, and non-obvious.

2. Start11 v2 does indeed offer rounded corners on the taskbar. But you must first enter its Taskbar controls, turn that rounding feature on (Under the “Advanced rounded taskbar settings” heading), then restart. After that, there ’tis — but only on local displays. Doesn’t show up in a Remote Desktop (Connection) window. Suggestion to Stardock: see if this is indeed a remote access phenomenon. I see only square taskbar corners in Remote Desktop Connection. Using the Remote Desktop app, I may see rounded taskbar corners in a less-than-full-screen view, but they’re squared off in full screen view. I really can’t tell if they’re working or not…

And That’s the Thing About Blivets

They’re just mostly annoying and somewhat outside normal expectations. I still like Start11 (even the v2) version. I just have to vent when things get a little odd or annoying. And is that ever the way things must go in Windows-World, particularly when dealing with beta, new, and/or preview software. What fun!


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!


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!


Key Combo Kills Screen Toggle

I’ve been here too many times before. Part of my morning routine is a the daily challenge at the Microsoft Solitaire Connection. Occasionally my right hand screen (my playing field, so to speak) will flicker on and off while I’m playing. If it persists more than a few times, I know I need a fix. Over time, Ive learned that a certain key combo kills screen toggle (on-off) effects. For the record that combo is WinKey+Ctrl+Shift+B. Sometimes it works, sometimes it doesn’t. This morning, it did the trick quite nicely.

Which Key Combo Kills Screen Toggle?

Interestingly enough, Mayank Parmar wrote a story about the Winkey+Ctrl+Shift+B key combo at Windows Latest this morning. I suppose since I was running Windows 10 (not 11 as in the title of that item) I should observe that this trick works there, too. In fact, as he reports there correctly, this combo has been part of Windows since Vista made the scene in 2006.

I’ve been in situations like the one I described above (e.g playing MS Solitaire and the screen starts blinking on and off) when the key combo does NOT fix things. Oddly enough when that has happened in the past, it’s been readily rectified by running GeForce Experience to determine that a new graphics driver is available. And so far, when those two things are true (screen is toggling; new driver is ready to download) switching from the old to a new driver has fixed the problem.

For More Serious Graphics Issues…

If neither the WinKey+Ctrl+Shift+B combo, nor a new driver, fixes things life suddenly gets more interesting. Trying the driver version prior to the one that was running will sometimes work (and sometimes not). After that, it usually requires checking the GPU and making sure it’s seated properly, checking and possibly swapping graphics cables from GPU to monitor, and checking the monitor itself. On a laptop that all happens internally (and for many folks, may require a trip to the repair shop or an OEM depot).

For all our sakes, I hope things don’t go that far if the display starts acting a little flaky. FWIW, the key combo almost always works for me. May it do the same for you!


Author, Editor, Expert Witness