Doesn't open with boot #259
Comments
tellmewhy12
changed the title
|
We're currently in the process of developing a next major version (version X/v10) We offer bleeding edge builds to our Telegram insider group, if you're up for that. |
|
Telegram? Interesting, usually these cults are on Discord or Slack :P |
|
Overlord @Armin2208 is a telegram fanboi, as such we reside there! |
|
Version X is out, please download, try again and close the issue if it works |
|
@Spiritreader Awesome! I will check it out. |
|
On the time page, you might have to put it to disabled, and then back to the setting you had before to make it work. |
|
Hello again! Okay, the App still didn't start with boot. But what improved this time is that it automatically switched theme after I started the app and I didn't have to click "Apply" anymore! And there is a tray Icon. I really like the new features btw. Accent colour is great 🤩 I have Login-Task unchecked right now. If I try checking it I get the error But after starting it in Administrator mode it didn't give me an error. I will try restarting my PC and see if it starts the App. EDIT: It didn't work, I might try putting it into shell:startup |
|
Can you attach the service.log? (make sure you remove all geographic coordinates before) |
|
|
Is there an commandline argument to let it run only in the background? For if the shell:startup shortcut workaround works it might also be an alternative |
|
Two things that are happening here: However, without logon task, the auto start entry appears to set without exeption, meaning that the registry key should in theory pop up. Since I cannot reproduce this on any test system, I can't say it's a definite bug and may be a permission issue (note: administrator rights. The shell:startup shortcut would work, however, we would only want to resort to this measure, if we definitely know the auto start entry add method fails. Can you check whether you can add auto dark mode via powershell? Set-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\RunOnce" -Name 'AutoDarkMode' -Value "${REPLACE_WITH_PATH_TO/AutoDarkModeSvc.exe}"Replace the variable here If adding via powershell works, I will have to go through a few fixes probably to make it work, |
|
@Spiritreader Yes awesome, this worked! It opens in the tray now. I had to run PowerShell as Administrator, though. |
|
I'm also having issues with the newest X release and auto start is not working for me. On first launch after extraction to test if it runs at all... End result: No auto start. (In case this is better off in its own issue, please move it or let me know to recreate it) |
It's kind of a not-issue, as this is expected behavior. You can reset the auto start entry by going to the time page in the app, select disabled, and then your previous setting again. Alternatively, you can open the AutoDarkModeShell (found in the same directory), sending '--add-autostart' |
|
@mangoepic Could you please download the newest beta build (update 10.0.1.14 should be available via the beta channel)? I would like you to perform the following steps:
|
I renamed the original key and did the steps again. It created the key AutoDarkMode again.
|
|
Thank you very much! The regkeys were set by adm both times. In case you want to know why I asked you to do this:
So essentially, auto start works as expected. A behavior change is required to ensure the auto start entry is preserved when setting the logon task fails. |
- make the auto start setting more persistent if logon task fails (#259) - add more verbose error messages in app - fix oversight in gpu monitoring module
|
I have made it a lot more difficult to enable the logon task when ADM has insufficient permissions to use the task scheduler, or it fails due to other reasons. In addition, if the logon task operation errors, the auto start entry will no longer wrongfully be deleted. This is available from build 10.0.1.17 onwards. |
Thanks for your explanation, that helped a lot. @Spiritreader I still think this is not self-explanatory and users could easily run into similar issues. Throwing ideas here... Those could lead to a better interface and help the users solve potential problems on their own. |
|
@tooomm The only way to really remove it is by:
The autostart setting is not tracked by auto dark mode itself, you can either send an "add it" or a "remove it" command to it and it will comply. For your suggestions in general, please create a new issue for such ideas/improvements, as it is easier to track. |
The App doesn't start after boot and I have to start it manually and click apply for it to start working after booting (I installed as Administrator and unchecked Login-Task)
Any ideas?
OS: Windows 21H1
The text was updated successfully, but these errors were encountered: