Hi there,
referring to your question
Can you tell me more about your issue?
I start a new thread.
The system suffers from BSsOD. They are partly caused – as far as I understand – by driver and update errors. Last updates could not be installed properly. In order to narrow the problem I run SFCfix first. It detected more than 300 faulty files. Then continued with “sfc/scannow” and afterwards with “dism /online /cleanup-image /scanhealth”. 11 errors remained unfixed:
CheckSUR results:
Binary Version 6.1.7601.24382
2020-02-02 00:24
Checking Windows Servicing Packages
Checking Package Manifests and Catalogs
Checking Package Watchlist
Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-msauditevtlog_31bf3856ad364e35_0.0.0.0_none_eb1c6ffbc097b0f2 Package_214_for_KB3172605~31bf3856ad364e35~amd64~~6.1.1.4 Package registry presence failed, possibly an orphaned package on package watchlist
Checking Packages
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Xps-Foundation-Client-Package~31bf3856ad364e35~amd64~de-DE~6.1.7600.16385 failed to get CurrentState
(f) CBS Registry Error 0x80070002 Microsoft-Windows-Xps-Foundation-Client-Package~31bf3856ad364e35~amd64~de-DE~6.1.7600.16385 failed to get Visibility
(f) CBS Registry Error 0x80070002 Package_324_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5 failed to get Visibility
(f) CBS Registry Error 0x80070002 Package_326_for_KB4343900~31bf3856ad364e35~amd64~~6.1.1.5 failed to get CurrentState
(f) CBS Registry Error 0x80070103 Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23934.1.2 failed to get owner for package.
Checking Component Store
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..g.vc140.crt_f92d94485545da78_14.0.27012.0_db90ad45edef8d91 x86_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.27012.0_none_db90ad45edef8d91
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.crt_f92d94485545da78_14.0.27012.0_b7a28364e4fdb0e3 x86_avg.vc140.crt_f92d94485545da78_14.0.27012.0_none_b7a28364e4fdb0e3
(f) CSI C Mark Deployment Not Marked 0x00000000 c!avg.vc140.crt_f92d94485545da78_14.0.27012.0_6ff54c8dd08187dd amd64_avg.vc140.crt_f92d94485545da78_14.0.27012.0_none_6ff54c8dd08187dd
(f) CSI C Mark Deployment Not Marked 0x00000000 c!policy.14.0..g.vc140.crt_f92d94485545da78_14.0.27012.0_93e3766ed973648b amd64_policy.14.0.avg.vc140.crt_f92d94485545da78_14.0.27012.0_none_93e3766ed973648b
(f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.1_none_951ab4128654b0c9
To tackle the KB3172605 issue I checked which updates are installed; run “systeminfo.exe”. 245 KB-numbers are listed, except
KB3172605
KB3020369
KB3177467.
However, Windows-Explorer found files of KB3172605, KB3020369 and KB3177467 in
(1) c:\windows\system32\catroot
(2) c:\windows\servicing\packages.
With the information gathered I run “dism /online /get-packageinfo /packagename: packagename” (without space between : and p): KB3172605, KB3020369, KB3177467 are installed.
I supposed a removal and a new installation of KB3172605 would be helpful, but it is not possible to remove the package KB3172605 (it’s the same for KB3020369 and KB3177467):
dism error 87; 0x8000ffff.
What next?
I would be very grateful if someone could help me to fix the errors.
Thanks a lot.
