SFC errors, many files "Cannot be decompressed"

[BooII]

Tekno Venus,

Was the issue in this thread officially resolved?
It appears not, as there was no response to your last query (just above) dated 11-27-2014 10:21 PM .
Hopefully it has been resolved and documented for future reference, as I have an identical problem that has existed on my system since January 2015.
My system is a Dell Inspiron 13-7347 '2-in-1' laptop running the 'Windows 8.1 Update 1' x64 operating system.
My system is fully functional for my needs in that it can from the Internet download, install, and run any and all third party (as well as Microsoft) applications.
What it CAN'T do is verify that my Windows system files are fully intact (error free) as when the 'sfc /scannow' command is executed it reports a corrupt registry database.
It must be a partial registry corruption as my system is fully functional in every other respect.
Also (apparently because of this corruption) it CAN'T install Windows updates.
A consequence of this my system is a year behind in keeping updates current.
The system is protected from malicious attacks as it is operating behind a router and is further protected with an Internet security suite (aka 'Comodo Internet Security Pro').
So bottom line is the computer is free of any and all malware as determined using 'CIS Pro'.

I have a current 'SFC Details' log available from running the 'sfc /scannow' command in an administrator command prompt window (last night).
I was patient and let it run (the command execution) to completion without any interruptions which took hours as the log will attest to.

Would you please take a look at it as I think this is similar (if not exactly identical) to the issue addressed in this thread?
And tell me if there is a documented solution to this issue that may well solve my system's problem.

Thanks.

Bernard

 

[BooII]

Re: SFC cannot repair file: file cannot be decompressed

Tekno Venus,

Forgot to include 'SFC Details' log file attachment in post dated 01-11-2016 05:54 PM (just above).

It is included in this follow-up post.

Bernard

 

[Aura]

Hi Bernard :)

My name is Aura and I'll be assisting you with your issue. We do indeed have a method to fix the "file cannot be decompressed" error. Follow the instructions below please.

System File Checker (SFC)
Follow the instructions below to run a SFC scan on your system and to provide the CBS log in your next reply;

• On Windows Vista & 7, click on the Windows Start Menu, then enter cmd in the search box, right-click on the cmd icon and select
  
  Run as Administrator
• On Windows 8, drag your cursor in the bottom-left corner, and right-click on the metro menu preview, then select Command Prompt (Admin);
• On Windows 8.1, right click on the Windows logo in the bottom-left corner and select Command Prompt (Admin);
• Enter the command below and press on Enter;
  

  sfc /scannow

  Note: There's a space between "sfc" and "/scannow";
• Once the scan is complete, enter the command below and press on Enter
  

  copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"

• A file called cbs.txt will have appeared on your Desktop. Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

Note: Please note that the CBS.log is volatile, which means that if you don't upload it after the SFC scan is completed, it won't have the information from the scan anymore. So archive it and upload it as soon as you can.

 

[BooII]

Hi Aura,

I think what your requesting is provided in my post dated 01-11-2016 8:03 PM.
It is just above your post dated Today 12:58 PM. (Today = 01-14-2016)
It (your request) is from the CBS log file taken immediately after the 'sfc /scannow' command execution completed.
It is titled 'sfcdetails.txt' instead of 'cbs.txt' per your request.
It looks like you viewed it, as there are now 2 views (and I know I viewed it once to see if it (the attachment) posted intact.
I definitely won't post the content of a file request directly into the body of a post as this clutters the post requiring extensive scrolling making it hard to read and comprehend.

I can run 'sfc /scannow' again and upload its output to one of the cloud storage sites if you prefer.
I think I used OneDrive when I was working with you before on this problem.
I may have used DropBox, but I know I didn't use Google Drive.

Is there a problem with me just attaching it as a file like I did in my post date 01-11-2016 8:03 PM?
Let me know your preferences.
I can adapt to make things easier for you.

Here is first error report of many duplicated in the 'sfcdetails' file.
Note red highlighted text.

----------
2016-01-10 19:19:48, Info CSI 000003c6 [SR] Verifying 100 (0x0000000000000064) components
2016-01-10 19:19:48, Info CSI 000003c7 [SR] Beginning Verify and Repair transaction
2016-01-10 19:20:12, Info CSI 000003ca [SR] Cannot repair member file [l:34{17}]"FrameworkList.xml" of Microsoft-Windows-NetFx3-Core, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
2016-01-10 19:20:23, Info CSI 000003d1 [SR] Cannot repair member file [l:34{17}]"FrameworkList.xml" of Microsoft-Windows-NetFx3-Core, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
2016-01-10 19:20:23, Info CSI 000003d2 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx3-OC-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.NetFx3"
2016-01-10 19:20:36, Info CSI 000003fd [SR] Verify complete
----------

If it's of any consequence the version of DISM used on my system is 6.3.9600.17031.
The version of 'Microsoft-Windows-NetFx3-Core' that could not be decompressed is 6.3.9600.16384.
Brought this to your attention in case this version difference mattered.

Bernard

 

[Aura]

I need the full CBS.log, and not the sfcdetails.txt that was created using only a part of the CBS.log :) This being said, can you follow the instructions I posted above, then upload the CBS.log on a cloud storage site (OneDrive is fine if you already use it) and post the download URL for me? I need it to get more information on the files we need to address.

 

[BooII]

Aura,

For some reason I keep losing this post before I get it posted.
This time I'll submit it instead of proof reading it.
Below is a link to my most current complete CBS log file under 'Public' folders of OneDrive, per your request.
I'm not sure it contains what your looking for, as its contents is mostly devoted to something titled 'TiLight'.
My second post to this thread pertains to multiple files that could not be decompressed, as per the subject title of this thread.
I won't pretend to know what your looking for as I don't.
Please let me know if this complete 'cbs.txt' file is what you need and indeed looking for to begin searching for a solution to my problem.
Also note there are two files in 'Public' folder of OneDrive.
Select the one that is posted today, Monday 01/18/16.
https://onedrive.live.com/redir?res...1498&authkey=!AEZPJXuNNRkhW4w&ithint=file,txt
Thanks for your replies and for initiating an investigation and hopefully finding a solution to this problem that has existed for almost a year now.

Bernard

 

[Aura]

It seems that I'll need to take a look at your COMPONENTS Hive. I'll create a fix for 10-15 entries, and if it works, I'll try to find a way to automate the creation of the fix for the remaining entries because otherwise I have to do all of them (over a hundred) manually.

Retrieving the COMPONENTS Hive
Follow the instructions below to retrieve your COMPONENTS Hive and send me it.

• Open your Windows Explorer, and navigate to the C:\Windows\System32\Config folder;
• In this folder, find the COMPONENTS file (there's no extension), and copy it to your Desktop;
  Note: If you receive an error message saying that the COMPONENTS file is in use, restart your computer and try again. If the error message persist, let me know.
• Right-click on it, and select Send to... and choose Compressed (zipped) folder;
• Upload the file on Dropbox, Google Drive or OneDrive and post the download URL for it here;

 

[BooII]

Aura,

Here's the URL for the zipped 'Components' file you requested.

https://onedrive.live.com/redir?res...1499&authkey=!AOeKBhIoBgjGcIc&ithint=file,zip

Bernard

 

[Aura]

Sorry for the delay. I made a SFCFixScript that will fix 8 of these errors to see if it works or not. Sadly, it isn't realistic to do that for all the hundreds of files you have to fix... A Repair Install will be needed in your case. Here.

SFCFix - Fix Time

WARNING! The following fix is specific to the user's system in this thread. No one else should follow the instructions below to apply that fix, as it could damage your system. If you need assistance with an issue, please start a new thread and someone will assist you shortly.

Follow the instructions below to download and execute a SFCFix fix, and provide the log.

• Download SFCFix and move the executable on your Desktop;
• Download the attached SFCFixScript.txt and move the file to your Desktop;
  Note: Make sure that the file is named SFCFixScript.txt, do not rename it.
• Save any work you have open, and close every programs;
• Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it;
  
  
• SFCFix will launch, let it complete;
• Once done, a file will appear on your Desktop, called SFCFix.txt;
• Open the file, then copy and paste its content in your next reply;

SFCFixScript.txt

 

[BooII]

Aura,

[Please read carefully and respond. Thank you.]

I'm still pursuing a resolution to my partially corrupt configuration database.

My system is FULLY functional EXCEPT for:

1) 'System File Check' finding some corrupt files it was unable to repair.

and

2) Windows Update unable to successfully download and install security and
recommended updates.

At bottom (between dashed lines) is the file that is requested to 'copy and paste'
to this post in response to niemiro's 'SFCFix Collect COMPONENTS' utility.

The file text (between dashed lines) apparently provides you date and time
information for locating the file on Sysnatives's server with the results (output) of
the 'SFCFix Collect COMPONENTS' utility.

From what I've read this utility uploads my CBS logfile to Sysnative's server.

I'm assuming from the utility's title name 'SFCFix Collect COMPONENTS' and the
utility's code that that it gleans (retrieves) from the CBS logfile the COMPONENTS
Hive.

Your post on 01-20-2016, 11:18 AM instructed me how to locate and provide you
with a copy of my system's 'COMPONENTS Hive'.

Which I provided at Microsoft service in my
01-21-2016, 03:47 AM post.

Are these COMPONENTS (the one from niemiro's 'SFCFix Collect
COMPONENTS' utility and your request for my 'COMPONENTS Hive' from my C:
\Windows\System32\Config folder) providing the same information?

The former was uploaded to Sysnative's server when I dragged 'SFCFixScript.txt'
onto 'SFCFix.exe'.

Can you provide me a copy of 'SFCFix Collect COMPONENTS' results that was
downloaded to Sysnative's server?

I haven't yet tried (used) your 'SFCFix - Fix Time' fix as you indicated your weren't
very optimistic in getting my registry repaired because of the number of files
needing repair.

The sheer number of bad 'sfcdetails' [SR] files listed seems overwhelming but
when taking a closer look it is seen many of the files are associated with '.NET
Framework' version download that cannot be decompressed.

Seems that if the reason for the many files of the '.NET Framework' download that
cannot be decompressed was solved then the problem wouldn't seem so
overwhelming.

'SFC Errors, Many Files Cannot Be Decompressed' is the title of this thread.

I'm not sure why all these '.NET Framework' files cannot be decompressed.

There is some association between the files that cannot be decompressed and the
report 'System File Check' gives that there is a configuration registry database
corruption.

It isn't known what that association is but suspect there is a connection between
the two.

The problem is not knowing which of the two to place emphasis on to yield a
solution.

One is cause (effect) and the other is result (affect).

So is the corrupt registry causing files that cannot be decompressed or is it files
that cannot be decompressed causing the corrupt registry?

The Windows operating system is very convoluted.

If everything is not JUST RIGHT there is a problem or one that looming (waiting) to
happen.

So Aura, if you can provide answers to my two questions it would be greatly
appreciated.

Just below is information needed to locate the 'SFCFix Collect COMPONENTS'
results I request.

----------
SFCFix version 2.4.9.2 by niemiro.
Start time: 2016-02-21 16:58:39.824
Microsoft Windows 8.1 Update 3 - amd64
Using .txt script file at C:\Users\Bernard Spaulding\Desktop\SFCFixScript.txt [2]

Collect:: directive completed successfully.

Successfully processed all directives.
SFCFix version 2.4.9.2 by niemiro has completed.
Currently storing 19 datablocks.
Finish time: 2016-02-21 17:03:11.527
----------------------EOF-----------------------
----------

Bernard

 

[Aura]

So Aura, if you can provide answers to my two questions it would be greatly
appreciated.

I'll be honest Bernard, the way you type makes it very, very hard for me to understand what you're asking. Are these your two questions?

1. Are these COMPONENTS (the one from niemiro's 'SFCFix Collect COMPONENTS' utility and your request for my 'COMPONENTS Hive' from my C:\Windows\System32\Config folder) providing the same information?
2. Can you provide me a copy of 'SFCFix Collect COMPONENTS' results that was downloaded to Sysnative's server?

Because I'm seeing a third one below....

3. So is the corrupt registry causing files that cannot be decompressed or is it files that cannot be decompressed causing the corrupt registry?

If so, here's your answers:

1. In order for me to answer that question, I would need to see what was the content of the SFCFixScript.txt used with SFCFix for the Collect:: directive. And your COMPONENTS Hive is indeed located in C:\Windows\System32\config\COMPONENTS.
2. I do not have access to the server SFCFix upload collected samples to. Richard (niemiro) does, so I would have to ask him.
3. Both. Because the files cannot be decompressed, a certain value for that file in the Registry needs to be changed in order for it to not be flagged as corruption anymore.