![windows 10 update kb4074588 windows 10 update kb4074588](https://www.repairwin.com/wp-content/uploads/2021/04/image-9.png)
- WINDOWS 10 UPDATE KB4074588 PATCH
- WINDOWS 10 UPDATE KB4074588 SOFTWARE
- WINDOWS 10 UPDATE KB4074588 WINDOWS
However, on this occasion I was not successful. I'm afraid I've only today had the time to follow up and I apologize for the delay. Once again thank you so much for your suggestions. The problems you described in your previous thread have likely reappeared because you rolled your system back to an earlier date so you might have to repeat the same troubleshooting steps [e.g., disabling Fast Startup, refreshing your N360 installation using the Norton Remove and Reinstall (NRnR) tool at to get Norton working correctly again.ģ2-bit Vista Home Premium SP2 * Firefox ESR v52.6.0 * NS Premium v22.12.0.104 * MB v3.1.1
WINDOWS 10 UPDATE KB4074588 WINDOWS
Here's an image of my own Windows registry from 1:Īs noted in your previous thread N360 disappears after LiveUpdate, replaced by non-working N Security, it sounds like your Norton 360 problems are related to the recent the new Single Layout feature included in the recent v22.12.0.104 update (see the Features Changes section of Norton 22.12 Product Update Available Now).
WINDOWS 10 UPDATE KB4074588 PATCH
If this registry entry were missing then Windows Update would not be able to deliver KB4074588 or other available updates to your computer, so the fact that Windows Update installed your February 2018 Patch Tuesday updates is a good indication that your registry entry has already been set to the correct value. Security expert Kevin Beaumount's spreadsheet at shows that Norton products are fully compatible ( "Y", "Y" in the spreadsheet) assuming you have v22.11.2.7 or later, and this registry key was also discussed in Tom Run's thread Is NIS 21.7.0.11 compatible with the Windows update KB4056894 for Meltdown & Spectre Vul.
![windows 10 update kb4074588 windows 10 update kb4074588](https://www.repairwin.com/wp-content/uploads/2021/04/image-8.png)
WINDOWS 10 UPDATE KB4074588 SOFTWARE
This registry key must be present to ensure your antivirus software is compatible with the January 2018 Security Updates for the Meltdown vulnerability and prevent possible BSODs - see the MS support article Important: Windows security updates released January-February, 2018, and antivirus software for more information. Symantec confirmed Norton users have had this required registry key since early January 2018. KB4074588 is an OS Build that includes the following caution - "Because of an issue that affects some versions of antivirus software, this fix applies only to computers on which the antivirus ISV updated the ALLOW REGKEY." I am not sure what this means but end users are advised to "Contact your antivirus manufacturer to verify that their software is compatible and that they have set the following REGKEY on the computer - Key="HKEY_LOCAL_MACHINE"Subkey="SOFTWARE\Microsoft\Windows\CurrentVersion\Qualit圜ompat" I have turned off 'fast boot' but have not run RnR yet in light of the following. As ever any help would be very much appreciated.
![windows 10 update kb4074588 windows 10 update kb4074588](https://s3.manualzz.com/store/data/052945400_1-4995a4a252e9b45e324e4f6596798418.png)
I apologise for the long post but it does seem that there is an ongoing conflict of some kind with one or more MS updates. I ran LiveUpdate several times and each time it said a patch needed to be applied, restarting out of necessity after each update.On the last occasion N360) asked me to fix SONAR protection as it had become disabled and then said it was unable to do so. Running LiveUpdate consistently removed the N360 icon from the Task Bar notification area as well as resulting in the Program menu icon being unable to open N360 - or what had now become Norton Security. That said, I uninstalled KB4074588 but that did not resolve the N360 issues. Hence my question is does anyone know if N360 is consistent with the above and if not what can be done? I have turned off 'fast boot' but have not run RnR yet in light of the following. Everything worked fine until MS Update ran - automatically in Win 10 - and then the above problem reappeared. However I recently had to roll my system back using System Restore in order to fix an issue with Symantec (now Veritas) System Recovery. This appeared to be fixed by Norton Remove and Reinstall. I recently posted "N360 disappears after LiveUpdate, replaced by non-working N Security" - see below.