![]() ![]() To accomplish that task, follow these steps:Īdd the following to your Sysprep.inf file: If you are not using SP1 yet, then you should use Sysprep version 1.1 with the -CLEAN switch. The value should read exactly as shown here: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ Shell:REG_SZ:Explorer.exe Modify the following registry value removing the path to explorer and the trailing comma at the end of explorer as described in the Cause section above. The full path to Explorer.exe, including the command, results in this behavior. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\ Shell:REG_SZ:C:\Winnt\Explorer.exe, ![]() CauseĪfter running sysprep on the machine, the following registry entry will contain the path to Explorer.exe and a comma at the end of the value: "C:\Winnt\Explorer.exe," This behavior occurs only if you used SYSPREP to create the master image, and is language independent. Instead, Calc.exe acts like a background process. For example, if Calc.exe is scheduled by Task Scheduler at 3 P.M., Calc.exe runs at exactly 3 P.M. ![]() The Windows Task Manager shows the task as a process but not as an application. Task scheduler runs tasks as background processes after sysprep-ing the master computer.Īfter running mini-setup, in end-user mode, any scheduled task that is started through the Windows Task Scheduler never shows up as a window on the desktop. This article provides solutions to an issue where task scheduler runs tasks as background processes after you use sysprep to create the master image.Īpplies to: Windows 10 - all editions Original KB number: 253942 Symptoms ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |