Cannot see IE8 BrandGUID registry key on Win7 64 bit


I am using Wise Package Studio to create a custom IE8 package for WIndows 7 both 32 and 4 bit.  The script identifies the version of IE by looking for the registry key HKLM\Software\Microsoft\Internet Explorer\BrandGUID  .  For some reason it works perfectly on the 32 bit but not 64 bit - the same script.  It reports back a zero on 64 bit.  I have checked the registry key location manually on 64 bit and it is in exactly the same place and can be read.  I have tried getting a report from other keys in the same folder and it works.  Any ideas on this one?  I'm banging my head!!!

0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: joeostrander 10 years ago
Third Degree Blue Belt

It's probably running as a 32bit process and trying to read it here:

HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\BrandGUID 

  • I checked that out before and all the other registry keys are duplicated in this location except BrandGUID strangely. I searched the entire registry for this key in case it was located elsewhere and there are no other instances of it. I'm tearing my hair out :) - elvisgraham 10 years ago
  • If it doesn't exist in wow6432node, then it sounds like that's the problem (app running as 32bit). If your app/script is running 32bit on 64bit and the registry value you want only exists in the 64bit registry, then you need to force it to read the 64bit registry.

    As you may know....if the app/script is running 32bit, HKLM\Software = HKLM\Software\Wow6432Node.

    You can force your 32bit app/script to only check the 64bit reg in several ways. What type of script is it? - joeostrander 10 years ago
  • Using Wise Package Studio 8.0
    IE8 Install created with IEAK (32 bit version)
    Installing on Windows 7 Enterprise (64 bit version)

    The strange thing is that I can find the entry within the 64 bit registry manually. It just doesn't report back (or isn't seen) by Wise. The entry for both 32 and 64 bit is located at HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\BrandGUID - elvisgraham 10 years ago
  • Sorry, Correction to the last part of my last post - the registry key on Windows 7 32 and 64 bit is located at HKLM\Software\Microsoft\Internet Explorer\BrandGUID - elvisgraham 10 years ago
  • Maybe I'm not understanding what you're saying... please correct me if I'm wrong on any of these facts:

    1) you have a value that exists in HKLM\Software\Microsoft\Internet Explorer\BrandGUID
    2) you do not have the value in HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\BrandGUID
    3) the script you are using does not see the value

    If all these are true, then your script must be running as a 32bit process and therefore will look to HKLM\Software\Wow6432Node whenever HKLM\Software is referenced.

    Also... can you just change it to use HKLM\Software\Microsoft\Internet Explorer\Version?
    That value will exist regardless of whether the process is running as 32 or 64bit - joeostrander 10 years ago
  • ooh... 1 more question... why install IE8 on Win7 64bit? Win7 ships with IE8 - joeostrander 10 years ago
  • You have all of the above correct. The reason I can't use version is because the installer for IE 8 is a corporate 'branding' installation. When the 'branding only' is applied, the version number of the IE8 installation does not change in the registry. - elvisgraham 10 years ago
  • I think I have this solved. When I put the BrandGUID string into HKLM\Software\Wow6432Node\Microsoft\Internet Explorer\ manually, the script then reports correctly when I ask it to check HKLM\Software\Microsoft\Internet Explorer\BrandGUID. I can alter my script to tell the install to insert this entry if it finds a 64 bit OS version of Windows 7. What a headache this has given me!!!!!! - elvisgraham 10 years ago
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