> Load the user hive file into the local registry using the RegRestoreKey
api.
> Make your changes, then use RegSaveKey to write the hive to the hive file.

> Unfortunately, I have no sample code using those api's, but if you like, I
> can
> prepare some for you. Let me know.

> Bj?rn Holmgren
> Framfag/Guide AB

> > I have a program that will list all the user's accounts on a NT
> > system --could be a local NT system or a remote NT system. Based on the
> user
> > accounts the operator of the program can then pick a user from the list
of
> > accounts to make modifications to their registry. This means the program
> > will need to dynamically load the accounts hive programmatically. What
is
> > the best way to do this? I looked at the APIs LogonUser and
> > CreateProcessAsUser. I have noted that LogonUser will fail if the system
> is
> > a remote system.

> > I did find the article within the MSDN entitled, "Load a User's Hive
> > Programmatically" within the MSDN. Unfortunately the examples are all in
C
> > making it hard to read for this VB only programmer. Can anyone shed some
> > light on the best path forward to accomplish the aforementioned goal or
> have
> > some code samples in VB for loading a User's hive programmatically?

> > Thanks!

> > JR

> I did find the article within the MSDN entitled, "Load a User's Hive
> Programmatically" within the MSDN. Unfortunately the examples are all in C
> making it hard to read for this VB only programmer. Can anyone shed some
> light on the best path forward to accomplish the aforementioned goal or
have
> some code samples in VB for loading a User's hive programmatically?

> Thanks!

> JR

> Thanks for getting back to me!

> I read a bit about your suggestion and I was wondering....wouldn't
> RegOpenCurrentUser be a more logical choice? RegRestoreKey seems to be a
bit
> more dangerous in that in copies registry information wholesale into a
> specified key. There really is no way to use it in a surgical sense. But
> ultimately, neither RegRestoreKey or RegOpenCurrentUser are supported in
> NT4.

> > Bjorn,

> > Thanks for getting back to me!

> > I read a bit about your suggestion and I was wondering....wouldn't
> > RegOpenCurrentUser be a more logical choice? RegRestoreKey seems to be a
> bit
> > more dangerous in that in copies registry information wholesale into a
> > specified key. There really is no way to use it in a surgical sense. But
> > ultimately, neither RegRestoreKey or RegOpenCurrentUser are supported in
> > NT4.

> Not booted into NT right now, I couldn't tell you for sure, but MSDN says
> that RegRestoreKey works in NT3.1+, and as for RegOpenCurrentUser, it
isn't
> listed at all.

> HTH
> Stephen