[SOLVED] HRESULT: 0x800f0900 in Windows Features, Windowsupdates dont work / Server 2008 R2

PMM

Member
Joined
Apr 11, 2016
Posts
12
Hello @all,

im not able to see any Windowsfeature to install in the windows server manager, HRESULT: 0x800f0900 occures. Also no update is getting installed.


the CheckSUR.log is as follows:

=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-04-07 10:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3023215_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.20758_none_0448172b3dabf26e.manifest amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.20758_none_0448172b3dabf26e
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_18786745aab5b29da8140a4e445cd05d_b03f5f7f11d50a3a_6.1.7601.22970_none_fb4497ab5ede1311.manifest amd64_18786745aab5b29da8140a4e445cd05d_b03f5f7f11d50a3a_6.1.7601.22970_none_fb4497ab5ede1311
(f) CSI Payload File Corrupt 0x00000000 cmiv2.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_0b32a93025b365c1
(f) CSI Payload File Corrupt 0x00000000 wcp.dll x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_0b32a93025b365c1
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_2573c98045703331b4fe23201873e489_b03f5f7f11d50a3a_6.1.7601.18764_none_738a81bf14043582.manifest amd64_2573c98045703331b4fe23201873e489_b03f5f7f11d50a3a_6.1.7601.18764_none_738a81bf14043582
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.23040_de-de_ce239a94f1d040ac.manifest amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.23040_de-de_ce239a94f1d040ac
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.18839_de-de_cdadf82dd8a235be.manifest amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.18839_de-de_cdadf82dd8a235be
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.22970_de-de_109ecbdb229a3fab.manifest msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.22970_de-de_109ecbdb229a3fab
(f) CSI Payload File Corrupt 0x00000000 esscli.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7
(f) CSI Payload File Corrupt 0x00000000 cmitrust.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7
(f) CSI Payload File Corrupt 0x00000000 smiengine.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.18766_none_675144b3de10d6f7
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.18764_de-de_276b175508f42c81.manifest msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.18764_de-de_276b175508f42c81
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16644_none_03c549242489d157.manifest amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16644_none_03c549242489d157
(f) CSI Manifest Failed Catalog Check 0x00000000 winsxs\Manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_9.4.8112.16644_none_92236002293b7df7.manifest wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_9.4.8112.16644_none_92236002293b7df7
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_44c2fa8f476c66c9ea1a22f93f21a3af_b03f5f7f11d50a3a_6.1.7601.22970_none_27f50996ef957cae.manifest amd64_44c2fa8f476c66c9ea1a22f93f21a3af_b03f5f7f11d50a3a_6.1.7601.22970_none_27f50996ef957cae
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_318a3eeb99f83e6a.manifest amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_318a3eeb99f83e6a
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_70686d968ae000ef.manifest msil_system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_70686d968ae000ef
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_599c221ca4861419.manifest msil_system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_599c221ca4861419
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_1abdf371b39e5194.manifest amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_1abdf371b39e5194

Summary:
Seconds executed: 351
Found 28 errors
CSI Manifest All Zeros Total count: 11
CSI Manifest Failed Catalog Check Total count: 3
CSI Payload File Corrupt Total count: 5
CBS MUM Corrupt Total count: 4
CBS Catalog Corrupt Total count: 5

Unavailable repair files:
winsxs\manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.20758_none_0448172b3dabf26e.manifest
winsxs\manifests\amd64_18786745aab5b29da8140a4e445cd05d_b03f5f7f11d50a3a_6.1.7601.22970_none_fb4497ab5ede1311.manifest
winsxs\manifests\amd64_2573c98045703331b4fe23201873e489_b03f5f7f11d50a3a_6.1.7601.18764_none_738a81bf14043582.manifest
winsxs\manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.23040_de-de_ce239a94f1d040ac.manifest
winsxs\manifests\amd64_microsoft-windows-advapi32.resources_31bf3856ad364e35_6.1.7601.18839_de-de_cdadf82dd8a235be.manifest
winsxs\manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.22970_de-de_109ecbdb229a3fab.manifest
winsxs\manifests\msil_system.security.resources_b03f5f7f11d50a3a_6.1.7601.18764_de-de_276b175508f42c81.manifest
winsxs\manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16644_none_03c549242489d157.manifest
winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_9.4.8112.16644_none_92236002293b7df7.manifest
winsxs\manifests\amd64_44c2fa8f476c66c9ea1a22f93f21a3af_b03f5f7f11d50a3a_6.1.7601.22970_none_27f50996ef957cae.manifest
winsxs\manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_318a3eeb99f83e6a.manifest
winsxs\manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.18764_none_70686d968ae000ef.manifest
winsxs\manifests\msil_system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_599c221ca4861419.manifest
winsxs\manifests\amd64_netfx-system.security_b03f5f7f11d50a3a_6.1.7601.22970_none_1abdf371b39e5194.manifest
servicing\packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3023215_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.mum
servicing\packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_1_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_2_for_KB3032655~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_7_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3023215_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
servicing\packages\Package_for_KB3023215~31bf3856ad364e35~amd64~~6.1.1.0.cat



Any idea what to do? BR
 
Hello and welcome

Due to the precise nature of your corruption, you will receive help from a user named CKing123. He's one of our senior trainees here who's in his final phrase of his studies and needs to gain some real world experience in specific areas of Windows Update. This means that he'll be assisting you, but that I will first need to double check and approve his fixes before he posts them to you. If anything this is a good thing for you because it means that you've got at least two of us watching over your thread, but it will unfortunately add a slight delay between each reply. I hope that you understand and can accept the need for us to train up new members in this way in order to carry on doing what we do here, however, if for any reason you object to this setup, I will happily take on your thread myself.

Thank you very much for your understanding. We'll be with you very shortly.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top