I have a program operation that is initiated when a user is logged on, but it is long-running and non-interactive in nature, and could be completed in the background. I'm confused by the process lifecycle in windows.
Can aany user process reliably continue to run (in the background) in the face of:
- User signing out
- User switchingSwitching to a different account (without logoff)
- User locking the screen
- Power state switch (sleep/hibernate)
CanThere exist programs that can restart automatically following a simple process be resumedreboot/reopened automaticallypower cycle (i.e. without schedulingg. Edge reopens its tabs after an automatic software update). Are those special cased, or are those simply regular programs hooking into some onpower-restart event or such) after:event API?
- Wake up from sleep/hibernate
- Automatic reboot due to an update. (I often find browser tabs reopened in edge after an unexpected reboot. same goes for hyperv vms, which seem to be automatically paused and resumed)