Hallo,
ich habe nun schon seit einiger Zeit WIN7 - ohne Probleme. Nun habe wird beim Installieren des Updates KB2770660 die Fehlermeldung Code 800B0100 gemeldet, und die Installation des updates wird abgebrochen.
Alle Versuche, den Fehler automatisch zu beheben (fixit Tools) sind leider gescheitert.
Meine Konfiguration: WIN7 Home Premium 32 bit.
Anbei die Ausleitung mit Checksur - damit kann ICH leider nichts anfangen:
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.21645
Package Version 17.0
2013-01-19 18:36
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
(f) CBS MUM Corrupt 0x800F0900 servicing\Packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum Line 1:
(f) CBS Catalog Corrupt 0x800B0100 servicing\Packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
Checking Package Watchlist
Checking Component Watchlist
Checking Packages
Checking Component Store
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.17157_none_78cf33fc1ff8c0da.manifest x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.17157_none_78cf33fc1ff8c0da
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.22150_none_7b382dad36431856.manifest x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.22150_none_7b382dad36431856
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.17989_none_7a974b961d357d2c.manifest x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.17989_none_7a974b961d357d2c
(f) CSI Manifest All Zeros 0x00000000 winsxs\Manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.21360_none_794700bb3924c85b.manifest x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.21360_none_794700bb3924c85b
Summary:
Seconds executed: 965
Found 14 errors
CSI Manifest All Zeros Total count: 4
CBS MUM Corrupt Total count: 5
CBS Catalog Corrupt Total count: 5
Unavailable repair files:
winsxs\manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.17157_none_78cf33fc1ff8c0da.manifest
winsxs\manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.22150_none_7b382dad36431856.manifest
winsxs\manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7601.17989_none_7a974b961d357d2c.manifest
winsxs\manifests\x86_microsoft-windows-directx-directplay8_31bf3856ad364e35_6.1.7600.21360_none_794700bb3924c85b.manifest
servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.mum
servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_1_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_3_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660_RTM~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660_SP1~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
servicing\packages\Package_for_KB2770660~31bf3856ad364e35~x86~~6.1.1.0.cat
Habt ihr eine Idee, wie ich diesen Fehler beheben kann ?
Vielen Dank im voraus,
Frodo66