Yes, it's express cab alike, cannot be used without the associated .psf file, and only WU can handle it i don't know if they came up with this new formula to reduce download size, or just to break our UUP dump
Manually importing Windows10.0-KB5004071-x64.cab does not work either. Here is the dism log Code: 2021-06-08 16:04:57, Info DISM PID=3008 TID=2464 Scratch directory set to 'C:\Users\KLEINE~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2021-06-08 16:04:57, Info DISM PID=3008 TID=2464 DismCore.dll version: 10.0.21390.1 - CDISMManager::FinalConstruct 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Warning DISM PID=3008 TID=2464 Failed to archive the log file. Continuing with existing log file. - CDISMManager::CreateLocalImageSession(hr:0x80070002) 2021-06-08 16:04:57, Info DISM PID=3008 TID=2464 Successfully loaded the ImageSession at "C:\Windows\system32\Dism" - CDISMManager::LoadLocalImageSession 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Info DISM DISM Provider Store: PID=3008 TID=2464 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2021-06-08 16:04:57, Info DISM DISM.EXE: 2021-06-08 16:04:57, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2021-06-08 16:04:57, Info DISM DISM.EXE: 2021-06-08 16:04:57, Info DISM DISM.EXE: Host machine information: OS Version=10.0.21390, Running architecture=amd64, Number of processors=2 2021-06-08 16:04:57, Info DISM DISM.EXE: Dism.exe version: 10.0.21390.1 2021-06-08 16:04:57, Info DISM DISM.EXE: Executing command line: dism /online /add-package /packagepath:"C:\Users\KleineZiege\Desktop\Windows10.0-KB5004071-x64.cab" 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 physical location path: C:\ - CDISMManager::CreateImageSession 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Event name for current DISM session is Global\{BA090334-F785-48F6-A97E-66AABEBB1755} - CDISMManager::CheckSessionAndLock 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Create session event 0x204 for current DISM session and event name is Global\{BA090334-F785-48F6-A97E-66AABEBB1755} - CDISMManager::CheckSessionAndLock 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Copying DISM from "C:\Windows\System32\Dism" - CDISMManager::CreateImageSessionFromLocation 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Successfully loaded the ImageSession at "C:\Users\KLEINE~1\AppData\Local\Temp\748C33EA-3FE3-4C63-846C-D6A9334E56A5" - CDISMManager::LoadRemoteImageSession 2021-06-08 16:04:57, Info DISM DISM Image Session: PID=4676 TID=4136 Instantiating the Provider Store. - CDISMImageSession::get_ProviderStore 2021-06-08 16:04:57, Info DISM DISM OS Provider: PID=4676 TID=4136 Defaulting SystemPath to C:\ - CDISMOSServiceManager::Final_OnConnect 2021-06-08 16:04:57, Info DISM DISM OS Provider: PID=4676 TID=4136 Defaulting Windows folder to C:\Windows - CDISMOSServiceManager::Final_OnConnect 2021-06-08 16:04:57, Info DISM DISM Provider Store: PID=4676 TID=4136 Attempting to initialize the logger from the Image Session. - CDISMProviderStore::Final_OnConnect 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Info DISM DISM Provider Store: PID=4676 TID=4136 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Info DISM Initialized Panther logging at C:\Windows\Logs\DISM\dism.log 2021-06-08 16:04:57, Info DISM DISM Manager: PID=3008 TID=2464 Image session successfully loaded from the temporary location: C:\Users\KLEINE~1\AppData\Local\Temp\748C33EA-3FE3-4C63-846C-D6A9334E56A5 - CDISMManager::CreateImageSession 2021-06-08 16:04:57, Info DISM DISM.EXE: Target image information: OS Version=10.0.21390.1, Image architecture=amd64 2021-06-08 16:04:57, Info DISM DISM.EXE: Image session version: 10.0.21390.1 2021-06-08 16:04:57, Info DISM DISM Transmog Provider: PID=4676 TID=4136 Current image session is [ONLINE] - CTransmogManager::GetMode 2021-06-08 16:04:57, Info DISM DISM Transmog Provider: PID=4676 TID=4136 Audit Mode: [No] - CTransmogManager::Initialize 2021-06-08 16:04:57, Info DISM DISM Transmog Provider: PID=4676 TID=4136 GetProductType: ProductType = [WinNT] - CTransmogManager::GetProductType 2021-06-08 16:04:57, Info DISM DISM Transmog Provider: PID=4676 TID=4136 Product Type: [WinNT] - CTransmogManager::Initialize 2021-06-08 16:04:57, Info DISM DISM Transmog Provider: PID=4676 TID=4136 Product Type ServerNT : [No] - CTransmogManager::Initialize 2021-06-08 16:04:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2021-06-08 16:04:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_SUCCESS 2021-06-08 16:04:57, Info DISM DISM Driver Manager: PID=4676 TID=4136 Further logs for driver related operations can be found in the target operating system at %WINDIR%\inf\setupapi.offline.log - CDriverManager::Initialize 2021-06-08 16:04:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2021-06-08 16:04:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_SUCCESS 2021-06-08 16:04:57, Info DISM DISM OS Provider: PID=4676 TID=4136 Determined System directory to be C:\Windows\System32 - CDISMOSServiceManager::get_SystemDirectory 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Finished initializing the CbsConUI Handler. - CCbsConUIHandler::Initialize 2021-06-08 16:04:57, Info CSI 00000001 Shim considered [l:126]'\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_OBJECT_PATH_NOT_FOUND 2021-06-08 16:04:57, Info CSI 00000002 Shim considered [l:123]'\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.21390.1000_none_58f0e9ab64f38697\wcp.dll' : got STATUS_SUCCESS 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Encountered the option "packagepath" with value "C:\Users\KleineZiege\Desktop\Windows10.0-KB5004071-x64.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Package Package_for_RollupFix~31bf3856ad364e35~amd64~~21390.1000.1.0 with CBS state 2(CbsInstallStateResolved) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) - CDISMPackage::LogInstallStateMapping 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState 2021-06-08 16:04:57, Info DISM DISM Package Manager: PID=4676 TID=4136 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize 2021-06-08 16:05:16, Info DISM DISM Package Manager: PID=4676 TID=6104 Error in operation: (null) (CBS HRESULT=0x800f0988) - CCbsConUIHandler::Error 2021-06-08 16:05:16, Error DISM DISM Package Manager: PID=4676 TID=4136 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0988) 2021-06-08 16:05:16, Error DISM DISM Package Manager: PID=4676 TID=4136 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f0988) 2021-06-08 16:05:16, Info DISM DISM Package Manager: PID=4676 TID=4136 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession 2021-06-08 16:05:16, Error DISM DISM Package Manager: PID=4676 TID=4136 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0988) 2021-06-08 16:05:16, Info DISM DISM Package Manager: PID=4676 TID=4136 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine 2021-06-08 16:05:16, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0988 2021-06-08 16:05:16, Info DISM DISM Package Manager: PID=4676 TID=6104 Finalizing CBS core. - CDISMPackageManager::Finalize 2021-06-08 16:05:16, Info DISM DISM Manager: PID=3008 TID=2464 Closing session event handle 0x204 - CDISMManager::CleanupImageSessionEntry 2021-06-08 16:05:16, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2021-06-08 16:05:16, Info DISM DISM.EXE: 2021-06-08 16:05:16, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2021-06-08 16:05:16, Info DISM DISM.EXE:
Code: More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log i already checked that behavior with KB5003837 (21382.1000) it will not work without Windows10.0-KB5003837-x64.psf (UUP dump exclude it by default) and even with that, only WU can handle it and generate the payload files (to construct full KB5003837) although, express.psf.cix.xml can be parsed to manually generate the payload files but it's complicated and require multiple tools
Is this really official (21H2 remains vibranium and current cobalt gets canceled)? I was just about to jump on the Dev channel, thinking cobalt 21H2 was a sure deal after the name changed to co_relesae and nV started publishing updates to WDDM 3.0 developer drivers. This is strange after MS promised some new features to land this year which are doubtful to be included in a vibranium update. Is it possible they plan to backport features from co_relese to vibranium updates? Or do they plan to release both a vibranium update and a new co_refresh alongside each other this year (with the new cobalt or whatever new branch being radically new, possibly incompatible with old hardware...)?
windows10.0-kb5004071-x64.cab (17,123 KB) Windows10.0-KB5004071-x64.psf (23,596 KB) + pending (alike initial 10240 won't accept LCU offline) = Failed ? Q: Is it possible to eliminate pending state of an install.wim? 7Customizer always deletes Pending.xml.
You mean undo/remove the updates which set the pending flag? Code: dism /image:C:\ /cleanup-image /revertpendingactions
@xinso Z:\windows10.0-kb5004071-x64 contain windows10.0-kb5004071-x64.cab + Windows10.0-KB5004071-x64.psf? or expanded windows10.0-kb5004071-x64.cab + Windows10.0-KB5004071-x64.psf?
Do you have the patience? 1. Install all available SKUs 2. Install all avalable language packs 3. Install all avalable FOD packages 4. Windows Update 5. Restart 6. Shutdown 7. Capture all 21390.1000 packages 8. Combine and repack into normal windows10.0-kb5004071-x64.cab
Just got this ndp48 update offered on 21390.1000: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-638#post-1664562