Please confirm the following.
What version of the Modrinth App are you using?
Modrinth App 0.12.6
What operating systems are you seeing the problem on?
Windows
Describe the bug
While a similar issue has been fixed in November of 2025 mentioning the Modrinth App freezing when using a non-default file explorer, this issue is slightly different and my guess is that what happens now is the fix to the Modrinth App freezing previously. This is NOT an important issue and should receive attention only if the devs don't have something more important to handle imo.
When in any way the opening of a file explorer is triggered (e.g. "Open folder" Dialog on an instance.) the correct file explorer (non-default, for example; File Pilot. I will use it as an example for this issue) opens, but after ~30s the default Windows File Explorer opens up anyway, no matter if it's the default in the registry or not. While not a serious issue it gets somewhat bothersome when it happens every time I open a folder through the Modrinth App, since navigating to the folder yourself is a nuisance.
Steps to reproduce
- Set up a non-default File Explorer and make it your default through the registry, normally available through the app's settings. (e.g. File Pilot, Files, etc.)
- Open Modrinth App on a Windows Device
- Create or Open an existing Instance with any version/mod loader
- Click on the 3 dots in the top right corner of the instance page
- Click "Open folder"
- Wait till the Windows default File Explorer opens anyway
Expected behavior
The Modrinth App shouldn't open two different versions of a File explorer when the Windows File Explorer is not set as default in the registry.
Additional context
No response
Please confirm the following.
What version of the Modrinth App are you using?
Modrinth App 0.12.6
What operating systems are you seeing the problem on?
Windows
Describe the bug
While a similar issue has been fixed in November of 2025 mentioning the Modrinth App freezing when using a non-default file explorer, this issue is slightly different and my guess is that what happens now is the fix to the Modrinth App freezing previously. This is NOT an important issue and should receive attention only if the devs don't have something more important to handle imo.
When in any way the opening of a file explorer is triggered (e.g. "Open folder" Dialog on an instance.) the correct file explorer (non-default, for example; File Pilot. I will use it as an example for this issue) opens, but after ~30s the default Windows File Explorer opens up anyway, no matter if it's the default in the registry or not. While not a serious issue it gets somewhat bothersome when it happens every time I open a folder through the Modrinth App, since navigating to the folder yourself is a nuisance.
Steps to reproduce
Expected behavior
The Modrinth App shouldn't open two different versions of a File explorer when the Windows File Explorer is not set as default in the registry.
Additional context
No response