SamKI'm trying to launch wyupdate.exe /skipinfo from a console app, that's running under the SYSTEM account (it's launched through a scheduled task, with 'run whether user is logged in or not' enabled).
The application that needs to be updated is shut down, but still wyupdate hangs without continueing. If I run wyupdate.exe /skipinfo from an elevated normal cmdprompt, it works fine.
I'd love to see what it's freezing on, but the log switch only works when updating services. How can I debug this?
SamKNevermind, I narrowed it down. Evidently the console app that launches the update is where wyUpdate freezes on. This console app is in a subfolder of the to-be-updated application, but this subfolder isn't and never was in wyUpdate's updates.
So why is it still waiting for it to be closed?
Every process in the directory and below must be closed.
No, but you could monitor the processes and kill them after X seconds.
