Bluescreen2001

It seems most of these changes are between 5.5 and 5.1. I checked the file on my 5.5 version of my companies laptop and compared it with yours. It's the same. I tried that file in my 5.1 installation and it doesn't change anything. I also checked my file for special characters like tabs. There are none. I also cannot really believe that spaces or tabs can break such file. It is JSON format and since most of Cura seems to be written in Python, I thing it uses standard json libs and they normally accept this. Missing comma, or brackets or something would break them, yes. But what is interesting is ther version number. My Voron base file has version 2. Your's too. But the files in my AppData directory have version 4! I tried to change this for the voron2_extruder file there but it makes things worse. It the displays that file as incorrect, too. I the searched for the string "Voron_user" in all files in all the Cura directories and don't find it. Where the hell ist that "user profile" located? Oh, that was stupid Windows find function. Good old grep find some locations. I find one interesting thing in stderr.log: stderr.log:2023-11-16 18:22:40,485 - ERROR - [MainThread] UM.Settings.ContainerStack.deserialize [429]: When trying to deserialize Voron, we received an unknown container ID (Voron_user) stderr.log:2023-11-16 18:22:40,485 - ERROR - [MainThread] UM.Settings.ContainerRegistry.findContainers [217]: Exception: Error in the format of container Voron: When trying to deserialize Voron, we received an unknown container ID (Voron_user) Containers are found in C:\Users\<user>\AppData\Roaming\cura\5.1\machine_instances/Voron.global.cfg. There you find a container Voron_user with number 0 and voron2_300 with number 7. But to what does this reference.

Yes, I did this (closing with X). Then Cura starts with it's initial setup process (select printer, etc.). I closed that too, because I thought it will overwrite my settings then.

Hi Slashee Thank you for your answer. First, I cannot go to Show Configuration folder because I cannot start Cura without loosing my settings. I find the file named voron2_300.def.json in folder C:\Program Files\Ultimaker Cura 5.1.0\share\cura\resources\definitions. But this has an old modification date, which fits the installation date of Cura. So I don't think, this is the cause. I tried to remove it without success. The only new file there is voron2_base.def.json. I don't know, why it has a newer modification date. I attach it here. It seems to reference an extruder file named voron2_extruder_0 which also has an old modification date. I attach it, too. Strange is also that I now get two corrupt profiles: Voron and Voron_user. No Voron #2 anymore. The only way to start Cura is to delete the folder C:\Users\<username>\AppData\Roaming\cura. But then I loose all my settings. But what do I really loose this way? The printer settings itself is no great deal, because it's a standard Voron. But what about materials and some calibration settings like flow or something. Are these included my 3mf files of old jobs? For me it is very unclear where Cura stores which data. It would be much easier if there would be different file save/load options for things like materials, machine parameters, print profiles because then it would be clear. Now I never know where which parameters come from. So I always load an old project, delete all objects and insert the new ones. voron2_base.def.json.log voron2_extruder_0.def.json.log

Hi I just installed the "printer settings" plugin from the marketplace to my Cura 5.1 installation. After that I cannot start Cura anymore because of the following error message: No, I don't want to reset all my settings! So I quit Cura without doing anything else. I spend days for optimising and calibrating my settings. What can I do to solve that issue. I attach the Cura log to this message and hope someone can help me. Then mentioned Voron #2 profile was an early experiment to add a second (virtual) extruder. But this was there for ages and not used. If it is possible to remove this, mthat maybe a solution. cura.log