Oscar Powers
asked on
Microsoft Security Client error code 0x80092026
I deploy a new Windows 7 x64 image with SCCM 2012 R2.
At login you get the the pop up Microsoft Security Client error code 0x80092026 (Please check attach file). If you click OK it go away but come back when you click System Center Endpoint Protection. I can uninstall SCEP only like a local admin. But when I install again manually I got the same error again.
Also I delete the "MSC key" at HKEY_LOCAL_MACHINE\SOFTWAR E\Microsof t\Windows\ CurrentVer sion\Run\ but doesn't work
And "reg DELETE "HKLM\Policies\Microsoft\S ystemCerti ficates\Tr ustedPubli sher\Safer " /F" with not look
Any ideas!
error-code-0x80092026.JPG
At login you get the the pop up Microsoft Security Client error code 0x80092026 (Please check attach file). If you click OK it go away but come back when you click System Center Endpoint Protection. I can uninstall SCEP only like a local admin. But when I install again manually I got the same error again.
Also I delete the "MSC key" at HKEY_LOCAL_MACHINE\SOFTWAR
And "reg DELETE "HKLM\Policies\Microsoft\S
Any ideas!
error-code-0x80092026.JPG
Are any services also failing to start? (especially the cryptographic service ( services.msc ))
ASKER
Services look fine, cryptographic service is up.
I try a old image and works fine. I will recreate the image to test this option.
I try a old image and works fine. I will recreate the image to test this option.
ASKER
Any other idea
ASKER
I try this: I remove the computer from the domain and uninstalled SCEP.
Rebooted the PC and reinstalled SCEP again, it was working fine at this moment.
After that< the PC is re jointed to the domain and the error come back.
Can be any GPO the problem? If yes, how I can troubleshoot the problem?
We already have in place : Computer Configuration | Policies | Windows Settings | Security Settings | Public Key Policies/Certificate Path Validation Settings/Trusted Publishers/Trusted Publishers set to All administrators and users
Rebooted the PC and reinstalled SCEP again, it was working fine at this moment.
After that< the PC is re jointed to the domain and the error come back.
Can be any GPO the problem? If yes, how I can troubleshoot the problem?
We already have in place : Computer Configuration | Policies | Windows Settings | Security Settings | Public Key Policies/Certificate Path Validation Settings/Trusted Publishers/Trusted Publishers set to All administrators and users
Slightly different error code; but, check this: https://support.microsoft.com/en-us/kb/2832355
How are updates configured?
How are updates configured?
ASKER
We use SCCM 1012 R2 to deploy the updates.
All our client machines are Windows 7 Ent
All our client machines are Windows 7 Ent
Then that KB may apply. It says you have to have the workstations set to get updates from "Windows and other Microsoft Products".
ASKER
I do not have this option "Give me updates for other Microsoft products when I update Windows", please check attach file.
But another thing that we noticed yesterday, the problem is only on the old users, who log in in the first time witch Windows XP, New users do not have the error.
Capture.PNG
But another thing that we noticed yesterday, the problem is only on the old users, who log in in the first time witch Windows XP, New users do not have the error.
Capture.PNG
What do you get on both a working (new) and broken (old) user under Windows Update? Its a text entry saying "You receive updates:"
ASKER
Both say: "Managed by your system administrator"
We use WSUS for updates. The GPO for Windows updates only has two entries:
1-Allow signed updates from an intranet Microsoft update service location: Enabled
2-Configure automatic updates: Disabled
We use WSUS for updates. The GPO for Windows updates only has two entries:
1-Allow signed updates from an intranet Microsoft update service location: Enabled
2-Configure automatic updates: Disabled
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Award the author the points as he answered his own question. The problem was in bringing forward a very old user profile (from Windows XP) and was resolved by recreating it.
ASKER
Recreate the profile fix the problem for me.