This time, we will introduce how to deal with the situation where KB5007651 is repeatedly installed on Windows 11.
KB5007651 is an update to the Windows Security Platform antimalware platform.
The latest version, KB5007651 (Version 1.0.2306.10002), released on July 5, 2023,Resolves the issue where the warning "Local Security Authority Protection is turned off" appearsThat was done.
However, we have recently received inquiries from users reporting that KB5007651 (Version 1.0.2306.10002) is being installed multiple times.
In this user's environment, the version of Windows Security remains old (Version 1.0.2303.28002-0), and updating to the latest version appears to be failing.
Here, I would like to introduce some effective solutions to solve this problem.
*If the update fails, the error "0x80070643" may be displayed.
I'll post the details of my inquiry here, as I think it will be helpful to everyone.
Inquiry:
Resolved? KB5007651 "Local Security Authority Protection is turned off."I originally tried to post this in the article, but image verification didn't work so I apologize for not posting it here.
In our environment, we are experiencing an issue where KB5007651 (Version 1.0.2306.10002) is being installed multiple times.
The same thing happened with KB5007651 (Version 1.0.2303.27001).
I tried using sfc /scannow and DISM commands but it didn't solve the problem.
I contacted Microsoft via chat and performed a repair install, but it didn't solve the problem. (After the repair install, I ran sfc /scannow, which apparently fixed the corruption.)
I tried disabling it with "net stop wuauserv" in PowerShell, clearing the cache by deleting the contents of the Download folder in C:\Windows\SoftwareDistribution\Download, and then re-enabling it with "net start wuauserv," but this didn't solve the problem. After a repair install, KB4023057 would repeatedly install and put the computer in a pending restart state, but deleting the cache resolved the issue.
Additionally, I repaired and reset Windows Security from the app list, and also reinstalled Windows Defender by typing Get-AppxPackage Microsoft.SecHealthUI -AllUsers | Reset-AppxPackage in Windows PowerShell, but this did not solve the problem.
Microsoft has suggested that this could be a hardware issue. They say that a Windows update may be incompatible with your PC's drivers or hardware, and that this issue occurs when the drivers or hardware are unable to run the latest Windows 11 updates.
Microsoft has said that it expects the issue to be resolved in a future Windows update, commenting that "we're looking at a few months. It shouldn't reach six months."
One thing that concerns me is that the version of KB5007651 should match the Windows Security Service version of Windows Security, but in my environment it is 1.0.2303.28002-0.
In fact, in our environment, we upgraded from 10 to 11, so there were no warnings about Local Security Agency protection from the beginning.
I checked the registry editor and found that there was no registry key for this. It's supposed to be added when upgrading, but it seems to be a bug (Microsoft acknowledged this in the chat).
Specifically, when I looked at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa in the Registry Editor, I found that there were no RunAsPPLBoot or RunAsPPL items. So I selected "DWORD (32-bit) Value (D)" and created two items, setting their values to 2.
"LSASS.exe was launched as a level 4 protected process" is now displayed in the Event Viewer.
Currently, we have tried almost everything we can to resolve the issue of repeated installations, but the only thing we can do is hide them using a tool.
What to do if KB5007651 keeps installing
The next page provides the latest solutions.
1. Reset Windows Security
The next page introduces the commands to reinstall (reset) Microsoft Store apps and reset Windows Security, so please follow the steps.
Windows 11 Solved! Windows Security won't open
If the Windows Security files are corrupted, the KB5007651 update may fail.
2. ".NET Framework 3.5 and 4.8.1 Cumulative Update"
The KB5007651 update may also fail if the .NET Framework files are corrupted.
As of July 12, 2023, the latest version is "2023-07 Cumulative Update for .NET Framework 3.5 and 4.8.1 for Windows 11 x64, version 22H2 (KB5028851)."
Try uninstalling KB5028851, restarting your PC, and then running Windows Update.
If KB5028851 is not installed, uninstall the most recent cumulative updates for .NET Framework 3.5 and 4.8.1.
You may also be able to successfully update to KB5007651 by running Windows Update and installing the latest version of the .NET Framework 3.5 and 4.8.1 Cumulative Update.
3. Security software
If you are running security software other than Windows Security (Microsoft Defender), try pausing it before running Windows Update.
Some security software and Windows Update servicesConflictYou may have.
4. Reset Windows Update components
Please try "Resetting Windows Update Components" as described on the next page.
Causes and Fixes for Win11 Windows Update Error "0x8024a205"
5. Upcoming Windows Updates
This is a bug that has not been officially announced by Microsoft, so the problem may be resolved in a future Windows Update.
I'll update the article if I get any more information.
2023 / 07 / 13:
If the above method doesn't solve the problem, try the following:
How to check which version of Windows security services you are currently running
1.Task tray (notification area)Click the Windows Security icon in the
2. Windows Security will open, so click the Settings button in the bottom left and then click "About" on the right.
Here you can check your Windows Security Service version.
Check the Windows Security Service version in Task Manager
1. Click the Windows Security icon to open Windows Security.
2.Task managerand click the Details tab in the bottom left.
You will then see "SecurityHealthHost.exe" on the right side.
3. Right-click on "SecurityHealthHost.exe" and click "Open file location".
4. Now, you can check the Windows Security Service version by looking at the address bar at the top of File Explorer.
*This folder contains 50 items.
Reinstall the Windows Security app using the app installer
If resetting Windows Security using PowerShell doesn't fix the issue, try reinstalling the Windows Security app using the app installer.
1. Double-click the "Microsoft.SecHealthUI_8wekyb3d8bbwe" (APPX file) in the location of the "SecurityHealthHost.exe" file found in Task Manager.
2.The message "Windows Security is already installed" will be displayed, so click "Reinstall".
3. A message will appear saying "A newer version is already installed," so click "Reinstall."
Once the reinstallation is complete, the message "Windows Security is ready!" will appear in the bottom right corner of the screen.
Reinstall the old version of the Windows Security app and then update to the new version.
If you're having issues with your current version, reinstalling the older version of the Windows Security app and then updating to the newer version may resolve the issue.
1. Open the directory one level above the location of the "SecurityHealthHost.exe" file.
C:\Windows\System32\SecurityHealthThis is where older versions of Windows Security are stored.
*If you have newly installed Windows 11, the previous version may not exist.
2. Double-click "Microsoft.SecHealthUI_8wekyb3d8bbwe" in the old version folder to open it.
upper"Reinstall Windows Security from the app installerProceed with the installation as described in "
Once the installation is complete, the version of your Windows Security application will change to the older version.
3. Restart your PC.
After starting your PC, the Windows Security application will automatically update to the latest version after a while.
Verify that the Windows Security application version has been automatically updated to the latest version, then run Windows Update. This may resolve the issue of KB5007651 being installed multiple times.
update information
2023 / 09 / 10:
We have verified the issue of KB5007651 (Version 1.0.2306.10002) causing repeated installations, and have successfully created a situation where the installations would be repeated. We have confirmed that this has been fixed and the installations no longer occur.
The following image confirms the installation of "Reliability Monitor" KB5007651.
At around 15:30, I set up a situation where the installation was repeated multiple times, and when I manually checked for updates, the installation of KB5007651 was recorded each time I checked (twice).
When I manually checked for updates at 20:12, they were installed again and again (7 times).
After performing the repair after 21:40, when I manually checked for updates, the installation of KB5007651 was no longer recorded no matter how many times I checked.
Specifically, it involves manipulating files and the registry.
Currently, we have only tested it in one environment, and the operation method is quite difficult and complex for the average person, so it will likely take some time to update the article.
2023 / 09 / 12:
We have published a method to repair "SecurityHealth," which solves Windows security issues in Windows 11.
