This morning, I learned about a DCH graphics driver from Intel, which adds Windows 11 support. This is the discretionary new Intel 30.0.100.9805 graphics driver. It’s shown in the driver properties for the UHD 620 integrated graphics on my Lenovo ThinkPad X380 Yoga in the lead-in graphic. This driver installed quickly and easily on that test PC, albeit with a self-inflicted gotcha. Let me explain…

Why Say: Discretionary New Intel 30.0.100.9805 Graphics Driver?

Normally, graphics and other key Intel drivers come either through Windows Update or from the Intel Driver & Support Assistant (DSA). This time, things are a little different. I imagine it’s because this driver specifically targets Windows 11 (though it also works on Windows 10) that Intel hasn’t yet targeted it within DSA. Instead one must visit the Intel Graphics – Windows DCH Drivers page. There one must select the 30.0.100.9805 (Latest) version, and download either an .exe or .zip based installer. Here’s what it looks like online:

The download page offers .exe and .zip options.
[Click on image for full-sized view.]

Who Should Grab This Update?

All Intel CPUs 6th generation (Skylake) or newer are on Intel’s “covered platform list” for this upgrade. It works on Windows 10 releases 1809 through 21H1, and on Windows 11. Laptop and tablet users should be aware that OEMs sometimes offer customized Intel graphics drivers through their own update channels. By switching to this Intel update, you forgo those customizations. Some contortions — such as uninstalling the Intel drivers and software — may be required if you want to switch back to OEM drivers later on.

The gotcha I encountered in installing this driver is mostly self-inflicted, but worth reporting anyway. I started the install process through an RDP session from my production desktop. About half-way into the install, the process hung and didn’t advance further. When I ended the RDP session, and logged into the X380 Yoga locally, it picked back up and ran to completion. Sometimes, driver install MUST run locally to work properly. Apparently, this Intel driver requires a local session to run all the way through. By comparison, I did use DSA to update the PC’s LAN and Bluetooth drivers via RDP just before starting the display adapter update for the UHD 620 without issues.

And indeed, that’s the way things went today, here in Windows-World. Cheers!

Right now, I have two PC dedicated to Windows 11 testing and learning. Just recently, I discovered some vexing Windows 11 Antimalware platform update issues. The short version is: one of my PCs is up-to-date. It’s no longer subject to Automatic Sample Submission reset to off following each restart. Alas, the other remains stubbornly stuck on an earlier Antimalware platform release. None of the update options available work, so I can’t get no relief. Let me explain…

Fighting Vexing Windows 11 Antimalware Platform Update Issues

First, let me be clear. This is a known and documented Windows 11 issue. It’s been around since the initial release hit. Indeed, a fix exists: when the Antimalware Platform version gets to 4.18.2107.4 or higher, the problem disappears. For the record that problem is depicted in this story’s lead-in graphic. After every reboot, the Automatic Sample Submission feature for virus uploads in Defender is turned off. The feature is easy to turn back on, until the next reboot. OCD OS maintainer that I am, the workaround isn’t enough for me. I want it fixed, for good, now.

Here’s the vexing part. WU hasn’t yet deigned to update the antimalware engine behind the scenes. Ditto for the Protection updates option in Windows Security. There’s a registry hack documented on a related ElevenForum thread. There’s even a manual Defender update download that’s supposed to take the Antimalware engine release to 1.2.2107.02. It comes in a file named defender-update-kit-x64.zip. Alas, inspection of said update file shows the Antimalware engine to be 4.18.2015.5. It’s too old to fix the issue, in other words. Thus, no relief just yet, shy of a permanent registry hack.

The Perils of Perfectionism

Yes, I could hack the registry to turn this off. But I’d have to unhack it again when the fix finally shows up on the X380 Yoga that’s affected. I’m going to have to wait for WU to get around to providing me the latest antimalware engine on its own, or find a newer manual update. Alas, that’s the way things go sometimes, here in Windows-World. Oddly, I find myself hoping for a new Windows 11 build, in hopes the latest antimalware engine will be part of its contents. Stay tuned: I’ll let you know how all this shakes out.

Note Added August 4: Update Came!

Thanks to long-time and active TenForums and ElevenForum user @Cliff S, I learned this morning that Antimalware Client Version 4.18.2107.4 arrived via WU. Checking my own previously stuck test machine, I saw it too, had gotten this update. And now, my PC no longer reverts to Automatic Sample Submission=Off after each reboot. Fixed!

I’ve also determined this version is available through the Microsoft Update Catalog. Search for KB4052623, and grab the correct version, if WU doesn’t come through for you.

As it turns out, I should’ve read the Microsoft announcement more carefully. The Windows Insider blog post that announced a new Experience Pack warned me that things would be different for Beta Channel and Release Preview PCs. It said: “For Windows Insiders in the Release Preview Channel, this will be an optional update for you.” I just didn’t pay sufficient attention. And that, dear readers, led me to some unnecessary but still effective Experience Pack 120.2212.3920.0 follies yesterday.

What Kind of Experience Pack 120.2212.3920.0 Follies?

The kind where I decided that because WU didn’t offer my Release Preview PC an obvious and immediate download, I would get it by other means. So, I turned to TenForums.com, where sure enough. I found a thread with a link to a reliable online source. Because this was a .CAB file, I then ran DISM /add-package … to get it installed. It worked!

Then I found out that the Release Preview mechanism differed from the Beta Channel one. Beta Channel (Surface Pro 3) got a direct offer from WU. Release Preview had a new item show up as an “Optional Update” — just as the afore-linked blog post said.

Sigh. One of these days, I’ll slow down and pay more attention. I swear. As Jerry Pournelle used to say in his Byte column from Chaos Manor “Real soon now.” Fortunately, there’s usually more than one path between Points A and B here in Windows-World. Yesterday, mine took me off the beaten track, and had me do manually what WU would have done for me automatically. Sigh again.

I did get here eventually, but not via the most direct route.

One More Thing…

I used DISM to install the KB5004393 update on the Release Preview PC (Lenovo ThinkPad X380). Thus it doesn’t show up in WU Update History (unlike the screencap at the head of this story, which came from the Surface Pro 3). Indeed, I had to go into Programs and Features and use “View installed updates” to find it instead. When you do things manually, reporting changes, too. A word of warning, by way of factual observation.

I’ve just learned something potentially useful. As a Windows PC ages, it tends to lose vendor support somewhere along the way. And with that comes missing or incompatible drivers and firmware updates. I’ve hit that point now with my Lenovo X220 Tablet, which was built and purchased in 2012. It was my first-ever touchscreen PC bought to learn touch interaction in Windows 8. But because of increasing decrepitude, I must now say goodbye Lenovo X220 Tablet PC.

Why Say Goodbye Lenovo X220 Tablet PC?

Why? Because it takes longer for me to get the device update ready than it does to apply pending updates. As it’s been a Dev Channel test machine, that’s a lotta updates. Because this phenom includes Defender updates, it’s become a daily thing. Sigh.

I’ve developed a “workaround ritual” to keep the machine updated. First, I try WU by itself. Sometimes, it works. When only Defender updates fail, I next go to the updates button in Windows Security/Virus & Threat protection. If that doesn’t work, I manually download the latest update file and install it “by hand.”

If other updates are involved, I try WUMT. It often succeeds when WU hangs during either download or install phases. Sometimes, I have to reset the entire update environment using Shawn Brink’s Reset_Reregister_Windows_Update_Components.bat file. It’s nearly infallible.

Another problem that’s cropped up is the outright failure of the Intel Management Engine on that PC. I’m not especially worried about that, per se, but this does mean that I must remember to manually strike a key each time the system reboots (and it does so 3 or more times each time any upgrade is installed, which happens weekly on a Dev Channel test machine). Otherwise the system just waits for input before it can proceed further.

When It’s Time, It’s Time…

Long story short, it’s become too time-consuming to work around the X220 Tablet’s limitations and gotchas. I still love this machine, but as a freelancer I always have to keep one eye on the clock and manage my time carefully. This laptop is now more trouble than it’s worth, so I’ll be passing it onto the folks at ReGlue for a wipe and a LInux install. Some schoolkid will still get good use out of its 4-core/8 thread i7 2640M CPU, dual (small) SSDs, and 16 GB RAM.