Bug Windows 11 file type association problem

[JonasGrumby 1]

I'm unable to create file type associations for .gcode and .stl using Cura 5.2.1 on Windows 11. I have tried using Setting > Apps > Default Apps and I have tried right-clicking a file and choosing "open with". I have set Cura as the "default app" and still when I click one of these files it doesn't launch Cura. Instead I get this dialog box and clicking "Just Once" also doesn't launch Cura. Also the Cura icon is not displaying correctly in the dialog. Any ideas? Thanks.

 

[eremef 1]

same here, anyone?

[eremef 1]

@JonasGrumby: Run regedit, go to COMPUTER\HKEY_CLASSES_ROOT\ and remove all entries starting with .stl :)

Edited April 3, 2023 by eremef

[JonasGrumby 1]

@eremef

 

Thanks. It's not that simple. It's a registry problem. I had to run a run a .reg file like this. I have to do it again now that Cura v6 is out...

 

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.stl\OpenWithProgids]
".stl.4.13"=-

[-HKEY_CLASSES_ROOT\.stl.4.13]

[HKEY_CLASSES_ROOT\.stl]
@="Cura.model"

[HKEY_CLASSES_ROOT\Cura.model]
@="Standard Tessellation Language (STL) files"

[HKEY_CLASSES_ROOT\Cura.model\DefaultIcon]
@="C:\\Program Files\\Ultimaker Cura 5.2.1\\Ultimaker-Cura.exe,0"

[HKEY_CLASSES_ROOT\Cura.model\shell]
@="open"

[HKEY_CLASSES_ROOT\Cura.model\shell\open]
@="Open with Ultimaker Cura 5.2.1"

[HKEY_CLASSES_ROOT\Cura.model\shell\open\command]
@="C:\\Program Files\\Ultimaker Cura 5.2.1\\Ultimaker-Cura.exe \"%1\""

[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.stl]

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.stl\OpenWithProgids]
"Cura.model"=hex(0):

 

[lee-EB 0]

Solved:

 

I used Ctrl+F to Find all instances of "Cura" in the Registry Editor.

 

In every case where 5.3.1 existed along side 5.4.0, I deleted the 5.3.1 version.

 

In every case where 5.3.1 existed without a 5.4.0 equivalent, I modified it by only changing the "3.1" to "4.0".

 

This worked for me without doing anything additional.  Good luck.

 

 

Edited August 30, 2023 by lee-EB
I resolved the issue.

[TechieZero 0]

I did something similar to Jonas' solution above by verifying the existing registry entries. I saw that some looked weird, deleted those keys, downloaded the .MSI install and reinstalled. It works now.