Yesterday I started a new Windows 10 1803 project with a customer. They want to start deploying Windows 10 1803 to new machines and also start upgrade existing Windows 10 clients to 1803.
To upgrade existing clients, I’ve created a Task Sequence template that I’ve been using at many different customers in previous projects (including 1803).
But yesterday I got the following error displayed in a Command Prompt during the deployment:
winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name. Please consult the documentation for more information.
New (bare metal) deployment works as expected.
After some spending some time digging into to this issue and asking for ideas from other OSD experts (Johan Arwidmark and Michael Niehaus), I’ve come to the conclusion that the current release of the Windows 10 1803 ISO most likely is broken if you want do an in-place upgrade. New deployments works as expected.
I have tested the upgrade using 2 different versions of the 1803 ISO:
When using the “79647” build everything works as expected, but if I use the “82164” build, it fails. Unfortunately, it’s the version that is currently available the that fails.
Check this thread for more information: https://www.reddit.com/r/SCCM/comments/8nnx1q/win10_1703_to_1803_ts_upgrade_winpeshlini_error/
- If you bump into this problem, try to use an older version of the ISO (until it gets fixed).
- If you don’t have a copy of the old ISO the best option is to open a support ticket with Microsoft.
- Always keep a backup of you old Windows 10 ISO’s.
Happy upgrading… 🙂
Update: Microsoft has now confirmed the issue and has promised a fix.
Tip: If you can’t wait and need the old iso you can get it from MSDN. Thanks to Zvensch, for the tip.