VibranceGui only works if I close it completely, it degrades the image on return to normal

[DemonioLou]

Hello, this morning, after doing optimization adjustments in Windows 10 (Remove factory software, telemetry, etc.) something very strange happened to me.

first step that, when minimizing csgo once or twice, I could see that the game got quite dark, making it very difficult to distinguish the interface, it was solved after minimizing again, but, when closing the game and the application, out of nowhere the configuration of saturation was applied again, already with the program closed.
Now every time I open VibranceGui, I can notice that the "Vibrance Level windows" bar is automatically set to 100 (without changing the saturation of anything), and it's not until I close the program that the setting I put is applied.
It does not matter if I minimize the application, the changes are only applied if Vibrance Gui is closed, and these changes are permanent unless you run the application where it automatically returns to "normal" despite what is said with the Vibrance Level Windows section.

It is not only that, I could also notice that, when it is "normal", the colors are seen as "smeared", low depth of colors.

I tried everything, delete the graphics card drivers, recalibrate the colors from the windows options, deleting the VibranceGui folder in %appdata%, using the latest version, etc.

I don't know if it was related but, one of the things I touched this morning configuring windows was "allow windows applications to run in the background", I put it in "enabled" and below in "Force denial", I sense that something had What to see, I tried returning it to its original values ​​and redoing the above, but still nothing, I've been using the program for years and I never had a problem until today when I edited that parameter.

---

i leave the specifications of my equipment.

Windows 10
Ryzen 5 3400g
Zotac RTX 2060
2x8gb (2999mhz)

sorry if something is not fully understood, I am using google translate

[juv]

Do I understand you correctly, you mean that vibranceGUI is stopping you from altering the values in the NVIDIA Control Panel?

If yes, then I have also noticed this before. It appears that there might be some kind of "lock" being created in case an application is using the NVIDIA Api in the way vibranceGUI does it. And this "lock" persists until the application using the NVIDIA Api is closed (or unmounting the API internally).