Windows 10 Pro 64-Bit-Version 1607 kann KB3176938 mit 0x800F0922 nicht installieren

Windows 10 Pro 64-Bit-Version 1607 kann KB3176938 mit 0x800F0922 nicht installieren

Dies ist also ein Windows 10 Pro 64-Bit-System, Version 1607, Insider Edition, auf einem langsamen Ring. Vor einigen Tagen traten wiederholt KB3176934dieselben Fehler 0x800F0922auf. Ich habe die Grundursache und die Vorgehensweise zur Vermeidung nicht herausgefunden. Mein Ziel ist es, andere zu finden, die genau dasselbe Problem haben, und eine Lösung zu finden. Wenn jemand bereits eine Lösung hat – umso besser.

Wenn ich mir das CBS-Verzeichnis vom 26.08.2016 anschaue, als der KB3176934Fehler auftrat, sehe ich eine 22 GB (!) große Protokolldatei. Es scheint, als ob es „irgendeinen“ Deadlock gegeben hätte:

...
2016-08-26 20:18:37, Info                  CBS    Session: 30539793_3012262845 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2016-08-26 20:18:37, Info                  CBS    Opened cabinet package, package directory: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\, sandbox location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\, cabinet location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\Windows10.0-KB3176934-x64-EXPRESS.cab, manifest location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\update.mum
2016-08-26 20:18:37, Info                  DPX    Started DPX phase: Resume and Download Job
2016-08-26 20:18:37, Info                  DPX    Started DPX phase: Apply Deltas Provided In File
2016-08-26 20:18:37, Info                  DPX    Ended DPX phase: Apply Deltas Provided In File
2016-08-26 20:18:37, Info                  DPX    Started DPX phase: Apply Deltas Provided In File
2016-08-26 20:18:37, Info                  DPX    Ended DPX phase: Apply Deltas Provided In File
2016-08-26 20:18:37, Info                  DPX    CJob::Resume completed with status: 0x0
2016-08-26 20:18:37, Info                  DPX    Ended DPX phase: Resume and Download Job
2016-08-26 20:18:37, Info                  CBS    Exec: Asynchrous operation, session completes later
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsSession, level: 66, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsSession, level: 66, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsSession, level: 66, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
2016-08-26 20:18:37, Info                  CBS    Lock: Error found, inverse lock order, current lock held: CCbsExecutionCommunication, level: 130, lock attempted: CCbsWorkerQueue,  level: 60. This will lead to a potential deadlock
...

Dies dauert über eine Stunde und beansprucht 22 GB – das ist mal ein kleiner Deadlock!

Weiter zum 30.08.2016:

...
2016-08-30 15:16:03, Info                  CBS    Opened cabinet package, package directory: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\, sandbox location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\, cabinet location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\Windows10.0-KB3176934-x64-EXPRESS.cab, manifest location: \\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\update.mum
2016-08-30 15:16:03, Info                  DPX    Started DPX phase: Resume and Download Job
2016-08-30 15:16:03, Info                  DPX    Started DPX phase: Apply Deltas Provided In File
2016-08-30 15:16:03, Info                  DPX    Ended DPX phase: Apply Deltas Provided In File
2016-08-30 15:16:03, Info                  DPX    CJob::Resume completed with status: 0x0
2016-08-30 15:16:03, Info                  DPX    Ended DPX phase: Resume and Download Job
2016-08-30 15:16:03, Info                  DPX    Extraction of file: update.ses failed because it is not present in the container (\\?\C:\WINDOWS\SoftwareDistribution\Download\3717a62e3772d26d381fa9aea49eed42\Windows10.0-KB3176934-x64-EXPRESS.cab).
2016-08-30 15:16:03, Info                  DPX    DpxException hr=0x80070002 code=0x020109

30.08.2016 15:16:03, Info CBS Datei zum Extrahieren nicht möglich: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND] 30.08.2016 15:16:03, Info DPX DPX-Phase gestartet: Job fortsetzen und herunterladen

...passiert mehrmals und...

...
2016-09-01 19:28:39, Info                  CBS    SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2016-09-01 19:28:39, Info                  CBS    Reporting package change completion for package: Package_for_KB3189031~31bf3856ad364e35~amd64~~10.0.1.0, current: Installed, original: Absent, target: Installed, status: 0x0, failure source: Not Applicable, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 93, first merged sequence: 93, pending decision: PendingAvoided_DelayQueueSideStepped, primitive execution context: Interactive Flight: False
2016-09-01 19:28:39, Info                  CBS    The store corruption status report is incomplete. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-01 19:28:39, Info                  CBS    SQM: Package change report datapoints not populated because SQM is not initialized or not running online.
2016-09-01 19:28:39, Info                  CBS    FinalCommitPackagesState: Completed persisting state of packages
...

eine ganze Menge davon:

...
2016-09-02 14:07:33, Info                  CSI    000006cf    One of the components setting this value is Microsoft-Windows-shell32, version 10.0.14393.103, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2016-09-02 14:07:33, Info                  CSI    000006d0    Previously seen component setting this value is Microsoft-Windows-shell32, version 10.0.14393.103, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2016-09-02 14:07:33, Info                  CSI    000006d1 Warning - Overlap: Registry value collision found under key \REGISTRY\MACHINE\SOFTWARE\Classes\AllSyncRootObjects\shell\ErrorResolution\ for MultiSelectModel, only one component should set this value
...

Dies ist vielleicht nicht kritisch:

...
2016-09-02 14:07:58, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 0 out of 0. Percent progress: 10.
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 7, phase: 2, result 0, inf: input.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 8, phase: 2, result 0, inf: stornvme.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 9, phase: 2, result 0, inf: usbvideo.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 0, phase: 3, result 0, inf: acpi.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 1, phase: 3, result 0, inf: wnetvsc.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 2, phase: 3, result 0, inf: wstorvsp.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 3, phase: 3, result 0, inf: wvpcivsp.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 4, phase: 3, result 0, inf: BthLEEnum.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 5, phase: 3, result 0, inf: bth.inf
2016-09-02 14:07:58, Info                  CBS            INSTALL index: 6, phase: 3, result 0, inf: xinputhid.inf
2016-09-02 14:07:59, Info                  CBS            INSTALL index: 7, phase: 3, result 0, inf: input.inf
2016-09-02 14:07:59, Info                  CBS            INSTALL index: 8, phase: 3, result 0, inf: stornvme.inf
2016-09-02 14:07:59, Info                  CBS            INSTALL index: 9, phase: 3, result 0, inf: usbvideo.inf
2016-09-02 14:07:59, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070bc2 - ERROR_SUCCESS_REBOOT_REQUIRED]
2016-09-02 14:07:59, Info                  CBS    Doqe: System reboot required.
2016-09-02 14:07:59, Info                  CBS    Perf: Doqe: Install ended.
2016-09-02 14:07:59, Info                  CBS    Shtd: Non-critical driver operations completed successfully.
...

Ich probiere ein Sid aus S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139, das in meinem System nicht vorhanden ist. Und wir sind beim Schreiben von WER, das anscheinend selbst Probleme hat:

...
2016-09-02 14:09:01, Info                  CSI    000002f4 Performing HKCU for sid: S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139
2016-09-02 14:09:01, Error                 CSI    000002f5 (F) STATUS_OBJECT_NAME_NOT_FOUND #72233# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x46f1fbe60->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[78]'\Registry\USER\S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1864350776)[gle=0xd0000034]
2016-09-02 14:09:01, Error                 CSI    000002f6@2016/9/2:21:09:01.262 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(5238): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null) [gle=0x80004005]
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160830221525.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160827053046.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160827031613.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160826035948.cab to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160826022443.cab to WER report.
2016-09-02 14:09:01, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2016-09-02 14:09:01, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-02 14:09:01, Error                 CSI    000002f7 (F) STATUS_OBJECT_NAME_NOT_FOUND #72232# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x46f1fbe60->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[78]'\Registry\USER\S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 1864351756 [gle=0xd0000034]
2016-09-02 14:09:01, Error                 CSI    000002f8@2016/9/2:21:09:01.684 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(5238): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null)[gle=0x80004005]
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160830221525.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160827053046.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160827031613.log to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160826035948.cab to WER report.
2016-09-02 14:09:01, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20160826022443.cab to WER report.
2016-09-02 14:09:01, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2016-09-02 14:09:01, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
...

anscheinend führt das Fehlen dieser Angabe sidzum Absturz des Installationsprogramms, was sich im endgültigen Fehlercode in den Ereignisprotokollen widerspiegelt: 0x800f0922 - CBS_E_INSTALLERS_FAILED:

...
2016-09-02 14:13:05, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
2016-09-02 14:13:05, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed
2016-09-02 14:13:05, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagAdvancedInstallersFailed, SubStage: 0
2016-09-02 14:13:05, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
...

Bei der letzten Version KB3176938sehe ich dann ähnliche Fehler:

...
2016-09-02 16:15:33, Info                  DPX    Extraction of file: update.ses failed because it is not present in the container (\\?\C:\WINDOWS\SoftwareDistribution\Download\7dab6589581c4510df5e184be35f7c59\Windows10.0-KB3176938-x64-EXPRESS.cab).
2016-09-02 16:15:33, Info                  DPX    DpxException hr=0x80070002 code=0x020109
2016-09-02 16:15:33, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2016-09-02 16:15:34, Info                  DPX    Started DPX phase: Resume and Download Job
...

Verrücktheit

...
2016-09-02 19:05:26, Info                  CSI    000006d1 Warning - Overlap: Registry value collision found under key \REGISTRY\MACHINE\SOFTWARE\Classes\AllSyncRootObjects\shell\ErrorResolution\ for MultiSelectModel, only one component should set this value

2016-09-02 19:05:26, Info                  CSI    000006d2    One of the components setting this value is Microsoft-Windows-shell32, version 10.0.14393.103, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2016-09-02 19:05:26, Info                  CSI    000006d3    Previously seen component setting this value is Microsoft-Windows-shell32, version 10.0.14393.103, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35}
...

Gleicher nicht kritischer Fahrerunfall:

...
2016-09-02 19:05:39, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 0 out of 0. Percent progress: 11.
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 9, phase: 2, result 0, inf: usbvideo.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 0, phase: 3, result 0, inf: acpi.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 1, phase: 3, result 0, inf: wnetvsc.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 2, phase: 3, result 0, inf: wstorvsp.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 3, phase: 3, result 0, inf: wvpcivsp.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 4, phase: 3, result 0, inf: BthLEEnum.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 5, phase: 3, result 0, inf: bth.inf
2016-09-02 19:05:39, Info                  CBS            INSTALL index: 6, phase: 3, result 0, inf: xinputhid.inf
2016-09-02 19:05:40, Info                  CBS            INSTALL index: 7, phase: 3, result 0, inf: input.inf
2016-09-02 19:05:40, Info                  CBS            INSTALL index: 8, phase: 3, result 0, inf: stornvme.inf
2016-09-02 19:05:40, Info                  CBS            INSTALL index: 9, phase: 3, result 0, inf: usbvideo.inf
2016-09-02 19:05:40, Info                  CBS    DriverUpdateInstallUpdates failed [HRESULT = 0x80070bc2 - ERROR_SUCCESS_REBOOT_REQUIRED]
2016-09-02 19:05:40, Info                  CBS    Doqe: System reboot required.
2016-09-02 19:05:40, Info                  CBS    Perf: Doqe: Install ended.
2016-09-02 19:05:40, Info                  CBS    Shtd: Non-critical driver operations completed successfully.
...

Es scheint, als ob das Fehlen davon erneut sidden Rollback verursacht:

...
2016-09-02 19:06:43, Info                  CSI    000002f4 Performing HKCU for sid: S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139
2016-09-02 19:06:43, Error                 CSI    000002f5 (F) STATUS_OBJECT_NAME_NOT_FOUND #72233# from Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey(flg = (AllowAccessDenied), key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0x649a27c4f0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[78]'\Registry\USER\S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139'; a:(OBJ_CASE_INSENSITIVE)}, disp = Unmapped disposition: 2586297032)[gle=0xd0000034]
2016-09-02 19:06:43, Error                 CSI    000002f6@2016/9/3:02:06:43.692 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(5238): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectRegistryProvider::SysOpenKey expression: (null) [gle=0x80004005]
...

Der Schlüssel liegt also möglicherweise im sid S-1-5-80-1448039036-2013904622-3830678473-3382385916-2632875139, aber ich kann bei Websuchen nichts darüber finden.

Die Protokolldateien (CBS.zip): https://onedrive.live.com/?id=23A52F09515EBE7%216609&cid=023A52F09515EBE7

Systeminfo


Habe das Anniversary Update ( Windows10Upgrade28084.exe) heruntergeladen, es wird jedoch nur ein leeres Dialogfeld mit einer Schaltfläche „Beenden“ angezeigt.

Bildbeschreibung hier eingeben

Vielleicht liegt das Problem darin, dass es KB3176938sich immer in der Phase „Installiert und Neustart erforderlich“ befindet, sodass ich keine anderen Dinge installieren kann? Nur eine Vermutung …

Versuch, die Installation von KB3176938 zu erzwingen, nachdem die CABDatei manuell heruntergeladen wurde.


Auch die manuelle Installation von KB3176938 aus einem manuell heruntergeladenen Cabinet war nicht erfolgreich. Ich dachte darüber nach, die Installation vielleicht im abgesicherten Modus zu starten, aber der Fehler tritt erst am Ende des Installationsvorgangs auf, der Computer wurde neu gestartet und war wieder bei fast 100 %. Ich habe das Gefühl, ich befinde mich in einer Zwickmühle. Zuerst möchte ich verhindern, dass Windows Update dieses Update erzwingt.


Siehe Antwort. Nach der Reparatur Windows10_InsiderPreview_Client_x64_en-us_14393.isohabe ich KB3176934 und ein paar weitere Updates bekommen. Scheint jetzt gut zu funktionieren. Rückblickend habe ich vielleicht irgendwann das Jubiläumsupdate gemacht (oder das System hat es angeboten?)? Vielleicht ist das keine gute Idee für ein Insider Win10.

Antwort1

Die letzte Möglichkeit, ein Windows zu reparieren, heißtReparaturinstallation/Inplace-Upgrade.

Laden Sie die ISO-Datei 1607 herunter, mounten Sie die ISO-Datei per Doppelklick auf die ISO-Datei. Navigieren Sie nun zum virtuellen DVD-Laufwerk, führen Sie es aus setup.exeund wählen Sie, ob alle Anwendungen/Einstellungen beibehalten werden sollen.

Bildbeschreibung hier eingeben

Dadurch wird Windows repariert und das Problem sollte behoben sein.

verwandte Informationen