Recent content by valistral

Uninstalling superseeded KBs 3124275 and 3148198 resolved the last issue.

SFC is clean while now DISM shows 3 corrupt payloads which is unable to find on Windows Update and replace being: Checking System Update Readiness. (p) CSI Payload Corrupt wow64_microsoft-windows-ieframe_31bf3856ad364e35_11.0.9600.18283_none_72c7637ec56c23ed\ieframe.dll Repair...

Managed to (partially at least?) fix the registry and push the component cleanup process to the end. Will run SFC/DISM to see if there's any other issue popping up.

Follow up, trying to run DISM /Online /Cleanup-Image /Startcomponentcleanup will fail with error 0x8000ffff CBS log attached

For some reason that I yet have to determine, either a power failure or something else, the component store hive got corrupted and then automatically rebuilt by the system in the event logs it was also reported that some data was lost. Now running SFC /scannow and DISM /online /cleanup-image...

I think I can reasonably say it should be solved it run for a day without exceptions or fatal exceptions in the Component Based Servicing logs, all I see is some warns that can be safely ignored (?): CBS_E_INVALID_PACKAGE and that it fails to get visibility for...

Done Fix result of Farbar Recovery Scan Tool (x64) Version: 12-10-2019 02 Ran by <censored> (19-10-2019 08:11:18) Run:11 Running from C:\Users\<censored>\Desktop Loaded Profiles: <censored> & MediaAdmin$ & <censored> (Available Profiles: <censored> & MediaAdmin$ & <censored> & Administrator)...

I'm reporting more errors, because apparently the error is thrown also on update checks in CBS.log but it's not fatal, it also doesn't trigger corruption exception on DISM or SFC. Problem still seems to be amd64_microsoft-windows-xmllite_31bf3856ad364e35_6.3.9600.19416_none_7a474c33770b4dcc Log...

Here, Thanks again.

Also even just running: dism /online /cleanup-image /analyzecomponentstore Fails with component store corrupt exception while SFC /scannow and dism /scanhealth and /restorehealth show no corruption atm (after correcting the faulty registry key manually), and Always at the same bit being: Being...

No not replaced recently, memory diagnostics been run recently and were all okay. Did also run a test on the OS SSD, upon your suggestion too by the way sometime ago, but it was also okay.

Hello I'm resurrecting the thread as I noticed yet another corruption during the scheduled idle scavenge of components which fails while checking the applicability for Package_1050_for_KB3000850~31bf3856ad364e35~amd64~~6.3.1.8. Running SFC right after shows no corruption, but running DISM...

Rerun DISM and everything looks correct. Donation also sent, thanks very much for the help. 👍

Appears to be resolved, will try to install missing updates for dotnet 3.5 and rerun to see if something else pops up.

Done. SFCFix version 3.0.2.1 by niemiro. Start time: 2019-10-15 08:58:24.345 Microsoft Windows Server 2012 R2 Update 3 - amd64 Using .zip script file at C:\Users\<censored>\Desktop\SFCFix.zip [0] PowerCopy:: Successfully took permissions for file or folder...