我发现一台电脑正在运行 Windows 10 Pro 版本 1709，该版本自 2019/04/09 起已不再受支持，因此我尝试升级它，但一直失败。
尝试通过 Windows 更新升级失败，并出现错误A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install.。
尝试通过安装介质升级失败并出现以下错误：
0x8007001F - 0x20006
The installation failed in the SAFE_OS phase with an error during REPLICATE_OC operation
到目前为止，我已经尝试了所有能在网上找到的方法，甚至更多：
- 确保系统驱动器有足够的可用存储空间。
- 以管理员身份运行 Windows 更新疑难解答，据报道发现并修复了以下问题：
Potential Windows Update Database error detectedWindows Update components must be repairedCheck for pending updates
-
以管理员 身份运行以下命令 ：
3a。3b。3c。3d。3e 。net stop wuauservnet stop bitsren c:\windows\SoftwareDistribution SoftwareDistribution.oldnet start wuauservnet stop bits - 停止 Windows 服务
cryptsvc，将所有文件从%systemroot%\system32\catroot2\移动到%systemroot%\system32\catroot2.old，然后重新启动该服务。 .old-ed 文件夹C:\$WINDOWS.~BT\。- 删除该文件夹
C:\Windows10Upgrade\并重新运行Windows 10更新助手。 以管理员身份运行命令
sfc /scannow，没有报告任何问题：Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection did not find any integrity violations.以管理员身份运行命令
dism /online /cleanup-image /scanhealth，没有报告任何问题：Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.431 [==========================100.0%==========================] No component store corruption detected. The operation completed successfully.以管理员身份运行命令
DISM /online /Cleanup-Image /RestoreHealth，没有报告任何问题：Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.431 [==========================100.0%==========================] The restore operation completed successfully. The operation completed successfully.以管理员身份运行命令
chkdsk /scan，没有报告任何问题：The type of the file system is NTFS. Stage 1: Examining basic file system structure ... 2055168 file records processed. File verification completed. 12866 large file records processed. 0 bad file records processed. Stage 2: Examining file name linkage ... 26874 reparse records processed. 2699910 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered to lost and found. 26874 reparse records processed. Stage 3: Examining security descriptors ... Security descriptor verification completed. 322372 data files processed. CHKDSK is verifying Usn Journal... Usn Journal verification completed. Windows has scanned the file system and found no problems. No further action is required. 233916415 KB total disk space. 185713784 KB in 1632128 files. 724380 KB in 322373 indexes. 0 KB in bad sectors. 2138943 KB in use by the system. 65536 KB occupied by the log file. 45339308 KB available on disk. 4096 bytes in each allocation unit. 58479103 total allocation units on disk. 11334827 allocation units available on disk.下载了 Windows 10 v1909 64 位官方 ISO，安装并运行
setup.exe。- 下载了 Windows 10 v1903 64 位官方 ISO，安装并运行
setup.exe。 - 发现设备驱动程序已是最新的。
- 将 BIOS 固件更新至最新版本。
- 使用记录的方法https://errortools.com/windows/how-to-fix-safe_os-phase-error-during-replicate_oc-operation-error-in-windows-10/
\Windows\System32\mcupdate_GenuineIntel.dll从安装介质中删除文件。
我现在已经没有主意了，带外管理不可用，并且由于冠状病毒/ COVID-19，物理访问存在风险。
有人可以帮忙吗？
更新 2020/05/04 17:05：
回答Ramhound 的评论 #1：
1. 不，所有用户配置文件都单独位于系统驱动器 (C:)。
2. 我从以下位置下载并运行了 SetupDiag v1.6（最新版本）https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag→https://go.microsoft.com/fwlink/?linkid=870142报告内容如下：
Matching Profile found: OptionalComponentOpenPackageFailed - 22952520-EC89-4FBD-94E0-B67DF88347F6
SetupDiag version: 1.6.0.0
System Information:
Machine Name = [REDACTED]
Manufacturer = FUJITSU
Model = ESPRIMO E410
HostOSArchitecture = 2057
FirmwareType = PCAT
BiosReleaseDate = 20150422000000.000000+000
BiosVendor = BIOS Date: 04/22/15 12:46:17 Ver: 04.06.05
BiosVersion = V4.6.5.3 R1.30.0 for D3120-A1x
HostOSVersion = 10.0.16299
HostOSBuildString = 16299.431.amd64fre.rs3_release_svc_escrow.180502-1908
TargetOSBuildString = 10.0.17134.1 (rs4_release.180410-1804)
HostOSLanguageId =
HostOSEdition = Professional
RegisteredAV = Webroot SecureAnywhere
FilterDrivers = FileInfo
UpgradeStartTime = 04/05/2020 10:47:29
UpgradeEndTime = 04/05/2020 12:30:10
UpgradeElapsedTime = 01:42:41
CV = xaR0eqEoHEKd2Og6
ReportId =
Error: SetupDiag reports Optional Component installation failed to open OC Package.
Last Phase: Safe OS
Last Operation: Gather Optional Component status
Package Name: Foundation
Error: 0x8007001F
Refer to "https://support.microsoft.com/en-us/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness" for possible remediation information.
Recommend you check the "Windows Modules Installer" service (Trusted Installer) is started on the system and set to automatic start, reboot and try the update again. Optionally, you can check the status of optional components on the system (search for Windows Features), uninstall any unneeded optional components, reboot and try the update again.
Last Setup Phase:
Phase Name: Safe OS
Phase Started: 04/05/2020 12:30:01
Phase Ended: 01/01/0001 00:00:00
Phase Time Delta: 00:00:00
Completed Successfully? False
Last Setup Operation:
Operation Name: Gather Optional Component status
Operation Started: 04/05/2020 12:30:02
Operation Ended: 01/01/0001 00:00:00
Operation Time Delta: 0:00:00:00.0000000
Completed Successfully? False
有趣的是，我打开appwiz.cpl→Turn Windows features on or off查看安装了哪些可选组件，但它根本没有加载任何东西：
这让我https://support.microsoft.com/en-gb/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness因此我运行了以下 PowerShell 命令：
PS C:\WINDOWS\system32> Dism /Mount-Image /ImageFile:C:\Windows10v1909\sources\boot.wim /index:1 /MountDir:C:\Users\$Env:userName\Desktop\Mount
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Mounting image
[==========================100.0%==========================]
The operation completed successfully.
PS C:\WINDOWS\system32> Dism /Online /Cleanup-Image /RestoreHealth /Source:C:\Users\$Env:userName\Desktop\Mount\windows /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Image Version: 10.0.16299.431
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>
但是，升级到 v1909 也以同样的方式失败了。
回答Ramhound 的评论 #2：我不确定我怎么没碰到那篇帖子在我的研究过程中，但无论如何，我使用我的文件Windows_10_EnglishUK_1803_April2018Update_64bit.iso尝试直接路径升级，但以同样的方式失败：
回答约翰的评论：我尝试使用MediaCreationTool1909.exe→ Upgrade this PC now，但同样失败。
回答JW0914 的评论：
1. 该文件C:\Windows\Logs\CBS\CBS.log包含以下新条目（实际上有~48 行，App1:但我无法全部放进去）：
2020-05-04 15:50:42, Info CBS Failed to find a matching version for servicing stack: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.428_none_1704c21831ffb4a8\ [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-05-04 15:50:42, Info CBS Failed to find servicing stack directory in online store. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2020-05-04 15:50:42, Info CBS Loaded Servicing Stack v10.0.16299.428 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.16299.428_none_1704c21831ffb4a8\cbscore.dll
2020-05-04 15:50:42, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:50:42, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:50:42, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-05-04 15:50:42, Info CBS Session: 30810659_1653900665 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-05-04 15:50:42, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:50:42, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:50:42, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-05-04 15:50:45, Info CBS WU creates the package, AppID:Dynamic Update, UpdateID:{33D6CF13-224E-459B-AD4F-AF8C5E3CC469}, revision: 202
2020-05-04 15:50:45, Info CBS Session: 30810659_1685496589 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-05-04 15:50:46, Info CBS WU creates the package, AppID:Dynamic Update, UpdateID:{CAEF987D-2E08-49D8-8C68-5D6FA9F801E2}, revision: 200
2020-05-04 15:50:46, Info CBS Session: 30810659_1690150083 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
2020-05-04 15:50:46, Info CBS Appl: detect Parent, Package: Package_for_KB4497165~31bf3856ad364e35~amd64~~10.0.4.1, Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.18362.1, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
2020-05-04 15:50:46, Info CBS Appl: detectParent (exact match): Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.18362.1, parent state: Absent
2020-05-04 15:50:46, Info CBS Appl: Evaluating package applicability for package Package_for_KB4497165~31bf3856ad364e35~amd64~~10.0.4.1, applicable state: Absent
2020-05-04 15:52:19, Info CBS Session: 30810659_2621054062 initialized by client Setup360, external staging directory: (null), external registry directory: (null
2020-05-04 15:52:20, Info CBS Session: 30810659_2633102031 initialized by client OCLib, external staging directory: (null), external registry directory: (null
2020-05-04 15:52:20, Info CBS Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:52:20, Info CBS Failed to resolve package from moniker [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:52:20, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:52:20, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-05-04 15:53:00, Info CBS Session: 30810659_3031483361 initialized by client WinMgmt, external staging directory: (null), external registry directory: (null
2020-05-04 15:53:00, Info CBS Not able to find an installed package package from moniker: @Foundation [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:53:00, Info CBS Failed to resolve package from moniker [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:53:00, Info CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2020-05-04 15:53:00, Info CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
2020-05-04 15:55:00, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2020-05-04 15:55:00, Info CBS TiWorker signaled for shutdown, going to exit.
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-05-04 15:55:00, Info CBS Execution Engine Finalize
2020-05-04 15:55:00, Info CBS Execution Engine Finalize
2020-05-04 15:55:00, Info CBS Ending the TiWorker main loop.
2020-05-04 15:55:00, Info CBS Starting TiWorker finalization.
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: ManifestCacheFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2020-05-04 15:55:00, Info CBS CBS Engine already deativated
2020-05-04 15:55:00, Info CBS CBS Engine already deativated
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CoreResourcesUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: SessionManagerFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: WcpUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: DrupUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CfgMgr32Unload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: DpxUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: SrUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CbsEsdUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: CbsEventUnregister
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: AppContainerUnload
2020-05-04 15:55:00, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2020-05-04 15:55:00, Info CBS Ending TiWorker finalization.
2020-05-04 15:55:00, Info CBS Ending the TrustedInstaller main loop.
2020-05-04 15:55:00, Info CBS Starting TrustedInstaller finalization.
2020-05-04 15:55:00, Info CBS Ending TrustedInstaller finalization.
修复错误的建议0x800f0805 - CBS_E_INVALID_PACKAGE似乎是重置我已经尝试过的 Windows 更新组件。
2. 我运行了命令（下面的输出 - 我不确定那 20% 是怎么回事）并再次尝试，但升级以同样的方式失败。
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /StartComponentCleanup
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Image Version: 10.0.16299.431
[=========== 20.0% ]
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Image Version: 10.0.16299.431
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32> SFC /ScanNow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection did not find any integrity violations.
PS C:\WINDOWS\system32>
回答Ramhound 的评论 #3：为了确定 KB3022345 是否已安装，我尝试：
- 运行CMD命令
wmic qfe list brief /format:texttablewsys | find "KB3022345"但是它报告No Instance(s) Available. - 运行 PowerShell 命令
Get-Hotfix但它什么也没有输出。 - 运行 CMD 命令
systeminfo.exe但它输出Hotfix(s): N/A, 以及其他所有内容。 - 用于
regedit.exe搜索所有键、值和数据，KB3022345但未找到任何内容。 按照https://www.sysnative.com/forums/threads/windows-seven-cant-update.30365/post-286650，运行管理 CMD 命令
reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS，该命令已成功完成，然后使用Farbar 恢复扫描工具64 位版本 03-05-2020（最新）搜索注册表，KB3022345输出以下内容：Farbar Recovery Scan Tool (x64) Version: 03-05-2020 Ran by <username> (04-05-2020 16:50:19) Running from C:\Users\<username>\Desktop Boot Mode: Normal ================== Search Registry: "KB3022345" =========== ====== End of Search ======
更新 2020/05/07 15:52：
回答JW0914 的评论：我挂载了我的文件Windows_10_EnglishUK_1909_November2019Update_64bit.iso并运行了推荐的命令，输出以下内容：
PS C:\WINDOWS\system32> DISM /Get-WIMinfo /WIMfile:D:\sources\install.esd
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Details for image : D:\sources\install.esd
Index : 1
Name : Windows 10 S
Description : Windows 10 S
Size : 15,717,444,845 bytes
Index : 2
Name : Windows 10 S N
Description : Windows 10 S N
Size : 14,651,579,555 bytes
Index : 3
Name : Windows 10 Home
Description : Windows 10 Home
Size : 15,528,886,602 bytes
Index : 4
Name : Windows 10 Home N
Description : Windows 10 Home N
Size : 14,465,481,381 bytes
Index : 5
Name : Windows 10 Home Single Language
Description : Windows 10 Home Single Language
Size : 15,531,153,450 bytes
Index : 6
Name : Windows 10 Education
Description : Windows 10 Education
Size : 15,719,400,830 bytes
Index : 7
Name : Windows 10 Education N
Description : Windows 10 Education N
Size : 14,648,998,694 bytes
Index : 8
Name : Windows 10 Pro
Description : Windows 10 Pro
Size : 15,719,526,598 bytes
Index : 9
Name : Windows 10 Pro N
Description : Windows 10 Pro N
Size : 14,649,755,740 bytes
The operation completed successfully.
PS C:\WINDOWS\system32> DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:D:\sources\install.esd:8 /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.16299.15
Image Version: 10.0.16299.431
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
PS C:\WINDOWS\system32>
升级到v1909再次以同样的方式失败。
回答Ramhound 的评论：我发现 Webroot SecureAnywhere：
- 未列出
appwiz.cpl。 - 无法通过管理命令进行卸载，
"C:\Program Files (x86)\Webroot\WRSA.exe" -uninstall因为它所做的只是导致一个无字警告窗口提示询问是或否，并且两个选项都不起作用。 - 未被 Revo Uninstaller 检测到。
- 无法使用以下方式修复（安装）http://anywhere.webrootcloudav.com/zerol/wsainstall.exe，https://anywhere.webrootcloudav.com/zerol/wsasme.exe， 或者https://anywhere.webrootcloudav.com/zerol/wsasme.msi因为 EXE 只会导致 UI 打开，而 MSI 确实修复了
appwiz.cpl列表，但没有其他作用。
我想我只需要重新安装 Windows。
答案1
我手动平整了 Windows 10 v1709 的安装，并安装了 Windows 10 v1909，没有任何问题。
答案2
由于端点安全，我一个月前也遇到过同样的问题。检查软件安装。端点保护或安全软件阻止对系统驱动程序的更改。删除它并重试
答案3
我在通过网络上的本地提取 ISO 文件将 Windows 7 升级到 10 时遇到了同样的问题。原来是英特尔芯片组上缺少一些驱动程序。安装所有驱动程序后错误就会消失。