DISM / StartComponentCleanup失败,但/ ScanHealth报告运行状况良好


8

我的WinSxS清理任务给出的“上次运行结果” The component store has been corrupted. (0x80073712)。没问题,要提升命令提示符和DISM。

>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

好的,应该准备清洁了。

>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

奇怪,让我们解决这个问题。

>DISM /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.

为了安全起见,请重新扫描。

>DISM /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
No component store corruption detected.
The operation completed successfully.

然后进行清理

>DISM /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 14098

The component store has been corrupted.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

我完全不知所措。如何快速连续地报告为未损坏,已修复和已损坏?

任何考虑这个问题的人sfc也没有用。

>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.

TL; DR:我的SxS存储未损坏,已修复且已损坏。与此同时。不确定如何修复。


日志文件中关于发生了什么进一步的线索?C:\ Windows \ Logs \ CBS \ CBS.log和C:\ Windows \ Logs \ DISM \ dism.log ...您是否尝试过使用Powershell命令Repair-WindowsImage进行修复(不确定关闭顶部的开关)我的头对不起。)
CharlesH

1
上传CBS和DISM日志文件,我稍后再看。
magicandre1981

尽管完全没有帮助,但我决定应该发布结果。我重新启动,它工作正常。骄傲有点受损,我在发布之前没有尝试过,但是您可以使用。对不起,一切延迟!
LuckySpoon 2015年

您应该发布自己的答案,并接受该答案作为答案,这样很容易被其他人发现有帮助并且很明确的答案。
Pimp Juice IT

Answers:


1

原始发布者通过重新启动解决了该问题- dism /Online /Cleanup-Image /RestoreHealth确实是Windows 8及更高版本需要运行的命令。


在这种情况下,还有另一种工具可能会有所帮助:CheckSUR,也称为系统更新准备工具。您可以从KB947821下载适用于Windows 7和更低版本的Windows 7

根据此Microsoft博客文章,CheckSUR通常可以修复组件存储中的损坏,但是当无法修复时,仍然可以使用它来识别受影响的组件。CheckSUR日志的末尾是一个软件包列表。这些条目对应于Windows更新和KB文章。从中获取MSU https://support.microsoft.com/kb/NUMBER-HERE并将其放置在\Windows\CheckSur\packages您可能必须创建的文件夹中。对每个软件包执行完此操作后,请重新运行CheckSUR。

请注意,CheckSUR 可能需要一段时间才能完成其工作


虽然我无法进行测试,但这听起来像是一个不错的解决方案,所以我将标记为已接受
LuckySpoon

0

有同样的问题。我的是由反病毒冲突引起的

这是Microsoft Windows Server v.6.3.12010.0的ESET File Security

为C:\ Windows \ WinSxS添加了排除项

还为进程dism.exe添加了排除项



问题又回来了。不知所措。
马克

再次添加排除项,看看是否能像您第一次说的那样解决
Pimp Juice IT
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.