What is the state of my computer before the test:
- fresh installation of the latest win11 pro version with MAS activation.
- multiple installation of thorium 3.3.0 both appx (msstore) and github exe installer
What is worked before the test:
- When I first install the github exe installer everything works fine: open with association worked, as well as the opds custom scheme. After several restarts, Thorium's behaviour (first instance opened or closed) remained unchanged, everything was functioning correctly.
- I then installed the appx version from the Microsoft Store, and everything worked correctly again, without me knowing which instance of thorium was currently running on my computer
What is the issue:
- When I remove both version of thorium 3.3.0 (exe, appx)
- Then I install the msstore (appx) version, file association and opds custom scheme association only work on the first opening of the application.
- All subsequent attempts to open the Thorium application fail! I can therefore reproduce the issue.
- Same behaviour when I do the same thing with the exe installer version
So this is not an issue with the appx version neither with the exe installer, but from an installation mix between them, I cannot be 100% sure if the appx worked correctly before my dysfunctional test, because I ran mostly the exe installer first. What I find very strange, is why is it working on the first launch, and stop working then. File association and opds custom scheme both are working on the first start after fresh installation. But why, this is strange ? File association are working as a parameters on the command line arguments of the application. So in this case, maybe the argument position of the filepath is not the same, or not sent. Same thing for the opds custom scheme is it registered on the first start of the application and then triggered with a electron event. So maybe the system does not send the event properly. We need to deep dive in it and better understand how is it working under the hood on win11.
What is the state of my computer before the test:
What is worked before the test:
What is the issue:
So this is not an issue with the appx version neither with the exe installer, but from an installation mix between them, I cannot be 100% sure if the appx worked correctly before my dysfunctional test, because I ran mostly the exe installer first. What I find very strange, is why is it working on the first launch, and stop working then. File association and opds custom scheme both are working on the first start after fresh installation. But why, this is strange ? File association are working as a parameters on the command line arguments of the application. So in this case, maybe the argument position of the filepath is not the same, or not sent. Same thing for the opds custom scheme is it registered on the first start of the application and then triggered with a electron event. So maybe the system does not send the event properly. We need to deep dive in it and better understand how is it working under the hood on win11.