Submit qBittorrent for Windows to Microsoft Store

[rakleed]

Suggestion

Could you please submit qBittorent for Windows to the Microsoft Store so it's easier to download and users don't have to think about updates? With the release of Windows 11, it became possible to submit traditional desktop apps (Win32) in the Microsoft Store, not just UWP. Learn more: https://developer.microsoft.com/en-us/microsoft-store/desktop-apps/.

Use case

So it's easier to download and users don't have to think about updates.

Extra info/examples/attachments

Earlier you mentioned that you are not interested in distribution on Stores (#9165 (comment)). Your position has not changed since then, despite the fact that this is Microsoft's Store and you do not need to change the app to submit it?

[OpenSpaghettiSauce]

My word means nothing here, but:

• qBittorrent's installer/EXE is not signed. I think that's a requirement. It is extremely expensive and tedious to do so. (last time I checked)
• Not sure what kind of installer/setup Store requires. IIRC it uses MSIX?
• UWP had serious permission limitations last time I checked.
• qBittorrent offers many, many builds with each release. For example, Qt5/Qt6. Lt2 build. On Store, you can only deliver one.
• Store could also introduce many more issues that'd land right here. Ie.: What about configs? What about migrating installation? What about importing from other client scripts? What about upgrading between versions?
• Microsoft is the new Google. They changed their mind on this. Who knows when they will change it again?

I don't know, I'm just a bit skeptical about it. It's maybe just me though.

I think Store is great! Scammers use it all the time to re-package open-source applications and rip people off. So it is definitely useful for some (scammers). And less useful for others (actual users and the devs.)

[hichemfantar]

@OpenSpaghettiSauce on your third point, windows store now allows Win32 apps.
Although I agree, I don't see much value in publishing qbt to the windows store.

[Balls0fSteel]

Oh I know @hichemfantar , but it still requires preparation/changes on the packaging/installer end of things.

[Balls0fSteel]

Also, FIXME on this one, but qBittorrent's current installer allows for disabling the Windows path limit for example. Putting out an icon, etc. I am not sure if these are available if you use Store to install an app.

(Heck, this is a personal "issue" I suppose, but I cannot even find if something is installed. It may or may not appear in Start menu. Sometimes I have to open Store, find the application through My Library and then select it, and then Start. Then I have to pin it, so it may appear properly.)

But anyway! Code signing is a must for all of this.

[soredake]

I agree, I don't see much value in publishing qbt to the windows store.

Auto updates, maybe? If this #17698 will be fixed and installer will terminate running process and launch qbittorrent again.

[hichemfantar]

I personally have auto updates disabled in the windows store.
A better solution would be a built-in updater in qbt.

[soredake]

felixrieseberg/windows95#221

[RokeJulianLockhart]

Although @soredake links a useful issue, .msix support hasn't been necessary to publish to the Microsoft Store since Windows 11's release. However, can anyone confirm that due to https://winget.run/pkg/qBittorrent/qBittorrent, qBitTorrent is at least installable via the Microsoft Store's GUI, even if not via the Store's backend (store) repository via https://github.com/microsoft/winget-cli? It might/should be.

[soredake]

qBitTorrent is at least installable via the Microsoft Store's GUI, even if not via the Store's backend (store) repository via microsoft/winget-cli?

No, it's not, and never be. The point of submitting qbittorent to microsoft store is to use .msix format for easy updates (#18115 #18582) and signed executable (#18028)