Category Archives: WED Blog

Obvious Fix Addresses 0xC1900101 Install Error

I run two Dev Channel test PCs. Yesterday, the Lenovo ThinkPad X12 Hybrid failed to upgrade to Build 25284. And it threw a familiar error code — one I’d just written about on ElevenForum just two days ago. Fortunately, the obvious fix addresses 0xC1900101 install error, as I will explain. But gosh! What a coincidence to have dispensed advice about this error only to experience it myself shortly afterward.

What Obvious Fix Addresses 0xC1900101 Install Error?

First let me share the text from my ElevenForum post (from which a screencap appears above):

Check out this MS Learn article: it asserts that an incompatible driver is present when this error code presents: https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-10-upgrade-resolution-procedures

So what I did next was to review all of the device drivers on the problem PC, and to upgrade those that weren’t current. To that end, I used a 3rd-party tool from IObit called Driver Booster (available in both free and for-a-fee versions). It found over 20 drivers in need of updating, and I updated all of them.

Long story short: two reboots later (one from the drivers the program found, another from a Lenovo Vantage update) I retried the 25254 install. And this time it completed successfully, sans the driver-related error. As I poke around online, I also see this is a fairly common install error where the obvious repair strategy is most often effective.

Shoot! It’s nice when things work the way they’re supposed to. Luckily, that does happen here in Windows-World from time to time.

Facebooklinkedin
Facebooklinkedin

Winget Install Technology Hiccup

When I ran Winget to check for updates on the Lenovo P16 Workstation yesterday, something interesting happened. As you can see in the lead-in graphic, Winget found 2 packages in need of update. But it installed only one of them upon command. I discovered why when I attempted to force install the missing item. Indeed it produced what I’m calling a Winget install technology hiccup. Let me explain…

Overcoming the Winget Install Technology Hiccup Is Easy

The error message that resulted when I tried to force install RingCentral told me everything I needed to know. It reads:

A newer version was found, but the install technology is different from the current version installed. Please uninstall the package and install the newer version.

So that’s exactly what I did in the next two commands shown–namely:

winget uninstall ringcentral

winget install ringcentral

Luckily for me, the simple name “ringcentral” is sufficient to identify the unique and actual package name (“RingCentral.RingCentral”). Otherwise, I’d have been compelled to use that full, complete nomenclature to pull off the remove/replace maneuver that saw the hiccup overcome. That happens when multiple packages share common nomenclature, and a unique string for the desired package must be fully specified.

In this case, everything was easy-peasey. Just the way I like it: hiccup fixed!

Facebooklinkedin
Facebooklinkedin

Intel Drops iGPU OEM Warning

Once upon a time, the Intel Driver & Support Assistant (IDSA) used to warn laptop owners about its built-in GPU driver updates. There’s even an Intel Support Note on this topic. It reads in part “Installing this graphics driver from Intel may overwrite customizations from your … OEM.” Recently, Intel drops iGPU OEM warning. Why? Because it’s been reworked NOT to overwrite customizations. No more need, no more warning, I guess.

When Intel Drops iGPU OEM Warning, Then What?

If you look at the latest finding inside the IDSA in the graphic up top, you’ll see the warnings are gone. Nothing loath, I tried it out on my Lenovo ThinkPad X380 Yoga Dev Channel test laptop. It spun away for a bit before throwing up a “Begin installation” pane from the installer.

Intel Drops iGPU OEM Warning.begin

Next, it displayed the phases it would walk through, starting with a huge honkin license agreement to which installers must accede before the process gets underway. Click “I agree” to continue, as I just did.

Intel Drops iGPU OEM Warning.agree

Setup says it will install a driver and a graphics command center, after which one clicks start. Install shows progress bars for said driver and command center, with an option to “Show details” (lists changes as they’re made including registry entries, installing files, and so forth). Driver install takes several minutes to complete.

A reboot is required for changes to take effect. Once I had done so, I didn’t find the Intel Graphics Command Center (IGCC) installed. Thus, I visited the Microsoft Store to download and install same. It had me uninstall the apparently now-unnecessary Intel Graphics Control Panel.

Post Reboot, Things Get Interesting…

Once the PC restarted, the unit booted normally (the shut-down phase, when it was presumably writing new driver stuff did take a bit longer than usual). After the reboot the graphics look and work enough like the preceding iteration that I can’t see or tell anything different.

But when I tried to open the IGCC, it hung in “loading mode” (a line of balls moving from left to right at the bottom of the window). It never went anywhere. Turns out running two user sessions, each trying to start up IGCC isn’t a good idea. As soon as I killed one, the other started working. From there I was able to explore and play with the IGCC without further difficulty. Looks like I’ll have fun digging in and learning more. Stay tuned: I’ll report back.

Facebooklinkedin
Facebooklinkedin

Dev Channel 22H2 Notepad Gets Tabs

Another small step for a Windows app, another instance of tabbing inside its window. With Build 22623, Windows 11 Dev Channel 22H2 Notepad gets tabs. You can see them in the lead-in screencap. There, I’ve got a trio of program output files open: dberr.txt, ar.txt, and dxdiag.txt. (That last item shows DirectX detections for one of my Dev Channel test PCs.)

Good! Dev Channel 22H2 Notepad Gets Tabs

I manipulate a lot of text files in my work, across simple notes, quotes, log and trace files, program outputs, and more. I really appreciate the ability to open a single instance and multiple tabs to bounce around among them. It had been a “minor irritant” to have to right click on the Notepad icon and force it to open a fresh instance when I wanted multiple text files open at the same time.

This latest change makes all that fooling around moot. Now, I can open as many text files as I’m likely to use without issue. In practice, I seldom have more than 5 or 6 open at any given moment. It seems like this latest version of notepad has no problems with that. (MS Store identifies it as version 11.2212.33.0 with an 8/5/2019 release date; latest update occurred on 1/20/2023.)

Not As Much Notepad++ Now…

Multi-tabbing is just one of the many cool things that the Open Source Notepad++ (GNU General Public License) can do. I also like its automated formatting, language sensitive auto-completion, search and smart editing functions. But I won’t have to switch to it anymore simply to use multiple tabs for open text windows. I’m convinced that’s a good thing.

On your Dev Channel Windows 11 PCs, Notepad should auto-update to the latest (tabbed) version through the Microsoft Store. If not, visit that app, click the Library item on the left margin and force all updates to be applied. That should do it!

Facebooklinkedin
Facebooklinkedin

Windows 10 EOS Hits January 31

First, an explanation of what may be a purely idiosyncratic acronym. In the preceding headline “EOS” stands for “End of Sales.” Indeed, the EOL (“End of Life”) date for Windows 10 remains unchanged at October 14, 2025. But EOS impacts those who want to build new systems, and for Windows 10 EOS hits January 31 of this year.

MS hasn’t commented on whether or not this means OEMs won’t be able to ship their PCs with Windows 10 installed after this date, either. But as you can see in the lead-in graphic, MS itself will no longer offer Windows 10 downloads for sale after this month ends. Note: despite the mention of Windows 10 Pro at top, the price shown — $139 — is for Windows 10 Home (Download). For my purposes here, the “More about Windows 10” text block is what matters most.

After Windows 10 EOS Hits January 31, Then?

First things first: I don’t see any similar warning on the official MS Download Windows 10 page. Apparently, users who already have valid Windows 10 license keys (unused or otherwise) can keep grabbing Windows 10 ISOs for installation and repair after January 31. That’s a relief!

So who’s really affected? Those who build their own PCs, or buy barebones models and elect to do their own OS installs (along with whatever else they do completing such builds). For such folks, buying a new, virgin Windows 10 license key (and download) from MS will no longer be an option. Undoubtedly, the aftermarket will remain awash in valid copies of same for some time after this cutoff date. That’s because plenty of such stuff is (or will be) in inventory when MS EOS hits.

What About the OEMs?

Again there’s no official word on this from MS. Ditto, AFAICT from the OEMs. But I can’t see MS stopping fleet or bulk sales to big buyers after January 31, even though they’re apparently halting small-scale retail sales of Windows 10 at that point. Too much potential business and revenue could be impacted, so no…

This raises an interesting question: Why do this now? My best guess is that MS is signalling end users — pretty strongly, in fact — that it’s time to target Windows 11 (and only Windows 11) on new builds. Given that Panos Panay talked about a Windows 12 successor at CES this year in Las Vegas, January 3-8, this timing is surely no coincidence.

Two predictions:
1. MS resellers will stock up on Windows 10 media and key combinations, to cover upcoming demand as they project it.
2. OEMs will continue to build Windows 10 PCs on order from customers, even after January 31.

As always, it should be interesting to see how this turns out. Stay tuned, and I’ll keep you informed!

 

Facebooklinkedin
Facebooklinkedin

Windows 11 Power Options Oddity

OK, here’s one for the “Stranger Things” file. I was checking Power Options on a test laptop yesterday. In fact, it’s one of a pair of nearly identical machines: both are Lenovo ThinkPad X380 Yogas that differ only in SSD brand and OS variant (this one runs Beta Channel, the other one Dev). Yet this machine will show only two power plans under Power Options (see lead-in graphic). The other one shows all default items just as it should, and then some (see below) .

Windows 11 Power Options Oddity.devchannelx380

The Dev Channel X380 lets me view or hide additional plans; the Beta Channel X380 does not. What gives?
[Click image for full-sized view.]

Working Around Windows 11 Power Options Oddity

To attempt to fix the issue, I worked my way through the various — and terrific — Power Options tutorials over at ElevenForum.com. These include the following items:

Of those items, the first put the X380 in a state where I could restore missing power plans. The GUIDs for other plans remained available, but I couldn’t get the utility to offer an “Unhide” option so it would only show two Power Plans at any given moment. That said, having made other Power Plans accessible that workaround proved good enough for me.

Even the Master Remains Baffled

I exchanged a series of private messages with Shawn Brink, fellow WIMVP and a primary operator and tutorial writer at Eleven Forum on this mystery. We ended up concluding that a Lenovo OEM power management driver might be impacting the built-in Power Options control panel widget. I found and installed a new (Nov 29, 2022) Lenovo Power Management Driver for Windows 11.

At first, it made no difference in Power Options behavior. Following a reboot, though, while I still could not unhide other power plans in the initial Power Options pane shown as the lead-in graphic, when I click “Create a power plan,” it now shows all three default items correctly — namely Balanced, Power Saver and High Performance.

Windows 11 Power Options Oddity.partial fix

Here’s progress, of a sort. All the defaults show up when creating a custom plan. [Click image for full-sized view.]

I still have to work around the lack of an unhide capability to access invisible power plans using PowerShell. But at least I can now access and use all  such power plans. This time, close enough is also good enough. Sigh. And that’s how things sometimes go, here in Windows-World.

Note Added January 23

I built an ISO to match the currently running beta image (22623.1180) from UUPDump.net. Then, I performed an in-place repair upgrade. I’d hoped this would fix the Power Options oddities. No dice: apparently, this is among the few problems that a prair install won’t fix. Sigh again.

Facebooklinkedin
Facebooklinkedin

Windows Will Gain Added AI-Based Capabilities

Interesting news from Microsoft at CES recently. This comes thanks to a “guest slot” from Panos Panay in tandem with AMD’s CEO Dr. Lisa Su. It seems that Windows will gain added AI-based capabilities, courtesy of increasing proliferation of AI engines in hardware. (Case in point: cutting-edge AMD Ryzen chips working with added, Azure-based AI engines in the cloud). The initial impact will be to improve user interaction via language models, eyeball tracking, and more.

Here’s what Panay actually said, as quoted at Neowin:

AI is going to reinvent how you do everything on Windows, quite literally. Like these large generative models, think language models, code gen models, image models; these models are so powerful, so delightful, so useful, personal. But they are also very compute intensive, and so we haven’t been able to do this before. We have never seen these intense workloads at this scale before, and they’re right here. It’s gonna need an operating system that blurs the line between cloud and edge, and that’s what we are doing right now.

What Windows Will Gain Added AI-Based Capabilities Means…

This is happening as Microsoft continues doubling down on AI investments and technologies. Its support for the Open AI initiative is ongoing. It announced an Azure Open AI Service on January 17, along with a ChatGPT API for developers (source: Thurrott.com). The joint appearance with AMD at CES underscores the importance of integrating local hardware support and AI workloads in the cloud. Reading between the lines,  that’s how Windows 12 ups the ante for what an OS can be and do for users.

At the same time, this draws another “dividing line” for PC hardware. Indeed, it may very well limit (or restrict) who can use (or make the most of) upcoming Windows 12 capabilities. MS drew a “security line” for hardware capable of upgrading to 11. This may also draw an “AI line” for 12. That should be interesting to watch, and follow as things play out over the next couple of years.

Wishing Upon an AI Star

While MS is building out this AI-based and -integrated future, I’d like to ask them to think about building lots of AI user agents (if they’re not already so engaged). What does this mean?

As users interact with the OS, especially in the context of PowerShell (and related platforms, such as MS Power Apps) I’d like to see MS apply AI technologies to assist and automatically automate use of those tools. This could really help to boost productivity, and guide users and admins to desired results more quickly and easily.

Likewise, MS apps could (and probably should) gain AI user agents to observe how users put their capabilities to work. They can also support simple, basic automation, and provide input and insight on how to use such apps more efficiently and effectively as well.

I see great things coming from AI right now. I see even better things coming from AI in the future, especially as local PCs gain enhanced abilities to handle and coordinate AI workloads in edge computing fashion. This could provide the impetus to move users away from Windows 10 to more modern versions, even if another hardware upgrade is required — but only if the gains provided offset the costs and learning curves involved. Fingers crossed!

I was around for for one “AI wave” in the 1980s that involved Xerox Dolphin machines with LISP processing. I watched two other such waves roll out in the 90s and 00s for various niche markets and applications. Today, it seems like this wave is a tsunami that could change everything. Hopefully, in a good way. We’ll see…

Facebooklinkedin
Facebooklinkedin

WIMVP Award Extended for 2023

I’m so tickled! At the tail end of yesterday, official word arrived in my inbox from Microsoft. My Windows Insider MVP (WIMVP) status goes on for another year. That’s right: with the WIMVP award extended for 2023, it’s now been six (6) years since I joined the ranks of elite Windows advocates and insiders. Woo hoo! The lead-in graphic shows the header and the first paragraph from the official notification.

First things first: I’d like to thank Microsoft for adding another year to my WIMVP tenure. I’d also like to express my particular thanks to Brandon Patoc and the rest of the Insider Team for their ongoing help, information and support. Thanks also to the Lenovo Global Technology Communications team — most notably, Jeff Witt and Amanda Heater — for sending me the many evaluation and loaner units that have provided much of the fodder that drives my analyses and investigations. I couldn’t do it without ya, so thanks again!

WIMVP Award Extended for 2023: Next?

I’ll be keeping on with my daily blog posts here at edtittel.com. I’ve got upcoming and ongoing assignments for Windows coverage with ComputerWorld, various TechTarget outlets, and am preparing to pitch Tom’s Hardware for an ongoing series of troubleshooting reports. (Fingers crossed, it will be accepted!)

Topics of ongoing interest for 2023 will include:

  • Tracking and reporting on Windows Insider and production releases, updates, issues and fixes for Windows 10 and 11.
  • Continued investigation and testing of USB4 and Thunderbolt 4 tools and technologies, particularly those for docks and related peripherals (mostly USB-C).
  • Ongoing reporting on PowerShell approaches and techniques for managing Windows updates, clean-up and troubleshooting. Special emphasis on Winget and related third-party update tools.
  • Daily reports from the Windows trenches, as things happen and I figure out how to fix or work around them.
  • Other observations and ruminations on Windows growth, change and topics of interest and concern.

To some extend, it will be more of the same. But new things are always happening and popping up in Windows World. As I figure out what’s important or noteworthy, I’ll be sure to comment and point out useful, relevant resources from MS and third parties.

More About the WIMVP Program

To learn more about this program, which “recognizes technology experts and community leaders who are passionate about Windows and positive Windows advocates within their communities…” visit the WIMVP home page. Find my updated entry in the program amidst the WIMVP award holder listings (scroll down to “Get to know Windows Insider MVPs” and look around from there). Cheers, and thanks yet one more time.

 

Facebooklinkedin
Facebooklinkedin

2023 Gets Underway For Real

OK, then. The family is back from our later-than-usual winter vacation. On Saturday we returned from San Diego. This morning, son Gregory hopped another silver bird to return to school in Boston. So now, I’m catching up my modest PC fleet as 2023 gets underway for real here at Chez Tittel. As usual, there are numerous interesting items to report.

Once 2023 Gets Underway for Real, Then What?

First things first: I’m checking and updating all the Windows PCs around here. Here’s what things are looking like by some numbers — namely Winget updates and SUMo items:

PC Name         Winget     SUMo Items
i7Skylake          4           6
Surface (Pro 3)    1           3
X380Test           6           3
X380              12           9
P16 (Mobile WS)    1           4
X12 Hybrid Tablet  3           3
X1 Extreme         2           9
Yoga 7i            5           9
D7080 (wife PC)    1           4
AMD5800X           6           8

Of course, the time these various systems spent untended before the break affects the number of updates they need. It’s no exaggeration to observe that those with more updates in both columns (Winget and SUMo) had been idle longer than those with fewer (especially X380 and the AMD box).

Total time required to get everything caught up (except for the Lenovo P360 Ultra, which is still in the closet upstairs) was just under 3 hours. I learned a few interesting things along the way, too.

Update Lessons Learned

Zoom won’t auto-upgrade to the latest version in one jump. I had to upgrade several systems twice, to work through the sequence of updates since they were last accessed. Sigh.

I did finally find the new versions of Asrock App Shop, RGB Sync, and Restart to UEFI. I haven’t tried them on my Z170 mobo yet, but am curious to see if old and new are still close enough to work. And indeed, the new B550 targeted software still works on the old Z170 motherboard. Go figure…

For some odd reason, SUMo wants users to upgrade to beta versions of Firefox and SpaceDesk. I’m NOT going there, because I want my production PCs to run production software. If you make use of this otherwise excellent tool, be sure to check the provenance of recommended updates (like those two) before blindly following along.

2023, here I come. Stay tuned…

Facebooklinkedin
Facebooklinkedin

Winget Upgrade Include Unknown Gets Ilustrated

Here’s an interesting tidbit. I checked for upgrades this morning on my production PC. Winget informed me “1 package has a version number that cannot be determined.” It recommends using the “–include-unknown” parameter. And presto! Winget Upgrade include unknown gets illustrated nicely in forthcoming results. See the lead-in graphic…

When Winget Upgrade Include Unknown Gets Ilustrated…

An abstract explanation that Winget may not recognize an update’s version is one thing. But the example in the preceding graphic is clear and unmistakable. First, Winget finds no installable packages. It recommends using –include-known. Once used, an upgrade is found — and installed — without difficulty. How clear is that?

I’ve been using Winget daily on most of my PCs for more than six months now. Along the way, I’ve learned a lot about how (and when) it works best. Winget is now essential for my maintenance regimen. The foregoing illustration explains nicely why using –include-unknown is customary. It’s a peach!

Winget Upgrade Include Unknown Gets Ilustrated.SUMo

SUMo sees things that need updates (applications mostly, but also some apps) that Winget does not.

Where Winget Comes Up Short

Please examine the preceding screencap. It shows 4 updates and upgrades that Winget misses. That same shot also shows why I still use KC Softwares’ Software Update Monitor (SUMo, depicted).

Indeed I also use PatchMyPC updater as well. That’s mostly because while it doesn’t catch everything that SUMo does, what it does catch it also updates automatically. SUMo only does that if you use the for-a-fee version (and even then, it doesn’t always do it automatically, either). Sigh.

In addition to the items shown, other things occasionally pop up that Winget misses. Other browsers (e.g. Chrome) may appear, as do some apps/applications, including Kindle, Nitro Pro, and more. I’ve learned how to handle all of them by now — or not, as is sometimes a good idea. For example: I’ve never been able to find the version of ASRock APP Shop (2.0.0.3) that SUMo claims is current. There are a few other such “false positives” but nothing too major. Please read my December 28 item “Windows 10 OCD Update Stymied” for further ruminations on this topic.

‘Nuff said, for now!

Facebooklinkedin
Facebooklinkedin