SFC cannot repair file: file cannot be decompressed

M

mje

Member
Joined
Oct 4, 2014
Posts
7
The system I am currently running was rescued from a dying HDD and, as such, some files were corrupted in the process. I could repair most of the damage using dism and SFC, but there is a problem I can't get rid of:
Some of the corruptions affected the payloads used by sfc, and while I could repair them, something is still affecting the Windows Feature ".NET Framework 3.5 (includes .NET 2.0 and 3.0)"

The files themselves are not corrupted, as their hashes matches those of the installation media, however SFC insists on repairing the files and failing with the message "file cannot be decompressed", like shown below:
Code: 
2014-10-04 03:04:45, Error                 CSI    000008b1 (F) Failed on regenerating file [l:34{17}]"InstallCommon.sql"[gle=0x80004005]
2014-10-04 03:04:45, Info                  CSI    000008b2 [SR] Cannot repair member file [l:34{17}]"InstallCommon.sql" of NetFx-ASPNET_COMMON_SQL, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
2014-10-04 03:04:45, Info                  CSI    000008b3 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx2-OC-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.NetFx2"
2014-10-04 03:04:45, Error                 CSI    000008b5 (F) Failed on regenerating file [l:58{29}]"DefaultWsdlHelpGenerator.aspx"[gle=0x80004005]
2014-10-04 03:04:45, Info                  CSI    000008b6 [SR] Cannot repair member file [l:58{29}]"DefaultWsdlHelpGenerator.aspx" of NetFx-ASPNET_DEFWSDLHLPGEN, Version = 6.3.9600.16384, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope neutral, PublicKeyToken = {l:8 b:b03f5f7f11d50a3a}, Type neutral, TypeName neutral, PublicKey neutral in the store, file cannot be decompressed
2014-10-04 03:04:45, Info                  CSI    000008b7 [SR] This component was referenced by [l:162{81}]"Microsoft-Windows-NetFx2-OC-Package~31bf3856ad364e35~amd64~~6.3.9600.16384.NetFx2"

Things that I know/tested:

  • dism reports no problems in component store
  • files are not corrupt, however its replacement might be, or whatever place it is "decompressed" from (?)
  • InstallCommon.sql hash: 4f410c5aab8089eaeaa8e9d99a0f9a9f07c688a8
  • DefaultWsdlHelpGenerator.aspx hash: 9d3471806cf6912056d21c9131713d2425c8a72a
  • Turning off ".NET Framework 3.5 (includes .NET 2.0 and 3.0)" and running another SFC scan shows that everything is OK, re-enabling makes the problem return.

This error is not causing any problems as of now but I fear it might cause issues in the future in case I need to repair something or maybe install updates.
I could turn off the feature but that might cause problems for applications that require .net 2.x or 3.x. I'm not sure which apps would need that, maybe I'll test that later.

Any tips?

I am running Windows 8.1 Pro x64

SFCFix results:
Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-10-04 02:04:22.411
Not using a script file.




AutoAnalysis::
CORRUPT: C:\WINDOWS\winsxs\amd64_netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.3.9600.16384_none_e1e326934045dae2\InstallCommon.sql
CORRUPT: C:\WINDOWS\winsxs\x86_netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.3.9600.16384_none_29905d6a54c203e8\InstallCommon.sql
CORRUPT: C:\WINDOWS\winsxs\amd64_netfx-aspnet_defwsdlhlpgen_b03f5f7f11d50a3a_6.3.9600.16384_none_0bf3267afb4a57b1\DefaultWsdlHelpGenerator.aspx
CORRUPT: C:\WINDOWS\winsxs\x86_netfx-aspnet_defwsdlhlpgen_b03f5f7f11d50a3a_6.3.9600.16384_none_53a05d520fc680b7\DefaultWsdlHelpGenerator.aspx


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
   CBS & SFC total detected corruption count:     -5
   CBS & SFC total unimportant corruption count:  0
   CBS & SFC total fixed corruption count:        0
   SURT total detected corruption count:          0
   SURT total unimportant corruption count:       0
   SURT total fixed corruption count:             0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-10-04 02:34:09.277
----------------------EOF-----------------------
 
Welcome to Sysnative,

I'm sorry to report that this issue is currently one that we are not 100% sure how to resolve... This has been appearing on many Windows 8 machines recently, and we're still unsure of that exact cause of the problem.

What we do know is that Windows 8 introduces a new system for compressing the winsxs folder and SFC doesn't seem to like it. What's also interesting is some testing with the new Windows 10 build shows this same issue out of the box with a clean install on two systems. Now that is very odd indeed, but slightly off topic from your issue here.

In your scenario, it seems that SFC is expecting to find compressed files, but the files on your computer have not been compressed. It's interesting (and very useful) to know that it seems to be related to the .NET frameworks, because those errors are the same as a few other cases I've seen.

Let's see if we can find out the current state of the winsxs folder from DISM:

Command Prompt

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore

  4. Right-click on the Command Prompt window and click Select All, this will invert all of the colours by selecting the text, now press enter. All of this text is now copied.
  5. Paste (Ctrl+V) it into your next post please.

Regards,
Stephen
 
Thank you for the quick reply, Stephen. Sorry I'm not always at the computer, so I'll not be able to reply instantly most of the time.

I understand this is an uncommon error, as I could only find very limited information on the Internet unfortunately.

It is odd my component store seems clean, despite the ludicrous size. dism /scanhealth also reports 'No component store corruption detected.'
That's why this error is bugging me.

I also tried downloading the package and reinstalling from there in an attempt to refresh these files from the installer, but it only tells me to use 'Turn Windows Features on or off' screen...

One thing to note is that the component store is working as intended for everything else, since I got some replaced files after I disabled Hyper-V recently (apparently this is common: Disabling Hyper-V causes corruption)
Code: 
2014-10-04 03:04:21, Info                  CSI    000008ad [SR] Repairing corrupted file [ml:520{260},l:82{41}]"\??\C:\WINDOWS\System32\driverstore\en-US"\[l:34{17}]"wvms_vspp.inf_loc" from store
2014-10-04 03:04:21, Info                  CSI    000008ae [SR] Repairing corrupted file [ml:520{260},l:74{37}]"\??\C:\WINDOWS\System32\drivers\en-US"\[l:32{16}]"vmswitch.sys.mui" from store
2014-10-04 03:04:21, Info                  CSI    000008af [SR] Repairing corrupted file [ml:520{260},l:82{41}]"\??\C:\WINDOWS\System32\driverstore\en-US"\[l:30{15}]"wvms_pp.inf_loc" from store

Output from dism /online /cleanup-image /analyzecomponentstore:

Code: 
C:\WINDOWS\system32> dism /online /cleanup-image /analyzecomponentstore

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 6.58 GB

Actual Size of Component Store : 6.48 GB

    Shared with Windows : 4.68 GB
    Backups and Disabled Features : 778.91 MB
    Cache and Temporary Data : 1.03 GB

Date of Last Cleanup : 2014-10-04 00:04:07

Number of Reclaimable Packages : 0
Component Store Cleanup Recommended : No

The operation completed successfully.

PS: this message sometimes appears in the log. I don't know if that helps in your research.
I'll attach the logfile just in case.
Code: 
2014-10-04 03:04:45, Error                 CSI    000008b4@2014/10/4:06:04:45.902 (F) base\wcp\library\delta_library.cpp(287): Error NTSTATUS_FROM_WIN32(ERROR_INVALID_DATA) originated in function Windows::Rtl::DeltaDecompressBuffer expression: g_pfnApplyDeltaB(( (DELTA_FLAG_TYPE)0x00000000 ), ReferenceInput, CompressedInput, &UncompressedOutput)
[gle=0x80004005]
 

Attachments

Hi,

Don't worry about not getting back instantly, it's not a problem.

Can you please run SFC for me once more, and then follow these instructions straight after to upload your CBS folder and COMPONENTS hive to me for analysis.

SFCFix CBS & COMPONETS Collection

  1. Download SFCFix.exe using the following link and save the tool to your Desktop: [sfcfixdownload]Download SFCFix[/sfcfixdownload]
  2. Download SFCFixScript.txt and save this to your Desktop as well: https://dl.dropboxusercontent.com/u...lect/CBS and COMPONENTS/SFCFixScript.txt?dl=1
  3. On your Desktop, you should now see two files: SFCFix.exe and SFCFixScript.txt.
  4. Drag the file SFCFixScript.txt onto the file SFCFix.exe and release it.
  5. SFCFix will now begin to upload your CBS logfiles and COMPONENTS hive to our server.


Regards,
Stephen
 
Hello.

I somewhat screwed up this step. After downloading the files, I ran the utility and at the very end I noticed that I forgot to run SFC before that.
So I let it finish first, ran SFC as usual, then rerun the utility once more. I don't know if I ended up with two uploads, the utility doesn't tell.

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-10-06 00:30:07.568
Using .txt script file at C:\Users\Mario\Desktop\SFCFixScript.txt [0]




Collect:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-10-06 00:41:39.595
----------------------EOF-----------------------
 
Thanks for those, I'll take a look at them when I get some free time tomorrow evening and get back to you as soon as I can.

-Stephen
 
Hello mje, and welcome to Sysnative!

Since as we said above this is a rare problem, and that we haven't fixed one before, that means you've got the benefit of every analyst in town working on your thread. So you've got me too :) And Tom. And a bunch of others as well! How exciting :p



I need one further piece of information before I can set to work analysis all of the registry & file system data to see what's out of place - a report on exactly what's going on at the file system level for those components. It's time to dig out SFCFix again, but this time you get to use one of the rare analysis features.

Download SFCFix.exe and save this to your Desktop: https://www.sysnative.com/forums/downloads/sfcfix/
Download the SFCFixScript.txt file attached to this post, and save it to your Desktop also.

Go to your Desktop and single click on SFCFixScript.txt, drag it on top of SFCFix.exe, and release.

SFCFix will open and get that extra information about the files in question. Once it has finished (~5-10 minutes), it will open a logfile. Please copy and paste the logfile into your next post.

We'll then endeavour to get back to you as quickly as possible, but it may take 2-3 days because we need to carefully examine and discuss the data before coming back to you.

Richard
 

Attachments

That's good to hear. I don't have high expectations on fixing this issue but I hope it helps improving this utility, I see it helped a lot of people.

Code: 
SFCFix version 2.4.1.0 by niemiro.
Start time: 2014-10-07 21:36:20.879
Using .txt script file at C:\Users\Mario\Desktop\SFCFixScript.txt [1]




FileScan::
[0: 1] C:\Windows\SoftwareDistribution\Download\0f4baa14acbc19075e5415072eedbc1f\x86_netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.3.9600.16384_none_29905d6a54c203e8\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[1: 1] C:\Windows\SoftwareDistribution\Download\0f4baa14acbc19075e5415072eedbc1f\x86_netfx-aspnet_defwsdlhlpgen_b03f5f7f11d50a3a_6.3.9600.16384_none_53a05d520fc680b7\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: 7eOIHMsqL64mU8lPXtrMdyBw8iT4TvBrOYdbSu4P+8c=
 Version number not available.
Trace not available.



[2: 1] C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[3: 1] C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[4: 1] C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: o4on0xbyRxkVeSUSG4e9NIjftD4c0JBopOceNNlub4U=
 Version number not available.
Trace not available.



[5: 1] C:\Windows\Microsoft.NET\Framework\v4.0.30319\Config\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: o4on0xbyRxkVeSUSG4e9NIjftD4c0JBopOceNNlub4U=
 Version number not available.
Trace not available.



[6: 1] C:\Windows\WinSxS\x86_netfx4-defaultwsdlhelpgenerator_aspx_b03f5f7f11d50a3a_4.0.9600.16384_none_a00237ef6275fb33\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: dLqXIvV6EprXOF+7zxV3Y4zLtFmqO1qhlTBmfBfKg+A=
 Version number not available.
Trace not available.



[7: 1] C:\Windows\WinSxS\amd64_netfx4-defaultwsdlhelpgenerator_aspx_b03f5f7f11d50a3a_4.0.9600.16384_none_585501184df9d22d\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: dLqXIvV6EprXOF+7zxV3Y4zLtFmqO1qhlTBmfBfKg+A=
 Version number not available.
Trace not available.



[8: 1] C:\Windows\WinSxS\x86_netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.3.9600.16384_none_29905d6a54c203e8\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[9: 1] C:\Windows\WinSxS\x86_netfx-aspnet_defwsdlhlpgen_b03f5f7f11d50a3a_6.3.9600.16384_none_53a05d520fc680b7\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: 7eOIHMsqL64mU8lPXtrMdyBw8iT4TvBrOYdbSu4P+8c=
 Version number not available.
Trace not available.



[10: 1] C:\Windows\WinSxS\amd64_netfx-aspnet_common_sql_b03f5f7f11d50a3a_6.3.9600.16384_none_e1e326934045dae2\InstallCommon.sql
File is untraceable.
 Found: SWQmIf9gigYEvDMrrAc3kl0tX94qdWHoc+R8RNizqdI=
 Version number not available.
Trace not available.



[11: 1] C:\Windows\WinSxS\amd64_netfx-aspnet_defwsdlhlpgen_b03f5f7f11d50a3a_6.3.9600.16384_none_0bf3267afb4a57b1\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: 5nHfpJ22Wm9hL5sP6fRi9pDvjE5eUgOJF6FKsHiwgq4=
 Version number not available.
Trace not available.



[12: 1] C:\Windows\Microsoft.NET\Framework\v2.0.50727\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[13: 1] C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: 7eOIHMsqL64mU8lPXtrMdyBw8iT4TvBrOYdbSu4P+8c=
 Version number not available.
Trace not available.



[14: 1] C:\Windows\Microsoft.NET\Framework64\v2.0.50727\InstallCommon.sql
File is untraceable.
 Found: R6tfjNFXy+afZDVuyD5r0Vun2SciD9awi3r3uqUMYLM=
 Version number not available.
Trace not available.



[15: 1] C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\DefaultWsdlHelpGenerator.aspx
File is untraceable.
 Found: 7eOIHMsqL64mU8lPXtrMdyBw8iT4TvBrOYdbSu4P+8c=
 Version number not available.
Trace not available.



[16: 1] C:\Windows\WinSxS\x86_netfx4-installcommon_sql_b03f5f7f11d50a3a_4.0.9600.16384_none_5ab35e20bf512c14\InstallCommon.sql
File is untraceable.
 Found: SWQmIf9gigYEvDMrrAc3kl0tX94qdWHoc+R8RNizqdI=
 Version number not available.
Trace not available.



[17: 1] C:\Windows\WinSxS\amd64_netfx4-installcommon_sql_b03f5f7f11d50a3a_4.0.9600.16384_none_13062749aad5030e\InstallCommon.sql
File is untraceable.
 Found: SWQmIf9gigYEvDMrrAc3kl0tX94qdWHoc+R8RNizqdI=
 Version number not available.
Trace not available.
FileScan:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.1.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2014-10-07 21:36:21.876
Script hash: EDLXMdtPUNP9AyOc80uuuaYh+ojPOgs0xNCHkcPfjbA=
----------------------EOF-----------------------
 
Hello again :)

The good news is that we're pretty confident we've found the problem. Some of your winsxs directories and projections are tied in a pretty little knot, and it's no wonder SFC is getting confused. This should be perfectly fixable - we'll just delete them and remake them as they should be, make sure the registry is aligned with what we've set, and hopefully you'll be all good to go.

But before diving in headfirst I'm just making a few final checks and tests.

The bad news is that I'm away this weekend. I am genuinely sorry that your thread happened to coincide with the one weekend of the year I'm away, but it can't be helped and I don't really have any time at the moment as I've got lots of packing and organising to do.

So, can I please request that I return to this on Monday? Once again, I am very sorry that this is being dragged out, but I want to take the time to make a careful repair on Monday or Tuesday rather than rushing one out now.

Richard
 
I'm glad to hear that.
Don't worry about the time frame, as I said before, the corruption is not causing problems per se. I just don't want to leave the corruption in its current state, as it might or might not cause problems in future updates or repairs.
It's just I don't like to deal with possibilities with data integrity.

Do what you have to do and I'll keep this thread on tabs by email. I thank you for all the effort you've put so far, and please do not feel obliged on this resolution since that's not my intention here. I've learned a great deal about many things so far with this, and if I get it fixed is just another plus.

Oh, and I'm not sure I get what you meant by
make sure the registry is aligned with what we've set
Click to expand...
You mean the registry hive? Or winsxs store? I'm not sure about keeping it aligned either.

-- Mario J.
 
Hi,

Sorry for the extended delay - this has been a very troublesome problem to find a solution for but we think we've finally cracked it!

If you still need assistance, let me know.

Stephen
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top