You can use the ExitWindowsEx API function to do this, but I
would STRONGLY recommend that you do not do this. Users will not
be happy. Just out of curiosity, why do you need to do this?
Declare Function ExitWindowsEx Lib "user32" _
(ByVal uFlags As Long, ByVal dwReserved As Long) As Long
Const EWX_REBOOT = 2
I plan on using this in a macro that will be restricted (by password) for my use only. No other users will experience the reboot. The macro will launch one of two .reg files that will restrist or unrestrict various features, e.g., start/run, file options, find, etc. To take affect the PC must be rebooted. I thought since the macro was running anyway, why not have it reboot the PC too
I'm doing this to safeguard my PC from the children
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.