Blender Profile dumped into *.bak after PC restart

[Syah Keiko]

Hello everyone!

I've been looking through the Forum for a bit but could not find someone that has this issue. Google also didn't help.

So here's what is happening:
After the driver update from 10.8 to 10.9 it apparently wrote a *.bak folder into the Cfg folder where it stores all the profiles.
In this folder it would write Blender.bak which contains my Blender profile every time i restart the PC.

I have to manually copy the file into Cfg and rename Blender.bak to Blender.xml so it would actually use the Blender Shortcuts I made.

I tried to copy the first few lines from another profile file that it would keep throughout the restarts but that didn't help. It instead writes those new lines into the *.bak file as well.
I tried making minor changes to the profile hoping it would rewrite the file but that didn't work either.

Oh! I also deleted _ALL_ my other profiles because I didn't realize that the windows that changes to the current App has a "Delete every single profile!"-Button. Which adds greatly to my pleasure <3

[jwick]

It is rejecting your old file.
PM/email your file to me so I can see why.

Sometimes changes are made in an application (Blender) which makes old cfg files incompatible with the new application version.
What version of Blender are you running?

I can probably update your file to be compatible with the current Blender, so you don't lose your saved settings (and again every day...).

[Syah Keiko]

That is what I thought so I replaced the first few lines of the XML with the lines of another profile to see if that would catch. But instead it wrote the changed XML into the BAK folder

Sadly I am not "old enough" on this forum to PM people and I can't seem to find your email address.
I can however just post the contents of the whole XML/BAK file in here.

I am switching between Blender 3.6 and 4.2, mainly. It works fine with both versions simultaneously too, did so before and after the driverupdate.

[jwick]

Email sent to gmail.
You should be able to respond to it.
More than likely switching between those major Blender versions is the problem.

[jwick]

New file returned by email.
Let me know if it works.

[Syah Keiko]

Answered the Email but I feel like this needs closure here as well:

This... is one heavy load off of my mind. The XML you sent over is working.
Killed the driver, replaced the XML, restarted the PC, the XML was still there. Did a restart and a normal shut down to turn it on again and the file is STILL there.

After a mentally taxing week of considering buying a punching bag because everything around you is too expensive to throw at the wall. This really is a highlight, thank you so much!

Greetings, Syah

[jwick]

The solution was to increase the version of the user's cfg file to match the required version of the current default cfg file.

In general, this won't work.
We increase the version of the default cfg file when there is an incompatible change in either the application or the cfg.
IOW, when the user's cfg file won't work with the new default cfg, or, more commonly, with some incompatible application change.

In this case, the user didn't have any settings in his cfg file that conflicted with the new default cfg file. His cfg was able to be used with the new default cfg file.
Changing his file's version told the driver that, so it didn't discard the file.

User files are not deleted, they are moved to a bak dir, exactly so this sort of support can be provided.