https://bugs.winehq.org/show_bug.cgi?id=55598
Bug ID: 55598 Summary: Registry Editor and 'reg query' disparity (phantom state) Product: Wine-staging Version: 8.15 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dragonwarriorxtreme@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: ---
Created attachment 75130 --> https://bugs.winehq.org/attachment.cgi?id=75130 Searching the same key in the same wine prefix
Create a new prefix, then install some software. Now open Registry Editor, highlight the keys relative to the software, then close it. Make the software change the registry. Open it and you should see no actual change. Then create a new key and perform a query search in the command prompt. Wine will not see the key.
Does the clientside NTSaveKey patchset happen to be the culprit? I'm not proficient enough to understand how the registry is implemented in Wine. Not sure if this happens in devel, but I will test shortly.
cc @pgofman
https://bugs.winehq.org/show_bug.cgi?id=55598
--- Comment #1 from dragonwarriorxtreme@gmail.com --- Created attachment 75131 --> https://bugs.winehq.org/attachment.cgi?id=75131 Keys created in regedit do not show; some keys created even outside of regedit do not show at all
https://bugs.winehq.org/show_bug.cgi?id=55598
dragonwarriorxtreme@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Debian
https://bugs.winehq.org/show_bug.cgi?id=55598
dragonwarriorxtreme@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID
--- Comment #2 from dragonwarriorxtreme@gmail.com --- I did not look into the Wow64Node key; sorry for the confusion.
https://bugs.winehq.org/show_bug.cgi?id=55598
Gijs Vermeulen gijsvrm@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #3 from Gijs Vermeulen gijsvrm@gmail.com --- Closing.