forums.wsusoffline.net

As nice as it is to have the multiple reboots, I understand sometimes things go wrong where it is troublesome and ran into newer Windows machines at the time the updates lead to being at the password screen for woutemp with no user switch ability. Can autoreboot be used still or brought back if ran under an administrator user with no sign in password? Could we get a single reboot when finished if updates were applied (even if there's a popup at the start that more updates may exist and should be ran again if it reboots)? Changing power settings to idle the monitor rapidly after wsusoffline starts with no (auto)reboot makes it harder to quickly get through updates without repeatedly checking on the machine (and I normally try to not sit in front of a machine to use it while it is being updated).

As the autoreboot-feature caused some locked out users, we will keep it disabled.
You could write your own autoreboot-script...
- use FinalizationHook to determine if a reboot or recall is required (vars REBOOT_REQQUIRED and RECALL_REQUIRED)
- use a simple script in your autorun, that checks if some kind of flag is set (e.g. existance of C:\run_wsusoffline.txt) and then call wsusoffline

Any say about a 'reboot on completion' option, just like the "shut down on completion"? It would take the computer closer to the next step ending at a login screen (or desktop if set to autologin due to no password).