1. To begin with, isn't it a bad idea to use 'HKEY_CLASSES_ROOT' at all?
By design and definition, HKCR is not saved to a file like HKCU or HKLM, but is created in memory by combining entries found under HKCU\Software\Classes and HKLM\Software\Classses.
Moreover,
2. 'Common Item Dialog' is intended to be used to open or save a file for a classic application. If a developer hard-coded the dialog in one way or another, nothing you can do about it.
See: https://learn.microsoft.com/en-us/windows/win32/shell/common-file-dialog
By design and definition, HKCR is not saved to a file like HKCU or HKLM, but is created in memory by combining entries found under HKCU\Software\Classes and HKLM\Software\Classses.
Moreover,
See: https://learn.microsoft.com/en-us/windows/win32/sysinfo/hkey-classes-root-key...If you write keys to a key under HKEY_CLASSES_ROOT, the system stores the information under HKEY_LOCAL_MACHINE\Software\Classes. If you write values to a key under HKEY_CLASSES_ROOT, and the key already exists under HKEY_CURRENT_USER\Software\Classes, the system will store the information there instead of under HKEY_LOCAL_MACHINE\Software\Classes.
Processes running in a security context other than that of the interactive user should not use the HKEY_CLASSES_ROOT key with the registry functions...
2. 'Common Item Dialog' is intended to be used to open or save a file for a classic application. If a developer hard-coded the dialog in one way or another, nothing you can do about it.
See: https://learn.microsoft.com/en-us/windows/win32/shell/common-file-dialog
Statistics: Posted by beb — 2025-04-19, 02:34 UTC