AdguardTeam / AdguardForWindows

AdGuard for Windows open bug tracker
https://adguard.com/
690 stars 72 forks source link

UI agent was not started after update #398

Closed ameshkov closed 9 years ago

ameshkov commented 9 years ago

Here is what I see in the service log:

INFO, AdguardSvc, 3, 26.10.2015 22:07:08.349, Wait for apply.
INFO, AdguardSvc, 3, 26.10.2015 22:07:11.353, Start task.
INFO, AdguardSvc, 3, 26.10.2015 22:07:11.353, Executing command: cmd.exe /C "schtasks /run /tn AdguardUpdater" waitForExit=True timeout=3000 elevate=True
INFO, AdguardSvc, 3, 26.10.2015 22:07:11.391, Starting result is SUCCESS: Attempted to run the scheduled task "AdguardUpdater".
.
INFO, AdguardSvc, 3, 26.10.2015 22:07:11.391, Wait for cleanup.
INFO, AdguardSvc, 3, 26.10.2015 22:07:14.410, Cleanup.
INFO, AdguardSvc, 3, 26.10.2015 22:07:14.410, Executing command: cmd.exe /C "schtasks /delete /tn AdguardUpdater /f" waitForExit=True timeout=3000 elevate=True

Job was scheduled successfully (at least it looks like), but it was not executed

ameshkov commented 9 years ago

It is not yet clear why it does not start. Anyway there're some things we can improve right now.

bool success = ThreadingUtils.WaitFor(() => IsProcessRunning("Adguard"), TimeSpan.FromSeconds(10));
ameshkov commented 9 years ago

Thanks to @confessor-adguard we now know the problem is in "Power Management":)