/build/static/layout/Breadcrumb_cap_w.png

Script registry key verification ALWAYS fails.

The first step I go for is to verify a registry key exist - we don't want this thing annoying people that already have it removed so I chose in Verify:

1. Verify a Registry Key Exist
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\00004109110000000000000000F01FEC\Patches\5DD666CF85A8B104B9E1C2BB5491238E

I didn't put quotes, of course when it failed I tried quotes, but it doesn't get much more specific than that.  Even when running again a the system I exported that key from then copy-pasted the key into the blank it fails every single time.  Is there something I'm missing here?
Asked 9 years ago 3031 views
3 Comments   [ + ] Show comments
  • Is this a 32-bit or 64-bit reg key?
    If it is 64-bit put HKLM64 instead of HKEY_LOCAL_MACHINE. - flip1001 9 years ago
  • If the script is running as a 32 bit process on a 64 bit machine, you will not be able to access the 64 bit area of the registry. - EdT 9 years ago
  • It's a 32 bit version of Office it's checking, but a 64 bit OS. I'll experiment with the HKLM64 thing. I figured a copy/paste should have been direct enough. So far remote management of this particular fix isn't working too well, the utilities that were going to get called after the check aren't exactly working as advertised. The KBOX has made my life a lot easier, but occasionally you just have to use the GUI. - pecosdave 9 years ago

Answers (0)

Be the first to answer this question

 
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