Windows 8.1 Pro sfc /scannow unable to fix corrupted files

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 Computer

System One

  • OS
    Windows 3.1 > Windows 10
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Dell XPS 8700
    CPU
    I7
    Memory
    24 GB
It is running right now. Thank you.
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
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 Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
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 Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
Don't worry about the json files.
They are false positives.
 

My Computer

System One

  • OS
    Windows 8.1.1 Pro with Media Center
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Gateway
    CPU
    AMD K140 Cores 2 Threads 2 Name AMD K140 Package Socket FT1 BGA Technology 40nm
    Motherboard
    Manufacturer Gateway Model SX2110G (P0)
    Memory
    Type DDR3 Size 8192 MBytes DRAM Frequency 532.3 MHz
    Graphics Card(s)
    ATI AMD Radeon HD 7310 Graphics
    Sound Card
    AMD High Definition Audio Device Realtek High Definition Audio USB Audio Device
    Monitor(s) Displays
    Name 1950W on AMD Radeon HD 7310 Graphics Current Resolution 1366x768 pixels Work Resolution 1366x76
    Screen Resolution
    Current Resolution 1366x768 pixels Work Resolution 1366x768 pixels
    Hard Drives
    AMD K140
    Cores 2
    Threads 2
    Name AMD K140
    Package Socket FT1 BGA
    Technology 40nm
    Specification AMD E1-1200 APU with Radeon HD Graphics
    Family F
    Extended Family 14
    Model 2
    Extended Model 2
    Stepping 0
    Revision ON-C0
    Instruction
    Browser
    Opera 24.0
    Antivirus
    Avast Internet Security
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 :huh:
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
David Bailey said:
Don't worry about the json files.
They are false positives.
Click to expand...

:ditto: 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 Computer

System One

  • OS
    Windows 10 Pro 64bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    CyberPowerPC Gamer Xtreme 1502 (GX1502)
    CPU
    Intel Core i7 5820K 3.30 GHZ 64 bit 6-Core Processor
    Motherboard
    Gigabyte GA-X99-UD3
    Memory
    G.Skill 16GB Quad Channel DDR4-2400MHZ
    Graphics Card(s)
    EVGA GeForce GTX 970 SSC ACX 2.0+ DDR5 4GB
    Sound Card
    Creative Sound Blaster ZxR 5.1
    Monitor(s) Displays
    ASUS PA24Q 24" Pro Art IPS LCD/LED Backlit 1920x1200
    Screen Resolution
    1920x1200 16:10
    Hard Drives
    SAMSUNG 850 EVO 250GB SATA 6Gb/s 2.5" Internal SSD,
    Crucial MX100 512GB SATA 6Gb/s 2.5" Internal SSD,
    WD WD10EZEX-00RKKA0 1TB SATA 6Gb/s 3.5 Internal HDD
    PSU
    EVGA SuperNOVA 750 G2 750W 80 Plus Gold Full Modular
    Case
    AZZA Cosmas Black Gaming Case
    Cooling
    Cool Master Hyper 212 Evo Dual 120mm, ( 2) Noctua PWM 120mm Case Fans (1) Gelid PWM 120mm Blue LED
    Keyboard
    Logitech K800 Illumiated Wireless Keyboard
    Mouse
    Logitech M570 Wireless Trackball
    Internet Speed
    84mbps /94mbps
    Browser
    Mozilla Firefox 41.0.1 / Microsoft Edge/ IE 11
    Antivirus
    Norton Security 2015
    Other Info
    Pioneer BDR-209DBK 16x Blu-Ray Burner, LG 24x Dual Layer DVD Burner,
    StarTech Front Bay 22-in-1 USB 2.0 Internal Multi Media Memory Card Reader,Logitech Z906 5.1 Speaker system

My Computer

System One

  • OS
    Windows 8.1 64 bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Build
    CPU
    Intel i3570K
    Motherboard
    Gigabyte GA-77X-UD5H
    Memory
    16 GB
    Graphics Card(s)
    Sapphire R9 280X Toxic
    Sound Card
    Realtek on motherboard
    Monitor(s) Displays
    Viewsonic VP2770
    Screen Resolution
    2560 x 1440
    Hard Drives
    Intel 520 180GB SSD
    Seagate 2T HDD
    Seagate external 1T USB HDD
    PSU
    XFX 850W
    Case
    Nanoxia Deep Silence 1
    Cooling
    Noctua NH-D14
    Keyboard
    Microsoft
    Mouse
    Microsoft
    Internet Speed
    50Mbps
    Browser
    Chrome
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 Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
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 Computer

System One

  • OS
    Windows 8.1 Pro with Media Center © 2013 Version: 6.3.9600 Build 9600.16408
    System Manufacturer/Model
    HP Pavilion dv6t – 6100 CTO series Notebook PC LM328AV#ABA
    CPU
    Intel(R) Core(TM) I7-2720QM @ 2.20 GHz
    Motherboard
    unknown
    Memory
    8 GB
    Graphics Card(s)
    Intel HD + Radeon(TM) HD 6490M
    Sound Card
    IDT Beats Audio
    Screen Resolution
    1366 x 768 (Native)
    Cooling
    HP Cool Sene v.1
    Internet Speed
    Broadband (Cable)
    Browser
    IE 11 & Firefox Nightly28.0a1
    Other Info
    Intel Wireless Display
    Bluetooth 4.0
KB3035583 has been installed on my system but SFC still runs to completion without errors. I also don't have the Diagnostic Tracking Service as a result of installing KB3035583. It seems the SFC and DISM errors are due to update KB3022345 and the related update KB3068708.
 

My Computer

System One

  • OS
    Windows 8.1 64 bit
    Computer type
    PC/Desktop
    System Manufacturer/Model
    Home Build
    CPU
    Intel i3570K
    Motherboard
    Gigabyte GA-77X-UD5H
    Memory
    16 GB
    Graphics Card(s)
    Sapphire R9 280X Toxic
    Sound Card
    Realtek on motherboard
    Monitor(s) Displays
    Viewsonic VP2770
    Screen Resolution
    2560 x 1440
    Hard Drives
    Intel 520 180GB SSD
    Seagate 2T HDD
    Seagate external 1T USB HDD
    PSU
    XFX 850W
    Case
    Nanoxia Deep Silence 1
    Cooling
    Noctua NH-D14
    Keyboard
    Microsoft
    Mouse
    Microsoft
    Internet Speed
    50Mbps
    Browser
    Chrome
MKeezy, thanx. However, I believe that Microsoft should have given people the option of installing these updates. I, for one, have no intention of upgrading to Windows 10 in the immediate future. Thus, IMO, I shouldn't have this "la-la" on my system. These updates should have been packaged as a prerequisite for those who opted to upgrade to Windows 10. IMHO, the KB3022345 update that drops a Windows 10 icon reminder (and offer) in the task bar is tantamount of unsolicited advertising.
Sorry for the rant. My next post will show the results of my latest scan after removing KB3068708. KB3022345 had been removed a few weeks ago when I got tired of looking at the icon. If anyone has any ideas ...:rolleyes:
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
Having removed KB3068708 and KB3022345, still unfixable corrupted files found in the scan which I've run about 3 times following. Here the log file with the info pertinent to the corrupted files only:

[snip]
2015-07-15 12:19:17, Info CSI 00000313 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:19:20, Info CSI 0000032e [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:19:20, Info CSI 0000032f [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"

[snip]
2015-07-15 12:30:45, Info CSI 00000313 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:30:48, Info CSI 0000032e [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:30:48, Info CSI 0000032f [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"


[snip]
2015-07-15 12:34:51, Info CSI 00000918 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:34:51, Info CSI 0000091a [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:34:51, Info CSI 0000091b [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"
[snip]
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
Steve C said:
KB3035583 has been installed on my system but SFC still runs to completion without errors. I also don't have the Diagnostic Tracking Service as a result of installing KB3035583. It seems the SFC and DISM errors are due to update KB3022345 and the related update KB3068708.
Click to expand...


You are probably right about that, Steve C. I only know that all three of those updates lends themselves to accomplishing the same task, which is to prepare Windows 8 and 8.1 user for the eventual migration to the new Windows 10 platform. Microsoft uses the data collected by the added feature to help them work out and anticipate User Experience issues with both the upcoming Windows 10 OS platform and the current Windows 8 OS platform. However, their focus on resolving the issues of false positive results caused by the installation of these updates onto systems running previous versions of Windows is low on the list of priorities right now since the primary focus of R&D is to ensure the rollout of Windows 10 runs smoothly as those updates were designed specifically as prerequisites to upgrading to Windows 10 from existing previous versions of Windows.


What many user consider to be a problem is not really a problem as there is actually no file corruptions occurring on their system as a result of installing these updates despite the SFC Scanner and DISM results yielded concerning them to the contrary. In fact, removing KB3035583 will result in the lose of the Get Windows 10 (GWX) item running in your system tray. It is the most recent related update of the three in preparation of the Windows 10 upgrade migration. It is what installed that Get Windows 10 Icon into your system tray.

All I'm here saying is that many user are unsure of what these upgrades are and why their Safety Scanner and DISM utility is treating them like malware. They do collect data on your system. The KB3035583 scans your system for both hardware and software changes on a monthly basis in order to determine if your system's current configuration is still compatible with upgrading to Windows 10. It's a new version of the old Windows Upgrade advisor, except it's now built-in and standard in Windows 10. The same goes for the other two updates and all are prerequisites to being able to upgrade to windows 10.

I'm not sure whether once Windows 10 is release that Microsoft will once again return its attention back to resolving the current issues with these "Windows 10" prerequisite updates in older versions of Windows, but the focus right now is not on ensuring that user can run Safety Scans or DISM Scans and not receive the false positive result as the updates do not actually adversely effect your system's performance in any way. Albeit, users seem to have some very real issues of privacy concerns about the data being collect by Microsoft through the introduction of these seemingly invasive user data mining tools.

This seeming False positive system file corruption will automatically be fixed once upgraded to Windows 10 as the upgrades are designed for the windows 10 OS environment and not necessarily the Windows 8 and 8.1 in which they are currently running. This is why the hash string identifiers associated with these updates are returning an unexpected result by both the safety scanner and dim utility.
 

My Computer

System One

  • OS
    Windows 8.1 Pro with Media Center © 2013 Version: 6.3.9600 Build 9600.16408
    System Manufacturer/Model
    HP Pavilion dv6t – 6100 CTO series Notebook PC LM328AV#ABA
    CPU
    Intel(R) Core(TM) I7-2720QM @ 2.20 GHz
    Motherboard
    unknown
    Memory
    8 GB
    Graphics Card(s)
    Intel HD + Radeon(TM) HD 6490M
    Sound Card
    IDT Beats Audio
    Screen Resolution
    1366 x 768 (Native)
    Cooling
    HP Cool Sene v.1
    Internet Speed
    Broadband (Cable)
    Browser
    IE 11 & Firefox Nightly28.0a1
    Other Info
    Intel Wireless Display
    Bluetooth 4.0
Dorrin Birch said:
Having removed KB3068708 and KB3022345, still unfixable corrupted files found in the scan which I've run about 3 times following. Here the log file with the info pertinent to the corrupted files only:

[snip]
2015-07-15 12:19:17, Info CSI 00000313 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:19:20, Info CSI 0000032e [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:19:20, Info CSI 0000032f [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"

[snip]
2015-07-15 12:30:45, Info CSI 00000313 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:30:48, Info CSI 0000032e [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:30:48, Info CSI 0000032f [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"


[snip]
2015-07-15 12:34:51, Info CSI 00000918 [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:34:51, Info CSI 0000091a [SR] Cannot repair member file [l:22{11}]"jsproxy.dll" of Microsoft-Windows-IE-ClientNetworkProtocolImplementation, Version = 11.0.9600.17905, 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-15 12:34:51, Info CSI 0000091b [SR] This component was referenced by [l:158{79}]"Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0.3065822-93_neutral_GDR"
[snip]
Click to expand...



Hello Dorrin,


According to the information you have posted concerning your log result as to what is the source of your corruption result, the update you removed only partly was responsible for the corruption result.

hash mismatch
Package_43_for_KB3065822~31bf3856ad364e35~amd64~~6.3.1.0

It would appear that update package name KB3065822 is also causing problems. However, before you go uninstalling any updates, I'd advise you to research the them first. Occasionally, the update service my get it wrong and inject a non-applicable update into your systems update cue and even install it onto your system even though it isn't for your particular system, which might result in system file corruption. That doesn't happen often, which means that every update installed by the update service is suppose to be on your system.

That said. Any update that you uninstall through normal uninstall means should be offered to you again in your next Windows update cue. Simply re-install it if you find that performance issues arise as a result of uninstalling any update package you remove, especially if those update are non-optional updates.
 

My Computer

System One

  • OS
    Windows 8.1 Pro with Media Center © 2013 Version: 6.3.9600 Build 9600.16408
    System Manufacturer/Model
    HP Pavilion dv6t – 6100 CTO series Notebook PC LM328AV#ABA
    CPU
    Intel(R) Core(TM) I7-2720QM @ 2.20 GHz
    Motherboard
    unknown
    Memory
    8 GB
    Graphics Card(s)
    Intel HD + Radeon(TM) HD 6490M
    Sound Card
    IDT Beats Audio
    Screen Resolution
    1366 x 768 (Native)
    Cooling
    HP Cool Sene v.1
    Internet Speed
    Broadband (Cable)
    Browser
    IE 11 & Firefox Nightly28.0a1
    Other Info
    Intel Wireless Display
    Bluetooth 4.0
MKeezy, thank you. I checked on update K3065822 and it is an important security update mostly having to do with IE. I am not going to remove it even though I do not use MSIE. Can you tell me what "hash mismatch" indicates? Thanx again for your thorough post(s). :)
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
Dorrin Birch said:
MKeezy, thank you. I checked on update K3065822 and it is an important security update mostly having to do with IE. I am not going to remove it even though I do not use MSIE. Can you tell me what "hash mismatch" indicates? Thanx again for your thorough post(s). :)
Click to expand...


A hash mismatch typically happens when your systems registry calls for one particular update package to be needed and installed , but somehow a different update other than the one that was called for gets installed. The hash signature is an identifying string that your system's registry uses to ensure that ONLY the right items get installed on your specific system.

These has signatures typically can be found in the CBS and DISM log which pertain specifically to the item causing the issue. I'd make sure that you have al of the prerequisite updates which pertains to that update installed and more important that you have made sure that your browser has not been infected with a virus that could possibly change registry information about it.
 

My Computer

System One

  • OS
    Windows 8.1 Pro with Media Center © 2013 Version: 6.3.9600 Build 9600.16408
    System Manufacturer/Model
    HP Pavilion dv6t – 6100 CTO series Notebook PC LM328AV#ABA
    CPU
    Intel(R) Core(TM) I7-2720QM @ 2.20 GHz
    Motherboard
    unknown
    Memory
    8 GB
    Graphics Card(s)
    Intel HD + Radeon(TM) HD 6490M
    Sound Card
    IDT Beats Audio
    Screen Resolution
    1366 x 768 (Native)
    Cooling
    HP Cool Sene v.1
    Internet Speed
    Broadband (Cable)
    Browser
    IE 11 & Firefox Nightly28.0a1
    Other Info
    Intel Wireless Display
    Bluetooth 4.0
Thank you again, MKeezy. After reading again what update KB3065822 does, I think perhaps something was installed in this comprehensive update that does not pertain to my system, but I'm going to assume it will do no harm to ignore this particular unfixable file issue. Here is what MS states this update covers (not including the extensive list of files in different versions of MSIE that one can peruse at the link I've given at the bottom). I note the jsproxy.dll file is amongst those files listed for MSIE 11 and Windows 8.1 64-bit.

[h=1]MS15-065: Description of the security update for Internet Explorer: July 14, 2015[/h]
Update: KB3065822


[h=5]Summary[/h]
This security update resolves several reported vulnerabilities in Internet Explorer. The most severe of these vulnerabilities could allow remote code execution if a user views a specially crafted webpage in Internet Explorer. To learn more about the vulnerabilities, see Microsoft Security Bulletin MS15-065.

For more information about the other updates in this release, click the following article number to view the article in the Microsoft Knowledge Base: 3076321 MS15-065: Security Update for Internet Explorer: July 14, 2015
Additionally, this security update includes several nonsecurity-related fixes for Internet Explorer.


[h=5]How to obtain and install the update[/h]
[h=3]Method 1: Microsoft Update[/h]This update is available through Microsoft Update. When you turn on automatic updating, this update will be downloaded and installed automatically. For more information about how to turn on automatic updating, see Get security updates automatically.

Note For Windows RT and Windows RT 8.1, this update is available through Microsoft Update only.
[h=3]Method 2: Microsoft Download Center[/h]You can obtain the stand-alone update package through the Microsoft Download Center. Go to Microsoft Security Bulletin MS15-065 to find the download links for this update.
[h=5]More information[/h]
[h=3]Nonsecurity-related fixes that are included in this security update[/h]General distribution release (GDR) fixes

Individual updates may not be installed, depending on your version of Windows and the version of the affected application. You should view the individual articles to determine your update status.
KB articleTitle
3078175Internet Explorer 11 may crash when you drag the scroll box in a scroll bar control
3022771Authentication fails when you visit a website in Internet Explorer 11 through a proxy server
3078178Internet Explorer 11 or Internet Explorer 10 may crash when automation is used
3072449Installation of ActiveX controls may fail in Internet Explorer in Windows 8.1 or Windows 8
3071700Applications that host Internet Explorer 11 WebBrowser control may freeze when they use the sessionStorage


[h=3]File information[/h]The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files. [h=4]Windows Server 2003 file information[/h]
  • The files that apply to a specific milestone (SPn) and service branch (QFE, GDR) are noted in the "SP requirement" and "Service branch" columns.
  • GDR service branches contain only fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.
  • In addition to the files that are listed in these tables, this software update also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

https://support.microsoft.com/en-us/kb/3065822

If you feel the solutions for my particular issues have run their course and that this thread should be marked as closed, I will do so. Thank you to you and to everyone here who responded. This is a great forum. :thumbsup:
 

My Computer

System One

  • OS
    Windows 8.1 Pro
    Computer type
    Laptop
    System Manufacturer/Model
    HP ENVY TS 17 Notebook
    CPU
    2.40 gigahertz Intel Core i7-4700MQ
    Motherboard
    Board: Hewlett-Packard 1966 KBC Version 93.52
    Memory
    16318 Megabytes Usable Installed Memory
    Graphics Card(s)
    ntel(R) HD Graphics 4600 [Display adapter] NVIDIA GeForce GT 740M [Display adapter]
    Browser
    Firefox 39.0
    Antivirus
    Windows Defender
You must log in or register to reply here.
Back
Top