/build/static/layout/Breadcrumb_cap_w.png

Script to add registry key/value not working

I am trying to push a registry key and value to some test machines. I have created a script with several "Tasks" using the built-in option to "Add a new step" and "Set a registry key.." and "Set a registry value..."


Set “HKLM\SOFTWARE\Microsoft\Cryptography\Wintrust\Config!EnableCertPaddingCheck” to “0x00000001

Set “HKLM\Software\Wow6432Node\Microsoft\Cryptography\Wintrust\Config!EnableCertPaddingCheck” to “0x00000001”.

The *second* command works.  It creates the key and value under the Wow6432Node hive.

The *first" command does not work.  It will not create the key/value under the Microsoft hive.

Any ideas?  I have also tried creating the the path one key at a time, and then setting the value like this:

Set HKLM\SOFTWARE\Microsoft\Cryptography\Wintrust.
Set HKLM\SOFTWARE\Microsoft\Cryptography\Wintrust\Config.
Set HKLM\SOFTWARE\Microsoft\Cryptography\Wintrust\Config!EnableCertPaddingCheck to 0x00000001.

That does not work, either. 

Any ideas?  

Thanks


0 Comments   [ + ] Show comments

Answers (1)

Posted by: statikcat 1 month ago
White Belt
0

Just had the EXACT same issue but we are adding scripts via simple bat file with "reg add" command(s)

Check this thread:

https://www.itninja.com/question/problem-with-64-bit-registry

I added /reg:64 at the end of the command and it works. The Wow64 path did not need it but "HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Wintrust\Config" did.

Hope this helps!

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ