There are scheduling programs that will send keys to programs. I don't, however, know if this would be considered a user action. One could open notepad and have the scheduler program type in a letter every minute in the open document or something like that.

Perhaps Windows would treat that as a user action, but I'm not sure. I'm also not sure if a PC on a KVM switch would recognize it the same way.

Simpler idea: a miniature treadmill.
Tie the mouse in place, and give it some exercise.

And as it's All Hallows Eve, make a tiny mask, with a pointy nose, long whiskers, and big, round, black ears.

Or use one of these:
Barbie/doll treadmill

[WB8ILI wrote:]... Disable the Windows Update service. ...

... got my PC through this Patch Tuesday unscathed. Patches then applied at a point of my choosing. Thanks.

Hopeful event this afternoon (GMT-8 time zone): Checked my laptop machine and was greeted by a Win10 complaint that it couldn't install an update and to 'click here' to fix the 'problem'. (That'll be the day!) It was worth a chuckle, though. Instead, I checked that the duty-day was indeed set Midnight-to-Midnight. (It was.) That was my first (apparent) successful block of Windoze arrogance on this issue.

Then "the other shoe fell." Thinking "success", another Win10 machine was intended to be reset to Midnight-to-Midnight exclusion. As soon as begin-time was set to Midnight, a new message appeared, in bright yellow: Limits must be between one and twelve hours. Well, that's The End!

It seems reasonable to conclude that numerous people around the globe tried the same trick and caused a flurry of M$ activity to put the insurgency to ground. Hence the new limitation. M$ seemingly intends to assert its right to control our machines to the smallest of details.

(One wonders whether they'll withdraw WB8ILI's solution.)

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

What about blocking M$'s IP address, either on your computers or on the router?

If Microsoft is going to block every effort to stop there automatic updates the only solution I can think of is to go back to the practice of making frequent backups. This would allow you to do a restore after an unexpected reboot causes one or more models to crash. I know this is a nuisance, but, it is better than losing a model that you have 10 or more days of crunching invested in. There was a time, several years ago, when I used to make a new backup every morning.

---

Windows 10 "Creators Update" may help the Windows 10 users with minimizing unexpected update reboots. From Ars Technica:

Windows 10 has been criticized for rebooting for updates at awkward times. In 1703, updates can be snoozed for several days, and active hours, during which it shouldn't reboot, have been expanded to cover 18 hours per day, rather than 12 in the previous version. All updates can be paused for up to seven days, and the eventual reboots can be scheduled as well.

Automatic downloading of updates can be stopped completely by setting the connection to metered. You can then change this when you want to download updates or there may be a manual way to do it.