Tell us what should happen
Tell us what happens instead
Operating system:
Windows 10
Version of Telegram Desktop:
V. 1.0.29 (Windows Store Version)
Used theme:
Dark Blue (https://t.me/themes/104)
Logs:
Insert logs here (if necessary)
Here's an explanation from Microsoft on how it should be done.
https://blogs.msdn.microsoft.com/appconsult/2017/02/23/supporting-launch-at-startup-in-a-desktop-app-converted-with-the-desktop-bridge/
Same from me:
Settings for turn autostart on/off.
It doesn't start at boot and no settings for auto start.
Windows 10 (1703) / PRO, 64bit
v. 1.1.22 (Windows Store)
Default and Night Mode.
I made the neccesary changes to appx manifest, but couldn't set a build environment to test it. I guess build instruction is either wrong or incomplete.
@niks255 Where to you need help?
@auchri You can either help me set up my VS 2017 to build Telegram or build it yourself with my changes.
You can either help me set up my VS 2017 to build Telegram
Why do you thing the instructions are wrong?
@auchri Could you contact me in telegram please?
First of all, it's not clear which components of VS 2017 should be installed in order to build Telegram.
@niks255 No why? Others can benefit from our conversation here too.
I see. Well, I couldn't build LZMA SDK. Turned out, I needed Windows 8.1 SDK for that. So I installed it, but it failed to build because it couldn't find standart C++ libraries. I guess there's something wrong with build configuration?
startup folder:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
@ElvisPresly that is a workaround, not really a fix for this issue. Thanks anyways :)
I suggest the following registry changes:
This is usually what is done by a software that has the option start at boot. Since it doesn't start minimized this change will remain a workaround.
So we need an argument that will allow us to start it minimized. It seems to be possible since the Windows 10 Fall Creators Update. Maybe this link could be usefull: https://blogs.windows.com/buildingapps/2017/07/05/command-line-activation-universal-windows-apps/: it seems to be possible to define an alias and some arguments
Windows apps sucks ass, that is simple.
I'd like a true fix for this, not a workaround.
Telegram is a Win32 app, not UWP app. So it could use autostart since the release of desktop bridge. That is since anniversary update.
@niks255 Non-windows store version uses a shortcut to launch itself on boot. If there is an easy way to create such a shortcut for a window store win32 app please let me know, I'll quickly add it as well.
@niks255 But I'm not sure that even Win32 windows stora app has rights to write to the required user data folder. So I'm afraid it requires some other approach.
@john-preston You need to add some code to appx manifest. The tricky part is that you cannot pass any arguments to the executable file. So that means the app will not start minimized.
I suggest we write a small executable, which launches the main one with the background parameters and include it in the package. That is what f.lux did for their store package.
Here's how to do it:
https://blogs.msdn.microsoft.com/appconsult/2017/02/23/supporting-launch-at-startup-in-a-desktop-app-converted-with-the-desktop-bridge/
@niks255 Thanks for the info.
I'd really appreciate that feature, it's really annoying. I just discovered this repository so I'll try to learn how this feature must work in order to fix this issue asap.
I can do this, just need to set up a build environment.
If you already have a build environment, just contact me.
Was this fixed already? I'd really love to use more Windows Store apps from now on since developers port the most important apps I need over already and Auto-Updates are nice to have, but since almost none of them have Autostart it's annoying :(
This issue is still not fixed!
I have Slack installed from the Store and it has the settings to launch on startup and it works. So it's definitely possible.
Hope it will be fixed soon... Thank you.
There are still no settings for turning autostart on/off in telegram windows version. The workaround is no real workaround, since the app doesn't start minimized.
Hope it will be fixed soon. Thanks God autostart minimized on Linux works.
@pitlochry It works in Windows version from site.
As title of this issue says, we are talking about Windows Store version.
@revanmj My comment was about Linux mention above. That you don't need to go as far as Linux to find the autostart minimized :)
This issue is still not fixed :(
This issue has been opened over 1.5 years ago. How is it possible that something as easy and essential as this is still not implemented?
Is there someone working on this? If not, what can we do to help?
- Open File Explorer
- In the file address bar type shell:AppsFolder
- This will show all apps installed on your PC. Right click one of them and select "create Shortcut".
- It will create a shortcut on the the desktop.
- Finally copy the shortcut to the startup folder.
startup folder:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
It will only help till first update.
Because path to programm is different each update.
The MS blog article that was linked to twice in this thread no longer exists. (archived version)
The StartupTask class documentation and specifically remarks section has more information though that should be helpful for implementation.
Maybe I'll be able to take a look this weekend to get a buildenv going and/or create a PR for this, if nobody else picks this up.
/e: Project build setup looks quite cumbersome…
fix it please why you not fixing it
this issue is still valid?
Yes it is, there is no auto-start option and if you hack around it by starting the app from CMD, it will not start in the background. That option is missing as well.
Yeah, however You may want to try Unigram which doesn't have such problem (not sure if it's native or a workaround) and also has support for secret chats.On Jan 26, 2020 23:59, Aokromes notifications@github.com wrote:this issue is still valid?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
What a shame, Telegram team. The issue exists almost 3 years without fixing. Delete your Telegram from Windows Store if you don't support it. Save people's time to do not install Telegram twice: once from Windwos Store and then by traditional setup executable.
I suggest the following registry changes:
- Open the registry editor and go to
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run- Create a new REG_SZ Value, set the Name to Telegram (or whatever you like) and set its value to "C:\Windows\explorer.exe" "shell:appsFolder\TelegramMessengerLLP.TelegramDesktop_t4vj0pshhgkwm!Telegram.TelegramDesktop.Store"
This is usually what is done by a software that has the option start at boot. Since it doesn't start minimized this change will remain a workaround.
So we need an argument that will allow us to start it minimized. It seems to be possible since the Windows 10 Fall Creators Update. Maybe this link could be usefull: https://blogs.windows.com/buildingapps/2017/07/05/command-line-activation-universal-windows-apps/: it seems to be possible to define an alias and some arguments
Or at least : implement my workaround :
@JayBeeDe I don't want to play with registry changes. I just removed Windows Store version and installed classic version. That's it!
@Aokromes thanks for advice, possible this will help. Unfortunately I already switched to classic version of Telegram Desktop (not from Windows Store).
I’d been using it for a while until recently. I switched to Unigram now.
Отправлено из приложения "Почта" для Windows 10
От: Paul Melekhov
Отправлено: 3 февраля 2020 г. в 19:45
Кому: telegramdesktop/tdesktop
Копия: Alex Mill; Manual
Тема: Re: [telegramdesktop/tdesktop] Telegram Desktop (Windows Storeversion) doesn't start at boot (#3234)
@Aokromes thanks for advice, possible this will help. Unfortunately I already switched to classic version of Telegram Desktop (not from Windows Store).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
How does Unigram handle this issue? Can we take a look at the code that they have developed?. I'm not sure if this is a configuration issue or not
I’m not sure about the code, but it has an option like this
Come on, 3 years have passed and the store version still needs to be opened manually in each boot.
I don't understand why there's no solution in this time. Linux doesn't have this problem. There is an option that telegram starts at Linux boot... Please fix this, that we can do it via windows, too... Thanks.
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!
Anti-Stalebot-Comment... Hate this thing.
Yes, I can confirm...
Issue is still persistent on my side.
also in my side
I don't understand why there's no solution in this time.
Because it requires UWP API usage I guess
I don't understand why there's no solution in this time.
Because it requires UWP API usage I guess
no, I think you just need to update the appmanifest, need to add <desktop:StartupTask>
no, I think you just need to update the appmanifest, need to add
<desktop:StartupTask>
App manifest editing will add autostart without possibility to disable it from app
no, I think you just need to update the appmanifest, need to add
<desktop:StartupTask>
App manifest editing will add autostart without possibility to disable it from app
not sure that it is true, you have StartupTask object that you can able, but anyway user can disable and enable it from task manager (Startup tab)
not sure that it is true, you have StartupTask object that you can able
Don't understand that part of your message, documentation in one of the first comments of this issue clearly states that interacting with UWP API is needed in order to enable autostart of an app from its code
but anyway user can disable and enable it from task manager (Startup tab)
Core developers don't count that as an acceptable solution, that's why this is not implemented.
Brand new Windows 10 installation and the problem still appears. The latest version of Telegram 2.4.2
https://blogs.windows.com/windowsdeveloper/2017/08/01/configure-app-start-log/
I simple do not know why the developers don't want a StartupTask with "enabled=false" as a resolution.
For everyone who tries to come up with a solution (or workaround), thank you for your contribution!
But I also want to mention that the "Start Minimized" function is also an essential part of auto-start. At least I can't do that when using the Store version with manually adding a shortcut in shell:startup
folder as @Aokromes suggested here
Most helpful comment
This issue has been opened over 1.5 years ago. How is it possible that something as easy and essential as this is still not implemented?