Hi Guys. Today in this post How to Fix Windows Registry Issues That Prevent Microsoft Security Updates? Microsoft had released Windows Update patches that would be applied either immediately or on the normal Patch Tuesday, Jan. 9. But till now every Windows user not received the updates because the antivirus software they’re using was inconsistent with the update. So, If you don’t know or facing such kind of issues then please follow this proper article from the beginning to the end. Hope this will definitely solve this problem. So without wasting time start following now.
Fix Windows Registry Issues That Prevent Microsoft Security Updates
Windows Registry Issues:
The problem is rooted in the behavior of a few AV stocks that make unsupported requests to the Windows kernel memory.
These signals closely follow actions that are performed by some types of malware and in any case, they can change when Microsoft updates Windows. The result of this behavior is affectionately known as the blue screen of death or BSOD and it happens when Windows crashes.
To get around the BSOD problem, Microsoft is asking companies of AV and anti-malware products to certify that their products are compatible with Windows Update, and if they are, to change a setting in the Windows registry.
The reasons for not setting the key variables, but it’s essentially a matter of the time needed for developers to make and test the changes. But there are a few new anti-malware merchants that are helpful with the new updates but haven’t changed the registry key for reasons that are unclear.
Compounding the issue are computers that for whatever reason can’t run AV software. They’re fully supportive of the update expected for the processor fix, but because there’s no AV running, there’s nothing to make the change. For this reason, Microsoft has published instructions for changing the registry key manually.
If you’re running Windows 10, you should have received the update on or around Jan. 3, 2018. If you’re running anything besides Windows 10, the update should take place on or around Jan. 9, which is the normal Patch Tuesday.
For Windows Server, the situation is somewhat more complicated. You will need to make changes to the Registry, but you will also need to take a number of new steps, including a series of verification steps. Microsoft explains this in a security update article.
It’s also worth noting that PC’s with some AMD processors are also incompatible with the update that’s created to defend against the problem they’re not subject to the Meltdown issue.
According to the relevant Microsoft Knowledge Base entry, those updates have been paused until the issue is resolved. In that case, there’s nothing you can do until Microsoft and AMD work out a solution and publish it.
Once you’ve determined whether your lack of updates is related to your AV software, the next step is to find out whether the software vendor has plans to fix the registry setting problem and plans to make the software compatible with Windows Update, if that’s the issue.
Assuming that you find out your AV vendor’s software is compatible, then you can set the registry key yourself, or you can wait for the vendor to fix that problem. However, not all AV vendors plan to make that fix. So doing it yourself may be your only option. But be careful because making registry edits needs some knowledge of what you’re doing.
How to Fix Windows Registry Issues That Prevent Microsoft Security Updates
However, if you find out that the problem is your AV software and that the vendor isn’t planning to make it compatible with Windows Update, you have little choice but to change AV vendors.
Notwithstanding what your AV vendor may say, no single company has a monopoly on all essential security technology.
If your AV vendor doesn’t plan to fix this issue on a timely basis, retaining that vendor isn’t worth the risk.
This whole issue of conflicting AV came up when Microsoft released updates that would help defend against an exploit of the Meltdown vulnerabilities.
in Intel processors or the Spectre problem that exists in virtually all processors. When preparing the updates, Microsoft found that a few AV packages ignored the rules for application behavior and instead acted like the malware they were trying to defeat.
But whatever the reason, defense in depth is critical for a successful cyber-security protection plan and that has to include allowing Windows to perform updates.
Anything that delays updates is asking for trouble. The last thing you want is to explain why you allowed a vulnerability to exist in your enterprise when you knew it existed.