Fishwalker
New member
Use Case
When rebooting a system, at times the OS pauses reboot pending user input. This is common when rebooting while apps have open documents that haven't been saved. The OS displays: "This app is preventing shutdown". However, the Remotly application has already been terminated and interaction cannot occur.
When Windows receives no input, it locks the user session and returns to the lock screen, awaiting the user to interact with the system.
At this point, Remotly is still terminated, and there is no way to remotely resume operations. Physical interaction at the system is required, or remote power management to power-cycle the system, triggering Remotly to run on login. I have auto-login (as well as 'Always Power On' in the BIOS) on my main home computer, so Remotly resumes after reboot.
Proposed Solution
Other remote applications, such as Teamviewer or RDP, seem to remain active during required user-input after initiating a reboot. I'm not really sure how this could be implemented, but if it is possible to keep the remote session active past this input session before termination, that would be very helpful.
When rebooting a system, at times the OS pauses reboot pending user input. This is common when rebooting while apps have open documents that haven't been saved. The OS displays: "This app is preventing shutdown". However, the Remotly application has already been terminated and interaction cannot occur.
When Windows receives no input, it locks the user session and returns to the lock screen, awaiting the user to interact with the system.
At this point, Remotly is still terminated, and there is no way to remotely resume operations. Physical interaction at the system is required, or remote power management to power-cycle the system, triggering Remotly to run on login. I have auto-login (as well as 'Always Power On' in the BIOS) on my main home computer, so Remotly resumes after reboot.
Proposed Solution
Other remote applications, such as Teamviewer or RDP, seem to remain active during required user-input after initiating a reboot. I'm not really sure how this could be implemented, but if it is possible to keep the remote session active past this input session before termination, that would be very helpful.
