Windows 10 Ошибка обновления Ошибка 0x8000ffff - PullRequest
Новая
       56

Windows 10 Ошибка обновления Ошибка 0x8000ffff

0 голосов
/ 11 апреля 2020

Я пытался перевести мою систему в состояние, при котором она будет обновляться автоматически без ошибок.

Windows Обновление в настоящее время отчетов: 2020-02 Накопительное обновление для. NET Framework 3.5 и 4.8 для Windows 10 Версия 1903 для x64 (KB4534132) - Ошибка 0x8000ffff
2020-03 Накопительное обновление для Windows 10 Версия 1903 для систем на базе x64 (KB4551762) - Ошибка 0x8000ffff

Кажется, что следующая перезагрузка чтобы выполнить откат и дальнейшую перезагрузку.

Я потратил время, пытаясь решить эту проблему, используя различные онлайновые ресурсы, которые включают советы по проверке устройств с помощью диспетчера устройств, Windows настройки магазина и другие. Я провел некоторое время, бродя по журналам событий; но это помогает, если вы знаете, а) где искать и; б) что вы ищете.

Я нашел Страницы разрешения Microsoft , которые привели меня к SetupDiag , который сообщил мне, что мое последнее обновление прошло успешно:
Примечание : Обновление «Накопительное обновление для Windows 10 версии 1903» было перезапущено до запуска SetupDiag, чтобы убедиться, что у меня произошла ошибка fre sh, а не после перезагрузки / отката. 

SetupDiag v1.6.0.0
Copyright (©) Microsoft Corporation. All rights reserved.

Searching for setup logs...
Found C:\Windows\Panther\setupact.log with update date 24/09/2019 21:16:40 to be the correct setup log.

Gathering baseline information from setup logs...

SetupDiag: processing rule: CompatScanOnly.
...No match.


SetupDiag: processing rule: PlugInComplianceBlock.
...No match.


SetupDiag: processing rule: BitLockerHardblock.
...No match.


SetupDiag: processing rule: VHDHardblock.
...No match.


SetupDiag: processing rule: PortableWorkspaceHardblock.
...No match.


SetupDiag: processing rule: AuditModeHardblock.
...No match.


SetupDiag: processing rule: SafeModeHardblock.
...No match.


SetupDiag: processing rule: InsufficientSystemPartitionDiskSpaceHardblock.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationAutoUninstall.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationDismissable.
...No match.


SetupDiag: processing rule: CompatBlockedApplicationManualUninstall.
...No match.


SetupDiag: processing rule: HardblockDeviceOrDriver.
...No match.


SetupDiag: processing rule: HardblockMismatchedLanguage.
..No match.


SetupDiag: processing rule: HardblockFlightSigning.
..No match.


SetupDiag: processing rule: DiskSpaceBlockInDownLevel.
..No match.


SetupDiag: processing rule: DiskSpaceFailure.
..No match.


SetupDiag: processing rule: PreReleaseWimMountDriverFound.
..No match.


SetupDiag: processing rule: DeviceInstallHang.
...No match.


SetupDiag: processing rule: BootFailureDetected.
.No match.


SetupDiag: processing rule: WinSetupBootFilterFailure.
.No match.


SetupDiag: processing rule: FindDebugInfoFromRollbackLog.
.No match.


SetupDiag: processing rule: AdvancedInstallerFailed.
..No match.


SetupDiag: processing rule: AdvancedInstallerGenericFailure.
..No match.


SetupDiag: processing rule: FindMigApplyUnitFailure.
..No match.


SetupDiag: processing rule: FindMigGatherUnitFailure.
...No match.


SetupDiag: processing rule: FindMigGatherApplyFailure.
..No match.


SetupDiag: processing rule: OptionalComponentFailedToGetOCsFromPackage.
..No match.


SetupDiag: processing rule: OptionalComponentOpenPackageFailed.
..No match.


SetupDiag: processing rule: OptionalComponentInitCBSSessionFailed.
..No match.


SetupDiag: processing rule: CriticalSafeOSDUFailure.
..No match.


SetupDiag: processing rule: UserProfileCreationFailureDuringOnlineApply.
..No match.


SetupDiag: processing rule: UserProfileCreationFailureDuringFinalize.
..No match.


SetupDiag: processing rule: WimMountFailure.
..No match.


SetupDiag: processing rule: WimMountDriverIssue.
..No match.


SetupDiag: processing rule: WimApplyExtractFailure.
..No match.


SetupDiag: processing rule: UpdateAgentExpanderFailure.
.No match.


SetupDiag: processing rule: FindFatalPluginFailure.
...No match.


SetupDiag: processing rule: MigrationAbortedDueToPluginFailure.
...No match.


SetupDiag: processing rule: DISMAddPackageFailed.
..No match.


SetupDiag: processing rule: DISMImageSessionFailure.
..No match.


SetupDiag: processing rule: DISMproviderFailure.
..No match.


SetupDiag: processing rule: SysPrepLaunchModuleFailure.
..No match.


SetupDiag: processing rule: UserProvidedDriverInjectionFailure.
..No match.


SetupDiag: processing rule: FindSuccessfulUpgrade.
..
SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

SetupDiag found 1 matching issue.

SetupDiag results were logged to: .\SetupDiagResults.log
Logs ZipFile created at: .\Logs_2.zip

Это меня обмануло, обновление «Накопительное обновление для Windows 10 версии 1903», по-видимому, не создало журнал - или, если это так, не там, где SetupDiag ищет в C: \ Windows \ Panther \ setupact.log. Журнал SetupDiag содержит: 

Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-TRUNCATED
SetupDiag version: 1.6.0.0
System Information:
    Machine Name = NONAME
    Manufacturer = To Be Filled By O.E.M.
    Model = To Be Filled By O.E.M.
    HostOSArchitecture = x64
    FirmwareType = PCAT
    BiosReleaseDate = 20160329000000.000000+000
    BiosVendor = BIOS Date: 03/29/16 19:52:49 Ver: 04.06.05
    BiosVersion = P1.80
    HostOSVersion = 10.0.17134
    HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
    TargetOSBuildString = 10.0.18362.323 (19h1_release_svc_prod2.190809-2149)
    HostOSLanguageId = 
    HostOSEdition = Professional
    RegisteredAV = Windows Defender
    FilterDrivers = FileInfo
    UpgradeStartTime = 17/09/2019 11:05:04
    UpgradeEndTime = 24/09/2019 21:16:40
    UpgradeElapsedTime = 7.10:11:36
    CV = QZdr+diQKEOvuNto
    ReportId = WITHHELD


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
    Phase Started: 24/09/2019 21:13:48
    Phase Ended: 24/09/2019 21:13:48
    Phase Time Delta: 00:00:00
    Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
    Operation Started: 24/09/2019 21:13:36
    Operation Ended: 24/09/2019 21:13:40
    Operation Time Delta: 0:00:00:04.0000000
    Completed Successfully? True


Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-TRUNCATED
SetupDiag version: 1.6.0.0
System Information:
    Machine Name = NONAME
    Manufacturer = To Be Filled By O.E.M.
    Model = To Be Filled By O.E.M.
    HostOSArchitecture = 1033
    FirmwareType = PCAT
    BiosReleaseDate = 20160329000000.000000+000
    BiosVendor = BIOS Date: 03/29/16 19:52:49 Ver: 04.06.05
    BiosVersion = P1.80
    HostOSVersion = 10.0.17134
    HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
    TargetOSBuildString = 10.0.18362.323 (19h1_release_svc_prod2.190809-2149)
    HostOSLanguageId = 
    HostOSEdition = Professional
    RegisteredAV = Windows Defender
    FilterDrivers = FileInfo
    UpgradeStartTime = 17/09/2019 11:05:04
    UpgradeEndTime = 24/09/2019 21:16:40
    UpgradeElapsedTime = 7.10:11:36
    CV = QZdr+diQKEOvuNto
    ReportId = WITHHELD


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
    Phase Started: 24/09/2019 21:13:48
    Phase Ended: 24/09/2019 21:13:48
    Phase Time Delta: 00:00:00
    Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
    Operation Started: 24/09/2019 21:13:36
    Operation Ended: 24/09/2019 21:13:40
    Operation Time Delta: 0:00:00:04.0000000
    Completed Successfully? True


Matching Profile found: FindSuccessfulUpgrade - 8A0824C8-TRUNCATED
SetupDiag version: 1.6.0.0
System Information:
    Machine Name = NONAME
    Manufacturer = To Be Filled By O.E.M.
    Model = To Be Filled By O.E.M.
    HostOSArchitecture = 1033
    FirmwareType = PCAT
    BiosReleaseDate = 20160329000000.000000+000
    BiosVendor = BIOS Date: 03/29/16 19:52:49 Ver: 04.06.05
    BiosVersion = P1.80
    HostOSVersion = 10.0.17134
    HostOSBuildString = 17134.1.amd64fre.rs4_release.180410-1804
    TargetOSBuildString = 
    HostOSLanguageId = 
    HostOSEdition = Professional
    RegisteredAV = Windows Defender
    FilterDrivers = FileInfo
    UpgradeStartTime = 17/09/2019 11:05:04
    UpgradeEndTime = 24/09/2019 21:16:40
    UpgradeElapsedTime = 7.10:11:36
    CV = QZdr+diQKEOvuNto
    ReportId = WITHHELD


SetupDiag reports successful upgrade found.
This appears to be a successful update as the last operation was: OOBEBoot and the result was: success

Last Setup Phase:
Phase Name: End
    Phase Started: 24/09/2019 21:13:48
    Phase Ended: 24/09/2019 21:13:48
    Phase Time Delta: 00:00:00
    Completed Successfully? True


Last Setup Operation:
Operation Name: Start suspended services
    Operation Started: 24/09/2019 21:13:36
    Operation Ended: 24/09/2019 21:13:40
    Operation Time Delta: 0:00:00:04.0000000
    Completed Successfully? True

Справочная информация: у меня произошла ошибка материнской платы, на которую я обратился в декабре прошлого года с новой материнской платой, процессором и оперативной памятью. Я исправил ошибки, помеченные в диспетчере устройств, за исключением ошибок, связанных с ядрами моего процессора AMD Ryzen Это кажется исчезает при работе в безопасном режиме, и я понятия не имею, почему - машина работает нормально. Это может быть красная сельдь, поскольку она не объясняет, почему SetupDiag не находит журнал обновлений - в любом случае, вот он Ryzen error

Буду признателен за помощь в исправлении пожалуйста, эту проблему, или, по крайней мере, то, что я не включил, и вам, возможно, понадобится дать полезное мнение о проблеме и ее решении.

С наилучшими пожеланиями, Пол.

Добро пожаловать на сайт PullRequest, где вы можете задавать вопросы и получать ответы от других членов сообщества.

Похожие темы

...