none
Windows 10 fails to upgrade to 1803 from 1709 using SCCM 1802 RRS feed

  • Question

  • I have several machines failing to update.  Test push environment of 10 and 6 failures.  Can't push to production until I solve the Issue.  Windows logs are below and after a week and a half of troubleshooting I am no closer.   The logs in this case were not very helpful at all below is the relevant piece:

    2018/06/05 13:56:05.5678493 5152  4952  Agent           Refreshing global settings cache
    2018/06/05 13:56:05.5678535 5152  4952  Agent           WSUS server:  (Changed)
    2018/06/05 13:56:05.5678595 5152  4952  Agent           WSUS status server:  (Changed)
    2018/06/05 13:56:05.5678672 5152  4952  Agent           Alternate Download Server: http://localhost:8005 (Changed)
    2018/06/05 13:56:05.5678715 5152  4952  Agent           Fill Empty Content Urls: Yes (Changed)
    2018/06/05 13:56:05.5678758 5152  4952  Agent           Target group: (Unassigned Computers) (Unchanged)
    2018/06/05 13:56:05.5678809 5152  4952  Agent           Windows Update access disabled: No (Unchanged)
    2018/06/05 13:56:05.5678866 5152  4952  Agent           Do not connect to Windows Update Internet locations: No (Unchanged)
    2018/06/05 13:56:35.7263011 1588  7352  ComApi          * START *   Federated Search ClientId = CcmExec (cV: iwWh2R9jGUaKf8Hv.1.0)
    2018/06/05 13:56:35.7294822 5152  16112 IdleTimer       WU operation (SR.CcmExec ID 7) started; operation # 37; does use network; is not at background priority
    2018/06/05 13:56:35.7296419 5152  14608 IdleTimer       WU operation (SR.CcmExec ID 7, operation # 37) stopped; does use network; is not at background priority
    2018/06/05 13:56:35.7310331 1588  1172  ComApi          Federated Search: Starting search against 1 service(s) (cV = iwWh2R9jGUaKf8Hv.1.0)
    2018/06/05 13:56:35.7311206 1588  1172  ComApi          * START *   Search ClientId = CcmExec, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iwWh2R9jGUaKf8Hv.1.0.0)
    2018/06/05 13:56:35.7321689 5152  8796  IdleTimer       WU operation (CSearchCall::Init ID 8) started; operation # 40; does use network; is not at background priority
    2018/06/05 13:56:35.7440493 5152  8796  Agent           * START * Queueing Finding updates [CallerId = CcmExec  Id = 8]
    2018/06/05 13:56:35.7440564 5152  8796  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
    2018/06/05 13:56:35.7440601 5152  8796  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
    2018/06/05 13:56:35.7441810 5152  2888  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
    2018/06/05 13:56:35.7462071 5152  984   Agent           * END * Queueing Finding updates [CallerId = CcmExec  Id = 8]
    2018/06/05 13:56:35.7479288 5152  984   Agent           * START * Finding updates CallerId = CcmExec  Id = 8
    2018/06/05 13:56:35.7479308 5152  984   Agent           Online = Yes; Interactive = Yes; AllowCachedResults = No; Ignore download priority = Yes
    2018/06/05 13:56:35.7479348 5152  984   Agent           Criteria = (DeploymentAction=* AND Type='Software') OR (DeploymentAction=* AND Type='Driver')""
    2018/06/05 13:56:35.7479373 5152  984   Agent           ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2018/06/05 13:56:35.7479382 5152  984   Agent           Search Scope = {Machine}
    2018/06/05 13:56:35.7479408 5152  984   Agent           Caller SID for Applicability: S-1-5-18
    2018/06/05 13:56:35.7479488 5152  984   Agent           Include potentially superseded updates is set
    2018/06/05 13:56:35.7715073 5152  984   Misc            Got WSUS Client/Server URL: http:///ClientWebService/client.asmx""
    2018/06/05 13:56:35.7910872 5152  984   Driver          Skipping printer driver 5 due to incomplete info or mismatched environment - HWID[(null)] Provider[SHARP] MfgName[SHARP] Name[SHARP MX-5141N PCL6] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
    2018/06/05 13:56:35.7910906 5152  984   Driver          Skipping printer driver 6 due to incomplete info or mismatched environment - HWID[(null)] Provider[Microsoft] MfgName[Microsoft] Name[Remote Desktop Easy Print] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
    2018/06/05 13:56:35.7910934 5152  984   Driver          Skipping printer driver 9 due to incomplete info or mismatched environment - HWID[(null)] Provider[(null)] MfgName[(null)] Name[LogMeIn Printer Driver] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
    2018/06/05 13:56:35.7910960 5152  984   Driver          Skipping printer driver 10 due to incomplete info or mismatched environment - HWID[(null)] Provider[Adobe] MfgName[Adobe] Name[Adobe PDF Converter] pEnvironment[Windows x64] LocalPrintServerEnv[Windows x64]
    2018/06/05 13:56:35.7911026 5152  984   Driver          Skipping printer driver 11 due to incomplete info or mismatched environment - HWID[microsoftmicrosoft_musd] Provider[Microsoft] MfgName[Microsoft] Name[Microsoft enhanced Point and Print compatibility driver] pEnvironment[Windows NT x86] LocalPrintServerEnv[Windows x64]
    2018/06/05 13:56:36.1246281 5152  984   ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://P-I-SCCM-1.wecc.biz:8530/ClientWebService/client.asmx
    2018/06/05 13:56:36.1246397 5152  984   ProtocolTalker  OK to reuse existing configuration
    2018/06/05 13:56:36.1251911 5152  984   ProtocolTalker  Cached cookie has expired or new PID is available
    2018/06/05 13:56:36.1257362 5152  984   Misc            Got WSUS SimpleTargeting URL: ""
    2018/06/05 13:56:36.1260926 5152  984   IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie) started; operation # 41; does use network; is at background priority
    2018/06/05 13:56:36.1260963 5152  984   ProtocolTalker  Initializing simple targeting cookie, clientId = f97df219-d983-4ac9-9d02-17b2e57e5f69, target group = , DNS name = 
    2018/06/05 13:56:36.1260980 5152  984   ProtocolTalker    Server URL = http://SimpleAuthWebService/SimpleAuth.asmx
    2018/06/05 13:56:36.1261063 5152  984   WebServices     Auto proxy settings for this web service call.
    2018/06/05 13:56:36.1369931 5152  984   IdleTimer       WU operation (CAuthorizationCookieWrapper::InitializeSimpleTargetingCookie, operation # 41) stopped; does use network; is at background priority
    2018/06/05 13:56:36.1377908 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery) started; operation # 42; does use network; is at background priority
    2018/06/05 13:56:36.1378124 5152  984   WebServices     Auto proxy settings for this web service call.
    2018/06/05 13:56:36.1449329 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::GetCookie_WithRecovery, operation # 42) stopped; does use network; is at background priority
    2018/06/05 13:56:36.1449483 5152  984   ProtocolTalker  PTInfo: Server requested registration
    2018/06/05 13:56:38.9730218 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 43; does use network; is at background priority
    2018/06/05 13:56:38.9864853 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 43) stopped; does use network; is at background priority
    2018/06/05 13:56:39.0158178 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover) started; operation # 44; does use network; is at background priority
    2018/06/05 13:56:39.0249031 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::SyncUpdates_WithRecover, operation # 44) stopped; does use network; is at background priority
    2018/06/05 13:56:39.0249165 5152  984   ProtocolTalker  SyncUpdates round trips: 2
    2018/06/05 13:56:39.5331333 5152  984   EEHandler       *FAILED* [8007066F] EE: Error occurred in MSI QueryForPatchProperty
    2018/06/05 13:56:39.7356721 5152  984   ProtocolTalker  ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http:///ClientWebService/client.asmx
    2018/06/05 13:56:39.7356747 5152  984   ProtocolTalker  OK to reuse existing configuration
    2018/06/05 13:56:39.7356824 5152  984   ProtocolTalker  Existing cookie is valid, just use it
    2018/06/05 13:56:39.7356847 5152  984   ProtocolTalker  PTInfo: Server requested registration
    2018/06/05 13:56:39.7465022 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 45; does use network; is at background priority
    2018/06/05 13:56:39.7488394 5152  984   IdleTimer       WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 45) stopped; does use network; is at background priority
    2018/06/05 13:56:39.7692525 5152  984   SLS             *FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
    2018/06/05 13:56:39.7697326 5152  984   SLS             Retrieving SLS response from server...
    2018/06/05 13:56:39.7709089 5152  984   SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.16299.0/0?CH=82&L=en-US&P=&PT=0x4&WUA=10.0.16299.431&MK=Dell+Inc.&MD=OptiPlex+7020
    2018/06/05 13:56:40.3945401 5152  984   SLS             SLS Response is Error response type.  Attempting to extract the HRESULT in the payload...
    2018/06/05 13:56:40.3947034 5152  984   SLS             Succeeded in extracting the HRESULT from the payload => 0x80240042
    2018/06/05 13:56:40.3947254 5152  984   Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfig:793]
    2018/06/05 13:56:40.3947288 5152  984   Metadata        *FAILED* [80245004] GetFragmentSigningConfig (Using default enforcement mode: Audit)
    2018/06/05 13:56:40.3947314 5152  984   Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfigAndUpdateEnforcementPolicy:745]
    2018/06/05 13:56:40.3947351 5152  984   Metadata        Policy-driven service enabled. Using Ignore Policy.
    2018/06/05 13:56:40.3947448 5152  984   ProtocolTalker  SyncExtendedUpdateInfo - 0 bad out of 0 metadata signatures checked using Audit enforcement mode.
    2018/06/05 13:56:40.4792178 5152  984   Agent           Added update 8F57AC1E-B33E-4C28-BE69-ED7C5218F311.200 to search result
    2018/06/05 13:56:40.4792478 5152  984   Agent           Added update C3320F29-CB03-4A71-8FD0-A1D0BC0B3A67.200 to search result
    2018/06/05 13:56:40.4792572 5152  984   Agent           Added update 5345C02B-ED73-44AC-948F-3BE8FC02AAD6.200 to search result
    2018/06/05 13:56:40.4792652 5152  984   Agent           Added update D2C8782F-3779-4115-AF2A-5C11FA18AA62.200 to search result
    2018/06/05 13:56:40.4792712 5152  984   Agent           Added update F57A832F-623F-40B9-8F0C-255A2C1A0A28.200 to search result
    2018/06/05 13:56:40.4792894 5152  984   Agent           Added update 57EAD03E-38EF-4EA6-9BF4-F3D95FDA5CCD.200 to search result
    2018/06/05 13:56:40.4793096 5152  984   Agent           Added update 07609D43-D518-4E77-856E-D1B316D1B8A8.103 to search result
    2018/06/05 13:56:40.4793202 5152  984   Agent           Added update C324FD49-0FBF-42D8-911C-66AEB2989D3E.200 to search result
    2018/06/05 13:56:40.4793282 5152  984   Agent           Added update 2725C74E-3F4C-41FD-9D79-B2F7E8417A63.200 to search result
    2018/06/05 13:56:40.4793478 5152  984   Agent           Added update 5E568056-433A-45EC-91E3-3691BC753FC9.200 to search result
    2018/06/05 13:56:40.4793712 5152  984   Agent           Added update 5AF61766-FC91-4CCF-BDAB-A72D914E1C5F.200 to search result
    2018/06/05 13:56:40.4793843 5152  984   Agent           Added update 6F925671-1C4E-4A7D-89FC-8C726AAAED9A.200 to search result
    2018/06/05 13:56:40.4794006 5152  984   Agent           Added update 99D11A78-2DF9-48E9-985E-11968F50FBCD.201 to search result
    2018/06/05 13:56:40.4794080 5152  984   Agent           Added update D72FCA78-7BC8-4E9D-917E-261D8109D052.200 to search result
    2018/06/05 13:56:40.4794359 5152  984   Agent           Added update 17557D88-C388-40FE-9AD7-0E3B357F727B.200 to search result
    2018/06/05 13:56:40.4794488 5152  984   Agent           Added update C27B878D-EBA8-4350-9F81-CF66CF17F330.200 to search result
    2018/06/05 13:56:40.4794875 5152  984   Agent           Added update 96D2119C-C85D-4490-B58C-927D2EBE297C.200 to search result
    2018/06/05 13:56:40.4794961 5152  984   Agent           Added update 4064FC9E-46F4-4E2D-9A65-E67479754CD0.200 to search result
    2018/06/05 13:56:40.4795084 5152  984   Agent           Added update E21270A2-E678-4180-8BCB-3B39FA9AD0FE.202 to search result
    2018/06/05 13:56:40.4795451 5152  984   Agent           Added update D68E0CB2-9501-405E-AF9C-156F352D6735.107 to search result
    2018/06/05 13:56:40.4795625 5152  984   Agent           Added update 6CFDE3BA-D0D1-4771-9F9F-8EBF7E7CFF46.200 to search result
    2018/06/05 13:56:40.4795716 5152  984   Agent           Added update 4F7EDCBB-36DD-440E-ABD7-ED6646154C00.200 to search result
    2018/06/05 13:56:40.4795799 5152  984   Agent           Added update 3B5C77BE-5664-4EE1-A474-891EA35FBFB0.202 to search result
    2018/06/05 13:56:40.4796064 5152  984   Agent           Added update C03178C9-B5D2-4C5F-819F-C8871513E23D.200 to search result
    2018/06/05 13:56:40.4796461 5152  984   Agent           Added update 17170AE7-705A-4073-8DCE-375BD8D61864.201 to search result
    2018/06/05 13:56:40.4796677 5152  984   Agent           Added update 7F8555F4-95A6-4CFD-8B97-65FF36DB8858.200 to search result
    2018/06/05 13:56:40.4796786 5152  984   Agent           Added update 016EF8F6-A24F-48C8-8B12-1056B4233DF7.201 to search result
    2018/06/05 13:56:40.4802034 5152  984   Agent           Found 27 updates and 101 categories in search; evaluated appl. rules of 1489 out of 2736 deployed entities
    2018/06/05 13:56:40.4908590 5152  984   Agent           * END * Finding updates CallerId = CcmExec  Id = 8
    2018/06/05 13:56:40.4934442 5152  984   IdleTimer       WU operation (CSearchCall::Init ID 8, operation # 40) stopped; does use network; is not at background priority
    2018/06/05 13:56:40.4940061 1588  7352  ComApi          *RESUMED*   Search ClientId = CcmExec, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iwWh2R9jGUaKf8Hv.1.0.0)
    2018/06/05 13:56:40.5570237 1588  7352  ComApi          * END *   Search ClientId = CcmExec, Updates found = 27, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iwWh2R9jGUaKf8Hv.1.0.0)
    2018/06/05 13:56:40.5604922 1588  1172  ComApi          * END *   All federated searches have completed. Jobs = 1, Succeeded = 1, ClientId = CcmExec (cV = iwWh2R9jGUaKf8Hv.1.0)
    2018/06/05 13:56:48.8075892 1588  9776  ComApi          * START *   Federated Search ClientId = CcmExec (cV: iwWh2R9jGUaKf8Hv.2.0)
    2018/06/05 13:56:48.8093958 5152  2336  IdleTimer       WU operation (SR.CcmExec ID 9) started; operation # 61; does use network; is not at background priority
    2018/06/05 13:56:48.8094990 5152  14608 IdleTimer       WU operation (SR.CcmExec ID 9, operation # 61) stopped; does use network; is not at background priority
    2018/06/05 13:56:48.8106391 1588  17352 ComApi          Federated Search: Starting search against 1 service(s) (cV = iwWh2R9jGUaKf8Hv.2.0)
    2018/06/05 13:56:48.8107802 1588  17352 ComApi          * START *   Search ClientId = CcmExec, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = iwWh2R9jGUaKf8Hv.2.0.0)
    2018/06/05 13:56:48.8118185 5152  2336  IdleTimer       WU operation (CSearchCall::Init ID 10) started; operation # 64; does use network; is not at background priority
    2018/06/05 13:56:48.8202490 5152  2336  Agent           * START * Queueing Finding updates [CallerId = CcmExec  Id = 10]
    2018/06/05 13:56:48.8202529 5152  2336  Agent           Removing service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 from sequential scan list
    2018/06/05 13:56:48.8202561 5152  2336  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is not in sequential scan list
    2018/06/05 13:56:48.8202595 5152  2336  Agent           Added service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 to sequential scan list
    2018/06/05 13:56:48.8203473 5152  2888  Agent           Service 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 is in sequential scan list
    2018/06/05 13:56:48.8225385 5152  17356 Agent           * END * Queueing Finding updates [CallerId = CcmExec  Id = 10]
    2018/06/05 13:56:48.8247092 5152  17356 Agent           * START * Finding updates CallerId = CcmExec  Id = 10
    2018/06/05 13:56:48.8247118 5152  17356 Agent           Online = Yes; Interactive = Yes; AllowCachedResult


    ReliableWest

    Tuesday, June 5, 2018 10:18 PM

Answers

  • So i was getting the same issue when doing an upgrade via SCCM, or just manually running from the installation media.  The installation media i was using was SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-3_MLF_X21-82160.ISO which was downloaded from the VLSC site.

    When i was looking at the logs, i discovered the system was using the WINRE file to stage Windows PE instead of the BOOT.WIM file like i had assumed.  So what i did was copy the SOURCES folder out of the BOOT.WIM file from the installation media, and copy it to the WINRE.WIM file located in the Windows\System32\Recovery folder (inside the install.wim file).  Once i did that the upgrade completed perfectly.  

    It also lets you queue up the inplace upgrade package in SCCM or automate the deployment so you can do many machines.

    Hope it helps someone.

    • Marked as answer by WECCHelpDesk Thursday, June 14, 2018 2:28 PM
    Sunday, June 10, 2018 6:46 PM
  • Hello:

    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.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Saturday, June 16, 2018 6:50 PM

All replies

  •  

    I am upgrading from 1709 to 1803.  SCCM client fails the upgrade right away and won't attempt to install.  I created a bootable USB drive and get the above error on a Dell latitude laptop.  Virus protector has been removed.

    Following are log entries from the windows update log(get-windowsupdatelog):

    2018/06/04 15:57:14.2316015 4176  10600 ProtocolTalker  Existing cookie is valid, just use it

    2018/06/04 15:57:14.2316030 4176  10600 ProtocolTalker  PTInfo: Server requested registration
    2018/06/04 15:57:14.2413148 4176  10600 IdleTimer       WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery) started; operation # 44; does use network; is at background priority
    2018/06/04 15:57:14.2447092 4176  10600 IdleTimer       WU operation (CAgentProtocolTalker::GetExtendedUpdateInfo_WithRecovery, operation # 44) stopped; does use network; is at background priority
    2018/06/04 15:57:14.2642410 4176  10600 SLS             *FAILED* [80248007] Method failed [SlsDatastoreLookup:797]
    2018/06/04 15:57:14.2646867 4176  10600 SLS             Retrieving SLS response from server...
    2018/06/04 15:57:14.2665024 4176  10600 SLS             Making request with URL HTTPS://sls.update.microsoft.com/SLS/{3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}/x64/10.0.16299.0/0?CH=179&L=en-US&P=&PT=0x4&WUA=10.0.16299.431&MK=Dell+Inc.&MD=Latitude+5580
    2018/06/04 15:57:14.5948438 4176  10600 SLS             SLS Response is Error response type.  Attempting to extract the HRESULT in the payload...
    2018/06/04 15:57:14.5950011 4176  10600 SLS             Succeeded in extracting the HRESULT from the payload => 0x80240042
    2018/06/04 15:57:14.5950232 4176  10600 Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfig:793]
    2018/06/04 15:57:14.5950279 4176  10600 Metadata        *FAILED* [80245004] GetFragmentSigningConfig (Using default enforcement mode: Audit)
    2018/06/04 15:57:14.5950315 4176  10600 Metadata        *FAILED* [80245004] Method failed [MetadataIntegrity::SignatureVerifier::GetFragmentSigningConfigAndUpdateEnforcementPolicy:745]
    2018/06/04 15:57:14.5950327 4176  10600 Metadata        Policy-driven service enabled. Using Ignore Policy.
    2018/06/04 15:57:14.5950418 4176  10600 ProtocolTalker  SyncExtendedUpdateInfo - 0 bad out of 0 metadata signatures checked using Audit enforcement mode.
    2018/06/04 15:57:14.7249067 4176  10600 Agent           Found 0 updates and 95 categories in search; evaluated appl. rules of 1334 out of 2551 deployed entities
    2018/06/04 15:57:14.7315406 4176  10600 Agent           * END * Finding updates CallerId = UpdateOrchestrator  Id = 6
    2018/06/04 15:57:14.7333263 4176  10600 IdleTimer       WU operation (CSearchCall::Init ID 6, operation # 41) stopped; does use network; is at background priority
    2018/06/04 15:57:14.7351661 4176  4904  ComApi          *RESUMED*   Search ClientId = UpdateOrchestrator, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = 5UdqM8PrMEmOaB7L.0.1.0.0)
    2018/06/04 15:57:14.7355999 4176  4904  ComApi          * END *   Search ClientId = UpdateOrchestrator, Updates found = 0, ServiceId = 3DA21691-E39D-4DA6-8A4B-B43877BCB1B7 (cV = 5UdqM8PrMEmOaB7L.0.1.0.0)
    2018/06/04 15:57:14.7358772 4176  10596 ComApi          * END *   All federated searches have completed. Jobs = 1, Succeeded = 1, ClientId = UpdateOrchestrator (cV = 5UdqM8PrMEmOaB7L.0.1.0)
    2018/06/04 15:58:35.9265224 4176  4812  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 0.
    2018/06/04 15:58:46.8455889 4176  4812  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
    2018/06/04 15:58:47.8176269 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2018/06/04 15:58:49.9435800 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
    2018/06/04 15:58:54.4575327 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2018/06/04 15:58:54.4584540 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
    2018/06/04 15:58:54.4639300 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 2.
    2018/06/04 15:58:54.8101942 4176  4812  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 3.
    2018/06/04 16:00:01.3940132 2764  11196 AppAU           * START *
    2018/06/04 16:00:01.3940685 2764  11196 AppAU           Flight settings ring provisioned default, range-checked minimum search interval: 20 hours
    2018/06/04 16:00:01.3940713 2764  11196 AppAU           Skipping app au: duration since last check is too short (24003 < 72000)
    2018/06/04 16:00:01.3940851 2764  11196 AppAU           * END *, exit code = 0x00000000
    2018/06/04 16:02:04.2839463 10676 3784  ComApi          * START *   Federated Search ClientId = Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24) (cV: TYxdt2q+dUK3bghh.1.0)
    2018/06/04 16:02:04.2845602 4176  5916  IdleTimer       WU operation (SR.Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24) ID 7) started; operation # 54; does use network; is not at background priority
    2018/06/04 16:02:04.2846471 4176  7060  Agent           Processing auto/pending service registrations and recovery.
    2018/06/04 16:02:04.3107654 4176  7060  Misc            *FAILED* [80245002] Failed to obtain 9482F4B4-E343-43B6-B170-9A65BC822C77 redir SecondaryServiceAuth URL
    2018/06/04 16:02:04.3113272 4176  7060  Agent           Failed to verify authenticity of service 117cab2d-82b1-4b5a-a08c-4d62dbee7782, hr=0
    2018/06/04 16:02:04.3577540 4176  7060  IdleTimer       WU operation (SR.Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24) ID 7, operation # 54) stopped; does use network; is not at background priority
    2018/06/04 16:02:04.3602196 10676 1308  ComApi          Federated Search: Starting search against 2 service(s) (cV = TYxdt2q+dUK3bghh.1.0)
    2018/06/04 16:02:04.3602935 10676 1308  ComApi          * START *   Search ClientId = Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24), ServiceId = 9482F4B4-E343-43B6-B170-9A65BC822C77 (cV = TYxdt2q+dUK3bghh.1.0.0)
    2018/06/04 16:02:04.3610520 4176  5916  IdleTimer       WU operation (CSearchCall::Init ID 8) started; operation # 57; does use network; is not at background priority
    2018/06/04 16:02:04.3725740 4176  5916  Agent           * START * Queueing Finding updates [CallerId = Windows Defender Antivirus (77BDAF73-B396-481F-9042-AD358843EC24)  Id = 8]
    2018/06/04 16:02:04.3725811 4176  5916  Agent           Service 9482F4B4-E343-43B6-B170-9A65BC822C77 is not in sequential scan list
    Tuesday, June 5, 2018 5:25 PM
  • Hi,

    I noticed that you post another thread in the forum, since it is the same issue, let us focus on the thread here.

    The error 

    " a winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name." may result from a corrupted installation file, which lead to failure during setup.

    Did you create a servicing plan or task sequence to upgrade to windows 10 1803?

    If you use the servicing plan method, try to use the task sequence approach.

    In addition, you can rebuild the deployment package which used to store feature updates and re-ran the servicing plan rule to download content again.

    If nothing helps, please upload the complete log file to network drive and share the link here.

    https://docs.microsoft.com/en-us/sccm/core/plan-design/hierarchy/log-files

    In addition, you can also contact SCCM forum for help:

    https://social.technet.microsoft.com/Forums/en-US/home?category=systemcenter2012configurationmanager


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Wednesday, June 6, 2018 2:35 AM
  • 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. 
    Wednesday, June 6, 2018 2:44 PM
  • The reason I have two separate entries is because the results are different for the SCCM than they are for the USB upgrade, but the logs have similar entries.   The first attempt was deployed with windows 10 servicing in SCCM. the second attempt was via USB, the third attempt was through a task sequence.  When running this through the SCCM it fails immediately, only the USB gives the winpeshl.ini error.  You say this could be a corrupted installation file, I have tried several different ISO downloads all with the same results.  I will try rebuilding the deployment package for the task sequence as you suggested and get you the logs if it fails again.

    ReliableWest

    Wednesday, June 6, 2018 3:50 PM
  • I am experiencing the same issues.  I am able to create either a task sequence or a servicing update and deploy them.  However, when the update runs, I get a DOS window on reboot with "a winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name."

    The upgrade fails, and when in a TS, the rest of the task sequence completes.

    Veriifcation of WinVer shows still 1709, TS logs show that the OS upgrade section passed!

    Command line for extension .EXE is "%1" %* OSDUpgradeWindows 06/06/2018 15:52:12 13424 (0x3470)
    Set command line: "C:\WINDOWS\ccmcache\3d\SETUP.EXE" /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable OSDUpgradeWindows 06/06/2018 15:52:12 13424 (0x3470)
    Executing command line: "C:\WINDOWS\ccmcache\3d\SETUP.EXE" /ImageIndex 3 /auto Upgrade /quiet /noreboot /postoobe "C:\WINDOWS\SMSTSPostUpgrade\SetupComplete.cmd" /postrollback "C:\WINDOWS\SMSTSPostUpgrade\SetupRollback.cmd" /DynamicUpdate Disable OSDUpgradeWindows 06/06/2018 15:52:12 13424 (0x3470)
    Process completed with exit code 0 OSDUpgradeWindows 06/06/2018 16:26:29 13424 (0x3470)
    Windows Setup completed with exit code hexadecimal 0x00000000 (decimal 0)  OSDUpgradeWindows 06/06/2018 16:26:29 13424 (0x3470)
    Saving exit code of Windows upgrade - hexadecimal 0x00000000 (decimal 0) -  to Task sequence environment variable '_SMSTSOSUpgradeActionReturnCode', as decimal string OSDUpgradeWindows 06/06/2018 16:26:29 13424 (0x3470)
    Windows Setup completed successfully!  OSDUpgradeWindows 06/06/2018 16:26:29 13424 (0x3470)
    Exiting with code 0x00000000 OSDUpgradeWindows 06/06/2018 16:26:29 13424 (0x3470)
    Process completed with exit code 0 TSManager 06/06/2018 16:26:29 14088 (0x3708)

    Wednesday, June 6, 2018 9:59 PM
  • ok, so I figured this out. When it gets hung at the cmd prompt after the first reboot:

    CD to the root (cd\)

    Search for RecEnv.exe (dir RecEnv.exe /s)

    CD to that directory

    run the fire by typing it name exact RecEnv.exe

    Setup will now continue!

    Don't close the dos windows. It will finish on it's own from here!

    • Proposed as answer by MARKKUNZ Thursday, June 7, 2018 2:07 PM
    Thursday, June 7, 2018 1:57 PM
  • This worked for me. For what it's worth, I'm using Ivanti for deployment and ran into the same issue. Its nice to have a workaround but I hope a fix is coming, because this isn't scalable for upgrades
    Thursday, June 7, 2018 3:47 PM
  • Awesome I will try this.  I downloaded the ISO from MSDN instead of from VLSC and it worked by USB on one machine last night.  However, it still failed through the SCCM task sequence on another machine.

    ReliableWest

    Thursday, June 7, 2018 4:12 PM
  • Okay I have a solution. 

    The corruption is happening when the ISO is unpacked.  I have been mounting the ISO using windows explorer.  The USB worked because I created a bootable USB using RUFUS 3.0.  In SCCM when I created the TS package I unpacked the ISO directly to the folder and it apparently corrupted.  Using the same ISO download that succeeded for the USB still failed in the SCCM.  I copied the files from the USB drive directly to the folder where I had my TS package and overwrote the files there.  Now the SCCM is pushing and machines are happily upgrading.

    I suspect windows 10 isn't unpacking the ISO's correctly and causing the corruption.


    ReliableWest

    • Marked as answer by WECCHelpDesk Thursday, June 7, 2018 5:23 PM
    • Unmarked as answer by WECCHelpDesk Tuesday, June 12, 2018 3:18 PM
    Thursday, June 7, 2018 5:00 PM
  • ok, so I figured this out. When it gets hung at the cmd prompt after the first reboot:

    CD to the root (cd\)

    Search for RecEnv.exe (dir RecEnv.exe /s)

    CD to that directory

    run the fire by typing it name exact RecEnv.exe

    Setup will now continue!

    Don't close the dos windows. It will finish on it's own from here!

    This works. Thanks for the tip, highly appreciated!
    Sunday, June 10, 2018 5:18 PM
  • So i was getting the same issue when doing an upgrade via SCCM, or just manually running from the installation media.  The installation media i was using was SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_English_-3_MLF_X21-82160.ISO which was downloaded from the VLSC site.

    When i was looking at the logs, i discovered the system was using the WINRE file to stage Windows PE instead of the BOOT.WIM file like i had assumed.  So what i did was copy the SOURCES folder out of the BOOT.WIM file from the installation media, and copy it to the WINRE.WIM file located in the Windows\System32\Recovery folder (inside the install.wim file).  Once i did that the upgrade completed perfectly.  

    It also lets you queue up the inplace upgrade package in SCCM or automate the deployment so you can do many machines.

    Hope it helps someone.

    • Marked as answer by WECCHelpDesk Thursday, June 14, 2018 2:28 PM
    Sunday, June 10, 2018 6:46 PM
  • Hi Jeff, thanks for your Research and published solution. Do i understand correct, that you copy and overwrite the WINRE.WIM inside INSTALL.WIM (via DISM) with the boot.wim-File from SOURCES Directory of Installation media? Did you rename the boot.wim-File? Is there any other Operation you've done?

    I've tried a lot but nothing worked for me. Actually the winpeshl.ini error is gone but after realad Windows is asking for a clean Installation instead of an upgrade Progress.

    Thanks for your Feedback.


    Best Regards,

    Jochen


    Tuesday, June 12, 2018 1:25 PM
  • Hello - I'm also using Ivanti to push out upgrades from win7 enterprise to win10 1803. May I asked how you approached this and what method did you use? It works fine for me deploying a batch file using the setup.exe from the ISO. However, I am having an issue where it is not allowing me to keep the apps and settings. I found out that it is upgrading to Windows 10 pro instead of Enterprise. So, I deleted the other versions of Windows 10 from the install.wim and just left it with the the Enterprise version. However, I'm now running into that issue where I'm getting the error: "a winpeshl.ini file is present, but no commands were successfully launched. This could be caused by incorrect formatting or an invalid executable name." may result from a corrupted installation file, which lead to failure during setup". I tried the above solution but to no avail. Any input/suggestion would greatly be appreciated. Thanks!
    Tuesday, June 12, 2018 2:23 PM
  • Hi at all,

    extracting with RUFUS does not help in my case.

    And I think, manually modifing the install.wim or it's content is not an option for an enterprise environment.
    I hope, there will be a solution available in a timely matter.

    thanks to all of you for your investigations!

    best regards
    Marius

    Tuesday, June 12, 2018 2:29 PM
  • Marius,

    I downloaded the ISO from MSDN, I failed to mention that in my solution.  Are you able to download the ISO from MSDN instead of VLSC?  if so let me know and if the results are different and I will edit the update into my solution.


    ReliableWest

    Tuesday, June 12, 2018 2:34 PM
  • I think the most enterprise customers only able to download vlsc files. RUFUS wasnt a solution for me. Editing install.wim also does not work. As marius said, this couldnt be seriously the Microsoft-answered solution for an enterprise rollout?!
    Regards Jochen
    Tuesday, June 12, 2018 3:11 PM
  • I haven't seen Microsoft post a solution yet.  My solution was merely a work around to what Microsoft suggested was corrupt installer files.

    ReliableWest


    Tuesday, June 12, 2018 4:33 PM
  • Hello

    We are aware of the issue and are investigating solutions,

    Will update when we know more


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Wednesday, June 13, 2018 12:15 AM
  • I was having the same issue and I added the source directory(which i extracted from the boot.wim) to the winre.wim file as Jeff suggested.  Not sure why it is missing in the ISO Microsoft released.  That took care of the issue for us.

    Wednesday, June 13, 2018 5:05 PM
  • I am upgrading from 1709 to 1803 with task sequence. I am experiencing the same issues. 
    Wednesday, June 13, 2018 7:53 PM
  • Hi guys

    I summarized these posts and wrote a short blog post about my workaround. Check it: https://akosbakos.ch/solved-windows-10-1803-upgrade-with-winpeshl-ini-issue/



    • Edited by AkosBakos Thursday, June 14, 2018 6:23 AM
    Thursday, June 14, 2018 6:22 AM
  • Doesn't seem to work for me, copied the files to my share (get the same error). 
    Thursday, June 14, 2018 11:51 AM
  • Multiple forums posts and Reddit threads on this issue. The problem is the latest ISO on the VLSC. The previous ISO works but we can't download that now. The solution is a new ISO from microsoft. There are workarounds but as previously mentioned these are unsuitable for use in an Enterprise environment with a large quantity of machines to be upgraded. Now we all play the waiting game.


    • Edited by Madmac15 Thursday, June 14, 2018 12:22 PM grammar
    Thursday, June 14, 2018 12:21 PM
  • Fixing the winre.wim files worked for us as well.

    The gathered Information for this workaround is also available with german descriptions at: http://bitblick.de/369/winpeshl-ini-fehler-bei-windows-10-1803-inplace-upgrade/

    Hope for upcoming News from Microsoft fixing this finally.


    Best Regards, Jochen




    Thursday, June 14, 2018 2:26 PM
  • Grat!!! This Helped me.

    Saturday, June 16, 2018 11:04 AM
  • Hello:

    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.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.


    Saturday, June 16, 2018 6:50 PM
  • Great, thank you Darrell Gorter, we'll retry that Monday and feed you back and all the Folks here.

    Cherif Benammar

    Sunday, June 17, 2018 10:03 AM
  • I confirm, the new ISO is ok.

    I used the french version


    Cherif Benammar

    Sunday, June 17, 2018 3:08 PM
  • The ISO is still shows updated in March  on VLSC - Windows 10, Version 1803 (Updated Mar '18)

    Should this say June now?

    Monday, June 18, 2018 3:04 PM
  • Yes, you are right, but it worked.

    I have to say that BSOD happened on my laptop several times and I went back to 1709 till I find updated drivers.


    Cherif Benammar

    Monday, June 18, 2018 3:12 PM
  • Hello,

    No it should be the March date, the updated one is not yet available.


    Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Tuesday, June 19, 2018 6:05 PM
  • For me the new image works fine. Upgrade runs clearly without interruption. And yes, the image is still updated in March, but has updated binaries regarding the case discussed here Thanks for the very fast support, Microsoft
    Tuesday, June 19, 2018 8:18 PM
  • For anybody that's following this thread, the current ISO in VLSC is NOT a fix.  This is a previous ISO that has the issue where, sometimes but not always, the 500MB Recovery partition becomes a mapped drive after an in-place upgrade is ran.  The partition will be almost full and Windows will nag you that you're running out of disk space, this is the issue the newer ISO was supposed to fix.  The removal of the mapped drive requires command line intervention, it cannot be done through the GUI.  I warn you NOT to use this ISO if you're looking to upgrade thousands of computers like we are.  I was able to script a fix but we've decided to just wait for Microsoft to actually fix the problem. 
    Tuesday, June 19, 2018 10:30 PM
  • @IamNeedHelping Thank you for the warning.

    Sure, it is an older one with an old build number.
    I checked the upgrade several times on different Systems and cannot identify the issue you described.

    I hope, the June update will be release soon

    Wednesday, June 20, 2018 8:02 AM
  • I confirmed successful upgrade with the latest download, I need also to raise that after some time BSOD happened then rollback was the solution, then I'll wait till 1803 is stabilized.

    Cherif Benammar

    Wednesday, June 20, 2018 10:51 AM
  • I can also confirm that this ISO successfully upgrades without errors. It is even supported by Dell DDPE encrypted machines. However, I'll see how the next release (mentioned previously in this thread) goes before committing to a mass deployment.

    Thanks everyone for your feedback.

    Wednesday, June 20, 2018 1:11 PM
  • Thanks a lot for the person who provided this solution, which helped me to perform the upgrade correctly
    Thursday, June 21, 2018 2:39 PM
  • I'll need your confirmation that actual ISO file doesn't lead to BSOD.

    Actually i'm using 1709 till 1803 is reviewed or a new version released.


    Cherif Benammar

    Thursday, June 21, 2018 2:52 PM
  • New ISO's 'v4' are available on the VLK download site
    Example: English International:
    SW_DVD9_Win_Pro_Ent_Edu_N_10_1803_64BIT_Eng_Intl_-4_MLF_X21-87131.ISO



    Hello!


    • Edited by Grimson Tuesday, July 3, 2018 5:27 PM
    Tuesday, July 3, 2018 5:24 PM
  • Thank you for the notification.

    For me, Upgrade and new Installation runs fine

    Wednesday, July 4, 2018 10:59 AM
  • Yes it is, I see "Updated June 18", download on going and then upgrade,

    I'll feed you back if manual upgrade succeeds or still raising BSOD.


    Cherif Benammar

    Wednesday, July 4, 2018 2:47 PM
  • Ok, now I confirm that June Update for Windows 10 - 1803 is good.

    It was now more than 15 hours without any BSOD.


    Cherif Benammar

    Thursday, July 5, 2018 11:55 AM