{"id":337,"date":"2007-10-03T12:05:00","date_gmt":"2007-10-03T19:05:00","guid":{"rendered":"https:\/\/kb.terabyteunlimited.com\/kb-articles\/image-for-windows-fails-to-run-when-invoked-by-the-windows-task-scheduler-2\/"},"modified":"2021-09-07T15:25:31","modified_gmt":"2021-09-07T22:25:31","slug":"image-for-windows-fails-to-run-when-invoked-by-the-windows-task-scheduler-2","status":"publish","type":"lsvr_kba","link":"https:\/\/www.terabyteunlimited.com\/kb\/kb-articles\/image-for-windows-fails-to-run-when-invoked-by-the-windows-task-scheduler-2\/","title":{"rendered":"Image for Windows Fails to Run when Invoked by the Windows Task Scheduler"},"content":{"rendered":"

Problem:<\/font><\/strong><\/p>\r\n

While attempting to run Image for Windows using the Windows Task Scheduler without<\/em> the applicable user logged on (i.e. the user under whose context the task is running), the process doesn't seem to run at all.  Or, the process starts, but Image for Windows (imagew.exe<\/font>) seems to hang indefinitely.<\/p>\r\n

Cause:<\/font><\/strong><\/p>\r\n

Image for Windows is waiting for user input, but the prompt is not visible due to the process having been invoked by the Task Scheduler.<\/p>\r\n

Solution:<\/strong>
<\/font>
If you are running Image for Windows non-interactively, you will want to have Image for Windows automatically respond to Yes<\/strong>\/No<\/strong>, Abort<\/strong>\/Retry<\/strong>\/Ignore<\/strong>, and OK<\/strong>\/Cancel<\/strong> prompts that may appear.  This can be done using the unattended backup command line parameters supported by Image for Windows (as outlined in the Image for Windows PDF manual<\/a>).

Some examples of prompts that could appear and need to be handled by an automatic response:
<\/p>\r\n