tg links stop working if I move portable exe to another folder

[KosMos-pv]

I downloaded portable version of Telegram and it registered tg:// links so I can open them in any browser. But I decided to move my Telegram instance to another folder. And now I can't open these links anymore. I tried to run Telegram with admin rights but it did not help. Now tg:// protocol is registered to wrong location of Telegram and I need to edit registry manually to make it work again. It would be great that Telegram will check automatically on every startup if protocol is registered correctly, not only at first startup of portable version. ### Steps to reproduce 1. Unpack Telegram portable to any folder (ex D:\Soft\Telegram\). 2. Run Telegram and try to open any th link in any browser. It works fine. 3. Move Telegram to different folder (ex D:\Soft\Telegram new). ### Expected behaviour If I launch Telegram from new location it shoud automatically fix tg:// protocol for a new location of exe. ### Actual behaviour Nothing happens and I need to edit registry manually. I did not find any option to register portable version with tg:// protocol and starting app with admin rights doesn't resolve this problem. ### Configuration **Operating system:** Windows 10 version 1607 **Version of Telegram Desktop:** 0.10.19

[stek29]

Why does portable version even register custom protocol?..

[john-preston]

@KosMos-pv Thanks for your report.

[sergeevabc]

Faced this issue today. Almost a year passed since the initial report. Still not resolved?

[sergeevabc]

Moreover, after manual tg:// re-registration within a browser, Telegram Portable fails to use its current profile when is launched by browser — Telegram Portable forces user to create a new profile instead.

Pic 1. telegram.exe launched by user (works as expected).

Pic 2. telegram.exe + tdata moved to a new location and launched by browser (fails to use profile).

[auchri]

@sergeevabc Please look in the registry, I assume there are the old paths.

[sergeevabc]

Portable means no traces should be left in the registry. And if app does so, then it must handle own traces in a proper way when app's folder is moved, i.e. fix is required. Telegram developers, are you there?

[auchri]

@sergeevabc Yea, but please verify that the paths are wrong.

[auchri]

@sergeevabc Also I don't think that portable apps can registery protocol handler without using the registry.

[john-preston]

@sergeevabc I'm afraid "manual protocol registration within browser" isn't handled. Telegram Desktop for Windows uses its working dir as a place for data files, so I guess it is launched with different working dir from that "registration".

[kochetkov-av]

Telegram portable seems to overwrite association every time I start new instance. On my Windows 10 both version installed, first normal version, then two portables. And now it's a whole new quest, with registry and google search, to return tg:// association to my not portable version.

[ghost]

Hey there!

We're automatically closing this issue since there was no activity in this issue since 401 days ago. We therefore assume that the user has lost interest or resolved the problem on their own. Closed issues that remain inactive for a long period may get automatically locked.

Don't worry though; if this is in error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

_{(Please note that this is an automated comment.)}

[stek29]

Does it still occur?

[online]

@stek29 yes.

[Aokromes]

this issue is still valid?

[Neurotoxin001]

Still on 2.1.10

UPD: entering registertg in settings is helped

I think telegram should check hes last folder and if it's changed - registertg must be auto entered after launch.

[stale[bot]]

Hey there!

This issue will be automatically closed in 7 days if there would be no activity. We therefore assume that the user has lost interest or resolved the problem on their own.

Don't worry though; if this is an error, let us know with a comment and we'll be happy to reopen the issue.

Thanks!

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.