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

WinTerm Customization Remembered & Repeated

Leave a comment

I’m closing setting up and tweaking my Lenovo loaner SFF PC , just the way I like it. Indeed, I plan to switch my production desktop over from the 2016 vintage Skylake i7 I now use.Instead I’ll go with an uber-powerful ThinkStation P3 Ultra. It’s equipped with a 13th-Gen i9-13900, 64 GB RAM, Nvidia RTX A2000 12 GB, and a Hynix 2TB Gen 4 SSD. As a near-final step, I am fumbling through WinTerm customization remembered & repeated. You can see what I mean in the lead-in graphic…

Digging Thru WinTerm Customization Remembered & Repeated

It took four steps to get all the pieces lined up to customize my Windows Terminal as you see it in the graphic:

  1. Install Jan DeDobbeleer’s OhMyPosh for a custom prompt. That also required creating a $Profile file for startup. There are plenty of good how-tos around on this. I’m sad to report, however, that TekkiGurus.com is off the air. And thus, my series on this subject, too — find it instead on the WayBack Machine.
  2. Download and install the CaskaydiaCove Nerd Font (which I grabbed from NerdFonts.com) so that OhMyPosh can do its fancy thing with Windows Terminal prompt characters and environment variables. Handy now that drag-n-drop font install works inside Settings > Personalization > Fonts.
  3. Grabbed one of my favorite MS SpotLight images and then dimmed it up (30% opacity or thereabouts) to use as the Windows Terminal background. Dare I say I find it fetching?
  4. Ran the command Install-script WinFetch inside WinTerm to visit the script archive and install the eye candy that this displays about target systems when run.

Looks pretty good, doesn’t it? I’ve learned to expect and appreciate a bit of Windows Terminal pizazz to keep my eyeballs entertained while working at the command line.

And there you have it. Just another day in the paradise known to some as Windows-World. Good stuff!

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

Ongoing Win11 DISM WinSxS Cleanup Issues

Leave a comment

I’ve been writing about this since late 2021 or early 2022 — within months of the initial preview release for Windows 11. Something in the update environment produces ongoing Win11 DISM WinSxS cleanup issues. That is, running /analyzecomponentstore keeps popping up reclaimable packages even after /startcomponentcleanup reports cleanup success. Right now, I see this in almost every version of Windows 11 I have running, which includes:

  • Windows 11 23H2 Production (Build 22635.4435: 13 items)
  • Windows 11 24H2 Production (Build 26100.2161: 2 items)
  • Windows 11 Beta Channel (Build 222635.4435: 13 items)
  • Windows 11 Canary Channel (Build 277729.1000: 0 items)
  • Windows 11 24H2 Copilot+ PCs (26100.2033:  2 items)

You can see this at work in the lead-in graphic. Notice the initial reclaimables count is 16 at the top of that screencap.  After running cleanup, then analyzing again,  that count drops to lucky 13 instead of zero as one might expect. (Note: you may need to right-click the image and open it in its own tab to see that 13 value.) I’ve seen that count as high as 14 and as low as 1 or 2 in various Windows 11 builds over the past 3 years.

Fixing Ongoing Win11 DISM WinSxS Cleanup Issues

As Windows 11 issues go, this one is quite benign. I’m pretty sure that’s why it has been allowed to pop in and out of various Windows versions pretty much since the get-go. That said, one can fix this if one must (and you OCD types know who I mean). How do I know? I’ve done it myself…

You can perform an in-place upgrade repair install to make this issue go away. But it takes time (30 minutes  and counting on my Windows 11 PCs) and the issue keeps coming back after you apply upcoming Cumulative Updates. That’s why I don’t bother with fixing this myself (except when I need pristine screencaps for writing work) anymore. If you must zero this out, use Settings > System > Recovery, then click the “Reinstall now” button under the “Fix problems using Windows Update” heading. Easy-peasey!

There is a spot of forward-looking cheer, too. The current Canary Channel build (277729.1000) does NOT have this issue. Maybe when production catches up that far, it won’t continue. Fingers crossed…

 

Facebooklinkedin
Facebooklinkedin
Benchmarking, Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

Strange Yoga Slim 7 USB4 Behavior

Leave a comment

Seems like I’ve been messing about more than usual with USB ports of late. That’s why an apparent anomaly on my latest Copilot+ PC review unit — the Intel-based Yoga Slim 7i Aura Edition (15ILL9) — didn’t phase me for long. It delivered mSATA-level CrystalDiskMark results for a known, good, working Konyead USB4 NVMe enclosure. That is, when plugged into the right-side USB-C port. In the left-side port, its outputs ran somewhat under what I originally expected. What gives, you might ask? I’ll make some educated guesses…

More details on Strange Yoga Slim 7 USB4 Behavior

Even the Port 1 (left side) results weren’t fabulous for a USB4 NVMe device, but they’re within the realm of the expected. Here’s where things get interesting though: when I unplugged the enclosure from the left side, and plugged it into the right, the next set was much closer to expectations (and those recorded from the other side). The lead-in graphic shows left-side and right-side CrystalDiskMark results, each where you’d expect them per that ordering. Again I ask: what gives?

I can’t say with certainty, but I can guess with reasonable confidence that the device did not get properly detected the first time I plugged it in. The top 2 rows of CDM values were under 1K at left, and under 200 at right. The bottom 2 rows show random access to 4K segments, and seldom differ much across 5, 10 and 40 Gbps ports.

I do find the write values uniformly disappointing and significantly slower than what I’ve seen from Snapdragon X-based Copilot+ PCs. Could it be that Intel — the co-inventor and a major manufacturer of USB4/Thunderbolt 4 USB-C port controllers — isn’t as good at this as Qualcomm? Perish the thought. I’m thinking it may just be a lesser-grade part that’s not as fast as its Qualcomm counterpart.

Indeed, a quick jump into Settings > Bluetooth & devices > USB > USB4 hubs and devices lists the external NVMe as “Intel – USB4.0 SSD” and bandwidth as “40 Gbps/40Gbps (Gen 3, dual lane).” That’s exactly what it should be. So any performance differences seeming come from the parts themselves.

When in Doubt, Try a Different Device…

Just for grins I tried a different NVMe enclosure and SSD in the right-side port, then ran CrystalDiskMark again. Results initially came in nearly identical. As CDM continued through its read sequence, so did that similarity. Ditto for the write side of things with some slight improvements in the top 2 rows. I can only suggest that Qualcomm USB4 ports and controllers offer more balanced read/write performance than their Intel counterparts and better overall throughput. Isn’t that a surprise!

For those users who need max performance from external USB media, these differences might be worth considering as part of a purchase decision. Others are neither likely to notice, nor care.

 

Facebooklinkedin
Facebooklinkedin
Insider stuff, Recent Activity, Remote Desktop (RDP), WED Blog, Windows 10, Windows 11

Possible RDP Session Startup Delay Fix

Leave a comment

I have numerous PCs in my office right now, and a couple more elsewhere in the house. My usual modus operandi is to work from my primary desktop, and use Remote Desktop Connection (and the RDP protocol) to jump onto and work with those other machines. I do this dozens of times daily, as I check various Windows versions, VMs, and more. At least 1 time out of 4, when I start up an RDP connection it sits on the remote PC’s lock screen for some time (minutes, even). Only recently have I researched this, and come up with a possible RDP session startup delay fix. You can see it in the unchecked box at lower left in the lead-in graphic: persistent bitmap cache.

What Is This Possible RDP Session Startup Delay Fix?

Another workaround is to close the opening session, then open it again. This almost always works. But in reading over a set of possible fixes in an April 2024 TheWindowsClub story on this very topic, I came across one I’d neither heard of before, nor tried. So, of course, I tried it: it involves unchecking the “Persistent bitmap caching” entry on the expanded Remote Desktop Connection app’s Experience tab as shown above.

I tried that on a couple of PCs that were showing significant delays in starting RDP sessions just now. And guess what? After that tweak, they opened right up. I’m guessing the delay might come from loading the cache at session startup, which the app uses to speed reproduction of already-known (and cached) screens. So it’s gonna be a tradeoff: faster startup at first, but slower response when screens need to move across the network that would otherwise already be stored.

I’m not sure it’s a total win, but it’s interesting to try such things out and see how they work for you. To me that’s the essence of getting things right in Windows-World — namely finding and using the right controls, to do what you need in a way that you can live with.

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

24H2 Gets WU Boost

Leave a comment

Here’s something quite interesting. Yesterday, MS published a Windows IT Pro blog post entitled Windows 11, 24H2 improved update fundamentals. It’s worth reading, and makes claims for faster installs and restarts, lower CPU consumption, and smaller update packages in the latest OS version. Today, WindowsLatest  offered some data to back that up, showing that indeed 24H2 gets WU boost going forward. Its findings are interesting, too.

What 24H2 Gets WU Boost Apparently Means

As you can see in the lead-in graphic, WindowsLatest compared results for 2 PCs: one running Windows 23H2 was updated to 24H2 using the March update (it appears as “Well-maintained device”); the other was running 22H2 and had the same 24H2 update applied (it appears as “Outdated Device (18 months)”). In both cases, the numbers are noteworthy, and accord with my own recent experience in installing or updating Windows 23H2 PCs to 24H2 as well.

CPU utilization goes down by around 15% for newer Windows images, and by up to 25% when transitioning from 22H2 to 24H2. Restart times speed up by one-third or more, and installation by 40% or more. Download size also drops by 200 MB, thanks mostly to omitting MS Store app updates from that download package.

The Need for Speed…

This is good news in general for all Windows 11 users. But it’s especially good news for IT pros who typically handle fleet upgrades in time-constrained update windows. Often these fall on holiday weekends to make sure there’s enough time to get through the cycle (and fix any gotchas that pop up along the way, as they sometimes do). Anything MS can do to speed the time it takes to physically process updates also helps shorten the time window necessary to do them at scale. Thus, it’s a nice case of good news all the way around.

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, Thoughts & concerns, WED Blog

Snapdragon X DevKit Is Cancelled

Leave a comment

In hindsight, it’s no surprise. I signed up — and paid ~US$975 (including sales tax) — for the Qualcomm Copilot+ PC package they offered to the public in mid-July. Initial ship date was late August. Then, it slipped to late September. Finally, it was promised for mid-January, 2025. That’s when I asked kitmaker OEM (Arrow Electronics) for a refund. Last week, Qualcomm sent email  cancelling the project and refunding all orders. Ouch: the Snapdragon X DevKit is cancelled. Over. Kaput. No refund yet, either.

Why Snapdragon X DevKit Is Cancelled

For more info, read this October 18 Windows Central story Qualcomm cancels Snapdragon X Elite devkit… In an email, Qualcomm said the kit failed its “usual standards of excellence.” It cancelled the project and promised refunds for all. But gosh: they used my money and that of thousands of other would-be kit buyers for a long, long time before they killed the golden goose.

I’m not just disappointed that my planned purchase evaporated. It’s frustrating that they waited so long to cancel. I’m also ticked off that they’re still holding my money. When I cancelled my order on October 11 (see this X (Tweet) item), they promised a refund in 10 days. That’s today, generously allowing an extra day for order database updates. It’s not yet the end of the day, so it still might show up. But it hasn’t hit PayPal yet, as I write this.

I’m not holding my breath. I’m not happy, either. But that’s the way things go for those who, like me, want to stay on the edge and buy into emerging computing platforms and technologies. In the meantime, life goes on here in Windows-World, one day at a time. Sigh again…

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows Update

WU Throws First 24H2 Offer

Leave a comment

OK: I admit it. I already had 4 PCs running 24H2. Two are Copilot+ laptops (Lenovo ThinkPad T14s Gen 6 and Yoga Slim 7 15ILL9) and came that way. Two others were force-upgraded: the Ryzen 5800x desktop via in-place ISO-based upgrade, and the Lenovo ThinkPad P16 Gen 1 via the Windows 11 Installation Assistant. Last Friday, I saw the Dell D7080 SFF PC had received (and downloaded) the latest release on its own. That’s right: here at Chez Tittel, WU throws first 24H2 offer. It’s done and dusted now, in fact…

Success When WU Throws First 24H2 Offer

As you can see in the lead-in graphic, I didn’t even catch the notification until the target was already through the GUI-based portion of the install. Indeed, the D7080 informed me it needed a reboot to continue that process. Once allowed to proceed, in fact, it finished up in under 15 minutes (it’s an 11th Gen i7 with 64GB RAM and a reasonably fast SSD so it moved along right smartly). It’s now upgraded and running Build 26100.2033, and WU says it’s up-to-date.

Just for grins I checked my other production level Windows 11 machines, but both of them are still standing pat with 23H2 — namely:

  • Lenovo ThinkPad X1 Extreme (8th Gen i7)
  • Lenovo P360Ultra SFF PC (13th Gen i9)

I’m guessing they’re either subject to the Intel Audio hold (X1) or the well-known Gen13/14 issues with 24H2. I’m going to keep watching and will report when and as those holds lift, and WU extends further offers. But gosh: it’s nice to see things working as they oughter, here in Windows-World. Cheers!

Facebooklinkedin
Facebooklinkedin
Insider stuff, Microsoft 365, Recent Activity, Troubleshooting, WED Blog

MX Error Provokes Outlook Account Fix

Leave a comment

Ever since Microsoft pushed an Outlook update in late September, Outlook hasn’t let me access my primary email account. Something about handling of DNS info related to mailservers changed, and not for the better. Simply put, the configuration I’d been using to ingest incoming email and send outgoing email quit working. But when I checked the dreamhost config recommendations, everything agreed with same.  Despite repeated fix attempts, account setup kept foundering because of a reset to some whacko domain I never heard or read about –namely: smtp. mailchannels.net. This morning I had an astonishingly positive encounter with Microsoft 365 chat support, during which an MX error provokes Outlook account fix. Buckle up: this is going to take some explaining…

How an MX Error Provokes Outlook Account Fix

Outlook is obviously reading from MX records for the domain names it runs into. The only way I can get my home account (the one for this very website, in fact) to work is by over-riding both incoming and outgoing mail server values that the lookup process finds on its own.

It gets worse. If I tell Outlook to repair itself, it overwrites my over-rides with those selfsame values again. Fortunately, I’ve now got all this stuff memorized and I know how to fix it. But it wasn’t until we tried and failed to use my domain name (edtittel.com) for the mail servers that the inbuilt Outlook facility started reading the right MX records. Only then was I able to use those for the email host instead of whatever Outlook was dredging out of the MX records it finds on my behalf. Sigh.

Automation Had Best Be Correct…

I understand that MS is just trying to help by automating the mail server lookups and name assignments. That’s terrif, as long as they get those lookups right. But as I’ve just learned, over-riding errors in such lookups can get excessively interesting.

Shoot! I couldn’t even get email to work in Outlook until I figured out I should ignore its findings and insist on what the provider’s configuration page told me I should use. What’s interesting is that’s what was in there in the first place, and quit working late last month. I wasn’t able to get back into the fold, however, until I tried my own domain name, at which point the error trail finally located workable MX records.

Go figure! That’s what keeps me on the edge of my seat, and makes Windows-World an always-interesting place to work and live.

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

Intel’s Initial Copilot+ Salvo

Leave a comment

OK, then. As I was gearing up for medical adventures on Tuesday, Lenovo shipped me a new Copilot+ PC. Because I apparently munged my initial login, I wasn’t able to upgrade from Windows 11 Home to Pro at first. A factory reset (described in yesterday’s blog) set things right, and I’m now digging in to see and understand what I can about this Yoga Slim 7 15ILL9 unit. So far, Intel’s initial Copilot+ Salvo seems a little less bodacious than the Snapdragon X ThinkPad T14s Gen 6 I’m getting ready to send back to the reviews team. Let me explain…

Absorbing and Interpreting Intel’s Initial Copilot+ Salvo

We’ll start with the port map (side views) of the Lenovo Yoga Slim 7 15ILL9. You can see it sports 2 TB4/USB4 ports — one on each side — along with a power button, camera shutter, and USB Type A 5 Gbps, plus HDMI and 3.5mm audio jack. Very basic, very simple.

Here’s a more detailed list of its various innards:

CPU: Intel Core Ultra 7 256V (8 cores/8 logical processors)
RAM: 16 GB LPDDR5x-8533 (2 modules, soldered)
SSD: WD SN740 1TB (NVMe PCIe Gen4 x4; M.2 2242)
Integrated Intel Arc Graphics 140V
Display: 15.3″ 2880×1800 Touch screen
NPU Capacity: 45 TOPS

As configured, it costs US$1,322 at the Lenovo Store. Thus, this is clearly a consumer oriented mid-range laptop. This explains why it isn’t as full featured or snappy as the T14s I’m sending back (it doubled up RAM and offered a 12-core CPU, but lists for US$1,700).

Sorry About the Bloatware…

Unlike most other new Lenovo PCs and laptops I’ve encountered lately, this one comes a bit more laden with bloatware, including:

  • Numerous Lenovo helpware items: Hotkeys, Now, Vantage, and Vantage Service (I usually keep Hotkeys and Vantage)
  • McAfee Trialware: removed
  • WebAdvisor by McAfee: removed

Initial startup also flogged numerous subscriptions including YouTube and other video items, Amazon MusicDropBox 100 TB, and special offers (that’s what Lenovo Now delivers, I’m removing it). I’d rather see this kind of thing as opt-in if I have to see it at all. Thankfully, that’s how Lenovo handled it. If flogging is required, it should be easy to circumvent.

Initial Take on the Yoga Slim 7 15ILL9 Itself

The unit offers a bright, clear display with snappy graphics and handling. By default brightness was set to 13: I had to bump it up to 60-something to see things properly. It’s pretty lightweight, too (1.53kg/3.38lbs) despite the over 15″ display with narrow bezels. The all-aluminum case in gray is sturdy and attractive enough, but not in the same league as the ThinkPad. Wi-Fi7 (Intel BE201 320 MHz) is included in all configurations, too. Chez Tittel is still on 802.11ax, though…

Overall, I like the Snapdragon Yoga Slim 7X  better than this Intel model, but that’s mostly because its OLED monitor pops like crazy. I do think the 12 cores in the Snapdragon X somewhat outperform the Ultra Core 7 256V’s 8 cores, but that could be subjective. I’ll be digging deeper into SSD and USB4 port performance in the future, but so far this offering seems like a pretty good value. See this October 12 NoteBookCheck story for more details on this nice little notebook.

Facebooklinkedin
Facebooklinkedin
Copilot+ PCs, Insider stuff, Recent Activity, WED Blog, Windows 11

Upgrading Home to Pro Proves Challenging

Leave a comment

OK, then. It’s been a busy week, but not all work-related. I had a lens replacement (cataract surgery) in my right eye yesterday. Perforce that meant a day off. In the meantime, I’ve been involved in intake on a new Copilot+ PC: an Intel Model this time. It’s a Yoga Slim 7 15ILL9. And indeed, for this PC upgrading Home to Prove proves challenging. I had to perform a factory reset on the PC to get it to work. Let me explain…

Why Upgrading Home to Pro Proves Challenging

Simply put, when I tried to upgrade from Home to Pro, none of the keys I tried would work. In fact, not even an attempt to purchase one from the MS Store did the trick, either. That’s when I knew something with my login wasn’t copascetic. So I used the System > Reset > Recovery > Reset this PC option to restore the OS to its “fresh from the factory” reset state.

This time, when I logged in I duly furnished an MSA into which my login account could be tied. And guess what: that did the trick! I was able to run updates (they hadn’t worked either) and then used a one-time key from Visual Studio Subscriptions (Thanks, MVP Program!) to upgrade from Home to Pro. I’m now logged into the new test PC via RDP which is how I like to interact with my test/review machines.

Introducing the Yoga Slim 7 15ILL9

It’s got an Intel Core Ultra 7 256V, 16 GB RAM, 1 TB NVMe SSD, with something new to me: integrated Arc Graphics 140V. Compared to the Snapdragon X ThinkPad T14s I’m getting ready to return to Lenovo, it’s got 8 cores (instead of 12), half the RAM, and a different CPU architecture (x64 vs. ARM64). But so far, it seems to run reasonably well. It got through the Home to Pro upgrade in under 5 minutes, handled WU updates with alacrity, and chuffed through a dozen items via PatchMyPC Home updater in under 2 minutes. So far, so good.

Now that I’ve got the device set up on my network, I can start putting it through its paces. Stay tuned as I start understanding how Intel based Copilot+ PCs compare to their Snapdragon X counterparts. Should be interesting…

 

Facebooklinkedin
Facebooklinkedin

Author, Editor, Expert Witness