I want to change initial value of PATHEXT variable, so changing corresponding key of HKLM/System/Session Manager/Environment works fine. However after each wine update it restores the key default value. Why?
Also, lately there was a problem of re-creating '/' namespace in HKCU/Software/Windows/Windows Media/Namespace branch. I wanted to delete it but had to drop the idea being tired doing this each time wine updates.
However changing PATHEXT is very important thing to me, it is the only way to work. Why I had to do the same think again and again?
Why wine update breaks registry keys
Re: Why wine update breaks registry keys
lovyagin the why you are not going to particularly like. It is a bug and it is not a bug. There is a file called wine.inf this contains wine default registry. In case of upgrade the contents of this file are force applied on the registry. This is why HKCU/Software/Windows/Windows Media/Namespace comes back and PATHEXT gets nuked.
Why is this not 100 a bug. How do we tell the difference between you and infection exploit PATHEXT. The answer is we cannot simply. You really do need to open a bug stating what PATHEXT you require added. Even then if they exist most liking in update wine most likely should pop up a y/n message to ask if you wish to keep these due to the fact infections under windows play with the same variable. This one is bashing heads with something that has a security reason to be horible.
Now think everything in HKLM/System/Session Manager/Environment restored to default every upgrade. PATHEXT is the only bit of that overwrite that is bothering you.
HKCU/Software/Windows/Windows Media/Namespace this one is harder. Old versions of wine don't have this registry key. Yes being missing can be malware removal tool damage. Yes because malware can exist in that directory and some tools are stupid enough to delete the full directory so breaking other applications.
If you really don't want HKCU/Software/Windows/Windows Media/Namespace you most likely need to add a little .js script to startup services of wine. Check for its existence then delete if it exists script.
lovyagin basically wine is attempting to repair self each upgrade apply. Attempting to repair is the correct thing to be doing. But at times this repair process is a sledgehammer and needs some refinement and at other times its not enough of a sledgehammer.
Some breakages of applications when wine upgrades traces to wine not knowing that particular keys should be left alone. Most of the ones wine leaves alone most likely should own to some form of white list.
lovyagin PATHEXT is most likely a bug. I guess it has to remain changed so a particular application works. If is breaking an application is a bug. If it just for your personal preferences its a feature request.
Why is this not 100 a bug. How do we tell the difference between you and infection exploit PATHEXT. The answer is we cannot simply. You really do need to open a bug stating what PATHEXT you require added. Even then if they exist most liking in update wine most likely should pop up a y/n message to ask if you wish to keep these due to the fact infections under windows play with the same variable. This one is bashing heads with something that has a security reason to be horible.
Now think everything in HKLM/System/Session Manager/Environment restored to default every upgrade. PATHEXT is the only bit of that overwrite that is bothering you.
HKCU/Software/Windows/Windows Media/Namespace this one is harder. Old versions of wine don't have this registry key. Yes being missing can be malware removal tool damage. Yes because malware can exist in that directory and some tools are stupid enough to delete the full directory so breaking other applications.
If you really don't want HKCU/Software/Windows/Windows Media/Namespace you most likely need to add a little .js script to startup services of wine. Check for its existence then delete if it exists script.
lovyagin basically wine is attempting to repair self each upgrade apply. Attempting to repair is the correct thing to be doing. But at times this repair process is a sledgehammer and needs some refinement and at other times its not enough of a sledgehammer.
Some breakages of applications when wine upgrades traces to wine not knowing that particular keys should be left alone. Most of the ones wine leaves alone most likely should own to some form of white list.
lovyagin PATHEXT is most likely a bug. I guess it has to remain changed so a particular application works. If is breaking an application is a bug. If it just for your personal preferences its a feature request.
