Glad I'm not the only one old enough to use batch, it's actually surprisingly powerful if you bother to learn the idiosyncrasies of it. One of these days I'll get around to learning Powershell...

The scheduler job I posted earlier is doing the trick, my system has wanted to reboot for 3 days now and hasn't done it. I still have the notification that a reboot is pending (so good reminder it's...

Since the brute-force method was working, I cleaned it up. I've got this batch file (yeah, batch, I'm that old) scheduled to run at startup and repeat every hour after that:


Fun integer math...

Yes, you're missing something ... that's just an example of the commands, I actually have three jobs set to run:

At 2am, active hours are set to 1am-11am
At 10am, active hours are set to...

Well, only one way to find out ... I tracked down the registry entries, and I've created three scheduled tasks that use C:\Windows\System32\REG.EXE to update the window. Kind of brute-forced it this...

I wonder if you could defer update indefinitely by identifying where in the registry the active hours are stored and having a scheduled task that updates them automatically to keep moving the window...