Re: Strange Registry Virtualization issue

FromTheRafters wrote:
My understanding is that it reads both and presents a
merged view to the application with the virtualized keys
taking precedence over the ones in HKLM. If you want
to make HKLM take precedence - remove the keys from
the virtualized store and it should use the HKLM ones.

The issue is that there are no keys in the virtualized store, the keys are only in the HKLM one. So I don't understand why he can't read the one from HKLM.

In other words, make the virtual store keys in question
non-persistent and the HKLM will be used each time
because no virtualized version will be found.

I agree this is what should be happening, but it is not. Any hint on how to debug this so that we can find the root cause of this behavior?

Thanks,
Manu
.

Relevant Pages

  • Re: Windows Startup
    ... using F3 to find keys has never worked for me. ... >> thing that causes the System32 folder to open at startup. ... >> Right click hkcu on your Desktop and select: Edit | Select all the text ... >> Right click hklm on your Desktop and select: Edit | Select all the text ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: HKLM and HKCU Priority
    ... HKCU is for user DSN definition while HKLM is for system DSN definition. ... | to never remove old keys from the registry but I ...
    (microsoft.public.win2000.registry)
  • Re: Strange Registry Virtualization issue
    ... merged view to the application with the virtualized keys ... taking precedence over the ones in HKLM. ... The issue is that there are no keys in the virtualized store, the keys are only in the HKLM one. ...
    (microsoft.public.windows.vista.security)
  • Re: Strange Registry Virtualization issue
    ... merged view to the application with the virtualized keys ... taking precedence over the ones in HKLM. ... it doesn't have to use virtualization at all - which is the ...
    (microsoft.public.windows.vista.security)
  • Re: Registry Permissions Error
    ... I was not aware that users had full control in HKCU and limited access ... in HKLM. ... > security is "below" .net so applies to it also. ... the user is not able to create keys in the registry. ...
    (microsoft.public.dotnet.security)
Quantcast