Close Menu
    Facebook X (Twitter) Instagram
    Trending
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    • Speaking at Modern Endpoint Management Summit 2022
    • Speaking at Nordic Virtual Summit 2022 – 3nd Edition
    • CoLabora Recordings – January 2022
    RONNIPEDERSEN.COM
    • Home
    • Enterprise Mobility
      • Configuration Manager
      • Identity and Access
      • Information Protection
      • Intune
    • Cloud and Data Center
      • Data Center Management
      • Group Policy
      • Enterprise Security
      • Hyper-V
      • PowerShell
    • Guides
    • Webcasts
    • Links
    • About
      • Contact me
      • Disclaimer
    RONNIPEDERSEN.COM
    You are at:Home»Enterprise Mobility»Configuration Manager»Windows 10 1803: winpeshl.ini file is present, but no commands were successfully launched

    Windows 10 1803: winpeshl.ini file is present, but no commands were successfully launched

    18
    By Ronni Pedersen on June 12, 2018 Configuration Manager, Enterprise Mobility, Windows Deployment

    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:

    • SW_DVD5_Win_Pro_Ent_Edu_N_10_1803_64BIT_Danish_-2_MLF_X21-79647
    • SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_Danish_-3_MLF_X21-82164

    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/

    Conclusion

    1. If you bump into this problem, try to use an older version of the ISO (until it gets fixed).
    2. If you don’t have a copy of the old ISO the best option is to open a support ticket with Microsoft.
    3. Always keep a backup of you old Windows 10 ISO’s.

    Happy upgrading… 🙂

    Update 1: Microsoft has now confirmed the issue and has promised a fix.

    Update 2: Microsoft has now released an updated version of the ISO. SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-4_MLF_X21-87129 is now available form the Volume Licensing Service Center.

    /Enjoy

    +Ronni Pedersen

    • Tweet
    • Share 0
    • +1
    • LinkedIn 0

    Related

    Ronni Pedersen
    • Website
    • Facebook
    • X (Twitter)
    • LinkedIn

    My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.

    Related Posts

    Speaking at Nordic Virtual Summit

    Workplace Ninja User Group Denmark February Meetup

    Speaking at Modern Endpoint Management Summit 2022

    18 Comments

    1. Bo Bertelsen on June 14, 2018 13:10

      Can you do a follow up when they have released it?

      Reply
      • Ronni Pedersen on June 14, 2018 13:11

        Sure!

        Reply
        • Matt Conolly on June 26, 2018 20:12

          sources folder (containing RecEnv.exe and StartRep.exe) is missing from the winre.wim. I copied them from the boot.wim to correct the issue.

          Reply
    2. Anthony Banta on June 14, 2018 21:58

      Just for those who are curious…

      Inside the 79647 ISO:

      (for booting from CD\ISO)
      ISO > Sources > boot.wim > sources

      (In-Place upgrade\Windows recovery\Startup repair after install)
      ISO > Sources > install.wim > Windows > System32 > Recovery > WinRE.wim > sources

      The “sources” directory has the recenv.exe file which kick starts the recovery environment (Install for win10\startup repair)

      Inside the 82164 ISO

      (for booting from CD\ISO)
      ISO > Sources > boot.wim > sources
      The sources directory is there as expected (You can boot and install from CD\ISO)

      BUT

      ISO > Sources > install.wim > Windows > System32 > Recovery > WinRE.wim > Sources

      is missing. So when WinRE starts up (during in place upgrade\recovery\startup repair), it will pop up this error as the winpeshl.ini file references “%systemdrive%\sources\recenv.exe” which is missing from the WinRE.wim

      If you are friendly with DISM, you can mount the 82164 ISO and copy

      ISO > Sources > boot.wim > sources

      to

      ISO > Sources > install.wim > Windows > System32 > Recovery > WinRE.wim > sources

      Commit the winre wim, then commit the install wim. You should be good to go. I’m updating SCCM with the “new” install.wim now and will be testing later today to verify everything is good.

      Reply
    3. Dimitri on June 15, 2018 14:05

      Thank you! I have been searching for ages and finally found someone who explained the issue properly.

      Reply
    4. Keith N on June 25, 2018 23:47

      Any update on this yet?

      Reply
      • Ronni Pedersen on July 6, 2018 13:43

        Yes! Everything should be fine now if you use the latest ISO file.

        Reply
    5. leighana coe on June 27, 2018 22:07

      Would love to hear when this is fixed as well, I just started working with the ISO for in place upgrade via sccm and I am glad to have found this article.

      Reply
      • Ronni Pedersen on July 6, 2018 13:42

        It’s fixed now…

        Reply
        • Bo Bertelsen on July 6, 2018 18:18

          Thanks!

          Reply
    6. Sam on July 4, 2018 12:05

      Once it shows up is there a way to roll it back without any app or setting change

      Reply
      • Ronni Pedersen on July 6, 2018 13:42

        That should happen automatically 🙂

        Reply
        • Sam on July 8, 2018 06:07

          Thnaks for your reply roni. when i restarted after closing the cmd window i receive blue screen error saying critical service failed. for every restart it lops to the same error. Even if i run recenve.exe nothing happens.

          Reply
        • Anu varatharaju on April 17, 2020 21:16

          when i login the system cmd box shows error like, a winpeshl.ini file is present, but comments were successfully launched, this could be caused by incorrect formatting or an invalid executable name.

          So i can’t operate my system.. even my login page.could you please help me

          My system module is dell, windows 10model

          Reply
    7. Greg Esposito on July 6, 2018 13:06

      I had never thought about what the numbers at the end meant. After suffering the problem as noted above, now I can much better understand the differences in my ISOs. Thanks!

      Reply
    8. Pingback: Windows 10 1803 インストールエラー ([0x80070002]winpeshl.ini) | さるすべり

    9. Yiğit on October 10, 2018 10:14

      Is there a way to fix this issue without fresh install with fixed ISO provided by Microsoft? All of the items in Advanced Startup giving winpeshl.ini error.

      Reply
      • Ronni Pedersen on October 15, 2018 06:54

        AFAIK, the only way is to get the updated ISO, and re-install.

        Reply
    Leave A Reply Cancel Reply

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Follow
    APENTO

    Follow APENTO here:

    Subscribe to Blog via Email

    Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    About
    My name i s Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Endpoint Management and Security, based on Microsoft technologies. I'm also a Microsoft Certified Trainer and a dual Microsoft MVP in both Security and Windows.
    Recent Posts
    • Successful Adoption of a “Cloud First” Strategy
    • Speaking at Nordic Virtual Summit
    • Workplace Ninja User Group Denmark February Meetup
    • Workplace Ninja User Group Denmark Meetup – May 2022
    • Workplace Ninja User Group Denmark Meetup – April 2022
    Archives
    TOP POSTS
    • SCCM 2012 R2: Where is the SMSTS.log located?
    • Missing “UserType” attribute in Azure AD
    • Find the TimeZoneName for your SCCM/MDT Deployments
    • How to Access the MBAM BitLocker Recover Keys directly in SQL
    • Importing drivers for OSD in ConfigMgr 2012
    RECENT COMMENTS
    • Sebi on Prepare for Co-Management: Migrate Intune Devices without user affinity
    • Vadim P on SCCM: Failed to Get Client Identity (80004005)
    • TM on Active Directory Based Activation in an multi domain environment
    • unkown on Setting OSDComputerName using CustomSettings.ini
    • TJ Scott on Setting OSDComputerName using CustomSettings.ini
    DISCLAIMER
    The content on this website is presented "as-is" with no guarantees. The use of scripts from this website is at your own risk. Always test before putting something in production! Opinions expressed are my own.
    © 2025 ThemeSphere. Designed by ThemeSphere.

    Type above and press Enter to search. Press Esc to cancel.