I went to Scripting >> Configuration Policies >> Registry >> named it "prevent IE10 install"

In the "Registry File" box I typed:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Setup\10.0]

Then I pushed it out to my x64 machine.  It installed, but in HKLM\software\wow6432node.

Two questions, perhaps only 1.  

1) will it being added there actually prevent it from being installed (assuming the keys are correct, and I'm pretty sure they are).  If not,
2) How do I tell it to install in the location listed in the policy instead of the wow6432node location? 

Answer Summary:
0 Comments   [ - ] Hide Comments


Please log in to comment

Answer this question or Comment on this question for clarity



In answer to my first question, it being in wow6432node location DID NOT prevent IE10 from showing in Windows Updates.  I had to manually put it in the location I wanted it in in order for it to disappear from Windows Updates.

As a followup perhaps better question...is there a video or something specifically helping me with Registry scripts inside the 1000?  There's a danged link specifically for it, so I'd think it'd be an integrated and easy piece to deal with.

Answered 05/13/2014 by: DanHarmon
Blue Belt

  • I believe all you need to do is change the key to
    [HKLM64\SOFTWARE\Microsoft\Internet Explorer\Setup\10.0]
    • That's counter-intuitive, but that worked, thank you!
      • the reason is the client is 32bit so it gets pointed to the syswow64 by the system, that tells the system to get back in the 64bit hive
      • The Kace agent is 32-bit application that's why you have to force it to look to the 64-bit keys. Otherwise it will default to the wow6432 node.
  • http://www.kace.com/support/training/kke/archive?id=8840C5EC-9CC4-4C73-9C4C-87D1458B7AED&product=k1000&tag=scripting&language=en
Please log in to comment
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja