Category Archives: Windows 10

SFF Upgrade Opportunities Maximize Value

Last October, I wrote a review of a tiny and terrific SFF PC entitled “P360 Ultra Is Beautiful Inside.” This morning, I’ve been thinking about that review while reading about best of breed small form-factor (SFF) PCs across a broad range of vendors. My conclusion: SFF upgrade opportunities maximize value in a chassis that’s easy to open, access and upgrade. Let me explain…

Buy Low-end So SFF Upgrade Opportunities Maximize Value

In the P360 Ultra, for those who aren’t disinclined to swap out parts, I suggest purchasing a model with the highest-end CPU one can afford (the CPU is not listed as a field-replaceable unit, or FRU — see Manual). Then, one can hold the initial cost down by purchasing minimal memory and storage, and swapping out components purchased separately.

Thus, for example, a minimally configured unit with i7-12700K CPU costs ~US$1,500, while one with an i9-12900 goes for US$1,675. This comes with built-in GPU, 8 GB RAM, and a 512 GB PCIe X4 SSD. Generally, you can purchase additional memory and storage for less than half what the vendor charges (e.g. Amazon sells compatible 2 x 32 GB memory modules for US$260-280, where Lenovo charges US$700). Similarly, you can purchase an excellent 2 TB top-of-the line SSD from Newegg for about US$229, where Lenovo charges US$30 more for a “high-performance” 1 TB SSD.

Things Get Dicier with Graphics Cards

The P360 Ultra uses a special, compact interface to host graphics cards such as the Nvidia T400 4 GB GDDR6, the Nvidia RTX A2000 12 GB GDDR6, and Nvidia RTX A5000 mobile 16GB GDDR6. You can buy the first two of these three on the open market (I can’t find the mobile version of the third for sale anywhere). Lenovo sells the T400 more cheaply than I can find it online, and you may be able to save a little on the A2000 on the open market.

All this said, buying down and self-upgrading remains a good way to buy into an SFF machine. You can decide how much oomph you want to add vs. how much you want to spend, and save vis-a-vis preinstalled prices. Think about it for upcoming desktop/workstation purchases, please.

Facebooklinkedin
Facebooklinkedin

Visual Studio Build Tools 2017 Mystery Masticated

This was a weird one. The lead-in graphic shows that although I plainly installed version 15.9.51 of the Visual Studio Tools 2017, it reports in as version 15.8.9. No amount of uninstall/reinstall (aka R&R for “remove & replace”) made any difference. I finally solved my Visual Studio Build Tools 2017 mystery by installing the latest version of Visual Studio Enterprise. (That came free, thanks to my WIMVP privileges and its attendant VS subscription.)

Workaround Solves Visual Studio Build Tools 2017 Mystery

Take another look at the lead-in screencap. It shows me uninstalling version 15.8.9 using Winget. Then I force-install version 15.9.51 explicitly. But even so, Winget list still reports version 15.8.9 as clear and present. Sigh.

Thus, I resorted to a total workaround. Because I have access to a VS subscription — thanks to my 2022 WIMVP status (I’ll be finding out next week if it gets extended for 2023) — I installed a full-blown VS version. This was enough to kill the VS.2017.BuildTools update messages in Winget (at least, after I uninstalled same).

What Gives?

Because I can’t find any definitive explanation, I can only speculate. I’m guessing it’s either (a) a  mistaken version tag  for what is really version 15.9.51 or (b) a unreported install failure that leaves the Build Tools at version 15.8.9. Whatever that case might be, I switched from the free version to the for-a-fee version. That made my apparent problems disappear. I’m grateful!

Sometimes, solving Windows problems requires resorting to creative workarounds. I would definitely include today’s odd situation, and its equally odd solution, in that category.

Happy New Year 2023 to one and all. May the coming year bring you joy, prosperity, good health and plenty of interesting Windows issues to solve (or read about here). Best wishes!

 

Facebooklinkedin
Facebooklinkedin

Remote Wi-Fi Driver Update Magic

I remember the networking wars of the late 1980s. That was when Token Ring, ARCnet, LocalTalk and other physical media vied with Ethernet for market- and mindshare. Indeed, I’ve worked with versions of Ethernet all the way back to 10Base2 and 10Base5. Thus, I successfully upgraded the Wi-Fi drivers on my 2018 vintage Lenovo ThinkPad X1 Extreme (running Windows 11) with bemusement and appreciation minutes ago. Based on how earlier Windows versions worked, there was surely some remote Wi-Fi driver update magic involved.

The lead-in graphic is the Intel installer pane that announces a successful Wi-Fi driver install. What’s interesting about this? It’s inside a Wi-Fi based RDP session. I’m working on my production PC via Remote Desktop Connection to the X1 Extreme. It restored itself automatically once the driver install finished. It came back up, even though the connection dropped as that update occurred. No working driver means no Wi-Fi during the switchover from old to new.

What Makes Remote Wi-Fi Driver Update Magic Happen?

Good question! RDP apparently recognizes enough about the dropped session to bring it back to life. And FWIW, that occurs during the first “retry” — by default, RDP attempts resuscitation up to 5 times — without undue muss or fuss.

What makes this noteworthy? I can remember that even Windows 7 could not restore RDP sessions dropped during driver updates. Windows 8 (and 8.1) were hit or miss. It’s only since Windows 10 came along in 2015 (General Availability: 7/29/2015) that this capability has been both mainstream and dependable.

Once upon a time, Wi-Fi driver updates meant the end of open RDP sessions. Recovery was impossible: the only way back in was to fire Remote Desktop Connection up, and start afresh. It’s a small thing, really, but one I’ve learned to appreciate in modern Windows versions.

Thanks IEEE!

Modern Wi-Fi testifies to robust and practiced driver design. Indeed, it keeps working in the face of many predictable difficulties. Replacing drivers is a case in point, but Wi-Fi just keeps on chugging along. And that’s despite various source of interference, occasional hiccups with power, wireless gateways, and more. Having followed the technology as it’s grown and sped up I’m grateful it works well.

Facebooklinkedin
Facebooklinkedin

Windows 10 OCD Update Stymied

OK then: this morning I decided to check updates on my Windows 10 production desktop. Despite my December 19 contrary prediction, I found over 10 items that needed updates. But I saw my tendency to Windows 10 OCD update stymied by prior experience. Let me explain, first and foremost, that this means I updated what was either necessary or easy. I left the other stuff alone. Deets follow.

How Was Windows 10 OCD Update Stymied?

The list of items in need of update fell into two broad categories:

1. Items with automatic, built-in or easy update capabilities. These included: SUMO, Notepad++ and VS BuildTools (winget handled these automatically). Others included: Audacity, CPU-Z, GPU-Z, Intel ProSet and Zoom (these either include built-in updates, offer direct update links, or are easy to find online — e.g. ProSet).

2. Items I’ve learned not to mess with unnecessarily. These appear in the lead-in graphic above. SUMo likes to point me at versions of ASRock utilities (e.g. APP Shop) that don’t work with my 2016 vintage motherboard. Nitro Pro gets updated all the time, but the maker sends update notifications only when relevant security fixes are added. That’s not the case for going from version 13.67.0.45 to 12.709.2.40.

This gives me a nice delineation between what I can or must update, and what I can safely skip. Should some security issue pop up for Asrock App Shop, I’ll simply uninstall it: I don’t use it much anyway. And if a security fix comes along for Nitro Pro, the maker will notify me to upgrade and send a link.

Case Closed? OCD No More…

I wish I could claim that will never happen to me again. I have fallen prey to “It must be perfect” in the past. It could happen again in the future. I am hopeful that I can now tell the difference between what’s good enough and the perfect. I guess we’ll just have to wait and see.

Facebooklinkedin
Facebooklinkedin

Fixing WADK Upgrade Error 2008

Sometimes, strange things happen when using Winget (the built-in package manager in PowerShell). This morning, I got hit with an error when attempting to upgrade the Windows Assessment and Deployment Kit (aka WADK). This meant fixing WADK upgrade error 2008. Fortunately, I found a helpful GitHub post that explained how to overcome this issue.

Note: the lead-in graphic shows Winget commands to compare local ADK versions (in the list and show sub-commands) to the most current known ADK package (in the search sub-command).

Steps Toward Fixing WADK Upgrade Error 2008

Turns out the tried-and-true technique for fixing the upgrade error works here, too. First: uninstall the current version. Then, download and re-install that version (see this MS Learn article for that link). After that, all should work as it’s supposed to.

What’s interesting is the size and complexity of this environment. The adksetup.exe file is under 2MB in size, but it’s just a bootstrap loader. It brings in and sets up nearly 2GB of tools and supporting infrastructure. It also takes a while (about 5 minutes going and coming) to remove, then replace, that environment.

Once I worked through the maneuver, WADK no longer showed up in Winget. Nor did error 2008 recur, obviously.

When In Doubt, Remove/Replace Works Well

I’ve learned that when Winget gets wonky, there may be reasons connected to the runtime infrastructure at work in your Windows image. Often, the easiest way to clean that up is to remove the troubled package, reboot, then reinstall. This has bailed me out of difficulties on several occasions. That includes this morning’s encounter with the WADK.

If it works for me, it could work for you, too. As long as you have a fresh backup and can easily restore same, why not? I was covered today by my scheduled 9AM image, so I gave it a shot. It worked!

Going On (Brief) Hiatus

Let me take this opportunity to wish one and all the best possible end-of-year holiday. I’ll be silent here until Monday, December 26, as I take a break to spend time with family and friends. For those who celebrate the holiday: Merry Christmas! Otherwise, enjoy the break.

Facebooklinkedin
Facebooklinkedin

SSDs Versus HDDs Revisited

I just saw some pretty amazing sales prices on external 2TB SSDs at Neowin. I’m talking something in the neighborhood of US$120 -140 for something rated at 800 – 1,000 MBps. This has me thinking about SSDs versus HDDs revisited. Why? Because over the past 6 years, I’ve been moving steadily away from HDDs to increasingly fast and affordable SSDs. These prices kind of put a cap on the whole phenom, IMO.

SSDs Versus HDDs Revisited: Late 2022

I realized the value of compact, portable 2.5″ external drives in the first decade of this millenium, when laptops really took over business computing. I carried my first luggables far back as 1988. But compact, usable external storage for field use really didn’t catch on until small, USB-attached drives became practical in the wake of USB 2.0’s introduction in 2000.

Right now, I’ve still got 4 2.0 TB USB 3 HDDs (which I hardly use anymore: Seagate Firecudas purchased in 2016/2017). I’ve also got 2 5.0 TB Seagate BarraCudas purchased in 2018/2019. Those I still use. But the fact is, those drives all cost me more when I bought them than what you’ll pay for a 2TB Crucial X8 NVMe SSD on sale right now (pictured above). That shows the immense increase in storage density, and decrease in power needed to drive such storage in the recent past.

What Now, Storage Wise?

I’m getting ready to gift off all of my older 2 TB 2.5″ drives to the nice folks at Goodwill (my old friend, Ken Starks, has retired and shut down ReGlue.org). Except for very big 3.5″ drives (12 TB+) I don’t plan on buying any more HDDs, ever.

In fact, I’ve already moved onto NVMe-based USB drives, with USB 3.1/3.2 as my baseline, and USB4/ThunderBolt4 as my “stretch target.” The latter are still kinda expensive. I think it’s more than the current performance bump is worth, but that will change substantially in the next 12-18 months.

For the Record: The Speed Hierarchy

The following data is enough to convince me that portable USB-based NVMe storage is the right way to go nowadays. How ’bout you?

Type     Drive              Fastest R/W
HDD      FireCuda 2TB       ~61/71    MBps
HDD      BarraCuda 5TB     ~137/131   MBps
mSATA    Samsung 1TB       ~455/400   MBps
NVMe-3   Samsung 950 1TB   ~1060/1040 MBps
NVMe-4   Sabrent R4 1 TB   ~2820/1290 MBps

I just took all these measurements using CrystalDiskMark’s highest large-block read/write values (version 8.0.4.0). I know where I want to be on this performance ladder, especially for image backups (one of my primary reasons for using and carrying portable storage on the road). Again: how ’bout you?

Notes on the Test Rig

I ran the external drives via a Lenovo ThinkPad Universal Dock Pro (TB4-capable) through a TB4 connection into a Lenovo ThinkPad X12 Hybrid Tablet. FWIW, the NVMe-4 results are the best I’ve ever seen from an external drive. Nifty!

Facebooklinkedin
Facebooklinkedin

Observing EoY Windows Updates

I remember the old Morton salt motto: “When it rains, it pours.” Aside from providing an apt description for today’s weather in Central Texas, it also describes my reaction when running winget this morning. I find myself observing EoY Windows Updates (that’s short for “End of Year”). I’m thinking: lots of software makers are pushing updates now so they can take a holiday break, too.

Mucho Activity While Observing EoY Windows Updates

As you can see in the lead-in graphic — PowerShell snapshot — winget found 10 items in need of upgrade this morning. KC Software’s Software Update Monitor (SUMo) found an additional 10 over and above that number. Items included Zoom, CPU-Z, Ring Central, GeForce Experience, FileZilla, SnagIt, MTPW and more. Wow! Last week was dead quiet by comparison.

Then, I decide to check on other PCs here in the office, beyond my production desktop (i7 Skylake running Windows 10 current version). I don’t see as much activity there, but do find some:

Device                     OS     #Updates
----------------------   ------   --------
P16 Mobile Workstation   Win11P       0
ThinkPad X380 Yoga       Win11D       2
Surface Pro 3            Win10RP      3
ThinkPad X12 Hybrid      Win11D       0
ThinkPad X1 Extreme      Win11P
----------------------   -------   -------
P=Production; D=DevChannel, RP=Release Preview

Upon considering this data, I have to change my initial supposition. While it’s probably true that software makers are pushing a last round of updates out to Windows users, looks like it’s not coming in a total rush this morning. Because I updated all of those other machines Wed-Fri last week, I can say it’s been coming for a while now. Looks like I didn’t get around to my production PC until later, rather than sooner.

More Data Delivers More Insight

This just goes to show that a larger sample size is helpful in making observations about updates more informed and cogent. It’s probably a good idea to schedule one more update cycle before the holidays (if you haven’t done so already). After that, it should be safe to wait until January 3 — or later — to make a next check.

My gut feel is not much will be happening, update-wise, for the rest of the next couple of weeks. I guess that means the EoY break is at hand. Enjoy!

Note: I will be blogging through Wednesday, December 21. I’m off then, but I’ll resume on December 26. Happy Holidays to one and all.

Facebooklinkedin
Facebooklinkedin

Thunderbolt Docks Add Helpful Future-Proofing

I’m thinking about what kinds of hardware experiments I’ve conducted over the past couple of years. Especially this year (2022). Along the way, I’ve learned that Thunderbolt docks add helpful future-proofing for home and office users. Let me explain…

How Thunderbolt Docks Add Helpful Future-Proofing

Right now, Lenovo offers what can only be called a “Best Buy” in the arena of Thunderbolt 4 docks. Or maybe a couple of them, as I’ll recount shortly. Called the Universal TB4 Dock, it currently retails for just under US$290. This is about US$110 cheaper than its nearest competitors (e.g. Belkin and CalDigit, among others).

On December 8, I also wrote here about the Lenovo P27-u20 monitor, which includes a built-in TB4 dock. At US$527, with a 4K monitor included in the mix, it too, qualifies as a “Best Buy” IMO.

There is one thing, though: to make proper use of TB4, you also need TB4 peripherals. They will be no more than two years old (TB4 made its debut in H2’2020). There’s a lot of expense involved in climbing this technology bump. But if you’ve got newer peripherals, a TB4 dock is a great way to mate them up to PCs and laptops back to 8th Gen Intel (and equivalent AMD) CPUs. I’ve done that, and it works great.

Try TB3 for a Lower-Budget Approach

For readers who want to extend the life of a Windows 11 capable PC or laptop, it may make sense to invest in Thunderbolt 3 (TB3) instead. Such docks cost as little as US$40 (e.g. Dell refurb), and are readily available new for around or just under US$100. If you’ve already bought into USB-C (3.1 or 3.2 capability) or TB3 peripherals, this is a less expensive way to dock up. Worth researching anyway: I see lots of attractive options at Amazon and other online outlets.

Thanks, Lenovo!

While I’ve got your eye, I’d like to thank the laptop and peripherals teams at Lenovo for their outstanding support. They’ve sent me half-a-dozen different laptops (and one great SFF workstation), multiple docks and the aforementioned monitor this year to review.

It’s been incredibly educational and lots of fun to put different TB4 scenarios together. This lets me understand and measure how they work, and how to make them work best. A special shout-out to Jeff Witt and Amanda Heater for their great help and quick assistance this year (and beforehand). Happy holidays to one and all.

Facebooklinkedin
Facebooklinkedin

OCD Need Not Drive Software Updates

I’m something of a nut when it comes to keeping my fleet updated — now numbering 11 Windows desktops and laptops. But I’m learning that some updates are worth installing, while others are questionable. My OCD desires aside, a line between “must-have” and “nice-to-have” is coming clear. Hence the claim: OCD need not drive software updates. Let me explain, using the “free Kindle app” (Windows version), as an example.

Changes Occur, But OCD Need Not Drive Software Updates

Kindle illustrates my case in point. Check the lead-in graphic. It shows the General Options page for the Kindle App (Windows variety). Note the checkbox for “Automatically install updates …”  It’s checked! Note further: the Software Update Monitor tool (SUMo) reports ALL such updates.

Here’s the rub: Amazon/Kindle itself does not push updates unless they offer new functionality or security fixes. If SUMo catches one that the auto-update function does not push, catching up means extra work. First, one must uninstall the “outdated” version. Then, one must download and install the “current” version in its place. Winget does this easily, as I describe in my November 3 item. But Amazon/Kindle find it unnecessary (or they’d push it automatically).

Other Cases, Other Deferrals…

I’ve observed this pattern with other 3rd-party tools. One is ioBit Driver Booster Free (I run it as a test app on one Beta Channel PC). I emailed the company to ask about “skipped updates.” They responded with a helpful explanation. Paraphrased it reads “Some updates aren’t needed for existing installations.” They also offer updates explicitly whenever adding new stuff or security elements.

Thus, I’m learning to be choosy in updating applications. Perfect coverage takes time. I now understand that putting time saved elsewhere has benefits. That’s why I stress that OCD, however compelling, shouldn’t guide one’s update approach — especially mine!

Facebooklinkedin
Facebooklinkedin

Curious Reliability Monitor Incident Occurs

Sometimes, no news is itself news. One of my favorite Sherlock Holmes stories, The Adventure of Silver Blaze describes a “curious incident of the dog in the night-time” wherein “the dog did nothing…” Lately, as the lead-in graphic from Reliability Monitor shows, my production PS is such a dog. Over a 19-day period, it shows exactly one critical event. And that one is easily explained, thanks to an aging UPS battery.

Good News When a Curious Reliability Monitor Incident Occurs

According to WinFetch, I have 308 packages installed on my production desktop, of which Winget recognizes 226. Those numbers provide ample opportunities for things to go sideways. I confess: I check in on Reliability Monitor when seeking blog topics. It seldom fails to point toward interesting troubleshooting or clean-up exercises.

I use the heck out of my production PC: 8-10 hours a day, 6-7 days a week. Consequently, I’ve seen many less happy Reliability Monitor traces than the one at the head of this story. It is, in fact, something of an anomaly in my 6-plus years of working this PC as a daily driver. And that, to mangle Mr. Holmes, is what makes for a “curious incident” — namely that I could work both hard and long on this PC while maintaining a nearly perfect reliability score.

Windows 10 Gains a Ringing Endorsement

When nothing shows up in Reliability Monitor, the presumption is that the PC is behaving itself well. For example, I’m currently logged into 4 RDP sessions: 3 on various Windows 11 versions, 1 on Windows 10. Only one of them shows one critical error event like the lead-in graphic. It’s from a Dev Channel build that’s been running for 11 days, and the critical error it shows resolves into 4 events that occurred just after the new build installed on November 29.

The other 3 PCs show 3 or more critical events over the default 19-day interval typical for Reliability Monitor displays. And these, too, devolve into a half-dozen error events of one kind or another. My point is: the production PC is manifesting unusual calm and stability, especially as the other machines are less heavily used (though subject to beta software and primarily test or experimental situations).

I see this as another explanation for the relatively slow changeover from Windows 10 to 11 I wrote about yesterday (Where Windows 11 Business Use Stands). If the OS ain’t broke, there truly is no need to fix (or replace) it. I find it comforting, in a weird way; MS undoubtedly has more mixed feelings on this subject. But it offers a pretty compelling explanation as to why businesses aren’t yet taking the Windows 11 plunge in significant numbers.

Facebooklinkedin
Facebooklinkedin