File-New-Project / EarTrumpet

EarTrumpet - Volume Control for Windows
https://eartrumpet.app
Other
9.03k stars 515 forks source link

EarTrumpet does not lunch on start up #1569

Closed GRANDGG-1first closed 5 months ago

GRANDGG-1first commented 5 months ago

Summary

recnetly i had this problem with EarTrumpet not lunching on start up , i do enable it on the startup tab in task manager but after a reboot it is disable , i didn't have this prbleme until recently , it could be windows update or pc manager from microsoft wich is unistalled right now , another thing that could be related somehow is that my taskbar settings change either after a reboot or just in sleep mode stuff that i have turned off like news and interestes , and keeping only the search icon wich gets replaced by full search bar , and task view button too

Steps to reproduce

i dont know

EarTrumpet version

2.3.0.0

Windows version

10.0.19045.4529

Additional information

No response

riverar commented 5 months ago

Related: https://github.com/File-New-Project/EarTrumpet/issues/941

This is a long standing Windows bug; the team made changes in this area years ago (approximately May 13, 2020) and it seems like it's been slightly broken ever since. Compounding matters, there is no feedback channel for developer platform or OS bugs like this.

Can you try the steps here? https://github.com/File-New-Project/EarTrumpet/issues/417#issuecomment-566869108

GRANDGG-1first commented 5 months ago

i am not sure what to do with this exactly

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "EnableFullTrustStartupTasks"=dword:00000002 "EnableUwpStartupTasks"=dword:00000002 "SupportFullTrustStartupTasks"=dword:00000001 "SupportUwpStartupTasks"=dword:00000001

do i run this in cmd or somthing ? here is a screenshot from registry editor

image

riverar commented 5 months ago

You save that into a file (e.g. startup.reg) then double-click it. It will re-add the missing values and should fix startup.

riverar commented 5 months ago

Also, for my records, did you use any scripts/tools to clean/debloat Windows or adjust for privacy? Not blaming you, just trying to track down how these values disappeared.

GRANDGG-1first commented 5 months ago

i probebly did use windows debloter script when i freshly installed the os severral months but eartrumpet worked fine until a week or two now , plus i have the same setup (debloat+ear) on my desktop pc , but i never ran into this problem before until now

GRANDGG-1first commented 5 months ago

as i mentioned before this is also messing with taskbar settings .

GRANDGG-1first commented 5 months ago

fixed Thnak you for helping .

riverar commented 5 months ago

Cool, thanks for the heads up. I'll check with the debloater folks and ensure they're not removing these values!

AstralPhnx commented 3 months ago

Just as a heads up for anybody else having this issue and is still pulling their hair out over it, the best solution I have personally found is the following.

Navigate to shell:appsfolder using the run prompt Create a shortcut to EarTrumpet, place it anywhere. Create a new PowerShell script, just call it EarTrumpet.ps1 or something. In the script type add the following start 'C:/Path/To/EarTrumpet.lnk' Save the file Open the Windows task scheduler and create a new basic task, ask it to run this task on user logon When asked to select a program or script, point it to the EarTrumpet.ps1 script you made earlier. Save and reboot.

This has been the only way I've been able to consistently get EarTrumpet to launch properly on impacted systems. It's a bit of a backwards method of doing it but it's consistent and functional and really that's what matters at this point.

As a side note, the reason a script is required to launch EarTrumpet instead of just pointing directly to the EarTrumpet.lnk file is because for whatever reason trying to set the shortcut as a launch target in Task Scheduler pops up a rather comically vague error message that simply states "Catastrophic Failure". Using a script to launch the shortcut instead bypasses this, rather funny though.

Hopefully this helps those who are having a similar issue until we can finally get to the bottom of this!