Category Archives: Windows 10

Windows Updates Gain Expiration Dates

Take a look at the web page for this June vintage 19042 Windows 10 preview item KB5003690. As the concluding term in its title states, this item is EXPIRED. It’s also no longer available for download. Revised MS policies mean that some Windows Updates gain expiration dates (or status, anyway) when they reach obsolescence. The lead-in graphic for the story shows the revised KB5003690 title and its EXPIRED status above.

If Windows Updates Gain Expiration Dates, Then What?

It’s not exactly like a carton of milk from the grocery store. You won’t know in advance when any particular KB item might (or will) expire. This looks like the kind of thing that will pop up when you try to access older updates that Microsoft has removed from circulation.

The details of Microsoft’s EXPIRATION NOTICE read like this:

NEW 7/21/21
EXPIRATION NOTICE

IMPORTANT As of 7/21/2021, this KB is no longer available from Windows Update, the Microsoft Update Catalog, or other release channels.  We recommend that you update your devices to the latest security quality update. The latest security quality update is cumulative and contains all the addressed issues in this update.

Apparently, the idea is that as certain updates age out, they will no longer clutter up the update universe. WindowsLatest opines this will be a boon to those who might pause or skip updates, by reducing download items and data volume. They also assert that “… older and redundant packages will now expire automatically, which can improve the performance of Windows Updates and reduce update cache size.” Same effect applies to scan time: with fewer updates to look through, scan results should come back more quickly as Windows PCs “Check for updates” in WU.

Less Is More?

Certainly from data management and networking perspectives, reducing the population of update items is a good thing. I’ll be curious to watch for this status to start coming up when checking KB items.

Just for grins I checked a newer Preview update for status. KB5005101 (released on 9/1/2021) remains available, and its Catalog download likewise. Looks like expiration dates don’t kick in until an item — even a Preview item — gets to be four months old, or older. Time will tell if that boundary is flexible, or fixed…

Facebooklinkedin
Facebooklinkedin

UWP Came — Now It’s Going

For some odd reason, the old French saying “Le roi est mort, vive le roi!” comes to mind. Announced with great fanfare and stunning promises along with Windows 10 in 2015, the Universal Windows Platform (UWP) is now mostly history. The lead-in graphic shows that UWP was short on neither vision nor ambition (source: MS). But as dramatically as UWP came — now it’s going, as Microsoft recommends developers migrate their UWP code to the Windows App SDK.

First UWP Came — Now It’s Going. What Next?

From being the key to developing apps that could run on Windows Phone, desktop, or Xbox platforms  — and more (Surface Hub, HoloLens, IoT, etc.) — UWP is falling by the wayside. Long time development guru Rafael Rivera temporarily suspended his Twitter boycott to post about the afore-linked migration advice from MS.

His comment on where UWP is going could be summarized as nowhere, fast. This is what he said:

This signals what I already told you before: UWP will only get “bug, reliability, and security fixes”.

The Windows App SDK is the new king of the development hill. Vive le roi! The Docs item walks developers through the migration process in step-by-step fashion, following these headings:

  • Install the Windows App SDK VSIX (Visual Studio extension)
  • Create a new project
  • Migrate code with the least dependencies first
  • Copy files, or copy file contents?
  • Folder and file name differences (C++/WinRT)
  • If you change the name of your migrated project
  • Install the same NuGet packages that were installed in the source project

To further guide developers MS includes links to a PhotoLab case study and a Photo Editor case study. It also lists WinRT APIs no supported in desktop apps.

Out with the Old, In with the New

Curiously, MS doesn’t spend much text on explaining this change or touting the benefits of the new Windows App SDK. It simply makes  matter-of-fact assertion that “The Windows App SDK provides a broad set of Windows APIs — with implementations that are decoupled from the OS, and released to developers via NuGet packages.” Later on it says “With the Windows App SDK you can incorporate the latest runtime, language and platform features into your app.” And that’s about it.

It will be fascinating to observe uptake and reactions from the Windows developer community. Given that occasional API reworking have occurred before in this world, I’m curious to see how this goes over. Stay tuned, and I’ll revisit this as news and events decree.

Facebooklinkedin
Facebooklinkedin

Loaner Laptop Poses Weird USB Situation

I took delivery of a nifty new laptop here at Chez Tittel late last week. Among the zillions of other things going on around here, I’ve been fooling with this machine since it arrived. This loaner laptop poses weird USB situation, though: I get faster throughput from its USB-A 3.2 Gen1 port than either of its USB4 Type-C/Thunderbolt 4 ports. Throughput is about 10X faster on the USB-A port than on USB-C. That’s not how it’s supposed to work. Go figure!

Driver Issues Explain How Loaner Laptop Poses Weird USB Situation

Once I realized what was going on. I jumped into Device Manager. Sure enough there’s an issue with the ThinkPad Thunderbolt Retimer Firmware. Whaddya bet this could impact USB-C/Thunderbolt 4 timing?

And then, things get more interesting. Lenovo Vantage thinks the firmware update is already installed. Device Manager shows “Firmware update was unsuccessful.” Attempts to uninstall/reinstall don’t work, and manual installation of the downloaded firmware package N32TT02W.exe from Lenovo Support don’t work either.

I need some firmware juju. So I’m contacting Lenovo Support to see what they can tell me. I’ll admit I got fooled when Vantage told me the update was installed (and didn’t check DevMgr until later). Now, it looks like I’ll have to roll the machine back to Windows 10 so I can make sure the update gets properly applied. And then, I’ll roll forward again to Windows 11. Just another day in the life, here in Windows-World!

Checking Updates, Post Install

It hasn’t eluded me that checking the firmware install before upgrading to 11 would have been a peachy idea. I’m not one to rush into such things normally. But I wanted to see how the new PC would work with the new OS. I guess I’m  starting to understand there’s at least one good reason why Lenovo didn’t send me the device with Windows 11 already installed.

As I look around the Lenovo site, I see they have Thunderbolt drivers for Windows 11 aplenty. It’s just that they don’t have one for my X1 Carbon Gen 9 laptop just yet. Live and learn, dear readers: that’s why I’m going to try to do.

Facebooklinkedin
Facebooklinkedin

Bad Move: Opening MSA in Default Admin Account

I admit it. I screwed up, and then I paid the price. Yesterday I got a new review PC delivered. It came from Lenovo: a new X1 Carbon Gen 9 PC. That unit feature an i7 4core CPU, 16 GB RAM, and 512 GB NVMe SSD with Thunderbolt 4 support. Typical for review units, it opens into a local admin account. Inside that account I made a bad move: opening MSA in default admin account. Alas, this caused all kinds of problems.  Let me explain… (I’ll add that MSA is a common acronym for “MS account” aka “Microsoft account.”)

What Happens After Bad Move: Opening MSA in Default Admin Account

My MSA picture got associated with the local account. That was my first cluethat something was off. On other loaner units, I’ve always been careful to set up a second account for my MSA. Then I give it admin privileges and work from there after that. This time, I logged into the Microsoft Store inside the local account. Big mistake.

As soon as I set up my MSA as a separate account, the Store quit working. The associated error code clearly explained it was an MSA login problem. Apparently, the MS Store decided that if it couldn’t distinguish a local account from an MSA, it wouldn’t open for either account on that machine. None of the usual repairs (uninstall/reinstall Store) did any good, either.

Cleaning Up the Mess

Forunately, I had to take a break to go see the “Friday Night Lights.” It was homecoming night at my son’s high school, and the Boss and I wanted to drink in the pageantry and celebration. While I was away from the munged review unit, I realized what I needed to do:

1. Set up another local account
2. Give that local account admin privileges
3. Delete the problem default account

This took a while to orchestrate and set up. I had to be reminded that the “Family account” sub-menus is where one sets up local accounts on Windows 10 and 11. After making sure my MSA and the other local account were properly privileged, I deleted the problem account. And immediately, the MS Store returned to working order. Self-inflicted wounds smart a little extra when one realizes who’s to blame for the hoopla.

Stay tuned: I’ll have a lot to say about this new loaner unit in an upcoming “First Looks” piece early next week. I’ll tease some planned topics to whet your interest, though:

1. Thunderbolt 4/USB-C proves surprisingly speedy
2. Interesting issues with Secure Boot and clean install attempts
3. Unit shows up with Windows 10 installed, not Windows 11
4. Timing and experience in upgrading to Windows 11
5. Interesting issues with Windows Hello

Be sure to check back in when that “First Looks” item appears. Cheers!

 

Facebooklinkedin
Facebooklinkedin

MS Streamlines Windows 11 Update Handling

MS tracks and delivers changes (and reverse operations) to OS images using “forward and reverse differentials.” This started in Windows 10, Version 1809. Now, MS adds slick optimization that reduces repeat references to objects and instructions. Thus, MS streamlines Windows 11 update handling further. It’s all explained in an October 12 Microsoft Windows IT Pro blog post. That post is entitled “How Microsoft reduced Windows 11 update size by 40%.” It explains how MS further reduced update volume without boosting installation time.

How MS Streamlines Windows 11 Update Handling

In the afore-linked blog post, MS explains its objectives as “reducing the size of Windows 11 updates.” At the same time, the company sought to:

  • decrease size of network downloads for updates
  • keep install times unchanged (not slowed)
  • keep updates compatible with all distribution channels (e.g. WU, WSUS, SCCM, InTune/AutoPilot and so forth). Thus, IT pros need make no config changes.

According to the blog post, “since Windows 10, version 1809, …servicing has used paired forward and reverse differential compression.” What MS did, at a high level, with Windows 11 was to add a catalog to remap virtual addresses when function addresses or other relative references change. This replaces forward and reverse differentials for such addresses with (much shorter) lookup table references.

Such operations are easy to reverse, too. These might be required if an update fails prior to completion. This returns the OS image to a known, working stable state. OTOH, it might be required if the user decides to uninstall or roll back an update.

MS’s analyses show that this new approach provides a “40% reduction in update size.” This means not just smaller updates, but less overall consumption of network bandwidth to transport updates. For software with millions (Windows 11) to billions (Windows 10) of users, this is a big deal. No wonder MS is working to patent this technology…

Facebooklinkedin
Facebooklinkedin

Nvidia Drivers Gain Considerable Heft

I noticed early this afternoon that my GeForce GTX 1070 GPU needed a driver update. The lead-in graphic shows the download size for the 496.13 version at 830.3 MB. When expanded and installed, that translates into 1.5 GB in the DriverStore (see RAPR screenshot below). That’s why I claim that  Nvidia drivers gain considerable heft. The preceding version, as that same screencap shows, weighs in at a slighty-less-ginormous 1.3 GB. Heft!

Nvidia Drivers Gain Considerable Heft.rapr

Driver Store Explorer (RAPR.exe) shows some big driversizes for Nvidia stuff!
[Click image for full-sized view.]

As Nvidia Drivers Gain Considerable Heft, What to Do?

Clean up old ones, obviously! With that kind of space consumption you wouldn’t want to keep too many of them in the DriverStore. I will usually keep the previous version around for a week or so. I’ve been bitten in the past by new driver issues, and have learned to support rollback long enough to make sure everything’s OK.

I can remember only a couple of years ago, when Nvidia drivers routinely weighed in at 600-800 MB each. They’ve doubled in size since then as more bells, whistles and game tweaks get rolled up underneath their capacious umbrellas. Even then, I advised cleaning up if more than 2 copies reside in the DriverStore, and have personally seen that single cleanup maneuver — namely, removing older drivers from the store — free up 3-5 GB of disk space.

Note: by default, Windows 10 or 11 will allow an arbitrary number of versions of the same driver in the store. For big drivers this can produce unnecessary bloat. As you roll new Nvidia (or AMD Radeon) drivers in, make sure you also take the time to roll old ones out. Cheers!

Note: RAPR Pointer

If you’re not already familiar with the excellent Driver Store Explorer tool (aka RAPR.exe), download a free copy from its Github home page. An invaluable tool that I use myself at least once a month. All you have to do is click the “Select Old Driver(s)” button to clean up obsolete driverstore elements.

Facebooklinkedin
Facebooklinkedin

Clean Install Still Cuts Gordian Knot

The old, old story of the Gordian knot traces back over 2 millennia. It’s meant to illustrate that difficult problems may be overcome by a variety of means. Usually, as with the original story itself, some of them are drastic. When unable to untie the knot, Alexander the Great drew his sword and cut it through instead. He lost the rope, but solved the problem. And so it is with some Windows problems, where a clean install still cuts gordian knot issues that other repairs cannot address.

If Clean Install Still Cuts Gordian Knot, What Made it Necessary This Time?

I’ve been helping a friend over the past two weekends try to solve an iCloud to Outlook synchronization problem. To his credit, he put in two lengthy calls with MS Support, and performed an in-place upgrade repair install. His primary symptoms were:

1. Unable to download iCloud from the MS Store
2. If installed manually, unable to get iCloud and Outlook to synchronize. Interesting but weird error messages about “no default Outlook profile” suggested possible fixes, but none of those worked.

After attempting numerous manual repairs and tricks last weekend without success, I showed up this weekend planning to perform a clean install on his wife’s laptop, a Dell Latitude 7155 (i5, 4th gen Intel CPU). It took me somewhat longer to get the disk cleaned up and a pristine image laid down on her NVMe SSD than I had thought it would.

But once a clean Windows 10 image was installed and updates applied, I was able to download iCloud from the Store. Next, I revisited office.microsoft.com and re-installed Office 365. The acid test followed immediately thereafter: I attempted to synch with iCloud for messages, contacts, and other Outlook items.

To nobody’s particular surprise, it worked. But gosh, it sure took a while to get everything ready (Macrium Reflect came in hand indeed). And it took longer to install and update the OS image than I was expecting. But in the end, the outcome was as desired. So far, we’ve put about 7 hours into this repair effort. Alas, it’s still not quite done just yet.

One More Thing…

I mounted the Macrium backup to make it available for copying older files to the rebuilt desktop. But because of permissions problems I wasn’t able to access some key stuff. So, I’m going back in one more time to fix those and grab the additional stuff my friend needs. Hopefully, that will be as routine as I anticipate. In the meantime, I’m boning up on the ICACLS command so I can reset permissions wholesale, and make everything one might need from the backup available in one go.

At the end of the day, it’s nice to know the tried-and-true methods work like they’re supposed to. I can only guess that some vital plumbing between the Outlook and iCloud APIs got munged in the old runtime environment. By creating a new, pristine one, we have apparently fixed what was broken. Old school still rules. Good-oh!

 

Facebooklinkedin
Facebooklinkedin

Switch Replacement Fixes Network Woes

A few months ago, I found a failing NIC that knocked the network down. Before that, one of my ISP-provided boundary devices started failing. Yesterday, I lost the Ethernet side of my network. That is, the Wi-Fi from the boundary device kept working while the rest of the network crashed. Fortunately, I had a pretty good idea that my primary GbE switch might need replacement and had already ordered one through Dell in July. Even more fortunately, a quick switch replacement fixes network woes, and brings Ethernet back to life.

Literal Switch Replacement Fixes Network Woes

The funny thing is, I’ve been using the same switch in my office since we moved into this house in April 2006. And when I went to re-order, the same switch remains available at a knock-out price of US$40. It’s the venerable Netgear GS-108 unmanaged 8-port GbE switch and it works like a charm. I guess 15-plus years of uninterrupted, heavy-duty service ain’t bad. In fact, I’ve used all 8 ports all the time and that device is as close to a network backbone as the 12-15 devices around our house can access.

The blurb on the NetGear site reads “Set it and forget it, energy-efficient switches are built like tanks and last for decades.” In fact, I can’t remember when I bought the original. I know it must’ve been some time around 1998, when I moved into my previous house. Thus, I’d have to agree with that seeming hyperbole.

Dead-Simple Replacement

I unplugged power jack from the old switch. Then I removed all 8 of the RJ-45 cables plugged into its face (see lead-in graphic). I unpacked the new device, plugged in its power supply, and plugged in the RJ-45 cables. The power light came up, after which the activity LEDs started blinking. Problem solved.

There’s another GS-108 of about the same vintage upstairs under my wife’s desk, where it serves to distribute Ethernet to that floor of the house. I have another replacement in my spares closet, ready to take over for the old one should it fail, too.

How I Knew It Was the Switch, Stupid!

When the Ethernet side of things goes down, it has to be a device that makes the side work. That means it could have been a switch, of which I have 4 on my network. One is in the recently-replaced router/wi-fi/switch device from Spectrum, replaced in June. Another is in my Asus AX6000 wi-fi/switch/router: it’s Wi-Fi was still working so I guessed that meant the switch portion was still working, too. Thus, it was likely one of the two GS-108s. Logic dictated the heavily-used one in my office would be the one to fail first. This time, logic prevailed — or so it seemed.

i’m just glad I had a spare on hand. I’m even gladder that the switch  swap was as simple and painless as I hoped it would be. Sometimes, here in Windows-World one does catch a break. With plenty of real work to do yesterday, I was appropriately grateful.

Or Maybe Not, But Real Cause Emerges Quickly

About two hours after I posted this, my problems returned in full force. That left only one other possible cause: some element in the Ethernet network had to be failing intermittently. I had two prime candidates:

  1. My 8-year-old Surface Pro 3 dock, whose GbE port has been flaky in the past. That wasn’t it.
  2. The cable from my switch to the filing cabinet by the window in my office goes under my desk, where I can’t help but kick that cable occasionally. Apparently, I’ve kicked it often enough to introduce an intermittent short. Now that it’s removed from the network all is once again good.

I guess I can keep my ancient GS-108 Switch around as a spare, because it obviously was NOT the cause. And that’s how it goes when troubleshooting intermittent Ethernet gotchas. Live and learn!

Facebooklinkedin
Facebooklinkedin

21H1 Build 19044.1237 Represents Upcoming Release

The last cumulative update for the Release Preview Channel hit Insiders on September 14. In fact, looks like MS put a ribbon around this upcoming 21H2 release. According to deskmodder.de, KB5005565 is as close to final as a preview release can get. Thus, 21H1 Build 19044.1237 represents upcoming release on the Windows 10 track.

Who says: 21H1 Build 19044.1237 Represents Upcoming Release?

Deskmodder. de is an unusually well-informed and highly reliable German website that’s got a great track record for predicting releases. In English, his story headline translates as “Windows 10 21H2: ‘Final’ version will be 19044.1237” (link is to German original). My only dedicated Windows 10 test machine right now is a 2014 vintage Surface Pro 3 (4th gen Intel CPU, 8 GB RAM, 256 GB SSD). It’s the source for the lead-in graphic for this story.

I’m actually thinking about keeping my old 2016-vintage i7-6700K desktop up and running for Windows 10, too. I’ve decided to build my new production desktop in a retired PC’s Antec 900 case. It remains a quiet, capable and useful enclosure, especially as I’ve added a Thunderbolt/USB-C/USB-A 3.1 Gen 2 5.25″ drive bay to that unit. That gives me more and better high-speed ports than the 2010 vintage case itself provides.

Keeping On With Windows 10

Until now, my Windows release tracking strategy has been: follow the latest, abandon the rest. But this time the controversy over hardware requirements tells me a substantial segment of the user population will stay with Windows 10 until the bitter end in October 2025. Thus, it behooves me to keep up with Windows 10 releases and issues on the trailing edge. And of course, I’ll be upgrading the bulk of my fleet (9 PCs: 3 laptops and 6 desktops) to Windows 11.

The deskmodder article airs the speculation that 21H2 may be the last “real upgrade” to the Windows 10 development fork. I’m not sure I agree with that, especially given the similarity between the Win10 and Win11 code bases, and my gut feel for the size of the user base that will stick with the older OS. I’m pretty sure MS will back-port important stuff especially if the sizable and potent base of business users does not jump early and often onto Windows 11.

As I think back on business migration patterns to new Windows OSes, it seems  that 2 years after initial release is when those users really start gearing up. Given that 2025 is still 4 years away, I think Windows 10 will remain dominant in business until 2023. Unless MS comes out with “killer features” that businesses can’t live without beforehand, that’s the way they’ve always done it. So far, I don’t see any compelling reasons why Windows 11 uptake should be any different.

As usual, only time will tell. For the next two years at least, Windows 10 and Windows 11 will very much be parallel efforts, IMHO at least.

Facebooklinkedin
Facebooklinkedin

Chrome Software Reporter Tool Monopolizes CPU

After upgrading my Lenovo X12 Hybrid Tablet to Windows 11 Build 22454 , I noticed CPU usage stayed elevated. For a long time, in fact: at least 5 minutes or longer. Checking Task Manager the culprit was obvious. Item software_reporter_tool.exe consumed half or more of available CPU cycles. Upon further investigation, I learned two things. (1) plenty of other people have experienced this. (2) it’s a part of Chrome’s Cleanup toolkit, designed to remove software that could cause potential issues with Chrome. Having just rebooted, Chrome wasn’t even running. But that apparently didn’t stop its background tasks from executing. And that, dear readers, is how I learned that sometimes the Chrome Software Reporter tool monopolizes CPU on Windows PCs.

Do This When Chrome Software Reporter Tool Monopolizes CPU

I found an article from Martin Brinkmann at Ghacks.net about this phenomenon dated January 2018. It provides a battery of potential fixes. These include a variety of blocking techniques based on file permissions, and Chrome policies (via registry hack). I actually found a 2020 Codersera article that offered a more direct approach.

It’s the one I implemented, and it’s working well so far:
1. Open Chrome controls (vertical ellipsis symbol at upper left of browser window).
2. Click “Settings” resulting pop-up menu
3. Click down-arrow next to “Advanced” near bottom of that window.
4. Scroll down to “System” section and turn off item that reads “Continue running background apps when Google Chrome is closed” (move slider to left).

That should do it. At least, it seems to have worked for me: I haven’t seen any recurrences since I made this configuration change.

When Odd Processes Stand Out, Research Helps

This technique is a familiar one to those keep an eye on Windows performance. It’s often a good way to start digging into slowdowns like the one I ran into last week. I generally try to rely on well-known and -respected resources when it comes to fixes (if not the maker or vendor’s own tech support info). But usually, when there’s a will to fix such things, a way to fix them can be found.

If worst comes to worst (and I have a recent backup) I might even right-click the offending process and select “End process tree” to see what happens. Please note: don’t do this with Windows OS components, or you’re likely to experience a BSOD. ‘Nuff said.

Facebooklinkedin
Facebooklinkedin