Category Archives: Windows 11

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

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!

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

WU Finally Proffers 23H2

OK, then. The wait is over — for the Ryzen 5800X system anywho. I just checked WU on that machine and got an offer. Now that WU finally proffers 23H2 on that system, it’s kind of an anticlimax. Took less than 3 minutes to download and install, reboot and everything.

As WU Finally Proffers 23H2, I Install It!

I’ve been deliberately waiting on this offer, to see how long it would take for WU to make it happen. Now I know: this time, it took 9 days after the original info came out for WU to come knocking at my door. One wonders, sometimes, how these things happen. I’m just glad the new release is finally arriving through “official channels.”

On my “big beast” test PCs — most notably, the P16 and P1 Gen 6 Mobile Workstation Thinkpads — I wasn’t inclined to wait. I simply grabbed the MSU file that Shawn Brink posted at ElevenForum.com, and had at it right away. I could be patient where the Asrock B550 (Ryzen 5800X, 64 GB RAM, 1 TB SSD) and Dell Optiplex 7080 (11th-gen i7, 32GB RAM, 1 TB SSD) were concerned.

So, whatever the holdup may have been, it came off sometime in the last 24 hours (I last checked these PCs in the morning yesterday, so it could be more like 30 hours, but no more). And now, things are upgraded.

Known Issues Sez…

I’d wondered if the BitLocker or Intel Smart Sound Technology issues on the Known Issues list might have been involved. I see they’ve both been “Mitigated.” But neither has been updated since October 31. So neither is an obvious culprit for the hold on those two PCs, either.

Sigh: I may never know what slowed the offer, or what eventually made it come through. Can I live with that? Heck, yeah! That just the way things sometimes go, here in Windows-World. By now, I’m used to it…

 

 

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

Start11 v2 Face-Up

I have to laugh. It’s something along Godfather III lines. I’d recently concluded I don’t need Start11 any more because I’m completely at home in the native Start menu. So I’m out. Then, Stardock introduces Start11 v2 — a completely new version for which users must pay to upgrade. Reading about its cool new features, they pull me back in. The lead-in screencap conveys its coolness quite nicely.

Look Top Right: See Start11 v2 Face-Up (Mine!)

Simply put, Start11 v2 lets the built-in Start menu shine through. But it provides all kinds of extras that it can’t do, too. Let’s start with my smiling face up top in the extra right-hand panel. Below, there’s  one-click access the old Library items (Documents, Downloads, etc.). But also my User folder root, Control Panel, Settings, the Run box and This PC in File Explorer (shows as “Computer” at bottom for what I guess are historical reasons).

You can choose from a palette of start menu looks and layouts. Mine is called Windows Pro Style as you can see in the next screencap:

Start11 v2 Face-Up.startstyles

7 start menu styles, many with controls for additional tweaks and twists.

In addition, Start11 v2 provides controls for the Start button itself (I like the Windows 11 logo), the taskbar and taskbar pins (including the ability to pin folders and folder menu pop-ups there), multiple search options and more. Because Start11 v2 accepts a multitude of tweaks, you can also save all that stuff (it’s called “Settings backup”) to a file, then restore and reset settings as you might like. If you have Voidtools Everything installed (part of my basic Windows toolkit), when you search inside the Start11 search facility its results are what come back to you in return. Great stuff!!!

Just When I Thought I Was Out…

Stardock comes along with a truly great uprade to its old stalwart Start menu replacement tool. But I guess we should call it a Start menu enhancement tool these days, eh? Because it was so cheap I sprung for the 5-pack. At under US$13 ($2.60 per instance) it’s too good a deal to pass up — especially against a US$5.99 single copy price.

Historical note: I got into Stardock’s start menu tools with Start8. I cheerfully confess to having been totally befuddled and put off when the “new, redesigned” native Start menu appeared in that OS. I’ve been a pretty loyal user ever since (including Start10). In a “let’s keep a good thing going” kind of way, I’m actually glad to have a reason to WANT to buy into Start11 v2. It had become mostly optional on my 10 or so Windows 11 PCs, tablets and notebooks.

Facebooklinkedin
Facebooklinkedin

Attaining Windows 11 23H2

In everything but name, I’ve already been running Windows 11 23H2 for a while. That level of functionality has been trickling into Windows 11 since September 11 with the release of KB5030310 (a preview update). A few days ago, the release of KB5031455 took Windows 11 to Build 22621.2506. Note the version and build numbers in the lead-in graphic. They support my assertion that there’s little difference between the two.

Steps to  Attaining Windows 11 23H2

Over at ElevenForum.com I’ve been reading about various ways to get to 23H2 in its Installation, Updates and Activation forum for the past few weeks. None of the easy methods outlined there did the trick for me. I wasn’t motivated enough to try the longer, harder ones — e.g. an in-place repair install using the recently published Windows 11 23H2 ISO (it’s now present on the Download Windows 11 page). Why not? I knew an enablement package for 23H2 was coming soon. (Note: for those not already hip, an enablement package is a small, quick update that simply turns on features and stuff already present in Windows but not yet visible or active.)

Today (or more precisely, yesterday) that changed with the release of KB5027397. It describes that very enablement package, and announces its availability. I’ve not been able to get WU to proffer it to me (though I did have pre-requisite KB5031455 already installed). Instead I grabbed the MSU link from ElevenForum admin @Brink (real name: Shawn Brink, a fellow WIMVP). It comes from an October 31 thread entitled KB5027397 Enablement Package for Windows 11 version 23H2 Feature Update.

It’s a ZIP file, so must be unpacked before it may be run. But run it does — and quickly, too: the whole shebang was done in under 2 minutes on my Lenovo ThinkPad P16 Mobile Workstation. After a reboot, the target PC should produce nearly the same winver information shown above. Note the “Version 23H2” moniker in the second line of the fine print. Nerdvana!

Facebooklinkedin
Facebooklinkedin

Beta Build 22635.2552 Adds System Components

I’ve known this was coming for some time now. Last month, I researched changes to the Windows Troubleshooters to a Get Help facility in Windows 11. Note: “Get Help” works for Windows 10, too. Indeed, it fell under a general heading of “System Components” as explained at MS Support. Thus it came with more of a sense of inevitability, not surprise, when Beta Build 22635.2552 adds System Components to its Settings → System subhead lineup. You can see that pretty clearly in the lead-in graphic, which has Winver superimposed to show Build info.

What Else Appears When Beta Build 22635.2552 Adds System Components?

If you look at the lead-in graphic you’ll notice the following list of elements under the System Components heading (in order of appearance):

  • Game Bar: former Xbox Game Bar app, now renamed to drop Xbox.
  • Get Help: Built in Windows troubleshooting facilities now runs as an app (and auto-launches when the OS itself spots trouble).
  • Microsoft Store: Primary source for Windows apps of all kinds.
  • Phone Link: Provides link and synch facilities between smartphones and Windows PCs (iOS and Android devices).
  • Tips: Built-in Windows notification, advertisement and “information” items.
  • Windows Security: Home to Defender’s AV, account protection, firewall & Internet controls, device security, health and family options.

Essentially this positions these specific apps as Windows built-ins that “come with the OS.” Thus, they can’t be uninstalled: inspection will show their Remove buttons are greyed out in Advanced Options. And although they can be terminated, from a runtime perspective, they’ll “keep coming back from the dead” in Halloween-appropriate fashion.

I find it interesting that MS lumps in Game Bar and Phone Link along with the other built-ins that comprise “system components.” It will also be instructive to watch this category to see when and if it expands, exactly what else appears under this heading. Stay tuned!

 

Facebooklinkedin
Facebooklinkedin

Experiment: Reset this PC

After digging further into Reliability Monitor on the P1 Gen6 ThinkPad, I realized things were unacceptably unstable. As an experiment, reset this PC came to the fore. It’s the option available as Settings → System → Recovery from the “Reset PC” button. The resulting window serves as the lead-in graphic for this story (above).

Why Conduct the Experiment: Reset this PC?

Alas, I had four straight days of error behavior like that shown in the next Reliability Monitor screencap. That is, over a dozen serious Critical events, including:

  • Windows stopped working (2)
  • Windows was not properly shut down (2)
  • Hardware error (2)
  • Windows shut down unexpectedly (2)
  • Various NVIDIA-related “Stopped working” errors (4)

Experiment: Reset this PC (ReliMon)

Whoa! That’s a lot of Critical errors for one day…and I had 3 more just like it. [Click image for full-sized view]

In addition, the OS install was showing other odd and unexpected behaviors. For example, I couldn’t get the Edge browser to run. The display was occasionally flashing on and off (probably related to the NVIDIA errors shown). File Explorer was herky-jerkey when traversing the file system. There was probably more, but that was more than enough for me to realize something wicked had already come onto that desktop. Hence, the reset experiment…

Since performing the reset, I’ve experienced exactly one (1) critical error over the past 24 hours. It may still be too early to tell if the reset really fixed things. It might just be having left this PC alone for the last while that’s kept things quiet.

Going through the Reset Process

It seems like Reset is an awful lot like an in-place upgrade repair install, except that it wants the end user to reinstall apps and applications one at a time (each had an “Install” entry in the Start menu/All apps after the first reboot). I’m too lazy to do one-offs like that, so I used the bulk installer built into PatchMyPC Home Updater instead. Works like a peach! Alternatively, I could have done most of those installs using winget instead.

I wasn’t sure if the reset function would take the PC back to its fresh-from-the-factory state. No, it didn’t: it simply reinstalled — via a cloud download — the same version of DevChannel Insider Preview already running on this test PC. Good to know!

Stay tuned: I’ll report back if the earlier instability persists. I had attributed it to an Intel firmware update. I’ll end up poking it one way or another over the next days and see if it blows up again.

 

Facebooklinkedin
Facebooklinkedin

New GSOD Implicates Intel Firmware

Here’s something nobody wants to see on a Windows PC. The lead-in graphic shows a Windows crash screen. Because this one is green, it’s sometimes called a GSOD (“Green Screen of Death”). The error message it carries is one I’ve not seen before — namely: secure_pci_config_space_access_violation. A bit of online research, and some inspection of reliability monitor’s copious error output tells me this new GSOD implicates Intel firmware.

Why Say: New GSOD Implicates Intel Firmware?

It’s not like I didn’t have plenty of potential issues from which to choose. Relimon pointed to Windows stop errors, improper shutdowns, unexepected shutdowns, and hardware errors. Indeed the actual BlueScreen error that provoked the GSOD refers to (and depicts) a CPU-Z .sys file. So again: why point at Intel firmware?

Online research (Reddit, Lenovo forums, and more) all report this very same error code after Intel firmware updates. And indeed WU itself delivered a — you guessed it — Intel Firmware update just before I upgraded to the most recent version of the DevChannel Insider Preview on this test PC.

One More Thing:

After I removed the program that caused the GSOD: Piriform Speccy, the problems have completely ceased and desisted. I imagine this program attempted to check the firmware during its scans, and that’s what threw the error. I’m guessing that a fix will come along in a future update. As long as my system stays stable otherwise, I’ll leave it alone and hope it does the same for me.

Stay tuned: I’ll keep you posted…

Facebooklinkedin
Facebooklinkedin