Reply to thread

Message

<blockquote data-quote="MLH01" data-source="post: 476855" data-attributes="member: 89532">Hi,After the second unattended reboot, everything is working well <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />I have decided to continue using the HTPC with the full admin account, which as Paranoid Delusion mentioned, seems to keep everything working quite smoothly.You might be able to start a batch file upon startup (put a link in the startup folder) if there is an option in the schtasks.exe command.&nbsp; When I tried the reboot script in the startup folder the other day, it almost worked.&nbsp; I needed to have it create the schedule to run once.&nbsp; The problem was that it would try to create the same schedule and throw an error upon the next reboot, effectively rendering the schedule useless.&nbsp; There might be a way to have it delete the previous schedule before re-creating it - perhaps using 2 'schtasks.exe' commands in the one batch script.&nbsp; This would prevent an error caused by trying to create a schedule that has already been created.&nbsp; I think that might be the only way you can do this from a normal user account.Let me know how you go.MLH01.</blockquote>

[QUOTE="MLH01, post: 476855, member: 89532"] Hi, After the second unattended reboot, everything is working well :) I have decided to continue using the HTPC with the full admin account, which as Paranoid Delusion mentioned, seems to keep everything working quite smoothly. You might be able to start a batch file upon startup (put a link in the startup folder) if there is an option in the schtasks.exe command. When I tried the reboot script in the startup folder the other day, it almost worked. I needed to have it create the schedule to run once. The problem was that it would try to create the same schedule and throw an error upon the next reboot, effectively rendering the schedule useless. There might be a way to have it delete the previous schedule before re-creating it - perhaps using 2 'schtasks.exe' commands in the one batch script. This would prevent an error caused by trying to create a schedule that has already been created. I think that might be the only way you can do this from a normal user account. Let me know how you go. MLH01. [/QUOTE]

Verification