[Nut-upsuser] Windows: SHUTDOWNCMD stopped working after Creators Update

Humberto Möckel hamberthm at gmail.com
Fri Apr 14 02:22:48 UTC 2017

Hi all!

All was working fine with all my UPSs and Windows 10 machines, NUT will notify events to NOTIFYCMD (which point to a .bat script to show messages) and finally will shutdown the system via SHUTDOWNCMD, that is another .bat file that simply uses shutdown.exe to hibernate the system.

Today I upgraded all my machines to the latest Creators Update, and now NOTIFYCMD works as I can see messages, but when a forced shutdown is called via fsd command NUT will shutdown all the processes as usual but it won’t call out the SHUTDOWNCMD batch file. It’s not a problem with the script as I have tested it with other ones, it simply doesn’t call it anymore, so the system will stay on without NUT running.

Any ideas?


Gesendet von Mail für Windows 10

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20170413/d99e57f7/attachment.html>

More information about the Nut-upsuser mailing list