Tag Archives: featured

Windows 11 Says Sayonara WMIC

Because it was announced in Windows 10 21H1, it was just a matter of time. The Windows Management Interface Command-Line utility, aka WMIC, is deprecated. No longer simply slated for oblivion, WMIC is missing from the Dev Channel version of Windows 11. The lead-in graphic shows what (doesn’t) come up in cmd.exe for Build 22483 and higher. Hence my title: Windows 11 says Sayonara WMIC. For the record, it’s still in production Windows 11 versions but reads “WMIC is deprecated.” in red.

Windows 11 Says Sayonara WMIC.Win11-prod

Notice the red text at top of help response. It’s MIA In Dev Channel versions now.[Click image for full-sized view.]

Though Windows 11 Says Sayonara WMIC, WMI Remains Around

Microsoft has good advice for would-be WMIC users. They should  use PowerShell replacement cmdlets instead. Turns out that the Windows Management Interface (WMI) remains alive and well. In a story about this change-over, WinAero.com suggests using a specific PowerShell command to learn more:

Get-Command -Noun WMI*

For the record, that string produces the following output that shows this is just the beginning of a sizable set of cmdlet documentation.Windows 11 Says Sayonara WMIC.ps-info

The 5 cmdlet WMI facilities: Get, Invoke, Register, Remove and Set.
[Click image for full-sized view.]

Each of these five facilities has its own muti-level help files. Looks like the switch-over is supported. That said, it requires climbing a new learning curve to bring users under the PowerShell umbrella.
Cheers!

Facebooklinkedin
Facebooklinkedin

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

Windows 11 Gets New Update Stack Package

Last June, MS announced the release of a Windows Feature Experience Pack (120.2212.3920.0) to Insiders in Beta and Release Preview Channels. In yesterday’s Dev Channel Preview Build 22478 release notes, they announced something called “Update Stack Packages.” Let’s call the former WFEPs and the latter USPs for brevity. USPs provide a “…new process for delivering new update improvements to our customers outside of major OS updates…” But if Windows 11 gets new Update Stack Package, what does that really mean?

Sussing Out Windows 11 Gets New Update Stack Package

The key to understanding comes from a sentence in the release notes discussion of USPs. It reads “The Update Stack Package will help ensure that your PC has the highest likelihood of successfully installing new updates with the best and least disruptive experience available.” Sounds like a mechanism to make sure the OS image is free of potential impediments to upcoming updates. Why does this remind me of “servicing stack updates?”

Overall, the discussion of USPs is much like that for WFEPs earlier this year. To wit:

1. USPs are currently limited to “a very small set of update-related system files … developed independently of the OS.” WFEPs have been small and limited since their June 2021 introduction. That said, they focus on “feature improvements to customers outside of major Windows 10 feature updates.”

2. USPs and WFEPs both come to Windows installations via WU.

3. Both seek to sanity-check and test their approach and capabilities with Insiders, but ultimately aim to “expand the scope and frequency of releases in the future” (quote from WFEP June announcement).

Looking for Enlightenment…

What’s really going on here? MS seems to be experimenting with different kinds of update mechanisms independent of “major OS updates.” Given that feature updates are dropping back to yearly frequency, this provides a way to introduce changes more often than that. I’m curious to see either (or both) of these mechanisms deliver something meaty. So far, they’ve been used only for tentative, small-scale updates and changes. I guess we’ll have to wait and see how they behave when they get a more serious workout.

Right now, for both USPs and WFEPs there’s far more fanfare than clarity or understanding. Hopefully time and experience will cure that imbalance and bring some useful demonstrations of what these things are for, and what they can do when exercised more heavily.

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

Why Is Windows 7 Still Running on 1 of 5 PCs Worldwide?

The mind reels. I just checked the Operating system market share by version stats at NetMarketShare.com. To my outright astonishment, 20.93% of PCs worldwide still run Windows 7. By contrast, Windows 10 has a 62.16% share and MacOS 6.21% (the numbers in the figure only run through September; these are for October). Thus, I have to ask: “Why Is Windows 7 Still Running on 1 of 5 PCs Worldwide?”

Answering Why Is Windows 7 Still Running on 1 of 5 PCs Worldwide?

In a piece from Microsoft Story Labs with a 2018 copyright date, the company claims “there are more than 1.3B devices running Windows 10.” If that represents 62.16% of the number of PCs running globally, that means that 437 million PCs could be running Windows 7.  (I know: I’m making assumptions willy-nilly, but this is a strawperson argument anyway.) That said, both The Verge and ZDNet reported in January 2021 that there could be somewhere over 100 million (Verge) and under 200 million (ZDNet) Windows 7 PCs still in use. Whatever that real number may be, my question is: “Why?”

Windows 7 hit EOL in January 2020. Microsoft does offer annual Extended Security Updates (ESU) for such machines, but that costs US$62 per license as of January 2021. Nobody knows for sure how many PCs are under ESU coverage (MS doesn’t disclose those numbers). But I’d be surprised if more than 20 million PCs were under contract.

What does that mean for the other 80 to 180 million Windows 7 PCs still in use? Big security exposure, and the onus for support on their owners. To me, this falls under the heading of “unacceptable risk.”

Again: Why Keep on with Windows 7?

Surely, the biggest answers have to be:

1. Inertia/laziness: Owners (individuals and businesses) don’t want to change.
2. Budget constraints/parsimony: Owners don’t want to spend the money (or time and effort) required for migration and possibly also, hardware refresh
3. Legacy app tie-downs: Businesses running custom apps based on Windows 7 don’t want to port or rewrite the code for newer Windows versions.

I understand these reasons, but I don’t understand that users and companies/organizations are willing to take big security risks as a consequence. I am flabbergasted that the curve showing in the lead-in graphic is declining so slowly. 5% in 10 months translates into 6% annually. That means that assuming the rate of decline remains constant, Windows 7 will remain in use for another 3 years and then some. All I can say is: Mind completely blown!

What could — and probably will — change this leisurely decline is some major security exploit that’s sure to come along. When owners must face clear, immediate and present danger of financial loss or legal liability they’ll get on the stick and start migrating faster. In the meantime, inertia continues to rule. Amazing!

Facebooklinkedin
Facebooklinkedin

Brand-new AMD PC Gets No Windows 11 Love

OK, then. I’m  a little puzzled. Last month, I upgraded one of my desktops to a rockin’ configuration. I did this specifically to prepare for yesterday’s Windows 11 GA date. That PC includes an AMD Ryzen 7 5800X, 64 GB RAM, and more. It completely meets the Windows 11 requirements (and PC Health Check agrees with my assessment). But this machine gets nothing like the “Great news” item that appears on my X380 Yoga (see lead-in graphic). That’s right: my brand-new AMD PC gets no Windows 11 love from WU.

If Brand-new AMD PC Gets No Windows 11 Love, Now What?

Because I purpose built the machine for Windows 11, I could use the ISO I grabbed from MS yesterday. I’d mount that image, then run setup.exe to perform an in-place upgrade install instead. I wrote on Monday that it can take a while for machines to get the WU offer at Microsoft’s discretion. Little did I know that my new AMD PC (less than a month old) would fall outside that limit. Go figure!

I have to laugh. It’s always been a bit of a mystery as to how MS opens up availability during a “gradual rollout.” Ditto for the criteria it uses to gradually extend that availability to an ever-increasing population of PCs over time. I expected that new stuff would meet those criteria sooner rather than later. My expectations have been dashed, but I don’t take that personally.  I just need to decide what to do.

Upgrade Now Vs. Upgrade Later?

Because there’s no compelling reason for that AMD PC to run Windows 11, I’m tempted to wait and see how long it takes to get an offer from WU. As I observed in my Monday post, “The first machines to get an upgrade offer will be those for which telemetry shows no upgrade problems.” I’ve heard from plenty of AMD owners over at Elevenforum that they’ve successfully installed Windows 11 on such PCs. That includes builds with 5800X CPUs, just like mine.

Thus, it comes down to patience and curiosity. I’ll try to hold onto the former so I can further exercise the latter. But if history is any guide, I probably won’t last much past Halloween before I hitch that machine to the Windows 11 star. Stay tuned: I’ll keep you posted.

News of Performance Issues Say: “Later”

Just this morning a number of stories about Windows 11 performance issues on AMD CPUs have surfaced. See, for example this NeoWin item “AMD processors hit by performance issues…” Or this OnMSFT story “AMD acknowledges Windows 11 performance issues…” Looks like the “lack of love” comes out of genuine concerns for less-than-positive outcomes. I bet my status changes after the promised and forthcoming AMD performance patch is out. We’ll see!

 

Facebooklinkedin
Facebooklinkedin

Windows 11: Revisiting Microsoft Gradual Rollouts

As I write this item on the morning of October 4, I’m sure I’m not the only person anticipating tomorrow’s General Availability release for the lastest Windows version. But with the approaching October 5 onset of Windows 11: Revisiting Microsoft Gradual Rollouts should help readers properly craft their expectations.

For Windows 11: Revisiting Microsoft Gradual Rollouts Sets the Stage

The watchwords here are “gradual rollouts.” This means that MS will start the release of Windows 11 with a trickle. The first machines to get an upgrade offer will be those for which telemetry shows no upgrade problems. That trickle will gradually increase over time as known problems get solved.

Another source of upgradability comes from so-called “seekers.” Seekers are those who grab upgrades via download without waiting for an offer from WU. Their telemetry will also show other machines that offer reasonable expectations of a positive upgrade experience. They, too, will start to get offers.

How Long to Get from Trickle to Flood?

If recent Windows 10 version upgrades are any indicator, it can take six months to a year before the gradual rollout switches over to wholesale access. It’s truly a data-driven exercise, in which telemetry provides the input to steer users into a new version “at the right time.”

My own track record is one of less patience, more WTF. I’ve tried to let WU dictate the pacing of upgrade offers for previous version. But I’ve not once been able to let WU drive upgrades for all six or seven of my production machines. These are the ones that run the current version of Windows 10, whatever it may be. Of that half-dozen, at least 5 meet Windows 11 requirements and will get the offer at some time or another.

Once again, I will wait awhile to see when that offer might come. It might take MS more than a month to extend it to my newest PCs (11th gen Intel and Ryzen 5800X CPUs). If so, I’ll do an ISO-based install from setup.exe soon thereafter. I’m just not that relaxed about making the 10-to-11 transition, I guess…

Stay tuned: I’ll keep you posted.

Facebooklinkedin
Facebooklinkedin