HP T530 Windows 10 Thin Client - Factory Image - can't apply 2018 October update KB4462917

[MikeW1927]

Hi - We have deployed HP Device Manager 4.7 SP10 - and have received a number of T530 thin clients we wish to standardise and update. They arrive with Windows 10 Enterprise 2016 LTSB Version 1607 OS Build 14393.2311 - as per organisation requirements.

We have since redeployed the image Imported from HP Update Center - image 17WWETAJ603_ABA_1019.ibr "Win10IoT Image 17WWETAJ603 English (Sept 2017)". This version is the only English version available  - resulting Image Version in HP DM is 17WWETAJ603#SABA#DABA - Noted that the devices seemed to ship with with a mixture of 17WWETBJ601#SABG#DABG and 17WWETBJ602#SABG#DABG. Anyway - the issue is - 

We Imported the KB4462917 update from HP Update Center. It cannot deploy.

The Error is 0x800f081e The specified package is not applicable to this image. 

I think the package is applicable - the reason being:

*** The update worked once on this same T530 with the out of box image 602 (if I recall correctly it was originally 602 but not now) and did not at all work with 601 I.e. I deployed simultaneously to two devices - this 602 subject device worked, the current 601 device did not.

So in summary, currently we have the same problem with two images:

A) an out-of-box 17WWETBJ601 image

B) an HP Update Center 17WWETAJ603 image

Can anyone advise what I should do?

The DISM.log shows:

2018-11-27 07:31:44, Info                  DISM   DISM Package Manager: PID=3136 TID=2524 Encountered the option "packagepath" with value "C:\TEMP\windows10.0-kb4462917-x64_b78ba2c94a6c18007e94127cbec2b0c35115f49f.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
2018-11-27 07:31:50, Info                  DISM   DISM Package Manager: PID=3136 TID=2524 Package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7 with CBS state 0(CbsInstallStateAbsent) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) - CDISMPackage::LogInstallStateMapping
2018-11-27 07:31:50, Error                 DISM   DISM Package Manager: PID=3136 TID=2524 The package Package_for_RollupFix is not applicable to the image. - CPackageManagerCLIHandler::Private_ProcessPackageChange
2018-11-27 07:31:50, Info                  DISM   DISM Package Manager: PID=3136 TID=2524 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
2018-11-27 07:31:51, Info                  DISM   DISM Package Manager: PID=3136 TID=2524 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
2018-11-27 07:31:51, Info                  DISM   DISM Package Manager: PID=3136 TID=936  Error in operation: the package is not applicable. (CBS HRESULT=0x800f081e) - CCbsConUIHandler::Error

The CBS.log shows:

2018-11-27 07:31:47, Info                  CBS    Opened cabinet package, package directory: \\?\C:\TEMP\, sandbox location: \\?\C:\TEMP\8095974B-C1B2-496F-9D8C-CA950F4CBCC5\, cabinet location: \\?\C:\TEMP\windows10.0-kb4462917-x64_b78ba2c94a6c18007e94127cbec2b0c35115f49f.cab, manifest location: \\?\C:\TEMP\8095974B-C1B2-496F-9D8C-CA950F4CBCC5\update.mum

2018-11-27 07:31:50, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-11-27 07:31:50, Info                  CBS    Appl: detect Parent, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, Parent: Package_for_KB4132216~31bf3856ad364e35~amd64~~10.0.1.0, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2018-11-27 07:31:50, Info                  CBS    Appl: detectParent: no parent found, go absent
2018-11-27 07:31:50, Info                  CBS    Appl: Evaluating package applicability for package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, applicable state: Absent

2018-11-27 07:31:51, Info                  CBS    Exec: Processing started.  Client: DISM Package Manager Provider, Session: 30705078_1211498541, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7
2018-11-27 07:31:51, Info                  CBS    Exec: Using execution sequence: 20
2018-11-27 07:31:51, Info                  CBS    Reboot mark set
2018-11-27 07:31:51, Info                  CBS    Winlogon: Registering for CreateSession notifications
2018-11-27 07:31:51, Info                  CBS    Winlogon: Loading SysNotify DLL
2018-11-27 07:31:51, Info                  CBS    Winlogon: Starting notify server
2018-11-27 07:31:51, Info                  CBS    Disabling LKG boot option
2018-11-27 07:31:51, Info                  CBS    Exec: Creating restore point: Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, current: Absent, targeted: Absent
2018-11-27 07:31:51, Info                  CBS    Restore point type: Install
2018-11-27 07:31:51, Info                  CBS    Perf: Begin: nested restore point - begin
2018-11-27 07:31:51, Info                  CBS    Failed setting restore point [HRESULT = 0x80070422 - ERROR_SERVICE_DISABLED]
2018-11-27 07:31:51, Info                  CBS    Exec: Begin: nested restore point - failed, ignoring and continuing. [HRESULT = 0x80070422 - ERROR_SERVICE_DISABLED]
2018-11-27 07:31:51, Info                  CBS    Appl: detect Parent, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, Parent: Package_for_KB4132216~31bf3856ad364e35~amd64~~10.0.1.0, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2018-11-27 07:31:51, Info                  CBS    Appl: detectParent: no parent found, go absent
2018-11-27 07:31:51, Info                  CBS    Appl: Evaluating package applicability for package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, applicable state: Absent
2018-11-27 07:31:51, Info                  CBS    Plan: Skipping package since its start state and target state are both absent for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7, current: Absent, pending: Default, start: Absent, applicable: Absent, targeted: Absent, limit: Installed
2018-11-27 07:31:51, Info                  CBS    Perf: Entering stage: Planning
2018-11-27 07:31:51, Info                  CBS    FLOW: Entering stage: Planning
2018-11-27 07:31:51, Info                  CBS    Exec: Single phase execution, there's no package planned, skip the rest of execution
2018-11-27 07:31:51, Info                  CBS    Reboot mark cleared
2018-11-27 07:31:51, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2018-11-27 07:31:51, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2018-11-27 07:31:51, Info                  CBS    Enabling LKG boot option
2018-11-27 07:31:51, Info                  CBS    Exec: Processing complete.  Session: 30705078_1211498541, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2551.1.7 [HRESULT = 0x00000000 - S_OK]
2018-11-27 07:31:51, Info                  CBS    Session: 30705078_1211498541 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]

[Chen_HPDM]

Hi Mike,

This is the command that HPDM is using to install the windows update

DISM.exe /Online /Add-Package /PackagePath:"%__PACKAGE_LOCAL_PATH__%" /NoRestart

Can you please try install it manually on the thin client to see the error message? I don't have the image by side to check but the error usually indicate there are some depencies before installing the package.

[MikeW1927]

Hi Chen

On the device I ran a Command Prompt as local Admin, Winver says Version 1607 (OS Build 14393.1715) with the "Windows 10 Enterprise 2016 LTSB" trademark banner.

I mapped a drive to the repository and copied the update CAB to C:\TEMP, and manually ran the DISM command from C:\TEMP,

The error is exactly the same as per the HP DM task log (previous error message), and aligns with the DISM and CBS log.

Error: 0x800f081e

The specified package is not applicable to this image

The error comes back relatively quickly (inside of 30 seconds). There is no other significant information shown about any pre-requisites or such. 

My colleague and I suspect the factory image is not up to date enough to install the further update. And the client cannot update itself perhaps as Microsoft intended because A) Windows Update service is disabled (presumably out of the factory image as we have not disabled it to our knowledge) and B) there is no direct Internet access anyway in our case.

There is definitely no UPDATE.SES in the CAB file. Maybe the CAB file format is newer, and the Servicing Stack is not up to date enough.

2018-11-27 07:48:54, Info                  CBS    Loaded Servicing Stack v10.0.14393.1051 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.1051_none_7f2bf7ea21d201b2\cbscore.dll
2018-11-27 07:48:54, Info                  CBS    NonStart: Set pending store consistency check.
2018-11-27 07:48:54, Info                  CBS    Session: 30705080_2922312335 initialized by client LanguageFeaturesOnDemand, external staging directory: (null), external registry directory: (null
2018-11-27 07:48:54, Info                  CBS    Failed to get services collection [HRESULT = 0x80070422 - ERROR_SERVICE_DISABLED]
2018-11-27 07:48:54, Info                  CBS    Failed to get windows update server configuration. [HRESULT = 0x80070422 - ERROR_SERVICE_DISABLED]
2018-11-27 07:48:54, Info                  CBS    DWLD: Failed to begin WU search [HRESULT = 0x80070422 - ERROR_SERVICE_DISABLED]
2018-11-27 07:48:54, Info                  CBS    Failed to search Windows update [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]
2018-11-27 07:48:54, Info                  CBS    Failed to enumerate cloud capabilities [HRESULT = 0x800f0906 - CBS_E_DOWNLOAD_FAILURE]

[Chen_HPDM]

Sorry Mike that I don't have much experience on the windows operating system.

If the package is not installable manually on the client side, then I'm sorry that there is nothing HPDM can do.

I would suggest you raise a case to support team in your region and let them to provide a fix.

[MikeW1927]

I found the release notes for KB4462917 and they suggest the missing dependency is KB4132216 which is indeed an update for the Servicing Stack.

I downloaded the KB4132216 .msu file, and made a package for deploying (it requires Windows Update service to be enabled, in order to install KB4132216 using WUSA.EXE command line), and right now I'm trying to test it.

NB: The 603 factory image imported from HP Update Center - the image I deployed - it is not the best.

A) the Write Filter disabled B) The File Exclusion list is blank. C) The HP Write Filter is well out of date (1.0.16).

If the Write Filter is then enabled, the HP DM Agent "cached task" functionality is broken for deploying the October 2018 update because the update is 1.4GB and the Overlay is only 1GB.

Upgrading to the latest fails because "a deprecated version of this product is installed" and "uninstall the current version first". I have to manually uninstall. Then reinstalling the latest Write Filter from Update Center works.

[MaDDeRHaTTeR]

Please tell me how to do this!! I am no where near as computer literate as you are

! But I am a pretty quick study, and a suitable enough tinkerer to figure out when I am on the right track to fixing issues as best I can! I have this ... that led me to your post here... I see HP couldn't even help you... Please show me how you fixed yours!:

CBS Exec: Processing complete, session(Corruption Detecting): 30757487_1247916451 [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Try to wake up thread for execution: 15620
2019-08-14 00:49:08, Info CBS Session: 30757487_1247916451 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Thread ready for execution: 15620
2019-08-14 00:49:08, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30757487_2127541166
2019-08-14 00:49:08, Info CBS Reboot mark set
2019-08-14 00:49:08, Info CBS Winlogon: Registering for CreateSession notifications
2019-08-14 00:49:08, Info CBS FLOW: Entering stage: CheckCbs
2019-08-14 00:49:08, Info CSI 0000127b Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127c Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127d Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127e Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127f Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001280 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001281 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001282 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001283 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001284 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001285 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001286 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001287 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001288 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001289 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000128a Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000128b

Expected: {l:32 ml:33 b:ae595236832a3884d2aa3f913454ac6ff4c735f55e819c7f391c94b653281f92}.
Actual: {l:32 b:dd2decdbc6ec0357ddbd952ad3c29c0a05fc7368badb377648bb8f0964eedeec}.
2019-08-14 00:48:54, Info CSI 0000000a Warning: Unable to repair payload file ([l:19]'MSFT_MpThreat.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2019-08-14 00:48:54, Info CSI 0000000b Hashes for file member [l:26]'MSFT_MpThreatCatalog.cdxml' do not match.
Expected: {l:32 ml:33 b:106d459542c3ec7dd9b7e545d74a4a98f0ad74c7db6a1333cfcd9168e2a3c076}.
Actual: {l:32 b:ff8bbde3d74745abc4b8bef6278c46bd9bba05c2e61f0eb033787443cde80f44}.
2019-08-14 00:48:54, Info CSI 0000000c Warning: Unable to repair payload file ([l:26]'MSFT_MpThreatCatalog.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2019-08-14 00:48:54, Info CSI 0000000d Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
2019-08-14 00:48:54, Info CSI 0000000e Warning: Unable to repair payload file ([l:28]'MSFT_MpThreatDetection.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2019-08-14 00:48:54, Info CSI 0000000f Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
2019-08-14 00:48:54, Info CSI 00000010 Warning: Unable to repair payload file ([l:23]'MSFT_MpPreference.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2019-08-14 00:49:07, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2019-08-14 00:49:07, Info CBS Count of times corruption detected: 1
2019-08-14 00:49:07, Info CBS Failed to delete current corruption first found value. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-08-14 00:49:07, Info CBS Failed getting last corruption first found time [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-08-14 00:49:07, Info CBS Seconds between initial corruption detections: -1
2019-08-14 00:49:07, Info CBS Seconds between corruption and repair: -1
2019-08-14 00:49:08, Info CBS Reboot mark cleared
2019-08-14 00:49:08, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-08-14 00:49:08, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-08-14 00:49:08, Info CBS Exec: Processing complete, session(Corruption Detecting): 30757487_1247916451 [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Try to wake up thread for execution: 15620
2019-08-14 00:49:08, Info CBS Session: 30757487_1247916451 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Thread ready for execution: 15620
2019-08-14 00:49:08, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30757487_2127541166
2019-08-14 00:49:08, Info CBS Reboot mark set
2019-08-14 00:49:08, Info CBS Winlogon: Registering for CreateSession notifications
2019-08-14 00:49:08, Info CBS FLOW: Entering stage: CheckCbs
2019-08-14 00:49:08, Info CSI 0000127b Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127c Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127d Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127e Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127f Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001280 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001281 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001282 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001283 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001284 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001285 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001286 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001287 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001288 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001289 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000128a Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000128b

CBS Appl: detect Parent, Package: Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.1, Parent: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.1, state: Staged
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.239, state: Staged
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.267, state: Staged
2019-08-13 18:37:02, Info CBS Appl: Evaluating package applicability for package Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.1, applicable state: Staged
2019-08-13 18:37:02, Info CBS FOD: Package found on the server, but not applicable to the system: \\?\C:\WINDOWS\Servicing\InboxFodMetadataCache\metadata\Rsat.FailoverCluster.Management.Tools~~1.0.mum
2019-08-13 18:37:02,

I got this by Running sfc scan.... I can see the language similarity between your case and mine... mind you I am CLUELESS as to what ANY of this means... 😞