Windows 8 and 8.1 Forums


Windows 8.1 Pro sfc /scannow unable to fix corrupted files

  1. #21


    Posts : 2,690
    Windows 3.1 > Windows 10


    yes

    Dism /Online /Cleanup-Image /ScanHealth

    gives a better dism.log summary

    Code:
    Checking System Update Readiness.
    (p) CSI Payload Corrupt   amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\utc.app.json
    (p) CSI Payload Corrupt   amd64_microsoft-windows-u..ed-telemetry-client_31bf3856ad364e35_6.3.9600.17747_none_90df8130dac08ee0\telemetry.ASM-WindowsDefault.json
    Summary:
    Operation: Detect only 
    Operation result: 0x0
    Last Successful Step: CSI store detection completes.
    Total Detected Corruption: 2

      My System SpecsSystem Spec

  2. #22


    Posts : 21
    Windows 8.1 Pro


    It is running right now. Thank you.
      My System SpecsSystem Spec

  3. #23


    Posts : 21
    Windows 8.1 Pro


    It says at the prompt upon completion, "No component store corruption detected." Is this for 'component store?' WIT? Thank you. What happened to all the other corrupted files shown in the log?
    Wait! I'll check the log file! Be right back. TY!
      My System SpecsSystem Spec

  4. #24


    Posts : 21
    Windows 8.1 Pro


    Here is what the partial log shows now, starting with where the corrupted files were logged. Looks pretty much the same:

    2015-07-14 13:59:30, Info CSI 000004cb [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:31, Info CSI 000004cd [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 13:59:31, Info CSI 000004cf [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 13:59:35, Info CSI 000004d4 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 13:59:35, Info CSI 000004d5 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-07-14 13:59:35, Info CSI 000004d7 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 13:59:35, Info CSI 000004d8 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-07-14 13:59:35, Info CSI 000004e3 [SR] Verify complete
    2015-07-14 13:59:36, Info CSI 000004e4 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:36, Info CSI 000004e5 [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:40, Info CSI 000004ef [SR] Verify complete
    2015-07-14 13:59:40, Info CSI 000004f0 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:40, Info CSI 000004f1 [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:43, Info CSI 000004fc [SR] Verify complete
    2015-07-14 13:59:43, Info CSI 000004fd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:43, Info CSI 000004fe [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:47, Info CSI 00000515 [SR] Verify complete
    2015-07-14 13:59:47, Info CSI 00000516 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:47, Info CSI 00000517 [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:50, Info CSI 00000518 [SR] Verify complete
    2015-07-14 13:59:50, Info CSI 00000519 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:50, Info CSI 0000051a [SR] Beginning Verify and Repair transaction
    2015-07-14 13:59:54, Info CSI 0000051c [SR] Verify complete
    2015-07-14 13:59:54, Info CSI 0000051d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 13:59:54, Info CSI 0000051e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:00, Info CSI 0000051f [SR] Verify complete
    2015-07-14 14:00:00, Info CSI 00000520 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:00, Info CSI 00000521 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:04, Info CSI 0000053c [SR] Verify complete
    2015-07-14 14:00:04, Info CSI 0000053d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:04, Info CSI 0000053e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:08, Info CSI 0000055e [SR] Verify complete
    2015-07-14 14:00:08, Info CSI 0000055f [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:08, Info CSI 00000560 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:11, Info CSI 00000571 [SR] Verify complete
    2015-07-14 14:00:11, Info CSI 00000572 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:11, Info CSI 00000573 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:13, Info CSI 00000574 [SR] Verify complete
    2015-07-14 14:00:14, Info CSI 00000575 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:14, Info CSI 00000576 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:16, Info CSI 00000577 [SR] Verify complete
    2015-07-14 14:00:16, Info CSI 00000578 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:16, Info CSI 00000579 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:20, Info CSI 0000057b [SR] Verify complete
    2015-07-14 14:00:20, Info CSI 0000057c [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:20, Info CSI 0000057d [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:23, Info CSI 0000057e [SR] Verify complete
    2015-07-14 14:00:23, Info CSI 0000057f [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:23, Info CSI 00000580 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:26, Info CSI 00000581 [SR] Verify complete
    2015-07-14 14:00:26, Info CSI 00000582 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:26, Info CSI 00000583 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:28, Info CSI 00000584 [SR] Verify complete
    2015-07-14 14:00:28, Info CSI 00000585 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:28, Info CSI 00000586 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:31, Info CSI 00000587 [SR] Verify complete
    2015-07-14 14:00:31, Info CSI 00000588 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:31, Info CSI 00000589 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:33, Info CSI 0000058a [SR] Verify complete
    2015-07-14 14:00:34, Info CSI 0000058b [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:34, Info CSI 0000058c [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:36, Info CSI 0000058d [SR] Verify complete
    2015-07-14 14:00:36, Info CSI 0000058e [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:36, Info CSI 0000058f [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:39, Info CSI 00000590 [SR] Verify complete
    2015-07-14 14:00:39, Info CSI 00000591 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:39, Info CSI 00000592 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:41, Info CSI 000005bb [SR] Verify complete
    2015-07-14 14:00:41, Info CSI 000005bc [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:41, Info CSI 000005bd [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:44, Info CSI 000005be [SR] Verify complete
    2015-07-14 14:00:44, Info CSI 000005bf [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:44, Info CSI 000005c0 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:50, Info CSI 000005c3 [SR] Verify complete
    2015-07-14 14:00:50, Info CSI 000005c4 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:50, Info CSI 000005c5 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:55, Info CSI 000005c6 [SR] Verify complete
    2015-07-14 14:00:55, Info CSI 000005c7 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:55, Info CSI 000005c8 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:00:58, Info CSI 000005c9 [SR] Verify complete
    2015-07-14 14:00:58, Info CSI 000005ca [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:00:58, Info CSI 000005cb [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:01, Info CSI 000005cc [SR] Verify complete
    2015-07-14 14:01:01, Info CSI 000005cd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:01, Info CSI 000005ce [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:05, Info CSI 000005cf [SR] Verify complete
    2015-07-14 14:01:05, Info CSI 000005d0 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:05, Info CSI 000005d1 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:11, Info CSI 000005dc [SR] Verify complete
    2015-07-14 14:01:11, Info CSI 000005dd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:11, Info CSI 000005de [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:14, Info CSI 000005df [SR] Verify complete
    2015-07-14 14:01:14, Info CSI 000005e0 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:14, Info CSI 000005e1 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:17, Info CSI 000005e2 [SR] Verify complete
    2015-07-14 14:01:17, Info CSI 000005e3 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:17, Info CSI 000005e4 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:20, Info CSI 00000651 [SR] Verify complete
    2015-07-14 14:01:20, Info CSI 00000652 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:20, Info CSI 00000653 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:23, Info CSI 00000655 [SR] Verify complete
    2015-07-14 14:01:23, Info CSI 00000656 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:23, Info CSI 00000657 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:25, Info CSI 0000065a [SR] Verify complete
    2015-07-14 14:01:25, Info CSI 0000065b [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:25, Info CSI 0000065c [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:28, Info CSI 0000065d [SR] Verify complete
    2015-07-14 14:01:28, Info CSI 0000065e [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:28, Info CSI 0000065f [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:30, Info CSI 00000660 [SR] Verify complete
    2015-07-14 14:01:30, Info CSI 00000661 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:30, Info CSI 00000662 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:33, Info CSI 00000663 [SR] Verify complete
    2015-07-14 14:01:33, Info CSI 00000664 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:33, Info CSI 00000665 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:36, Info CSI 00000666 [SR] Verify complete
    2015-07-14 14:01:36, Info CSI 00000667 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:36, Info CSI 00000668 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:40, Info CSI 00000681 [SR] Verify complete
    2015-07-14 14:01:40, Info CSI 00000682 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:40, Info CSI 00000683 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:43, Info CSI 0000068f [SR] Verify complete
    2015-07-14 14:01:44, Info CSI 00000690 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:44, Info CSI 00000691 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:48, Info CSI 000006a2 [SR] Verify complete
    2015-07-14 14:01:48, Info CSI 000006a3 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:48, Info CSI 000006a4 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:50, Info CSI 000006a6 [SR] Verify complete
    2015-07-14 14:01:50, Info CSI 000006a7 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:50, Info CSI 000006a8 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:52, Info CSI 000006a9 [SR] Verify complete
    2015-07-14 14:01:52, Info CSI 000006aa [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:52, Info CSI 000006ab [SR] Beginning Verify and Repair transaction
    2015-07-14 14:01:57, Info CSI 000006b9 [SR] Verify complete
    2015-07-14 14:01:57, Info CSI 000006ba [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:01:57, Info CSI 000006bb [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:02, Info CSI 000006bc [SR] Verify complete
    2015-07-14 14:02:02, Info CSI 000006bd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:02, Info CSI 000006be [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:06, Info CSI 000006e0 [SR] Verify complete
    2015-07-14 14:02:06, Info CSI 000006e1 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:06, Info CSI 000006e2 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:10, Info CSI 000006ec [SR] Verify complete
    2015-07-14 14:02:10, Info CSI 000006ed [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:10, Info CSI 000006ee [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:14, Info CSI 000006fa [SR] Verify complete
    2015-07-14 14:02:15, Info CSI 000006fb [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:15, Info CSI 000006fc [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:20, Info CSI 0000071c [SR] Verify complete
    2015-07-14 14:02:20, Info CSI 0000071d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:20, Info CSI 0000071e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:25, Info CSI 0000076e [SR] Verify complete
    2015-07-14 14:02:25, Info CSI 0000076f [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:25, Info CSI 00000770 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:28, Info CSI 00000772 [SR] Verify complete
    2015-07-14 14:02:28, Info CSI 00000773 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:28, Info CSI 00000774 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:32, Info CSI 00000775 [SR] Verify complete
    2015-07-14 14:02:32, Info CSI 00000776 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:32, Info CSI 00000777 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:34, Info CSI 0000077a [SR] Verify complete
    2015-07-14 14:02:35, Info CSI 0000077b [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:35, Info CSI 0000077c [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:38, Info CSI 00000796 [SR] Verify complete
    2015-07-14 14:02:38, Info CSI 00000797 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:38, Info CSI 00000798 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:42, Info CSI 000007be [SR] Verify complete
    2015-07-14 14:02:42, Info CSI 000007bf [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:42, Info CSI 000007c0 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:45, Info CSI 000007c3 [SR] Verify complete
    2015-07-14 14:02:45, Info CSI 000007c4 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:45, Info CSI 000007c5 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:48, Info CSI 000007cd [SR] Verify complete
    2015-07-14 14:02:48, Info CSI 000007ce [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:48, Info CSI 000007cf [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:53, Info CSI 000007d0 [SR] Verify complete
    2015-07-14 14:02:53, Info CSI 000007d1 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:53, Info CSI 000007d2 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:02:56, Info CSI 000007dc [SR] Verify complete
    2015-07-14 14:02:56, Info CSI 000007dd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:02:56, Info CSI 000007de [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:02, Info CSI 00000800 [SR] Verify complete
    2015-07-14 14:03:02, Info CSI 00000801 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:02, Info CSI 00000802 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:05, Info CSI 00000810 [SR] Verify complete
    2015-07-14 14:03:05, Info CSI 00000811 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:05, Info CSI 00000812 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:08, Info CSI 0000081c [SR] Verify complete
    2015-07-14 14:03:08, Info CSI 0000081d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:08, Info CSI 0000081e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:09, Info CSI 00000820 [SR] Verify complete
    2015-07-14 14:03:09, Info CSI 00000821 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:09, Info CSI 00000822 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:14, Info CSI 0000082c [SR] Verify complete
    2015-07-14 14:03:14, Info CSI 0000082d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:14, Info CSI 0000082e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:17, Info CSI 00000847 [SR] Verify complete
    2015-07-14 14:03:18, Info CSI 00000848 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:18, Info CSI 00000849 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:20, Info CSI 0000084a [SR] Verify complete
    2015-07-14 14:03:20, Info CSI 0000084b [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:20, Info CSI 0000084c [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:24, Info CSI 00000852 [SR] Verify complete
    2015-07-14 14:03:24, Info CSI 00000853 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:24, Info CSI 00000854 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:32, Info CSI 00000873 [SR] Verify complete
    2015-07-14 14:03:32, Info CSI 00000874 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:32, Info CSI 00000875 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:36, Info CSI 00000885 [SR] Verify complete
    2015-07-14 14:03:36, Info CSI 00000886 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:36, Info CSI 00000887 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:44, Info CSI 000008a8 [SR] Verify complete
    2015-07-14 14:03:44, Info CSI 000008a9 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:44, Info CSI 000008aa [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:47, Info CSI 000008ac [SR] Verify complete
    2015-07-14 14:03:47, Info CSI 000008ad [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:47, Info CSI 000008ae [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:50, Info CSI 000008bf [SR] Verify complete
    2015-07-14 14:03:50, Info CSI 000008c0 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:50, Info CSI 000008c1 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:52, Info CSI 000008c4 [SR] Verify complete
    2015-07-14 14:03:53, Info CSI 000008c5 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:53, Info CSI 000008c6 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:55, Info CSI 000008c9 [SR] Verify complete
    2015-07-14 14:03:55, Info CSI 000008ca [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:55, Info CSI 000008cb [SR] Beginning Verify and Repair transaction
    2015-07-14 14:03:59, Info CSI 000008cf [SR] Verify complete
    2015-07-14 14:03:59, Info CSI 000008d0 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:03:59, Info CSI 000008d1 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:02, Info CSI 000008d5 [SR] Verify complete
    2015-07-14 14:04:02, Info CSI 000008d6 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:02, Info CSI 000008d7 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:05, Info CSI 000008db [SR] Verify complete
    2015-07-14 14:04:05, Info CSI 000008dc [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:05, Info CSI 000008dd [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:08, Info CSI 000008e0 [SR] Verify complete
    2015-07-14 14:04:08, Info CSI 000008e1 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:08, Info CSI 000008e2 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:11, Info CSI 000008e7 [SR] Verify complete
    2015-07-14 14:04:11, Info CSI 000008e8 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:11, Info CSI 000008e9 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:14, Info CSI 000008ec [SR] Verify complete
    2015-07-14 14:04:14, Info CSI 000008ed [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:14, Info CSI 000008ee [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:17, Info CSI 000008f6 [SR] Verify complete
    2015-07-14 14:04:17, Info CSI 000008f7 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:17, Info CSI 000008f8 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:21, Info CSI 000008fc [SR] Verify complete
    2015-07-14 14:04:21, Info CSI 000008fd [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:21, Info CSI 000008fe [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:24, Info CSI 000008ff [SR] Verify complete
    2015-07-14 14:04:24, Info CSI 00000900 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:24, Info CSI 00000901 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:27, Info CSI 00000903 [SR] Verify complete
    2015-07-14 14:04:27, Info CSI 00000904 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:27, Info CSI 00000905 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:30, Info CSI 00000906 [SR] Verify complete
    2015-07-14 14:04:30, Info CSI 00000907 [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:30, Info CSI 00000908 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:32, Info CSI 00000909 [SR] Verify complete
    2015-07-14 14:04:32, Info CSI 0000090a [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:32, Info CSI 0000090b [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:35, Info CSI 0000090c [SR] Verify complete
    2015-07-14 14:04:35, Info CSI 0000090d [SR] Verifying 100 (0x0000000000000064) components
    2015-07-14 14:04:35, Info CSI 0000090e [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:38, Info CSI 0000090f [SR] Verify complete
    2015-07-14 14:04:38, Info CSI 00000910 [SR] Verifying 94 (0x000000000000005e) components
    2015-07-14 14:04:38, Info CSI 00000911 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:41, Info CSI 00000914 [SR] Verify complete
    2015-07-14 14:04:41, Info CSI 00000915 [SR] Repairing 1 components
    2015-07-14 14:04:41, Info CSI 00000916 [SR] Beginning Verify and Repair transaction
    2015-07-14 14:04:41, Info CSI 00000918 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 14:04:41, Info CSI 0000091a [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 14:04:41, Info CSI 0000091c [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 14:04:41, Info CSI 0000091d [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-07-14 14:04:41, Info CSI 0000091f [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.3.9600.17842, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
    2015-07-14 14:04:41, Info CSI 00000920 [SR] This component was referenced by [l:154{77}]"Package_1_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0.3068708-1_neutral_GDR"
    2015-07-14 14:04:41, Info CSI 00000922 [SR] Repair complete
    2015-07-14 14:04:41, Info CSI 00000923 [SR] Committing transaction
    2015-07-14 14:04:42, Info CSI 00000928 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired
      My System SpecsSystem Spec

  5. #25


    Harrisonburg, Va.
    Posts : 10,488
    Windows 8.1.1 Pro with Media Center


    Don't worry about the json files.
    They are false positives.
      My System SpecsSystem Spec

  6. #26


    Posts : 21
    Windows 8.1 Pro


    Okay, seems I'm where I was when I came here. Alas, poor Yorick. Gotta sign off for the day. Thanx, everyone, for trying to help me. DB
      My System SpecsSystem Spec

  7. #27


    N.Y.
    Posts : 2,214
    Windows 10 Pro 64bit


    Quote Originally Posted by David Bailey View Post
    Don't worry about the json files.
    They are false positives.
    Should of been cleared up by now, mine is fine, been saying this in so many posts as i did have this issue also once from windows updates
      My System SpecsSystem Spec

  8. #28


    UK
    Posts : 275
    Windows 8.1 64 bit


    My thread below may help - I had to remove both of the Windows updates to enable SFC and DISM to run without errors. I've now hidden these updates until Microsoft fixes the problem.

    DISM Command Fails
      My System SpecsSystem Spec

  9. #29


    Posts : 21
    Windows 8.1 Pro


    Steve, thank you for the link. I removed one of these updates, but I will remove the other which apparently is some sort of telemetry tracking update, surely something not needed in the least. I'll let the forum know how the scan goes following removal of the other update.
      My System SpecsSystem Spec

  10. #30


    Posts : 108
    Windows 8.1 Pro with Media Center © 2013 Version: 6.3.9600 Build 9600.16408


    Hey Guys,

    As you may already know that Microsoft is about to roll out it's most recent Operating System (OS) member, windows 10 in just about 2 weeks time from today.


    I recently discovered an issue with a few of the updates that were offered to me and which I accepted and installed by way of the Windows Update Service. At first glance, there didn't seem to be a problem with my system, but upon conducting both a Safety Scan using the built-in Microsoft Safety Scanner tool and a check health scan using the Deployment Image Servicing and Management (DISM.exe) utility, which both found and was unable to repair these seeming file corruptions.


    That said. I did some research and realized that pretty much ever system out there that have received and installed certain updates also experience this same file corruption issue. Below are a list of the windows updates that are causing the file corruption issues upon install:

    KB3022345
    Package_for_KB3022345~31bf3856ad364e35~amd64~~6.3.1.5

    KB3068708
    Package_for_KB3068708~31bf3856ad364e35~amd64~~6.3.1.0

    KB3035583
    Package_for_KB3035583~31bf3856ad364e35~amd64~~6.3.1.29


    The above are windows update packages that seem to be causing file corruption problems for Windows 8 and 8.1 users by their respective "Knowledge Base" Package Names. Two of these Updates were initially release through the Windows Update Service as "OPTIONAL UPDATES." However, the first of these three updates was re-released as a recent mandatory or "IMPORTANT UPDATE" under the update name "KB3068708" to replace the original optional update referred to as "KB3022345."

    These update pretty much all do the same thing, which is to install a new service which runs in the background called the "DIAGNOSTIC TRACKING SERVICE" among your system's list of services that run in the background on a pretty regular basis by way of your systems TASK SCHEDULER routine.
    The included service uses SSL (TCP Port 443) to download manifests and upload data to Microsoft when data is available for upload. The service uses the following DNS endpoints:•vortex-win.data.microsoft.com
    •settings-win.data.microsoft.com
    This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:
    •telemetry.ASM-WindowsDefault.json
    •utc.app.json
    The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or actual corruption on a device that is running this update, and this issue will be fixed in a later service update.
    Having these updates installed on your system doesn't typically cause any real problems to users, other than those of privacy and returning a Safety Scan result of your system having seeming file corruptions, as this service is used to relay system usage data back to Microsoft Servers for what they describe as being "Customer Experience Monitoring" to be used by them to improve your systems' overall performance and to allow Microsoft to address resulting system use issues by way of future updates and patch releases.


    I, personally, uninstalled every instance of these updates, only to have my system really begin to behave strangely, as these updates are part of the Service Pack 1 for the Windows 8 OS platform. I eventually had to re-install these updates as a couple of them are now no longer simply optional updates, but have been made MANDATORY updates in anticipation of an eventual upgrade migration to the Windows 10 OS platform later.


    **Remember, they are not really different or separate updates, but are rather the same update by different names and offered by Windows Update Service as either an Optional or Important update.**



    For anyone who would like one uninstall these updates, BE WARNED!!! These updates will eventually find their way onto your system somehow, via the Windows Update Service, at some point in the future, whether as a (mandatory) Important Update or an Optional Update. Just note that once uninstalled, these updates WILL, turn up once again in your update cue for re-installation back onto your system and removal may cause your system to become unstable.


    You can remove these updates from your system a number of ways. However uninstalling them using your update history is the simplest way to do so. Below are the instructions for doing so:

    Method 1:
    Take these steps to be certain you want to remove an update:
    • Open Installed Updates by clicking the Start button , clicking Control Panel, clicking Programs, and then, under Programs and Features, clicking View installed updates.
    • Select the update that you want to remove, and then click Uninstall.


    Method 2:
    Take these steps to be certain you want to remove an update:
    1. Open a Command Prompt as a system Administrator, swipe or mouse right to bring up the Charms Menu , type CMD, and then, Right click to select Run As Administrator.
    2. Type the following into the Command Prompt window without the quotes. "DISM.exe /Online /Remove-Package /PackageName:Package_for_KBXXXXXXX~31bf3856ad364e35~amd64~~X.X.X.X"
    3. You will be asked by command prompt once the process completes if you would like to, then restart your system to save the uninstall changes made by typing either Y/N, so type "Y" to complete the process and restart your system to save the changes.
    4. Repeat the above mentioned steps for each of the update packages you wish to remove from your system one by one also restarting your system each time.


    According to Microsoft's own Technical Support Department, this issue both can and will only be resolved at the moment by migrating/upgrading to Windows 10. These updates were released to prepare your system for the eventual upgrade to the new and latest version of Windows. These updates are prerequisites for upgrading to Windows 10 from older versions and the resulting features they add will be standard in Windows 10.
      My System SpecsSystem Spec

Page 3 of 4 FirstFirst 1234 LastLast
Windows 8.1 Pro sfc /scannow unable to fix corrupted files
Related Threads
*I am running windows 8.1 Pro, this issue came up last night when I was suddenly unable to save or view image files (.png, .jpg, etc). Troubleshooting led to discovering corrupt system files, now I am here: Running sfc /scannow in the command prompt (admin level) yielded some interesting...
After trying to run a game I got an error message saying that MSVCR120.dll could not be found. I then downloaded the Microsoft Visual Studio 2012 again in hopes it will restore the file. I then downloaded that file and put it in the System32 folder but it still did not work. I then tried to run...
Solved SFC /Scannow Unable to fix error. in Performance & Maintenance
Hey guy's I've been having alittle bit of issues but nothing major or no BSOD's but I did my monthly tune up virus scan etc etc and i also decided to run SFC /Scannow command to see what would turn up well i have a error that couldn't be fixed and i already ran DISM Command and sill the same issue....
Solved Sfc /scannow cannot fix the corrupted files in Performance & Maintenance
Hello, so as the title said, I have done sfc/ scannow a few time and cannot fix the corrupted files. I was wondering what can I do to fix all these problem? Here are the CBS file. Been looking at a few thread and it seems that uploading this file will be helpful. 48256
Hello, today I am posting in the Eight Forums to ask about how to fix a corrupted looking Windows 8 start menu with no corrupted files found. I know that's a really bad way to explain the situation. I have uploaded a screenshot which I hope explains the issues. I wanted to add the blank squares do...
Solved SFC /Scannow - Corrupted Files in Performance & Maintenance
so here's the deal - my machine is screaming fast right now and set up just the way i like it, runs like a champ and everything seems to be working perfectly - but being the a-retentive guy that i am, i still usually run a few diagnostics fairly often, and that's how i came across these corrupted...
It was confirmed that the sfc should work the same in W8. So I am getting corrupted file messages. Ran it 3 times and it did not clear itself. What would be the next avenue I need to pursue to get the system perfect for a system image? Thanks for any assistance! Glenn
Eight Forums Android App Eight Forums IOS App Follow us on Facebook