Associate .3mf and .stl files with PrusaSlicer in Windows #8332
Labels
Comments
ygoe
changed the title
|
Have you checked the settings in Windows? https://support.microsoft.com/en-us/windows/change-default-programs-in-windows-e5d82cad-17d1-c53b-3505-f10a32e1894d It should look like this then and works fine |
|
One may certainly register PrusaSlicer manually. We implemented automatic registration into PrusaSlicer Windows build, however it may not work correctly as it manipulates registry the old way. @enricoturri1966 is responsible for that. |
|
In the Windows settings, both file extensions had no default app. I could select PrusaSlicer from the list and now they open as expected. That's how I do it manually. And what does the option in the PrusaSlicer settings do? |
|
We investigated the issue further. Since Windows 10 applications are no more allowed to register file extensions. Thus we will have to remove the option from PrusaSlicer settings. We are investigating futher whether the installer will be allowed to register the file extension. |
|
This isn't true, lots of other applications can do it as well. Maybe it's the API that has changed. Note that file extensions can be registered per system (required admin rights) or per user (works anytime). |
|
This isn't true, lots of other applications can do it as well.
Which applications?
Two of us PrusaSlicer developers believe that Microsoft made a lot of
effort to disable such functionality. We will be most happy if you point us
to the API we should use.
Note that file extensions can be registered per system (required admin
rights) or per user (works anytime).
By the application or by the user?
AFAIK it is not possible by the application. Yes, you can register the
extension manually.
po 23. 5. 2022 v 8:30 odesílatel Yves Goergen ***@***.***>
napsal:
… This isn't true, lots of other applications can do it as well. Maybe it's
the API that has changed. Note that file extensions can be registered per
system (required admin rights) or per user (works anytime).
—
Reply to this email directly, view it on GitHub
<#8332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI6P5ETW4R4LZ54CMTDVLMQWZANCNFSM5V56QWVQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Which applications can register their file extensions? At least in a way that Windows asks next time and suggests the new app in a list of alternatives? Umm, let me go through my installed applications...
I usually open files through a file commander (like Explorer) and not through the app itself, so I know when it doesn't work. That's the most common apps. I don't know how they do it. Most of them are open source. Maybe you can investigate how Inno Setup does it, IIRC it has a command to register file extensions for the installed app. Also, Stack Overflow is a good resource to ask for advice. It's been a while since I last registered a file extension for one of my apps, but it did work in Windows 10 as before without problems. After all, there's a registry branch that contains all the data. You can always write it yourself: HKEY_CURRENT_USER\SOFTWARE\Classes This should work: Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Classes\.3mf]
@="Prusa.Slicer.1"
[HKEY_CURRENT_USER\SOFTWARE\Classes\Prusa.Slicer.1\Shell\Open\Command]
@="\"C:\\Program Files\\Prusa3D\\PrusaSlicer\\prusa-slicer.exe\" \"%1\""And here's the Inno Setup script to register *.fl with my app. Seems to use the system-wide settings. |
|
It may be that it was not the application, but the application installer
that did the registration. We are looking into it.
Applications are not allowed to change registration anymore. Installers
likely are. PrusaSlicer team is only writing the application while another
team is doing the installer for us. We are working on that.
po 23. 5. 2022 v 14:19 odesílatel Yves Goergen ***@***.***>
napsal:
… Which applications can register their file extensions? At least in a way
that Windows asks next time and suggests the new app in a list of
alternatives? Umm, let me go through my installed applications...
- Firefox (.html, .url) (same for Brave and Chrome if you wanted)
- Visual Studio (.sln, .csproj, .cs and loads more)
- DBeaver (.sql)
- Inno Setup / Inno Script Studio (.iss)
- OpenSCAD (.scad) (I think FreeCAD also has one, I haven't really
used it yet)
- Microsoft Office (.docx, .xlsx and loads more) (LibreOffice should
also have a few)
- Acrobat Reader (.pdf with some strange instructions)
- Paint.NET (.png, .jpg ...)
- Affinity Photo/Designer (.afphoto, .afdesign)
- VLC (.mkv, .mp4 ...)
- Notepad++ (.txt and anything you want, with manual setup within the
app settings, not Windows)
I usually open files through a file commander (like Explorer) and not
through the app itself, so I know when it doesn't work.
That's the most common apps. I don't know how they do it. Most of them are
open source. Maybe you can investigate how Inno Setup does it, IIRC it has
a command to register file extensions for the installed app. Also, Stack
Overflow is a good resource to ask for advice. It's been a while since I
last registered a file extension for one of my apps, but it did work in
Windows 10 as before without problems.
After all, there's a registry branch that contains all the data. You can
always write it yourself: HKEY_CURRENT_USER\SOFTWARE\Classes
This should work:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Classes\.3mf]@="Prusa.Slicer.1"
[HKEY_CURRENT_USER\SOFTWARE\Classes\Prusa.Slicer.1\Shell\Open\Command]@="\"C:\\Program Files\\Prusa3D\\PrusaSlicer\\prusa-slicer.exe\" \"%1\""
And here's the Inno Setup script to register *.fl with my app. Seems to
use the system-wide settings.
[Registry]
; Register .fl file name extension
Root: HKCR; Subkey: ".fl"; ValueType: string; ValueName: ""; ValueData: "FieldLogFile"; Flags: uninsdeletevalue
Root: HKCR; Subkey: "FieldLogFile"; ValueType: string; ValueName: ""; ValueData: "FieldLog file"; Flags: uninsdeletekey
Root: HKCR; Subkey: "FieldLogFile\DefaultIcon"; ValueType: string; ValueName: ""; ValueData: "{app}\FieldLogViewer.exe,1"
Root: HKCR; Subkey: "FieldLogFile\shell\open\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" ""%1"""
Root: HKCR; Subkey: "FieldLogFile\shell\opensingle"; ValueType: string; ValueName: ""; ValueData: "{cm:OpenSingleFileCommand}"
Root: HKCR; Subkey: "FieldLogFile\shell\opensingle\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" /s ""%1"""
; Add to .fl "Open with" menu
Root: HKCR; Subkey: ".fl\OpenWithList\FieldLogViewer.exe"; ValueType: string; ValueName: ""; ValueData: ""; Flags: uninsdeletekey
Root: HKCR; Subkey: "Applications\FieldLogViewer.exe"; ValueType: string; ValueName: "FriendlyAppName"; ValueData: "FieldLogViewer"; Flags: uninsdeletekey
Root: HKCR; Subkey: "Applications\FieldLogViewer.exe\shell\open"; ValueType: string; ValueName: "FriendlyAppName"; ValueData: "FieldLogViewer"
Root: HKCR; Subkey: "Applications\FieldLogViewer.exe\shell\open\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" ""%1"""
—
Reply to this email directly, view it on GitHub
<#8332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSI5E3TI4IXRBEKVV6TTVLNZTRANCNFSM5V56QWVQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
After all, there's a registry branch that contains all the data. You can
always write it yourself: HKEY_CURRENT_USER\SOFTWARE\Classes
Since Windows 10, this section needs to be signed and the code to sign the
section is not public. The manual registration does not work if it is not
signed properly.
po 23. 5. 2022 v 17:10 odesílatel Vojtech Bubnik ***@***.***>
napsal:
… It may be that it was not the application, but the application installer
that did the registration. We are looking into it.
Applications are not allowed to change registration anymore. Installers
likely are. PrusaSlicer team is only writing the application while another
team is doing the installer for us. We are working on that.
po 23. 5. 2022 v 14:19 odesílatel Yves Goergen ***@***.***>
napsal:
> Which applications can register their file extensions? At least in a way
> that Windows asks next time and suggests the new app in a list of
> alternatives? Umm, let me go through my installed applications...
>
> - Firefox (.html, .url) (same for Brave and Chrome if you wanted)
> - Visual Studio (.sln, .csproj, .cs and loads more)
> - DBeaver (.sql)
> - Inno Setup / Inno Script Studio (.iss)
> - OpenSCAD (.scad) (I think FreeCAD also has one, I haven't really
> used it yet)
> - Microsoft Office (.docx, .xlsx and loads more) (LibreOffice should
> also have a few)
> - Acrobat Reader (.pdf with some strange instructions)
> - Paint.NET (.png, .jpg ...)
> - Affinity Photo/Designer (.afphoto, .afdesign)
> - VLC (.mkv, .mp4 ...)
> - Notepad++ (.txt and anything you want, with manual setup within the
> app settings, not Windows)
>
> I usually open files through a file commander (like Explorer) and not
> through the app itself, so I know when it doesn't work.
>
> That's the most common apps. I don't know how they do it. Most of them
> are open source. Maybe you can investigate how Inno Setup does it, IIRC it
> has a command to register file extensions for the installed app. Also,
> Stack Overflow is a good resource to ask for advice. It's been a while
> since I last registered a file extension for one of my apps, but it did
> work in Windows 10 as before without problems.
>
> After all, there's a registry branch that contains all the data. You can
> always write it yourself: HKEY_CURRENT_USER\SOFTWARE\Classes
>
> This should work:
>
> Windows Registry Editor Version 5.00
>
> [HKEY_CURRENT_USER\SOFTWARE\Classes\.3mf]@="Prusa.Slicer.1"
>
> [HKEY_CURRENT_USER\SOFTWARE\Classes\Prusa.Slicer.1\Shell\Open\Command]@="\"C:\\Program Files\\Prusa3D\\PrusaSlicer\\prusa-slicer.exe\" \"%1\""
>
> And here's the Inno Setup script to register *.fl with my app. Seems to
> use the system-wide settings.
>
> [Registry]
> ; Register .fl file name extension
> Root: HKCR; Subkey: ".fl"; ValueType: string; ValueName: ""; ValueData: "FieldLogFile"; Flags: uninsdeletevalue
> Root: HKCR; Subkey: "FieldLogFile"; ValueType: string; ValueName: ""; ValueData: "FieldLog file"; Flags: uninsdeletekey
> Root: HKCR; Subkey: "FieldLogFile\DefaultIcon"; ValueType: string; ValueName: ""; ValueData: "{app}\FieldLogViewer.exe,1"
> Root: HKCR; Subkey: "FieldLogFile\shell\open\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" ""%1"""
> Root: HKCR; Subkey: "FieldLogFile\shell\opensingle"; ValueType: string; ValueName: ""; ValueData: "{cm:OpenSingleFileCommand}"
> Root: HKCR; Subkey: "FieldLogFile\shell\opensingle\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" /s ""%1"""
>
> ; Add to .fl "Open with" menu
> Root: HKCR; Subkey: ".fl\OpenWithList\FieldLogViewer.exe"; ValueType: string; ValueName: ""; ValueData: ""; Flags: uninsdeletekey
> Root: HKCR; Subkey: "Applications\FieldLogViewer.exe"; ValueType: string; ValueName: "FriendlyAppName"; ValueData: "FieldLogViewer"; Flags: uninsdeletekey
> Root: HKCR; Subkey: "Applications\FieldLogViewer.exe\shell\open"; ValueType: string; ValueName: "FriendlyAppName"; ValueData: "FieldLogViewer"
> Root: HKCR; Subkey: "Applications\FieldLogViewer.exe\shell\open\command"; ValueType: string; ValueName: ""; ValueData: """{app}\FieldLogViewer.exe"" ""%1"""
>
> —
> Reply to this email directly, view it on GitHub
> <#8332 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABMPSI5E3TI4IXRBEKVV6TTVLNZTRANCNFSM5V56QWVQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
Hm, I thought that installers were just applications, too. (I'm talking about Inno Setup, Nullsoft Installer or other custom installers, not that MSI crap.) The registry API is available to all processes, within their user account privilege limits. And the current_user hive is certainly writeable by the user, that's what it's there for. It means that format associations are only set for the current user, not all users on the system, but that's totally fine actually. It doesn't matter if it's the installer or the app itself that does the association, it's just a matter of user experience. The installer provides a little more comfort and an easy start (and can register for all users if already installing for all users as admin); the app setting allows easy later changes. I'm fine with either one. And tell me more about that "registry signing"? Never heard of that. |
|
I was as surprised as you are.
https://www.howtogeek.com/fyi/microsoft-broke-windows-10s-file-associations-with-a-botched-update/
https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/
http://woshub.com/managing-default-file-associations-in-windows-10/
https://devblogs.microsoft.com/oldnewthing/?p=96175
https://www.winhelponline.com/blog/windows-10-resetting-file-associations/
I have to digest it myself. Maybe they block just those extensions to be
modified which were already registered. For us it means we cannot change
registration of 3MFs, because they were associated with the microsoft 3D
Builder.
po 23. 5. 2022 v 18:01 odesílatel Yves Goergen ***@***.***>
napsal:
… Hm, I thought that installers were just applications, too. (I'm talking
about Inno Setup, Nullsoft Installer or other custom installers, not that
MSI crap.) The registry API is available to all processes, within their
user account privilege limits. And the current_user hive is certainly
writeable by the user, that's what it's there for. It means that format
associations are only set for the current user, not all users on the
system, but that's totally fine actually. It doesn't matter if it's the
installer or the app itself that does the association, it's just a matter
of user experience. The installer provides a little more comfort and an
easy start (and can register for all users if already installing for all
users as admin); the app setting allows easy later changes. I'm fine with
either one.
And tell me more about that "registry signing"? Never heard of that.
—
Reply to this email directly, view it on GitHub
<#8332 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMPSIYS3PXYRQC4KC532DDVLOTXFANCNFSM5V56QWVQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
https://docs.microsoft.com/en-us/archive/blogs/windowsinternals/windows-10-how-to-configure-file-associations-for-it-pros
út 24. 5. 2022 v 5:42 odesílatel Vojtech Bubnik ***@***.***>
napsal:
… I was as surprised as you are.
https://www.howtogeek.com/fyi/microsoft-broke-windows-10s-file-associations-with-a-botched-update/
https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/
http://woshub.com/managing-default-file-associations-in-windows-10/
https://devblogs.microsoft.com/oldnewthing/?p=96175
https://www.winhelponline.com/blog/windows-10-resetting-file-associations/
I have to digest it myself. Maybe they block just those extensions to be
modified which were already registered. For us it means we cannot change
registration of 3MFs, because they were associated with the microsoft 3D
Builder.
po 23. 5. 2022 v 18:01 odesílatel Yves Goergen ***@***.***>
napsal:
> Hm, I thought that installers were just applications, too. (I'm talking
> about Inno Setup, Nullsoft Installer or other custom installers, not that
> MSI crap.) The registry API is available to all processes, within their
> user account privilege limits. And the current_user hive is certainly
> writeable by the user, that's what it's there for. It means that format
> associations are only set for the current user, not all users on the
> system, but that's totally fine actually. It doesn't matter if it's the
> installer or the app itself that does the association, it's just a matter
> of user experience. The installer provides a little more comfort and an
> easy start (and can register for all users if already installing for all
> users as admin); the app setting allows easy later changes. I'm fine with
> either one.
>
> And tell me more about that "registry signing"? Never heard of that.
>
> —
> Reply to this email directly, view it on GitHub
> <#8332 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/ABMPSIYS3PXYRQC4KC532DDVLOTXFANCNFSM5V56QWVQ>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
|
https://danysys.com/set-file-type-association-default-application-command-line-windows-10-userchoice-hash-internal-method/
Source code of the hash generator
https://pastebin.com/yVhWeQ3X
and how Mozilla did it
https://searchfox.org/mozilla-central/source/browser/components/shell/WindowsUserChoice.cpp#194
https://hg.mozilla.org/mozilla-central/rev/e928b3e95a6c3b7257d0ba475fc2303bfbad1874
https://hg.mozilla.org/releases/mozilla-release/diff/7e775ce432b599c6daf7ac379aa42f1e9b3b33ed/browser/components/shell/WindowsUserChoice.cpp
út 24. 5. 2022 v 6:19 odesílatel Vojtech Bubnik ***@***.***>
napsal:
… Implementation of the hashing algorithm in some obscure basic-like language
https://github.com/DanysysTeam/SFTA
https://www.theverge.com/2021/9/13/22671182/mozilla-default-browser-windows-protections-firefox
https://news.ycombinator.com/item?id=28510490&p=2
You see, that's why we still don't have the FDM tree supports.
út 24. 5. 2022 v 6:06 odesílatel Vojtech Bubnik ***@***.***>
napsal:
>
> https://docs.microsoft.com/en-us/archive/blogs/windowsinternals/windows-10-how-to-configure-file-associations-for-it-pros
>
> út 24. 5. 2022 v 5:42 odesílatel Vojtech Bubnik <
> ***@***.***> napsal:
>
>> I was as surprised as you are.
>>
>>
>> https://www.howtogeek.com/fyi/microsoft-broke-windows-10s-file-associations-with-a-botched-update/
>>
>> https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/
>> http://woshub.com/managing-default-file-associations-in-windows-10/
>> https://devblogs.microsoft.com/oldnewthing/?p=96175
>>
>> https://www.winhelponline.com/blog/windows-10-resetting-file-associations/
>>
>> I have to digest it myself. Maybe they block just those extensions to be
>> modified which were already registered. For us it means we cannot change
>> registration of 3MFs, because they were associated with the microsoft 3D
>> Builder.
>>
>>
>>
>> po 23. 5. 2022 v 18:01 odesílatel Yves Goergen ***@***.***>
>> napsal:
>>
>>> Hm, I thought that installers were just applications, too. (I'm talking
>>> about Inno Setup, Nullsoft Installer or other custom installers, not that
>>> MSI crap.) The registry API is available to all processes, within their
>>> user account privilege limits. And the current_user hive is certainly
>>> writeable by the user, that's what it's there for. It means that format
>>> associations are only set for the current user, not all users on the
>>> system, but that's totally fine actually. It doesn't matter if it's the
>>> installer or the app itself that does the association, it's just a matter
>>> of user experience. The installer provides a little more comfort and an
>>> easy start (and can register for all users if already installing for all
>>> users as admin); the app setting allows easy later changes. I'm fine with
>>> either one.
>>>
>>> And tell me more about that "registry signing"? Never heard of that.
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <#8332 (comment)>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/ABMPSIYS3PXYRQC4KC532DDVLOTXFANCNFSM5V56QWVQ>
>>> .
>>> You are receiving this because you commented.Message ID:
>>> ***@***.***>
>>>
>>
|
enricoturri1966
added a commit
that referenced
this issue
May 25, 2022
…rusaSlicer as default application for .3mf and .stl files and GCodeViewer as default application for .gcode files
2 tasks
|
Implementation of the hashing algorithm in some obscure basic-like language
https://github.com/DanysysTeam/SFTA
https://www.theverge.com/2021/9/13/22671182/mozilla-default-browser-windows-protections-firefox
https://news.ycombinator.com/item?id=28510490&p=2
You see, that's why we still don't have the FDM tree supports.
út 24. 5. 2022 v 6:06 odesílatel Vojtech Bubnik ***@***.***>
napsal:
…
https://docs.microsoft.com/en-us/archive/blogs/windowsinternals/windows-10-how-to-configure-file-associations-for-it-pros
út 24. 5. 2022 v 5:42 odesílatel Vojtech Bubnik ***@***.***>
napsal:
> I was as surprised as you are.
>
>
> https://www.howtogeek.com/fyi/microsoft-broke-windows-10s-file-associations-with-a-botched-update/
>
> https://kolbi.cz/blog/2017/10/25/setuserfta-userchoice-hash-defeated-set-file-type-associations-per-user/
> http://woshub.com/managing-default-file-associations-in-windows-10/
> https://devblogs.microsoft.com/oldnewthing/?p=96175
> https://www.winhelponline.com/blog/windows-10-resetting-file-associations/
>
> I have to digest it myself. Maybe they block just those extensions to be
> modified which were already registered. For us it means we cannot change
> registration of 3MFs, because they were associated with the microsoft 3D
> Builder.
>
>
>
> po 23. 5. 2022 v 18:01 odesílatel Yves Goergen ***@***.***>
> napsal:
>
>> Hm, I thought that installers were just applications, too. (I'm talking
>> about Inno Setup, Nullsoft Installer or other custom installers, not that
>> MSI crap.) The registry API is available to all processes, within their
>> user account privilege limits. And the current_user hive is certainly
>> writeable by the user, that's what it's there for. It means that format
>> associations are only set for the current user, not all users on the
>> system, but that's totally fine actually. It doesn't matter if it's the
>> installer or the app itself that does the association, it's just a matter
>> of user experience. The installer provides a little more comfort and an
>> easy start (and can register for all users if already installing for all
>> users as admin); the app setting allows easy later changes. I'm fine with
>> either one.
>>
>> And tell me more about that "registry signing"? Never heard of that.
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#8332 (comment)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/ABMPSIYS3PXYRQC4KC532DDVLOTXFANCNFSM5V56QWVQ>
>> .
>> You are receiving this because you commented.Message ID:
>> ***@***.***>
>>
>
|
|
We tried to fix this in 2.6.0-alpha2. Feedback is appreciated. |
|
I'm not 100% if this is the same issue but I cannot open .stl files using prusa slicer 2.6.0-alpha2.
Not sure if this is caused by multiple installations (both alpha and stable), I tried removing others but issue persists. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of the bug
.3mf files are not opened with any application in SpeedCommander. They also have no icon. When double-clicking, I get the error message that there is no application associated with this file type. When double-clicking in Windows Explorer, it opens in Paint 3D. I guess that's an error.
Similar problem for .stl files. No associated app for Speed Commander. Explorer at least asks how to open the file and includes PrusaSlicer in the options. I selected it and it opened so. Next time, it didn't ask but open in Paint 3D instead. Looks like Microsoft doesn't like PrusaSlicer for some obscure reason.
I already checked the program settings and enabled the corresponding option to associate PrusaSlicer with these formats. The setting is also saved for the next program start. But it has zero effect.
Project file & How to reproduce
All .3mf files
Checklist of files included above
Version of PrusaSlicer
2.4.2+win64
Operating system
Windows 10 21H2
Printer model
Mini+ (irrelevant)
The text was updated successfully, but these errors were encountered: