-
-
Notifications
You must be signed in to change notification settings - Fork 58
After each PC restart, all WinPaletter settings are reset to the Windows default settings #231
Comments
I can't solve this problem at all and I can't reproduce this issue. This issue happened with someone else: #218 (comment) Do you have multiple Windows users or not? Can you test older versions like |
I don't have multiple Windows users I had just tested the following versions: 1.0.6.1 and 1.0.7.2 With both versions, the changes are retained after a PC restart, but not after the quiet state and not even after the energy saving mode |
After I also tried the both versions 1.0.6.1 and 1.0.7.2, the behavior of the 1.0.9.2 stable has changed. For whatever reason. That's strange. I don't understand the behavior. After restarting the PC, the changes are now retained. |
That is an extremely weird issue that I couldn't reproduce or fix. There is nothing new in applying mechanism in 1.0.9.2. Please keep this issue open. When I find a solution, I'll post an update. |
I have noticed something else in the meantime, namely that some color changes are retained by WinPaletter, while others are not. I'm not sure, but maybe the color settings changed by WinPaletter are only not saved with very “old” programs, after hibernation and after energy saving mode. I use several old programs on Windows 11, such as Adobe Photoshop 5.5 (from 1999) and ACDsee 32 v.2.41 (image viewer from 1997) Perhaps you can reproduce the error using this information? You can still find “ACDsee 32 v.2.41” as a free download here:
|
Thanks for this information. I'll try to reproduce this again, and once I find a solution, I'll post an update. I'll inform you if I found something new in this issue. |
❌ Error report
Describe the error
Under Windows 11 Pro 23H2, all changes made by WinPaletter are lost as soon as the computer is restarted, as well as when waking up from power saving mode and from sleep mode.
The problem exists, at least for me, with the following versions:
1.0.8.0-Stable, 1.0.8.4-Stable, 1.0.9.0-Stable, 1.0.9.1-Stable, 1.0.9.2-Stable
Can the problem be solved somehow?
The text was updated successfully, but these errors were encountered: