This was the case when running a project under Vista and noticing that the load hive command is no longer accepted because it requires administrative permission (even tought I was logged on an account wich belongs to the administration group) - end result: project fails because the hive isn't created as needed.
Tried to accomplish the same effect manually using reg.exe to load the hive, but it also refused.
These sort of API just get refused without notice - like reg.exe wich no longer seems to be able to load an hive into the local system registry.
How can I load an external hive now?
Anyone knows a good workaround or is there something that needs to be done prior to this?
RunAs also seems a valid way to get reg.exe going - but I didn't tried it since I'm looking for an unnatended method for loading the hive without requiring to enter username details. (unless there is a way to do this with runas and someone shares how..)
Here is a blog entry with some details and feedback from other users who also have some similar issues:
http://blogs.msdn.co...dows-vista.aspx
The author specifically mentions that *only* under some conditions the application will be executed under full administrative rights:
1. If the application has a manifest that explicitly asks for administrator privilege.
2. The application is one of the well known setup installers.
3. Application Compatibility testing reveals that the application requires admin privilege.
4. A certain heuristics to determine if the application is an installer. For example, if the application name contains "setup" or "installer", it is a good indication that the application is an installer, thus requires administrator privilege.
So the third option seems reasonable to achieve - but I'm still wondering - how do we use the Application Compatibility to allow loading hives once again in wb?
Anyone?
Thanks!
Forgot to mention that one other option would be editing the hives without loading them onto the local registry - but this would certainly require a very detailed knowledge on how they work to code a stable tool and avoid messing the reg data..