Woo hoo! Just got the email today from the Windows Insider team. Seems they accepted my (belated) renewal application for Windows 10/Windows Insider MVP. So I’m in the program for another year, and will be attending the MVP Summit in Redmond and Bellevue in March (3/17-22). I really, really enjoyed last year’s meetings. Thus, I’m looking forward to a happy repeat in about three months. That’s one major reason I’m really tickled that my Windows Insider MVP renewed 2019.
The upcoming conference is one of the program’s best benefits. Last year, over 2,100 MVPs of all kinds (and related insiders) attended the conference.
The coolest thing about the 2018 MVP Summit was that over half the attendees came from the Eastern Hemisphere. It’s the first big conference I’ve ever attended in the US that had “natives” in the minority. That made it very cosmopolitan, and way cool.
What Windows Insider MVP Renewed 2019 Really Means
Sure, the program does include benefits. We get free MS subscriptions, access to regular online meetings with MS employees, and inside information from time to time. About that last item: anything hot is under NDA, so please don’t ask me for inside scoop. Sorry: sharing not allowed! But the real and best benefit is access to a savvy, active and knowledgeable community of experts, practitioners, and developers. I get to rub shoulders with most of the TenForums team (the core group that runs the site), plus people like Ed Bott, Rafael Rivera, Greg Carmack, Andre da Costa, Dan Godin, Jason Coombes, Corrine Chorney, Sherry Malik, Richard Hay, Nuno Silva, and a whole bunch more.
There’s also a Yammer set up just for Windows Insider MVPs. I get a daily dose of info and discussion from those colleagues there, too. It often provides an excellent source for info about Windows 10 issues, sometimes with answers or workarounds, too. It’s a great program, and I’m proud and pleased to find myself still in it. Happy New Year, all!
I watched a significant anniversary for this blog slip past earlier this year. Depending on how you count, it hit its tenth-year anniversary this year. September 29 and October 1 of 2008, featured the initial announcement and the first post of substance, respectively. The reigning title at inception was “Vista Enterprise Desktop.” When Windows 7 came along, the name changed to follow suit. By the time 8 arrived, TechTarget and I agreed something more enduring would be good. Windows Enterprise Desktop (WED) proved more durable and descriptive. And that’s what it’s been ever since.
The original list of proposed topics, with a little tweaking remains surprisingly relevant even today. If you like, you can find that whole list in Post#1: Welcome to Vista Enterprise Desktop. Here’s an abridged sampling of key elements:
Working with Windows Upgrades
Dealing with failed Microsoft Updates
Managing application compatibility
Setup, configuration, updates, maintenance, and uninstalls for Windows
Windows deployment tools
Windows Automated Installation Kit (WAIK)
Using the Windows Preinstallation Environment (WinPE)
Working with Sysprep
Desktop virtualization and VMs
A ten year anniversary for a blog that now covers Windows 10 deserves a numeric image, yes?
[Source: Miguel A. Padrinan, Pexels 10161133]
When Windows Enterprise Desktop Turns Ten Years Old, What Does History Say?
To a large degree, these topics still inform and drive the kind of coverage I provide in WED today. Looking back at the WordPress environment in which the blog runs, I see nearly 1,500 posts (1,499 to be exact) of which I wrote 1,427. That works out to roughly 143 posts per year. My contract with TechTarget actually calls for me to provide 12 posts a month at a frequency of three posts per week (144 per year). Given vacations, illness, family situations, and the way life sometimes interferes with work, I’d say this proves I’ve come as close to meeting my commitments as anybody could.
This blog has been pretty popular with TechTarget readers, too. Each of the most visited blog posts (the top 10) averages 6,700 page views. The most popular of them all, at nearly double the average (12,277), dates back to 2011. Surprisingly, it deals with Microsoft Security Essentials (MSE). MSE was a precursor to Windows Defender, available as a free add-on to Windows 7. Actually, while those details are stale now, the general advice it offers still describes a good all-around approach to dealing with Windows updates, and the problems they can occasionally cause. Most of the rest of the top 10 posts feature interesting and possibly helpful troubleshooting and problem-solving advice. I’d to think that’s what keeps the readers coming back. Average annual pageviews have been over 200K for the past 7 years, so at least some readers appear to agree.
As WED moves into its second decade, let me wish readers a happy New Year. May you all have a safe and prosperous 2019, with surprises mostly pleasant, and a rising tide to float all boats. I hope you’ll stick with me for another ten years or longer. RIP 2018, here comes 2019!
Found a simply magnificent MS reference thanks to the great folks at TenForums today. With special thanks to user Caledon Ken, check out this technical guide entitled “Resolve Windows 10 Upgrade Errors.” Thankfully, it brings a huge amount of valuable and useful technical advice together in one place. It’s especially informative for those seeking insight and possible fixes for upgrade issues and errors.
Trust me: This innocuous title does no justice to the Guide’s many treasures.
Exploring the Windows 10 Upgrade Errors Guide
Really, you want to spend some time curled up with this reference. While you’re at it, get comfortable and grab a beverage. In fact, you’ll find yourself immersed in this material for half an hour or more. It’s simply chock-full of good and useful information.
Need proof? No problem. Next, I reproduce the Topic Index from the Guide (with live links) verbatim as the best possible advertisement for its wealth of riches:
Quick fixes: \Level 100\ Steps you can take to eliminate many Windows upgrade errors.
SetupDiag: \Level 300\ SetupDiag is a new tool to help you isolate the root cause of an upgrade failure.
Troubleshooting upgrade errors: \Level 300\ General advice and techniques for troubleshooting Windows 10 upgrade errors, and an explanation of phases used during the upgrade process.
Windows Error Reporting: \Level 300\ How to use Event Viewer to review details about a Windows 10 upgrade.
Upgrade error codes: \Level 400\ The components of an error code are explained.
Result codes: Information about result codes.
Extend codes: Information about extend codes.
Log files: \Level 400\ A list and description of log files useful for troubleshooting.
Log entry structure: The format of a log entry is described.
Analyze log files: General procedures for log file analysis, and an example.
Resolution procedures: \Level 200\ Causes and mitigation procedures associated with specific error codes.
0xC1900101: Information about the 0xC1900101 result code.
0x800xxxxx: Information about result codes that start with 0x800.
Other result codes: Additional causes and mitigation procedures are provided for some result codes.
Other error codes: Additional causes and mitigation procedures are provided for some error codes.
Submit Windows 10 upgrade errors: \Level 100\ Submit upgrade errors to Microsoft for analysis.
Windows 10 Upgrade Errors Explained
Let me help to make sense of this gem. Please understand that Level 100 is Basic, 200 Moderate, 300 Moderate advanced, and 400 Advanced in terms of technical level. In fact, the actual entry that caught my eye was the one for error code 0xC1900101. It includes a raft of tried-and-true techniques for avoiding errors that sometimes occur during the upgrade process. Among other good suggestions, these include:
- Uninstall antivirus applications beforehand
- Remove all unused/unnecessary SATA devices
- Remove all unused devices and drivers
- Update drivers and BIOS, especially the graphics/display driver(s)
- Disconnect all peripherals except keyboard, mouse and monitor
- Take the “Download and install update updates (recommended)” offer at the outset of the upgrade process
Great stuff. I’ve learned, used, and needed every single one of these exhortations over the years. Add this Guide to your bookmarks or favorites. You’ll be back!
When a program gets installed onto Windows, it can extend all kinds of hooks into the OS. It might make numerous Registry changes, add services, schedule tasks, and much, much more. When the same program gets uninstalled, even its makers may have trouble completely rooting out all traces of its former presence. That’s one reason why specific “removal tools” exist for a range of applications. These include things like security software or heavy-duty devices such as graphics cards.These programs are seldom standalone. Rather, they are best understood as tool suites, collections of intertwined programs. Where so much infrastructure needs cleaning up, removal tools can help. For cleaning up graphics card drivers and their attendant tool suites, Display Driver Uninstaller (DDU) is a nonpareil. That’s why I assert that DDU removes display drivers completely.
As you can see from the preceding tagline, the latest DDU version arrived on 12/20/2018, as of this writing. [Download page for 184.108.40.206.]
Why DDU Removes Display Drivers Completely Is a Good Thing
DDU is a free program (donationware) that comes from software toolmaker Wagnardsoft. You can always download the program from the Wagnardsoft home page, under the “Software” heading there. I’ve known about this tool for years, which does an ace job of rooting out any and all traces or remnants of Intel, Nvidia, and AMD graphics drivers.
I’ve used DDU on numerous past occasions. Recently, I had to put it to work on a couple of my PCs. Two of my PCs include GeForce GTX 1070 graphics cards. Nvidia’s been issuing beaucoups graphics drivers lately, not all of which have agreed with my 1809 or 19H1 Windows 10 installations. In fact, I’ve been subject to a spate of LiveKernelEvent (Code 117) errors lately on both machines. Turns out that issues with a couple of November and December GeForce drivers have been responsible.
It just so happens that when graphics driver errors recur, it’s often a good idea to root them out completely. After that, a clean install of a newer, better, or different driver may address (or prevent) further issues. That’s what I used DDU for last week, just before I upgraded to GeForce 417.35 on those machines. No subsequent problems since, either. DDU is worth knowing about because it can sometimes resolve graphics driver issues amenable to no other solution. Don’t bother to download it until you need it, though: the folks at Wagnardsoft update it regularly (usually in synch with driver releases from AMD, Intel and Nvidia).
On November 19, I wrote a blog post about an “interesting” UI issue in Event Viewer. On some PCs, its pulldown menus didn’t work properly unless the display on which the tool runs was set to 100%. Because the Win10 default for True HD and higher resolution monitors is 125%, this means the program may not work properly unless jiggered with. Now, it seems, the same phenomenon also affects Task Scheduler. In fact, Win10 Task Scheduler pulldown menus fail under those very same circumstances on some PCs.
Unless this display on which the pane appears is set to 100%, that list of months is absent. I was able to replicate this on some 1809 (Build 17763.195) and 19H1 (Build 18305.1003) PCs.
[Click Image for Full-Sized View.]
If Win10 Task Scheduler Pulldown Menus Fail, What Else?
If you look at properties for both Event Viewer and Task Scheduler, you’ll see that they are Microsoft Console (.msc) files. Furthermore, you can find at least 44 such files in the C:\Windows\System32 folder. Just for grins I did a random sampling of those files, including tools I know well. I looked at Device Manager, Local Security Policy, Group Policy Editor, Services, Certificate Manager, Performance Monitor, Reliability Monitor, Disk Management, and more.
None of those other consoles suffered from the pulldown menu fail at alternate resolutions. In some cases, that was because they didn’t use pulldown menus much, or at all. In other cases, pulldown menus worked as they should. Thus, I’m not able or willing to assert that this issue is more general than it appears. In other words, AFAIK only Event Viewer and Task Scheduler appear subject to this gotcha.
That said, when using a different Windows Console if you find yourself unable to access pulldown menus in the future, you might want to try changing your display resolution to 100%, at least temporarily. It might just cure what ails ya!
On the other hand, your PC(s) may not be subject to this gotcha. When I reported this to my friend and business partner Kari Finn, he was unable to repeat this issue on either a 4K display or a 1920×1080 Full HD display, at any resolution. He tried 100%, 125%, 150% and 175% and it worked fine for all of them. Apparently this is a hit-or-miss gotcha. If it doesn’t hit you (or your PCs), no worries. If it does, you know what to do: reset display resolution to 100% long enough to do what you must, after which you can revert to whatever you like.
A few weeks ago, I got an offer from a Logitech pop-up for a program named Logitech Options. I’ve been using Logitech mice since the 1990s, and have long been a fan of their various widgets. Figured I to myself “let’s give it a try.” Thus, I downloaded and installed the app without too much thought or reflection. The install process went swimmingly, and caused no visible issues. But I shoulda read the fine print, as the old saying goes. Over time, I realized that Logitech Options prove unnecessary on my PC. It does nothing because it’s incompatible with my M325c mouse and its Unifying receiver. In fact, here’s what I saw when I finally ran the program:
Lights on, but nobody home. Logitech Options doesn’t see my transceiver or mouse!
Learning Logitech Options Prove Unnecessary
As is often the case when I hit a Win10 snag, I turned to TenForums.com, where I posted my observations to this thread there “Latest Logitech Options Software.” It turns out that I should’ve read the “Works with these products” pop-up on the download page for Logitech Options before installing same. My M325c mouse, as you may have already guessed, appears nowhere on that list. The software detects no devices on my PC for the best of reasons. As it happens, the devices I use aren’t among the devices it can handle. Oops!
Getting rid of Logitech Options turned out to be easier than I thought. Given that it’s a UWP app, I thought I might have to research and run some PowerShell commands to make it disappear. Not so. I was able to use Revo Uninstaller to get rid of it. Noticing that my SetPoint Software did not spring back into action or availability after Logitech Options was removed, I read the fine print for it, too. Turns out I don’t need that software, either. (See the “When you don’t need SetPoint” section for those details.) So I removed it as well.
I’m happy to report that my Win10 install is now two (unneeded) applications lighter, and that my M325c mouse continues working as well as ever. Just because the vendor makes driver or special use software available doesn’t mean you need to install and/or (not) use it. Live and learn, my friends!
As of December 17, the latest version of Windows 10 is publicly available. Its version name is 1809. This indicates September 2018. After a trouble-wracked initial release on October 2, MS took 6 weeks to start dribbling out 1809 to a subset of users once again. Now, the latest word from the Windows 10 Update History page is “the taps are open!” Thus, it’s finally safe to proclaim Win10 1809 publicly available. Here’s a snip from the afore-linked Web page:
As of Monday (12/17), anyone who manually selects “Check for updates” in WU will get the 1809 upgrade. It’s been a long time coming.
[Click image for full-sized view.]
Win10 1809 Publicly Available, Now What?
Just because this update is available, does this mean that wholesale upgrades are a good idea? As with many interesting questions, the real answer is “That depends…” There are still enough potential gotchas out there — see Martin Brinkmann’s GHacks story for a good summary — to make “try it and see” the right approach to this upgrade. In other words, I wouldn’t recommend jumping on the upgrade without first making an image backup. Then, if something goes sideways, you’ll also want to have a bootable USB flash drive (UFD) with backup/recovery capability ready for action. Should the upgrade fail or manifest issues, use the UFD to restore the previous version and wait for the next Cumulative Update to 1809 to try again.
For me, this approach is SOP for Win10 feature upgrades anyway. I use the excellent Macrium Reflect Free. It includes a Rescue Media facility, which builds a bootable UFD with built-in backup recovery capability. I generally make an image backup just before applying a feature upgrade. Then, if the upgrade doesn’t complete (or the PC bluescreens or won’t boot), I can simply boot to the rescue UFD and tell it to restore that backup and keep on trucking. And FWIW, if the upgrade does succeed, I make another backup after I clean up Windows.old and the system disk. That way I can get back to a pristine image of the latest version any time I might need to. Please consider doing likewise yourselves: this strategy minimizes downtime and inconvenience.
Drat! I really like the built-in Windows 10 Deployment Image Servicing and Management (DISM) command. But I’ve discovered some DISM schisms. They embrace Version 1809 (Build 17633.134) and the Insider Preview (Build 18298.1000). Usually, DISM supports get and set operations for something called OSUninstallWindow. This describes the command’s ability to query (get) the number of days the OS will keep a previous version around after an upgrade. There’s also a corresponding command to change that number (set). Right now, neither will run with current Win10 versions. That leads me to claim OSUninstallWindow DISM difficulties.
Detecting OSUninstallWindow DISM Difficulties
It’s pretty easy to tell these commands don’t work as they should. On Version 1809, they throw “Error 3: The system cannot find the path specified.” On Version 19H1 (Build 12298), they throw “Error 1168: Element not found.” I’ve reported this to the Windows 10 Feedback Hub under the title “dism /online /get-osuninstallwindow not working.” I hope you’ll check the status on your Windows 10 PCs and upvote this item if you experience the same errors. I’ve checked all 9 PCs here at Chez Tittel, and all are subject to these errors. [As explained in the concluding section below, these errors will present on any PC where Windows.old has already been cleaned out.]
Here’s an illustration from a 19H1 Insider Preview test machine. It shows proper syntax for both commands in an admin PowerShell session. You can run them in an Administrative Command Prompt window, if you prefer.
Something, somewhere is going sideways with this usually ho-hum, dead easy DISM command sequence.
At present, default value for the OSUninstallWindow is 10. In fact, that means ten days. Thus, on Day 11 after you upgrade Windows 10, it fires off a disk cleanup task that gets rid of Windows.old and other leftovers from an upgrade install. When the aforementioned DISM command (Set-OSUninstallUpgrade) is working, that’s easy to change. But for the time being, it’s stuck at 10 days. You’ve been warned!
Again: check your PCs. If one of these errors pops up for you, please upvote my Feedback Hub item. Look for “dism /online /get-osuninstallwindow not working.” Thanks in advance for your help and support!
Explanation for the Errors
Having now spent a bit more time researching this matter, and working with my friend and business partner Kari Finn, I’ve got it figured out. These DISM commands work only if a Windows.old folder is present on the system drive. The retention info is apparently stored within that folder structure. If it’s not around, you can neither get nor set the value for OSUninstallWindow. How do I know? Because when those commands run on a Windows 10 install with Windows.old present, they work as advertised. When Windows.old is absent, either the path is missing or the item is absent depending on Win10 version.
I disagree with Microsoft’s implementation. To my way of thinking, right or wrong, the retention interval is an abstract value. Users should be able to set it whether Windows.old is present or absent. But that’s not how Microsoft handles the OSUninstallWindow. Thus, I’m changing my feedback hub request to ask them to turn it into a Group Policy or a Registry setting. It shouldn’t depend on the presence or absence of a specific folder hierarchy. ‘Nuff said.
Here’s an interesting tidbit of information, courtesy of Forbes magazine. That story references a December 10 Windows Insider Program blog post. It’s from Michael Fortin, MS CVP for Windows, entitled “Windows monthly security and quality updates overview.” In that memo, Fortin identifies update release labels: B, C, and D. The B release comes in the second week of the month: it’s the usual Patch Tuesday stuff. Likewise, C and D releases to WU come in weeks 3 and 4, respectively. Thankfully, Fortin describes C and D releases clearly. “These are preview releases, primarily for commercial customers and advanced users ‘seeking’ updates.” Thus, my post title that late-month WU items equal update previews. Like I said: interesting, eh?
Knowing recent Patch Tuesday dates are 11/13 and 12/11, it’s easy to tell that several updates shown here may qualify as “previews.” One 12/6 item even says “Preview.”
[Click image for full-sized view.]
What Late-Month WU Items Equal Update Previews Really Means
In addition, the afore-cited blog post explains further about C and D releases:
These updates have only non-security fixes. The intent of these releases is to provide visibility into, and enable testing of, the non-security fixes that will be included in the next Update Tuesday release. Advanced users can access the “C” and “D” releases by navigating to Settings > Update & Security > Windows Update and clicking the “Check for updates” box. The “D” release has proven popular for those “seeking” to validate the non-security content of the next “B” release.
OK, then. What does this really mean for run-of-the-mill users? Admins working on test/staging PCs? For one, ordinary users should “wait for WU updates.” Jumping early means installing preview level update code. For others — namely, admins, power users, and insiders — this is stuff for which advanced access is helpful. In fact, this goes double if you’re trying to create canonical images for your next upcoming, scheduled in-house update cycle.
If you want to play the WU game well, it helps to know the rules. Though they come as a bit of a surprise, I’m still grateful to Mr. Fortin and MS for clarifying things somewhat.
Last week, I blogged about Intel Windows 10 Modern Drivers. As it turns out, there was more going on with that than I recognized. In addition to a new set of drivers, Intel also offers a new set of UWP software as well. By grabbing the latest version of the Intel Ethernet Adapter Complete Driver Pack, downloaders will get a copy of a UWP-based PROSet tool. Because it’s named the Intel ProSet Adapter Configuration Utility, this blog post is entitled Intel Win10 UWP configuration utility. Here’s what it looks like:
This handy utility runs from the Start menu, and provides all kinds of useful information about and control over Intel Ethernet adapters
[Click image for full-sized view.]
What’s in the Intel Win10 UWP Configuration Utility?
If you inspect the preceding screenshot, you’ll see four panes of information inside its window. The left-hand pane lists all Intel Ethernet adapters present on the host PC. There are two panes in the center. Up top, you’ll find adapter info, including bus type, driver name, media type, and so forth. Down below, you’ll find buttons for cable, connection and hardware tests. There’s a display area at the very bottom of the pane for test result display. At right, users can access and update each network interface’s adapter settings. Previously available only in Device Manager’s Advanced Connection properties window, this interface is less cramped and more friendly.
I did encounter a couple of gotchas when using the tool, though. After running either the Cable or Connection tests, the network interface would drop off the network. This proved easy to fix, however. A restart does the trick. So does jumping into Device Manager, after which you’ll disable then re-enable the affected network interface. Either maneuver restores the network to normal, proper operation. Hopefully, some alert Intel networking developer will read this blog post, and take corrective action for an upcoming tool update.
Nevertheless, this tool is worth downloading, installing and using, IMO. If you try it yourself, I hope you’ll agree.
[Note added after initial publication] The runtime for this software also includes some interesting PowerShell stuff. Read this support note “Intel PROSet for Windows PowerShell Software” and you’ll be able to try this stuff out for yourself. Works like a champ!