Hi, I am curious, whether we can reset a registry to its default value. Assuming that my application is looking at a registry value[under one of the system's keys under hkey_localmachine], and My application doesn't know whether it has been changed by somebody or some other applcation before. Now, at this point, is it possible to find out the actual default value? (programmatically!) Thanks Sathish
As far as I know the only "Default" to check against would be against the original system hive when Windows was installed, a copy of which would be stored in C:\WINNT\repair. Mucking about with the System hive might lead to great headaches that could include the pc not being able to reboot. John satv73@gmail.com wrote: > Hi, > I am curious, whether we can reset a registry to its default value. > Assuming that my application is looking at a registry value[under one > of the system's keys under hkey_localmachine], and My application > doesn't know whether it has been changed by somebody or some other > applcation before. Now, at this point, is it possible to find out the > actual default value? (programmatically!) > > Thanks > Sathish >
In microsoft.public.win2000.registry John John wrote: > As far as I know the only "Default" to check against would be > against the original system hive when Windows was installed, a > copy of which would be stored in C:\WINNT\repair. Mucking about > with the System hive might lead to great headaches that could > include the pc not being able to reboot. I would use "at time of installation value" here rather than "default" OP. Just a niggle. Examining the installation log one (did/did not) make during application installation would be easiest I believe. Also the installation package might (or not) contain configuration files listing the installation registry changes in some cases. Occasionally an INF file might be a source. Another argument for regular Full Registry Backups to be made and archived periodically such they are stored against future reference need. But the "installation track and log" tool is my favorite documentation. Caution, this next is very application-dependent. With backup/export in hand and in some applications, "missing" keys and values may be auto-set to a "default" or "initial" state on application execution. In this case (HKLM) that would be when run under Administrator authority. YMMV widely. I withhold comments on possible "repair" effects in MSI apps. <G> > > satv73@gmail.com wrote: > >> Hi, >> I am curious, whether we can reset a registry to its default >> value. >> Assuming that my application is looking at a registry >> value[under one of the system's keys under hkey_localmachine], >> and My application doesn't know whether it has been changed by >> somebody or some other applcation before. Now, at this point, >> is it possible to find out the actual default value? >> (programmatically!) >> >> Thanks >> Sathish >> >
Mark V wrote: > In microsoft.public.win2000.registry John John wrote: > > >>As far as I know the only "Default" to check against would be >>against the original system hive when Windows was installed, a >>copy of which would be stored in C:\WINNT\repair. Mucking about >>with the System hive might lead to great headaches that could >>include the pc not being able to reboot. > > > I would use "at time of installation value" here rather than > "default" OP. Just a niggle. Indeed. Anything else might lead to major headaches, especially when it concerns the System hive! John
