I’m trying to delete a registry key from a system, and failing, and I’m not sure why.
I ran this through the debugger and it worked perfectly against my system. I then used it and created a fixlet, but it never shows it’s relevant to any systems, although I am targeting another system I
know
has the key.
Relevance:
exists key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\43D9BCB568E039D073A74A71D8511F7476089CC3” of registry
Action:
For now the action is empty, since I’m debugging, but eventually it will be:
Oh, and for what it’s worth - I originally tried running it as a fixlet after confirming I had the key, and it said it wasn’t applicable to my system. Then I ran it from the debugger and it worked fine. Bizarre?
From debugger:
Q: exists key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates\43D9BCB568E039D073A74A71D8511F7476089CC3” of registry
The system I’m targeting is not a 64 bit one. I tried native registry just in case, though, when I saw your post. It still shows “Not reported.” The weird thing is the client logs on that machine show it posting reports successfully, and if I click on “Send refresh” it updates almost right away.
First, very cool that you are going after that bogus certificate. It’s really criminal that we have to rely on such a fragile infrastructure to trust SSL-enabled sites.
Second… sounds like there is something simple that is wrong with the Fixlet. Can you try with a different reg key and different Fixlet just to troubleshoot?
