SOLVED: Windows 10 1803 Upgrade with winpeshl.ini Issue

Update, 18.06.2018, by Microsoft:
We are aware of an issue affecting the recent media on VLSC. The ISO has been replaced on VLSC.  If you have encountered issues installing with this media, we recommend you download and install the refreshed ISO now available on VLSC or wait until we release a new version later in June.

This blog post will be a short one. I just would like to publish my workaround regarding Windows 10 1803 upgrade issue.

Issue: after the upgrade, I’ve received this prompt message “A winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name.” It may result from a corrupted installation file, which lead to failure during setup.

This seems to be a problem with the current install media from VLSC (filename SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-3_MLF_X21-82160.iso).  It doesn’t matter if you run the upgrade through SCCM or just mount the ISO and run it through the GUI, it fails just like this. If you have a previous ISO version SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-3_MLF_X21-79647.iso it will work.

Microsoft says: We are aware of the issue and are investigating solutions. Will update when we know more. (Wednesday, June 13, 2018 12:15 AM)

Solution 1: when it gets hung at the command prompt after the first reboot.

  • Just search for RecEnv.exe 
  • Jump to that directory
  • Run this file
  • Setup will now continue!

Solution 2: modify install.wim file.

  • Mount boot.wim from the ISO
  • Check install.wim for indexes
  • Choose and mount your correct index
  • Mount winre.wim from mount directory
  • Copy sources folder
  • Unmount winre.wim file with commit command
  • Unmount install.wim file with commit command
  • Unmount boot.wim file

For sure, I prefer the solution 2. Because now you are able to update your deployment with this new modified install.wim media and automatize your upgrade process.

Until Microsoft is not updating this ISO file on the VLSC paltform, we have to work with this workaround. I hope this helps you!

3 Comments


  1. I got “‘cpi’ is not recognized as an internal or external command,
    operable program or batch file. error.” Can you help please?

    Reply

    1. You can use Copy-Item, Copy or CP as standard aliases too.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *