When I try to install an application (vendor's MSI) as non-admin account, I get the following error during install:

"Error creating registry key for "InstallLoc""

When I click 'ok', the installations continues and succesfully installs.

If I install as an account with admin rights, I do not get the error.

When I run regmon during install, as non admin I get:

IDriver.exe:1660 QueryKey HKCU SUCCESS Name: \REGISTRY\USER\S-1-5-21-207654885-1635884669-2869975507-10313_CLASSES

IDriver.exe:1660 OpenKey HKCU\Software\Hyprotech\HTFS\InstallLoc NOTFOUND

IDriver.exe:1660 OpenKey HKCR\Software\Hyprotech\HTFS\InstallLoc BADIMPERSONATION

When I run regmon as admin install, I get:

IDriver.exe:3220 QueryKey HKCU SUCCESS Name: \REGISTRY\USER\S-1-5-21-207654885-1635884669-69975507-35533_CLASSES

IDriver.exe:3220 OpenKey HKCU\Software\Hyprotech\HTFS\InstallLoc NOTFOUND

IDriver.exe:3220 OpenKey HKCR\Software\Hyprotech\HTFS\InstallLoc SUCCESS Access: 0x1

I have googled 'BADIMPERSONATION', there's an article suggesting changing policies on the users machine, this is not an option just for one app.

Has anyone had this before or have any ideas how to get round it?

0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


I've just realised this only happens when installed via deployment tool - installing using msiexec command locally works. Therefore I'm going to look at options on deployment tool...
Answered 08/29/2008 by: Meic
Second Degree Blue Belt

Please log in to comment
Does your “deployment tool” have its own admin account? To add something to HKCU you have to be logged in as that user. I wrote an installer for something and tried to deploy it through Altiris and had a similar error. I changed the package to run as logged on user and it was fine.
Answered 08/29/2008 by: Heresy
Senior Yellow Belt

Please log in to comment
Thanks for your suggestion Heresy.

I have just managed to get it working. It was the pre-req isscript 1150 that was causing issues. Once I changed isscript 1150 dcom properties from "The interactive user" to the "Launching User" is installs.
Answered 09/01/2008 by: Meic
Second Degree Blue Belt

Please log in to comment