[SOLVED] Windows Update is slow/non-repsonsive. SFC reports unrepairable errors.

[Weetje]

Hello,

Normally, I'm able to figure out Windows problems myself, but I'm kinda stuck.

I'm dealing with the laptop of my girl-friend, and it is very slow with Windows Update. "Searching for updates" ran forever. I ran the Windows Update Diagnostic file from Microsoft, and it repaired some things. And then I could do some updates. But after a restart, Windows Update is still slow, and slows down the entire machine. Running the diagnostic tool again let to the same repair as before.

So I ran sfc /scannow and it reported two corrupt files. It involved two files:

- CNBJ2530.DPB and prncacla.inf. I ran sfcfix as indicated in this thread: https://www.sysnative.com/forums/wi...prncacla-inf-corruptions-windows-8-8-1-a.html. Yesterday when I ran it, it said it repaired, but after running sfc /scannow again, the error still appeared. Today, I disabled Windows update (the laptop became a lot quicker), ran sfcfix again, and seems to have been repaired.

- Another error around invagent.dll is still there though.

I added the cbs.log and the sfcfix.txt.

I hope you are able to help out.

Weetje

 

[zcomputerwiz]

Hi there Weetje,

I'd like to take a look at the components hive. It looks like there are two updates that are conflicting for the version of that file.

Please manually upload the components hive by following these instructions:

Upload Components Hive

1. Navigate to C:\Windows\System32\config
2. Right-click on the current COMPONENTS file and select copy
   Note: If you get an error that the file is in use, reboot your computer and then try again.
3. Right-click on your Desktop and select paste
4. Right-click on the COMPONENTS file on your Desktop and select Send To -> Compressed (zipped) Folder
5. Upload the zip from your Desktop to a file sharing service such as DropBox, OneDrive, SendSpace, etc. and include the link with your reply.

 

[Weetje]

Thanks zcompterwiz!

In the meantime I did follow the procedure on http://wu.krelay.de/en/ to get Windows Update running more smoothly again. Apparently it was still having trouble finding the right files. After the manual update, Windows Update found a couple of important updates, and after the manual update they installed fine. It also seems everything is working more smoothly now, but I haven't been testing extensively (it is my girl's laptop).

Anyway, after a renewed sfc /scannow, the error on invagent.dll has stayed.

I zipped the components hive, and uploaded it on dropbox:
Dropbox - components.zip

Thanks again!
Weetje

 

[zcomputerwiz]

2017-01-30 14:56:35, Info                  CSI    0000014e Hashes for file member \??\C:\WINDOWS\System32\invagent.dll do not match actual file [l:24{12}]"invagent.dll" :
  Found: {l:32 b:xOpHteZMwNmkFgWBpxdRCnG5ybC2Q/Kcxh+1ZeH7RHM=} Expected: {l:32 b:iWgm+g91Ipr1hs3jhOiZUoOUYg97OI4FcPE9W8T/m8M=}
2017-01-30 14:56:35, Info                  CSI    0000014f [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\WINDOWS\System32"\[l:24{12}]"invagent.dll" from store
2017-01-30 14:56:35, Info                  CSI    00000150 WARNING: File [l:24{12}]"invagent.dll" in [l:46{23}]"\??\C:\WINDOWS\System32" switching ownership
    Old: Microsoft-Windows-Application-Experience-Inventory, Version = 6.3.9600.17647, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    New: Microsoft-Windows-Application-Experience-Program-Data, Version = 6.3.9600.18161, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral

Please try uninstalling kb2976978, then restart and run SFC again.
When SFC has completed, zip and attach C:\Windows\Logs\CBS\CBS.log with your reply.

 

[Weetje]

Thanks zcomputerwiz!

I uninstalled the update kb2976978 and ran sfc again.

It reported an error that it was able to repair. The logfile shows indeed one repair as far as I can tell, of invagent.dll, which was reporting the inconsistent hash before the uninstall. So it seems fixed!

2017-02-07 23:51:22, Info CSI 0000096d [SR] Repairing 1 components
2017-02-07 23:51:22, Info CSI 0000096e [SR] Beginning Verify and Repair transaction
2017-02-07 23:51:22, Info CSI 0000096f [SR] Repairing corrupted file [ml:520{260},l:46{23}]"\??\C:\WINDOWS\System32"\[l:24{12}]"invagent.dll" from store
2017-02-07 23:51:23, Info CSI 00000970 [SR] Repair complete
2017-02-07 23:51:23, Info CSI 00000971 [SR] Committing transaction
2017-02-07 23:51:23, Info CSI 00000972 Creating NT transaction (seq 6), objectname [6]"(null)"
2017-02-07 23:51:23, Info CSI 00000973 Created NT transaction (seq 6) result 0x00000000, handle @0x1364
2017-02-07 23:51:23, Info CSI 00000974@2017/2/7:22:51:23.728 Beginning NT transaction commit...
2017-02-07 23:51:23, Info CSI 00000975@2017/2/7:22:51:23.825 CSI perf trace:
CSIPERF:TXCOMMIT;95579
2017-02-07 23:51:23, Info CSI 00000976 [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

I see many appl-lines though, which make the log file large.

 

[zcomputerwiz]

Great!

I'll mark the thread solved. Please post back if you encounter any problems and I'll continue to assist you.