SFC: amd64/x86 winsxs comsvcs.dll's corrupted

[ravenize]

Then it proceeded to change back again. Looks like these files are being edited.

 

[ravenize]

Oh on another note, I was confusing the file hashes that you provided me with 32 bit versions. My mistake there. THE HASHES of the files you provided me were already the same as the ones that I already had in the store, and in c:\windows\syswow64\comsvcs.dll. However the hash of c:\windows\syswow64\comsvcs.dll temporarly changed momentarily.

 

[ravenize]

Also I accidentally run sfcfix.exe without importing your file and it attempted repairing files just as I closed it. Perhaps this fixed the sfc errors. It usually does but they always return.

 

[ravenize]

Ok, now 15 minutes later sfc scannow detected errors yet again. Its always the same error, I will upload it again just so you will see that.

 

[ravenize]

God I've been confusing here. My apologies brother. The sfc scan before last, after running your file, and sfcfix.exe, resulted in sfc /scannow detecting NO errors. THEN the errors returned 15 minutes later out of the blue, as they usually do.

 

[ravenize]

Yes I ran exactly what you told me to.

 

[Sysnative Windows Update]

Do not multiple post. If you would prefer to fix the issue yourself, just let me know. Otherwise, follow my instructions and wait for my reply. Carry out the instructions on the link below:

How to Fix Hard Drive Problems with Chkdsk in Windows 7, 8, and 10

When this is done, use the following tool and post the results in your reply: Dropbox - ListChkdskResult.exe

 

[ravenize]

I've done this previously on all drives while performing sfc scans, even wiping free space in case of some hidden malware. It still did not fix the issue. No errors detected on c:.

 

[Sysnative Windows Update]

Run SURT and attach CheckSUR.log.

 

[ravenize]

Ive done this a dozen or more times since this issue arrised. Surt does not detect errors. Here are the logs from running surt moments ago.



=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2018-08-04 20:36


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist


Checking Packages


Checking Component Store


Summary:
Seconds executed: 115
No errors detected

 

[Sysnative Windows Update]

Run a fresh SFC Scan and let me know if the file is reported as corrupt. If it is, export your whole CBS folder and attach the link to it. Good night.

 

[ravenize]

Done. No errors. They will return shortly as usual. Sometimes it takes a while. It might take a day. It might take two weeks. Though the only time it took a week or two, was while running a folder monitor to detect changes to the suspect file. Oddly, no corruptions took place, till I stopped monitoring the file. I've run combofix, most top of the line standalone anti-rootkit software, malwarebytes, adwcleaner, hitman pro, zemana, unhackme with partizan, windows defender is enabled. No viri. (I will consider an offline scan) Though, like I said earlier, I caught the file when it had a completely different hash today. I had copied the file to another drive, with no uncertainty it was not the same hash as usual.

CBS folder.zip :: Free File Hosting - File Dropper: File Host for Mp3, Videos, Music, Documents.

 

[ravenize]

Run a fresh SFC Scan and let me know if the file is reported as corrupt. If it is, export your whole CBS folder and attach the link to it. Good night.

Ok after running surt then an sfc scan there was no error, however the error is back shortly after, as demonstrated running another sfc scan. Here is the folder. CBS.7z :: Free File Hosting - File Dropper: File Host for Mp3, Videos, Music, Documents.

 

[Sysnative Windows Update]

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.

 

[ravenize]

ok...

 

[Sysnative Windows Update]

Would you be willing to upgrade the machine to Windows 10?

 

[ravenize]

Not ATM but in due time. I would much rather fix the issue at its source.

 

[Sysnative Windows Update]

I need a fresh SFC Scan result + this:

Step#1 - Export SideBySide

1. Click on the Start button and in the search box, type regedit
2. When you see regedit on the list, right-click on it and select Run as administrator
3. When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
   
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
   
4. Once selected, click File > Export....
5. Change the Save as type: to Registry Hive Files (*.*)
6. Name this file SxS (with no file extension) and save it to your Desktop.

Once done please upload this file via a file sharing service of your choice and provide the link.

 

[ravenize]

ok... lets see if this worked.

 

[Sysnative Windows Update]

You forgot to include the CBS.log from the fresh SFC Scan I requested.