{"id":341,"date":"2008-03-09T01:40:00","date_gmt":"2008-03-09T09:40:00","guid":{"rendered":"https:\/\/kb.terabyteunlimited.com\/kb-articles\/image-for-windows-fails-to-run-when-invoked-by-the-windows-task-scheduler\/"},"modified":"2021-09-10T23:44:42","modified_gmt":"2021-09-11T06:44:42","slug":"image-for-windows-fails-to-run-when-invoked-by-the-windows-task-scheduler","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\/","title":{"rendered":"Image for Windows Fails to Run when Invoked by the Windows Task Scheduler"},"content":{"rendered":"

Please note: <\/strong>This article applies to version 1 product(s) only.<\/p>\r\n

Problem:<\/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.\u00a0 Or, the process starts, but Image for Windows (imagew.exe<\/span>) seems to hang indefinitely.<\/p>\r\n

Cause:<\/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>
\r\n
\r\nUse the Image Auto Response option of the IFW<\/span> environment variable, as outlined in the Image for Windows PDF manual<\/a>.\u00a0 The recommended method for doing this is to run Image for Windows from a command script<\/a>, using commands similar to the following:
\r\n
\r\nsetlocal
\r\nset IFW=IAR:Y<\/span><\/p>\r\n