Jump to content


DCM and HKLM\Software\Microsoft

Recommended Posts

Nevermind; it really was a stupid mistake that cost me half a day.


For other that might find this post, it might be helpful to give them an idea as to what happens so that they don't do the same mistake as you.

Share this post

Link to post
Share on other sites



When dealing with configuration baselines and registry settings --


When you are creating an Execution Policy that looks at registry keys in HKLM\Software, make sure you tick the box for "This registry value is associated with a 64-bit application" if you don't want the rule to look in HKLM\Software\wow6432node.


I was setting a windows setting, which wasn't really associated with a 32bit or 64bit "application". I passed by this setting without really thinking about it. I ended up creating a really weird text string that I could search for and found it under the wow6432node key.


A lesson I won't forget!

Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Create New...