KB4012218, KB4012219: Windows Update processor generation detection

The March 2017 preview updates for Windows 7 and Windows 8.1 introduce Windows Update processor generation and hardware support detection.
Microsoft published KB4012218 for Windows 7 and Windows Server 2008 R2, and KB4012219 for Windows 8.1 and Windows Server 2012 and 2012 R2 yesterday evening.
These previews are only available through the Microsoft Update Catalog, and only include non-security updates.
They are designed to give system administrators, and interested home users, time to test cumulative updates for the operating systems they are released for before they are pushed out through Windows Update on the next Patch Day.
What's particularly interesting about these two preview updates is that they introduce the detection of the device's processor generation and hardware support.
Both include the following entry:
Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.
As you may know, Microsoft announced some time ago that it would not support the latest generation of processors on older versions of Windows. To hammer this home even more, Microsoft revealed that it will block updates on older versions of Windows if the device was powered by a processor of the latest generation.
Test showed that this was not the case at the time of revelation. It appears now though, that the updates KB4012218 and KB4012219 introduce that functionality on Windows 7 and Windows 8.1 (and the server versions).
Tests need to be conducted to find out whether this is indeed the case when the release updates are made available though.
For now though, it seems like a good idea to avoid these patches if your Windows device uses a cpu of the latest generation, or if you plan to equip it with one in the future.
KB4012218
- List of changes: On Windows 7 and Windows Server 2008 R2 update history page.
- Direct downloads: on Microsoft Update Catalog.
- KB4012218: support article.
Changelog:
- Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.
- Simplified listing of Approved Servers in the Point and Print group policies by allowing wildcards in the server name.
- Addressed issue that produces corrupt output when using fread() to read data from a pipe. The runtime will sometimes drop the newlines between lines.
- Addressed issue to update time zone information.
- Addressed issue with the Local Security Authority Subsystem Service process that crashes on the domain controller when making certain Lightweight Directory Access Protocol requests.
KB4012219
- List of changes: On Windows 8.1 and Windows Server 2012 / 2012 R2 update history page.
- Direct downloads: on Microsoft Update Catalog.
- KB4012219: support article.
Changelog:
- Enabled a warning message in Group Policy Management Console (GPMC) to alert administrators of a design change that may prevent the processing of a User Group after installing security update MS16-072.
- Addressed issue that prevents a smart card module from pairing with a contactless smart card reader.
- Addressed issue where a Scale-Out File Server that uses dual parity disks loses access to a disk if a disk fails while the parity log is being written.
- Addressed issue with the Spaceport driver that causes disks to detach after a hard restart.
- Addressed issue in multipath I/O when Driver Verifier is enabled.
- Addressed issue that causes workload disruption in Azure StorSimple appliances after installing KB3169982. Installation occurs using the KB3172614 rollup (released 2016.07).
- Addressed issue that causes crashes in a customer’s data path management software because of a regression in multipath I/O after installing KB3185279, KB3185331, or KB3192404.
- Addressed issue where installation of KB3121261 on a third-party, thinly provisioned Storage Area Network causes multipath I/O Event ID 48. This is in response to Small Computer System Interface status - 0X28 - SCSISTAT_QUEUE_FULL (SRB Status - 0X4 - SRB_STATUS_ERROR).
- Addressed issue to provide PowerShell cmdlets that enable and gather diagnostics for storage spaces.
- Addressed issue with multipath I/O failure that can lead to data corruption or application failures.
- Addressed issue that causes File Explorer to hang when performing a search on a network drive while connected using the Remote Desktop Protocol.
- Addressed issue that causes a crash when the user tries to connect to the server using WinShare and Remote Desktop Services. Stop error 0x50 at win32k!pDCIAdjClr+0x4f.
- Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.
- Improved support for networks by adding new entries to the Access Point Name (APN) database.
- Simplified listing of Approved Servers in the Point and Print group policies by allowing wildcards in the server name.
- Addressed issue to update Windows Defender on Windows 8.1.
- Addressed issue that prevents clients from accessing a file server when using Server Message Block 1.0 and NT LAN Manager authentication after installing MS16-110/KB3187754.
- Addressed issue that produces corrupted output when you use the fread() function to read data from a pipe.
- Addressed issue to set and persist the Quality of Service settings on a per-host basis.
- Addressed issue that breaks high-availability and fail over of a clustered virtual machine (VM). This occurs when the default data store settings for the VMs are configured inconsistently across the nodes in the cluster. For example, some data store settings are in %ProgramData%, while others use shared storage.
- Addressed issue where, under high load, the background tasks threads are blocked. None of the clusters that use Virtual Hard Disk Sharing can access their disks. This results in unresponsive virtual machines.
- Addressed issue (error 0x800b) that causes System Center Virtual Machine Manager to fail after live migrating a virtual machine between two Hyper-V clusters.
- Addressed issue where false file conflicts occur when Windows Server Work Folders is reinstalled after installing Azure Hybrid File Services.
- Addressed issue where share contents go offline if remote clients connect over slow links when encryption is enabled and offline caching is disabled for a server share.
- Addressed issue to generate Remote Desktop Services self-signed certificates to use SHA-2 instead of SHA-1. After this update, any existing self-signed certs in RD Session Host should be updated with SHA-2 certs. However, existing self-signed certs (if any) in Connection Broker and Gateway should be regenerated using the Remote Desktop Management Services (RDMS) UI.
- Addressed issue to allow a user to set the password for a virtual account.
- Addressed issue where IIS Automatic Certificate Rebind feature breaks client certificate mapping with active directory by disabling DS Mapper upon renewal of the server certificate. As a result, no user will be able to access the site unless an administrator manually remakes the binding and enables the DS Mapper.
- Addressed issue where Active Directory returns incorrect active thread count numbers for Lightweight Directory Access Protocol requests. Incorrect thread counts prevent Office 365 from load balancing correctly.
- Addressed issue to update time zone information.
- Addressed issue with random crashes on Hyper-V servers when users access Virtual Hard Disk files on Cluster Shared Volumes.
- Addressed issue that causes file share witnesses stored on a Scale-Out File Server cluster 2012R2 to fail. Event ID for this Error is 1562 and you will get an Error 64 in the Cluster Log for the failed Healthcheck (from RFC 7205769).
- Addressed issue where, after installing security update MS16-123, administrators cannot access some network drives that are mapped using the Distributed File System Namespace. This lack of accessibility occurs even though User Account Control and EnableLinkedConnections are enabled.
- Addressed issue where virtual Network File System (NFS) server shares intermittently fail to mount when another NFS share is assigned the same ID in a clustered environment.
- Addressed issue to add the LiveDump capture feature that will trigger a live kernel dump if requests are stuck for an extended period.
- Addressed issue where Failover Cluster Manager crashes when connecting to a cluster with a long name (15+ characters). This occurs after .NET 4.6.1 is installed.
- Addressed issue that crashes Exchange servers whenever a customer installs an Exchange cumulative or security update. Error code: STOP 0x3B
- Addressed issue that prevents the capture of network traffic when Microsoft Advanced Threat Analytics starts and stops the session that monitors traffic in promiscuous mode.
- Addressed issue where users cannot connect to wireless, proxy, and VPN authentication. The Online Certificate Status Protocol responder service intermittently returns an IIS 500 error when processing client requests. This causes the clients to fail revocation checking and fail authentication to the required service.
- Addressed issue to provide a maintenance mode for Active Directory domain controllers.
- Addressed issue where Active Directory Federation Services (AD FS) fails to authenticate external users because the ADFS proxy servers time out.


What mental age of reader are you targeting with the first sentence? 10?
Why not write an article on how to *avoid* upgrading from W10 to W11. Analogous to those like me who avoided upgrading from 7 to 10 for as long as possible.
If your paymaster Microsoft permits it, of course.
5. Rufus
6. Ventoy
PS. I hate reading these “SEO optimized” articles.
I used Rufus to create an installer for a 6th gen intel i5 that had MBR. It upgraded using Setup. No issues except for Win 11 always prompting me to replace my local account. Still using Win 10 Pro on all my other PCs to avoid the bullying.
bit pointless to upgrade for the sake of upgrading as you never know when you’ll get locked out because ms might suddenly not provide updates to unsupported systems.
ps…. time travelling?
written. Jan 15, 2023
Updated • Jan 13, 2023
This happens when you schedule a post in WordPress and update it before setting the publication date.
Anyone willing to downgrade to this awful OS must like inflicting themselves with harm.
I have become convinced now that anybody who has no qualms with using Windows 11/10 must fit into one of the following brackets:
1) Too young to remember a time before W10 and W11 (doesn’t know better)
2) Wants to play the latest games on their PC above anything else (or deeply needs some software which already dropped W7 support)
3) Doesn’t know too much about how computers work, worried that they’d be absolutely lost and in trouble without the “”latest security””
4) Microsoft apologist that tries to justify that the latest “features” and “changes” are actually a good thing, that improve Windows
5) Uses their computer to do a bare minimum of like 3 different things, browse web, check emails, etc, so really doesn’t fuss
Obviously that doesn’t cover everyone, there’s also the category that:
6) Actually liked W7 more than 10, and held out as long as possible before switching, begrudgingly uses 10 now
Have I missed any group off this list?
You have missed in this group just about any professional user that uses business software like CAD programs or ERP Programs which are 99% of all professional users from this list.
Linux doesn’t help anyone who is not a linux kid and apple is just a fancy facebook machine.
Microsoft has removed KB5029351 update
only from windows update though
KB5029351 is still available from the ms update catalog site
1. This update is labaled as PREVIEW if it causes issues to unintelligent people, then they shouldn’t have allowed Preview updates ot install.
2. I have installed it in a 11 years old computer, and no problems at all.
3. Making a big drama over a bluescreen for an updated labeled as preview is ridiculous.
This is probably another BS internet drama where people ran programs and scripts that modified the registry until they broke Windows, just for removing stuff that they weren’t even using just for the sake of it.
Maybe people should stop playing geeks and actually either use Windows 10 or Windows 11, but don’t try to modify things just for the sake of it.
Sometimes removing or stopping things (like defender is a perfect example) only need intelligence, not scripts or 3rd party programs that might mess with windows.
Windows 11 was a pointless release, it was just created because some of the Windows team wanted to boost sales with some sort of new and improved Windows 10. Instead, Microsoft cannot support one version well let alone two.
Windows 11 is the worst ugly shame by Microsoft ever. They should release with every new W11 version a complete free version of Starallback inside just to make this sh** OS functionally again.
motherboard maker MSI has recently released a statement regarding the “unsupported processor” blue screen error for their boards using Intel 600/700 series chipsets & to avoid the KB5029351 Win11 update:
https://www.msi.com/news/detail/MSI-On–UNSUPPORTED-PROCESSOR–Error-Message-of-Windows-11-Update-KB5029351-Preview-142215
check out the following recent articles:
Neowin – Microsoft puts little blame on its Windows update after UNSUPPORTED PROCESSOR BSOD bug:
https://www.neowin.net/news/microsoft-puts-little-blame-on-its-windows-update-after-unsupported-processor-bsod-bug/
BleepingComputer – Microsoft blames ‘unsupported processor’ blue screens on OEM vendors:
https://www.bleepingcomputer.com/news/microsoft/microsoft-blames-unsupported-processor-blue-screens-on-oem-vendors/
While there may be changes or updates to the Windows 10 Store for Business and Education in the future, it is premature to conclude that it will be discontinued based solely on rumors.
My advice, I left win 15 years ago. Now I’m a happy linux user (linuxmint) but there is Centos, Fedora, Ubuntu depending on your needs.
motherboard maker MSI has recently released new BIOS/firmware updates for their Intel 600 & 700 series motherboards to fix the “UNSUPPORTED_PROCESSOR” problem (Sept. 6):
https://www.msi.com/news/detail/Updated-BIOS-fixes-Error-Message–UNSUPPORTED-PROCESSOR–caused-BSOD-on-MSI-s-Intel-700-and-600-Series-Motherboards-142277
I try to disable the Diagnostics Tracking Service (Connected Devices Platform User Services) but it wont let me disable it, any help will be greatly appreciated.
Tank you for your help