none
Schedule Updates on OS Upgrade Package failing - SCCM 1902 RRS feed

  • Question

  • Hi,

    Can anyone help here? I'm trying to schedule updates on a Windows 10 1809 Operating System Upgrade Package. I've created two upgrade packages - one for en-US and one for en-GB. The en-US one works fine, the en-GB one doesn't. Everything I've done for the two packages I believe has been identical.

    I get the error message "Failed to apply one or more updates". The dism.log doesn't seem to indicate any particular issue that I can see. The OfflineServicingMgr.log file notes the failure but gives next to no details on why. 

    What I've tried so far: I've re-running the schedule, which resulted in failure. I've deleted the OSUP and recreated, which also resulted in failure. I've ran the schedule with just one update in - and it succeeded! There are now 38 updates in total that need to be injected.

    The relevant section of the log file reads thusly:

    Checking if update (34 of 38) with ID 17536335 needs to be applied on the image. 1 content binarie(s) are associated with the update.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 17:51:41	24244 (0x5EB4)
    Applicability State = APPLICABLE, Update Binary = E:\ConfigMgr_OfflineImageServicing\905a4705-4dbf-4fc3-8eab-1d31f5be7a9b\Windows10.0-KB4519338-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 17:52:17	24244 (0x5EB4)
    Applying update with ID 17536335 on image at index 3.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 17:52:17	24244 (0x5EB4)
    STATMSG: ID=7908 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=*** SITE=*** PID=4144 TID=24244 GMTDATE=Thu Oct 31 18:06:53.521 2019 ISTR0="17536335" ISTR1="***" ISTR2="3" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:06:53	24244 (0x5EB4)
    This update binary was successfully updated on the mounted image.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:06:53	24244 (0x5EB4)
    Schedule processing cancelled ...	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:06:53	24244 (0x5EB4)
    UnMounting Image (Commit Changes = 0) ...	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:06:53	24244 (0x5EB4)
    WARNING : Timed-out waiting for the processing thread to complete.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:07:54	8732 (0x221C)
    Offline Servicing Manager thread is exiting.	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:07:54	8732 (0x221C)
    Successfully run 'dism /cleanup-wim'	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Successfully run 'dism /cleanup-mountpoints'	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Completed processing image package ***. Status = Failed	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Not copying back  the image to source location	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Updated history for image package *** in the database	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Schedule processing failed	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    Processing completed for Schedule with ID 16777348	SMS_OFFLINE_SERVICING_MANAGER	31/10/2019 18:08:26	24244 (0x5EB4)
    

    Friday, November 1, 2019 10:41 AM

All replies

  • Hi,

    1.Please help review the DISM.log, DistMgr.log and OfflineServicingMgr.log to see if there is any clue? 

    2. Can we use the DISM command like below to manually inject the updates into the offline image? 

    Dism /Add-Package /Image:"E:\Source\OS\Windows10\EN 1803\offline" /PackagePath="E:\Source\Updates\Windows 10 1803\937c715f-a49e-4480-8b0c-e8f417e15164\Windows10.0-KB4100347-x64.cab"

    For more information, please refer to: WINDOWS 10 IMAGE MAINTENANCE & CLEANUP

    Thanks for your time.

    Best regards,
    Simon

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

    Monday, November 4, 2019 11:04 AM
  • Hi,

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

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

    Thursday, November 7, 2019 1:21 AM
  • Hi.

    I think I've narrowed it down to one or two updates. It's taken a little while as it's a slow process, and I wasn't able to identify the updates from the log file. It would mention things like "Update with ID 17536355" and I didn't know how to correlate that with the updates in SCCM.

    They appear to be .NET Framework 4.8, and the 2019-10 Cumulative Update for .NET Framework 4.8 that are causing the problem.

    I will try and inject these updates into the OSUP using DISM and see what results I get if you think this is the best way to proceed. Hopefully this won't break anything!

    Thanks

    FF.

    Friday, November 8, 2019 11:45 AM
  • So I manually imported the problematic update to the wim at all 11 indexes using DISM. I then ran the "Schedule Updates" task for the OSUP, and selected only the update that I'd manually installed via DISM. Observing the OfflineServicingMgr.log the update Applicability State is now INSTALLED rather than APPLICABLE.

    So far, so good. However, at a random point it fails again (even though it doesn't need to apply the update). The OfflineServicingMgr.log shows at the time of failure:

    Applicability State = INSTALLED, Update Binary = E:\ConfigMgr_OfflineImageServicing\0b8bf725-83b9-4132-a26a-435360a6530f\windows10.0-kb4486165-x64.cab.	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:02:50	14776 (0x39B8)
    No need to apply this update binary since it's already installed.	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:02:50	14776 (0x39B8)
    Schedule processing cancelled ...	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:02:50	14776 (0x39B8)
    UnMounting Image (Commit Changes = 0) ...	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:02:50	14776 (0x39B8)
    Successfully run 'dism /cleanup-wim'	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Successfully run 'dism /cleanup-mountpoints'	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Completed processing image package *****. Status = Failed	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Not copying back  the image to source location	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Successfully deleted entry from database for schedule ID=16777367 Name="" assigned to ImageID=***	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Updated history for image package *** in the database	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Schedule processing failed	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Processing completed for Schedule with ID 16777373	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    STATMSG: ID=7910 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_OFFLINE_SERVICING_MANAGER" SYS=***** SITE=*** PID=17540 TID=14776 GMTDATE=Thu Nov 21 18:04:42.912 2019 ISTR0="16777373" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:42	14776 (0x39B8)
    Schedule processing thread stopped	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:45	14776 (0x39B8)
    Offline Servicing Manager thread is exiting.	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:04:45	7948 (0x1F0C)
    SMS_EXECUTIVE started SMS_OFFLINE_SERVICING_MANAGER as thread ID 24036 (0x5DE4).	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:05:27	7016 (0x1B68)
    Inbox source is local on *****	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:05:27	24036 (0x5DE4)
    Offline Servicing staging drive is assigned to be E:	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:05:27	24036 (0x5DE4)
    Checking if there are schedule(s) which need to be run at this time.	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:05:27	24036 (0x5DE4)
    This Schedule with ID 16777286 does not have a next run time	SMS_OFFLINE_SERVICING_MANAGER	21/11/2019 18:05:28	24036 (0x5DE4)
    

    And the DISM.log from around the same time (18:04):

    2019-11-21 17:57:57, Info                  DISM   DISM.EXE: <----- Ending Dism.exe session ----->
    2019-11-21 17:57:57, Info                  DISM   DISM.EXE: 
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 17:57:57, Info                  DISM   DISM Provider Store: PID=10176 TID=22688 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll:                                            - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll:                                            - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll: Version 6.3.9600.17031 - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Enter DismInitializeInternal - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Initialized GlobalConfig - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Initialized SessionTable - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Waiting for m_pInternalThread to start - CCommandThread::Start
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=16492 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=16492 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 m_pInternalThread started - CCommandThread::Start
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Created g_internalDismSession - DismInitializeInternal
    2019-11-21 18:00:23, Info                  DISM   API: PID=20128 TID=24512 Leave DismInitializeInternal - DismInitializeInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Enter DismShutdownInternal - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=16492 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=16492 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=16492 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=16492 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2019-11-21 18:01:17, Info                  DISM   PID=20128 TID=16492 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2019-11-21 18:01:17, Info                  DISM   PID=20128 TID=16492 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2019-11-21 18:01:17, Info                  DISM   PID=20128 TID=16492 DismCore.dll version: 6.3.9600.19408 - CDISMManager::FinalConstruct
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=16492 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Deleted g_internalDismSession - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Shutdown SessionTable - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 Leave DismShutdownInternal - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll:                                          - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2019-11-21 18:01:17, Info                  DISM   API: PID=20128 TID=24512 DismApi.dll:                                          - DismShutdownInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll:                                            - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll:                                            - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll: Version 6.3.9600.17031 - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll: Parent process command line: C:\Windows\system32\wbem\wmiprvse.exe - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Enter DismInitializeInternal - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Input parameters: LogLevel: 2, LogFilePath: (null), ScratchDirectory: (null) - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Initialized GlobalConfig - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Initialized SessionTable - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Waiting for m_pInternalThread to start - CCommandThread::Start
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=25524 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=25524 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 m_pInternalThread started - CCommandThread::Start
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Created g_internalDismSession - DismInitializeInternal
    2019-11-21 18:02:56, Info                  DISM   API: PID=12052 TID=13848 Leave DismInitializeInternal - DismInitializeInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Enter DismShutdownInternal - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=25524 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=25524 Successfully dequeued command object - CCommandThread::DequeueCommandObject
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=25524 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=25524 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
    2019-11-21 18:03:41, Info                  DISM   PID=12052 TID=25524 Temporarily setting the scratch directory. This may be overridden by user later. - CDISMManager::FinalConstruct
    2019-11-21 18:03:41, Info                  DISM   PID=12052 TID=25524 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2019-11-21 18:03:41, Info                  DISM   PID=12052 TID=25524 DismCore.dll version: 6.3.9600.19408 - CDISMManager::FinalConstruct
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=25524 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Deleted g_internalDismSession - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Shutdown SessionTable - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 Leave DismShutdownInternal - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll:                                          - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
    2019-11-21 18:03:41, Info                  DISM   API: PID=12052 TID=13848 DismApi.dll:                                          - DismShutdownInternal
    2019-11-21 18:04:42, Info                  DISM   PID=18120 TID=22360 Scratch directory set to 'C:\Windows\TEMP\'. - CDISMManager::put_ScratchDir
    2019-11-21 18:04:42, Info                  DISM   PID=18120 TID=22360 DismCore.dll version: 10.0.17763.1 - CDISMManager::FinalConstruct
    2019-11-21 18:04:42, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2019-11-21 18:04:42, Info                  DISM   PID=18120 TID=22360 Successfully loaded the ImageSession at "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM" - CDISMManager::LoadLocalImageSession
    2019-11-21 18:04:42, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Failed to get and initialize the PE Provider.  Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2019-11-21 18:04:42, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\DISM\dism.log
    2019-11-21 18:04:42, Info                  DISM   DISM Manager: PID=18120 TID=22360 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: 
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: <----- Starting Dism.exe session ----->
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: 
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: Host machine information: OS Version=6.3.9600, Running architecture=amd64, Number of processors=16
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: Dism.exe version: 10.0.17763.1
    2019-11-21 18:04:42, Info                  DISM   DISM.EXE: Executing command line: "C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe"  /cleanup-wim 
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-11-21 18:04:42, Info                  DISM   DISM Provider Store: PID=18120 TID=22360 Connecting to the provider located at C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2019-1

    Any ideas why it's crashing out despite not having to install the updates?

    Thanks,

    FF.



    Friday, November 22, 2019 9:04 AM
  • I had the issue with servicing Server 2016 wim, it failed because of a bug in 1902.
    Since i didn´t want to edit the DB(not supported) and 1906 was out i upgraded to 1906 and the issue was gone

    vsoro00
    MSFT Official
    
    ConfigMgr team is aware of this. We have fixed this regression in 1906 caused by 1902 hotfix. Database table SuportedProductsForOfflineServicing has an incorrect value of build version for Windows Server 2016. If anyone is blocked by this, tech support can change a single database value if contacted. Table shows version 10240 for Windows Server 2016. While in fact it should be 14393.

    https://www.reddit.com/r/SCCM/comments/cdgoon/sccm_1902_server_2016_wim_offline_servicing/?ref=share&ref_source=embed&utm_content=title&utm_medium=post_embed&utm_name=e0f29111fb6a49c096386e50762cc5ae&utm_source=embedly&utm_term=cdgoon

    Friday, November 22, 2019 6:44 PM
  • Hi,

    Thanks for posting in TechNet and your sharing. Here's a short summary for the problem.

    Problem/Symptom:
    ===================
    Windows 10 1809 Operating System Upgrade Package failed with the error message "Failed to apply one or more updates" in SCCM version 1902

    Solution:
    ===================
    Upgraded to SCCM version 1906 and the issue was gone.

    Please kindly click "Mark as answer" to your answer. It would make the reply to the top and easier to be found for other people who has the similar question. Thanks again for your time.

    Best regards,
    Simon

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

    Tuesday, November 26, 2019 9:52 AM
  • Thanks for the info. I actually looked at the release notes for the 1906 update and didn't notice that this resolved problems updating offline WIMs. I'll update SCCM and see if this resolves the issue.
    Tuesday, November 26, 2019 9:58 AM
  • I updated SCCM to 1906 and it still fails :)
    Friday, November 29, 2019 8:39 AM
  • Does you wim have multiple indexes? I split up the images, then you can also run a cleanup at the end of the apply-drivers process.

    Also apply SUP Servicing stack Updates before CU Cumulative Updates. This also caused me some pain.

    Thursday, December 5, 2019 7:23 PM