Share via

An error occurred applying the Unattend.xml file from the .msu package.

Question

Tuesday, November 27, 2018 3:42 PM | 3 votes

I am unable to apply offline updates to the Windows 10 IoT 1607 x86 fro

2018-07 Cumulative Update for Windows 10 Version 1607 for x86-based Systems (KB4346877) Windows 10,Windows 10 LTSB Updates 7/30/2018

Anything after this update i.e after 7/30/2018, I get the above mentioned error.

I have applied the servicing stack update which is: (KB4132216). I have checksummed and checked the image, it is a stock image that comes from Microsoft

An excerpt from the DISM log is as follows:

2018-11-21 09:35:20, Error                 CBS    Failed to perform operation.  [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2018-11-21 09:35:20, Info                  CBS    Session: 6800_66313875 finalized. Reboot required: no [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2018-11-21 09:35:20, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0922)
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT
2018-11-21 09:35:22, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat
2018-11-21 09:35:22, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to process package changes in unattend file. - CPackageManagerUnattendHandler::Internal_ProcessChanges(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to process package changes. - CPackageManagerUnattendHandler::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to Apply the unattend. - CDISMPackageManager::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Unattend Manager: PID=6800 TID=4748 "Error applying unattend for provider: DISM Package Manager" - CUnattendManager::Apply(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed applying the unattend file from the MSU package. - CMsuPackage::ApplyMsuUnattend(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed to apply the MSU unattend file to the image. - CMsuPackage::Install(hr:0x800f0922)
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Info                  CBS    Offline image is writable
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SOFTWARE, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE' from path '\?\C:\Mount\Windows\System32\config\SOFTWARE'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SYSTEM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM' from path '\?\C:\Mount\Windows\System32\config\SYSTEM'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SECURITY, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY' from path '\?\C:\Mount\Windows\System32\config\SECURITY'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: SAM, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM' from path '\?\C:\Mount\Windows\System32\config\SAM'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: COMPONENTS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS' from path '\?\C:\Mount\Windows\System32\config\COMPONENTS'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: DRIVERS, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS' from path '\?\C:\Mount\Windows\System32\config\DRIVERS'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: DEFAULT, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT' from path '\?\C:\Mount\Windows\System32\config\DEFAULT'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: ntuser.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat' from path '\?\C:\Mount\Users\Default\ntuser.dat'.
2018-11-21 09:35:23, Info                  CBS    Loading offline registry hive: schema.dat, into registry key '{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat' from path '\?\C:\Mount\Windows\system32\smi\store\Machine\schema.dat'.
2018-11-21 09:35:23, Info                  CSI    00001913 CSI Store 205369904 initialized
2018-11-21 09:35:23, Info                  CBS    Session: 6800_66858718 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for offline use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
2018-11-21 09:35:23, Error                 DISM   DISM Package Manager: PID=6800 TID=4748 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0922)
2018-11-21 09:35:23, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0922
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Found the PE Provider.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DISM Package Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SOFTWARE, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SYSTEM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SECURITY, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/SAM, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/COMPONENTS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DRIVERS, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT
2018-11-21 09:35:23, Info                  CBS    Failed to unload offline registry: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/System32/config/DEFAULT, the client may still need it open. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Users/Default/ntuser.dat
2018-11-21 09:35:23, Info                  CBS    Unloading offline registry hive: {bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/Mount/Windows/system32/smi/store/Machine/schema.dat
2018-11-21 09:35:23, Info                  DISM   DISM Package Manager: PID=6800 TID=4748 Finalizing CBS core. - CDISMPackageManager::Finalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ManifestCacheFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ExecutionEngineFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: ComponentAnalyzerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: PackageTrackerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CoreResourcesUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: SessionManagerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CapabilityManagerFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: GetPublicObjectMonitor::Audit
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: PublicObjectMonitorFinalize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: Enter vCoreInitializeLock
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: WcpUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: DrupUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CfgMgr32Unload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: DpxUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: SrUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsEsdUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsTraceInfoUninitialize
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: CbsEventUnregister
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: AppContainerUnload
2018-11-21 09:35:23, Info                  CBS    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-11-21 09:35:23, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DISM Package Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(MsiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: MsiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(IntlManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: IntlManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(IBSManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: IBSManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DriverManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DriverManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(DISM Unattend Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: DISM Unattend Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(SmiManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: SmiManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(AppxManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: AppxManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(ProvManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: ProvManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(AssocManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: AssocManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(GenericManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: GenericManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(OfflineSetupManager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: OfflineSetupManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Finalizing the servicing provider(Edition Manager) - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: Edition Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Releasing the local reference to OSServices. - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Disconnecting Provider: OSServices - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM OS Provider: PID=6800 TID=4748 Successfully unloaded all registry hives. - CDISMOSServiceManager::Final_OnDisconnect
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=6800 TID=4748 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Manager: PID=2684 TID=6064 Closing session event handle 0x2bc - CDISMManager::CloseImageSession
2018-11-21 09:35:41, Info                  DISM   DISM.EXE: Image session has been closed. Reboot required=no.
2018-11-21 09:35:41, Info                  DISM   DISM.EXE:
2018-11-21 09:35:41, Info                  DISM   DISM.EXE: < Ending Dism.exe session >
2018-11-21 09:35:41, Info                  DISM   DISM.EXE:
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Found the OSServices.  Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Disconnecting Provider: SiloedPackageManager - CDISMProviderStore::Internal_DisconnectProvider
2018-11-21 09:35:41, Info                  DISM   DISM Provider Store: PID=2684 TID=6064 Releasing the local reference to DISMLogger.  Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

All replies (24)

Wednesday, November 28, 2018 6:17 AM

Hello Samer,

Did you apply the update on Windows IoT Core or Windows IoT Enterprise? And where did you get the offline update package?

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Wednesday, November 28, 2018 9:06 AM

Hi,

I applied this to the Windows 10 IoT Enterprise LTSB  2016 1607-x86. I got the packages from the the Microsoft catalogue which can be found here: https://www.catalog.update.microsoft.com/Search.aspx?q=Windows+10+Version+1607+for+x86-based+Systems

Regards,

Samer Tufail

Thursday, November 29, 2018 3:14 AM

Hello Samer,

I'm not sure why you are getting the unattend.xml reference. How did you add the .MSU though dism?

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Thursday, November 29, 2018 8:53 AM

Yes, this is applied through DISM. I am applying this to a Windows 10 LTSB 1607 image, which is not corrupted in any way and comes from a CD supplied by Microsoft. I first apply the (KB4132216) which is the service stack update. After which I even save and unmount the image before applying other updates. I then get any cumulative updates  (KB4343884) or any after that date, I get the same error. The same occurs if I apply security updates as well round the same release date as KB434884 or after.

Regards,

Samer Tufail.

Friday, November 30, 2018 8:59 AM

Hello Samer,

Have you tried that if you skip applying update the KB4132216 , and apply update KB4343884 directly, you would get the error or not?

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Friday, November 30, 2018 10:29 AM

Hi,

I tried that, the installation goes through really quickly. Then I check if the package is applied via DISM /Get-Packages and it hasn't and I assume it wouldn't have for a 700MB file that quick. So the KB4132216 is an absolute prereq.

Regards,

Samer Tufail

Thursday, December 6, 2018 5:57 AM

Hello Samer,

What command did you create the package with using? Here is a sample of you should be adding the .MSU.

dism /image:C:\temp\1709_servcing\mount /add-package /packagepath:C:\temp\
1709_servcing\Updates\windows10.0-kb4462932-x64_ce8ddc77b842c122931c4905ebbfc134
4ca2d9ad.msu

And more, I'm not sure why you are getting the unattend.xml reference. Could you please provide the flow steps?

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Friday, December 7, 2018 7:32 AM

Hello Samer,

Yes, I have confirmed that KB4132216 is a SSU which needs to be applied before CU KB4343884. 

Did you try to do other things at the same time as patching the wim?

Here is what you should do with examples. 
1. Mount wim for servicing:

dism /mount-image /imagefile:C:\temp\1709_servcing\install.wim /index:1 /m
ountdir:C:\temp\1709_servcing\mount

2. Add servicing stack update (SSU):

dism /image:C:\temp\1709_servcing\mount /add-package /packagepath:C:\temp\
1709_servcing\Updates\windows10.0-kb4339420-x64_18d8c2fb077e113d43931e6eb8f8cdbb
23538157.msu

3. Add cumulative update (CU):

dism /image:C:\temp\1709_servcing\mount /add-package /packagepath:C:\temp\
1709_servcing\Updates\windows10.0-kb4462932-x64_ce8ddc77b842c122931c4905ebbfc134
4ca2d9ad.msu

4. Seal it back up:

dism /commit-image /mountdir:C:\temp\1709_servcing\Mount

5. Finish sealing it back up:

dism /unmount-image /mountdir:C:\temp\1709_servcing\Mount /commit

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Saturday, December 8, 2018 12:09 PM

Hi Michael,

I am applying the updates as you mention. As far as I know the x64 version is okay. Try this with the x86 and you will probably see the same failure as I am seeing.

Regards,

Samer Tufail

Tuesday, December 11, 2018 2:21 AM

Hello Samer,

Could you please provide more detail information about the environment which you are doing the patching under?

Such as OS version, Windows Kits(ADK) version , DISM version and so on.

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Tuesday, December 11, 2018 9:08 AM

Hi,

I have exactly the same problem when I try to add a cumulative update on Windows 10 IoT Enterprise LTSB  2016 1607-x86.

The last CU I can add offline with dism is KB4346877, and since all the newer CU give me the error mentioned above (related to unattend.xml). The KB 4132216 SSU was added previously in the wim image and committed.

I use Windows 10 IoT Enterprise LTSB 2016 1607 x64 with Windows 10 ADK v10.1.14393.0 to service the wim images.

I tried also on a x86 edition with the ADK, but same error.

Also the latest CU are applied without error online after installation on a target machine.

Best regards,

Seb

Wednesday, December 12, 2018 8:20 AM

Hi Michael,

I am patching under a Windows 10, 1803 x86 environment for a Windows 10 IoT 1607 x86. The DISM I am using is the one that comes part of the Windows 10 ADK for 1607 version. It uses the correct environment variables and the DISM version which comes part of the 1607 ADK.

Regards,

Samer Tufail

Monday, December 17, 2018 2:44 AM

Hello Samer,

Could you please provide the following information:

  1. Application and System Event Logs on your PC. You can clear the events before applying the updates.
  2. output from command "DISM /online /Get-Packages /Format:Table  >  \tmp\Installed_Packages.txt", you can use another folder if necessary.
  3. The full DISM log including the failed installation (not sure if the forum post already lists the full log).

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Wednesday, December 19, 2018 1:46 AM

Hello Samer,

Please try to run the DISM command with using the /ScratchDir parameter pointing to a drive/path with several GB of free HDD space. If the error occurs again, then you can start the command a second time.

DISM  /image:D:\  /Add-Package  /PackagePath:D:\_MX\AMD64_X86-all-windows10.0-kb4346877-x86.msu  /ScratchDir:D:\_MX\tmp  /LogPath:D:\_MX\KB.log

In addition, you should ensure the RAM amount available on your device and how many free HDD space is available on C:\ drive containing the LTSB installation.

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Monday, December 24, 2018 5:44 AM

Hello Samer,

Did you fix the issue with above mentioned command? The **ScratchDir **parameter is used to specify a temporary directory that will be used when extracting files for temporary use during servicing. Please refer to this document(/en-us/windows-hardware/manufacture/desktop/dism-global-options-for-command-line-syntax). By default, if not specified, the \Windows<em>%Temp% directory will be used, in this scenario we should be ensure the space is enough.

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Friday, January 11, 2019 4:11 PM

Hi,

since I have the same problem as Samer, I looked at the memory and scratchdir : I have 16GB of memory, and the scratchdir has more than 100GB of free space. So that's not the problem...

If you have another idea, this will be great.

Best regards,

Seb

Friday, January 18, 2019 1:16 AM

Hello Seb,

Could you please provide your log? Did you get the same error with Samer's?

Best Regards,

Michael

MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].

Tuesday, April 9, 2019 4:14 PM | 1 vote

Has anyone found a solution to this?

I can confirm the x64 update process works fine, but the x32 one does not.

This is not related to scratchdir or available space, since the x64 packages are twice as big and work.

-Marine

Friday, April 19, 2019 3:26 PM

Hi Michael,

I had some time to try again updating offline my "Windows 10 IoT Enterprise LTSB  2016 1607 - x86" install.wim image file.
After mounting it and adding with success the latest SSU (KB4485447), I tried to add the latest Cumulative Update KB4489889. I used this command line, in Powershell :

Add-WindowsPackage -Path P:\essaiUpdate\mount -PackagePath P:\windows10.0-kb4489889-x86.msu -ScratchDirectory P:\essaiUpdate\scratchdir -Logpath P:\essaiUpdate\logs\Add_Package_KB4489889.log

And it fails again. No matter I save and dismount the image after adding the SSU, the result is the same. And the problem is always the same :

WARNING : Failed to add package P:\windows10.0-kb4489889-x86.msu
WARNING : Add-WindowsPackage failed. Error code = 0x800f0922
Add-WindowsPackage : An error occurred applying the Unattend.xml file from the .msu package.
For more information, review the log file.
Au caractère Ligne:1 : 1
+ Add-WindowsPackage -Path "P:\essaiUpdate\MOUNT\windows" -PackagePath  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Add-WindowsPackage], COMException
    + FullyQualifiedErrorId : Microsoft.Dism.Commands.AddWindowsPackageCommand

The log file is about 1.4 MB zipped, you can download it here : http://dl.free.fr/rQ2czmSym

Best Regards

Seb

Tuesday, April 23, 2019 8:14 AM

Seb,

Can you upload it to pastebin or similar? or the zipped to a free file share. I hope Michael gets around to it, I am still having the same problem and this has not been resolved.

Regards,

Samer Tufail

Wednesday, April 24, 2019 3:18 PM

Hi Samer, link added in the post. Hope it helps.

Wednesday, April 24, 2019 6:37 PM

Count me as someone who also has the problem applying the x86 update. Hope they figure out what broke.

Thursday, June 6, 2019 8:33 AM

Hello Michael,

I posted my logs a month and a half ago. Did you download them and find anything about the problem ?

Best regards,

Seb

Friday, June 7, 2019 3:08 PM

Hi,

I made a new try with the latest SSU KB4498947, and the latest CU KB4499177, but same result, error code 0x800f0922 :

Add-WindowsPackage : An error occured applying the Unattend.xml file from the .msu package.

Here are the logs files : http://dl.free.fr/kbsQEV0Bz

Regards,

Seb