[SOLVED] SFCFix stating corrupted netfxperf.dll

M

MrOats

Member
Joined
Dec 12, 2015
Posts
7
I've been trying to fix my computer lately, IE disappeared recently and wouldn't reinstall (but it is fixed now). So far, I'm down to these two corruptions I believe are related to .NET Frameworks, assistance would be lovely :)

P.S I ran this with and without the Windows 7 Ultimate 32-Bit install DVD.
P.S.S I've also ran netfx-verifier tool on all detected .NET installations. No errors have been reported. It did say though in the logs for the "netfxperf.dll" had no version reported unlike all the other dlls' checked.

View attachment SFCFix.txt
 
Hi MrOats :)

My name is Aura and I'll be assisting you with your issue. Follow the instructions below please.

EndqYRa.png
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
    Spcusrh.png
    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;
    Code: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    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.
 
I will need to trim my CBS log as it is over 300 MBs. No need to have that much information in it. Will do the scan in an hour and a half here.
 
You can rename the CBS.log prior to running SFC, as I need all the information from the SFC scan in it.

88fYBWt.png
Rename CBS.log file
Follow the instructions below to rename your CBS.log file.
  • 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
    Spcusrh.png
    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;
    Code: 
    ren %windir%\Logs\CBS\CBS.log CBS_old.log
    Note: If it says that the file is actually in use, restart your computer and try the command again.
  • Once it's done, let me know;
 
Windows is being extremely finicky, both times (before and after a restart), the file was in use by another process. Resource Monitor didn't show what was using it unfortunately. I'm going to boot up a Linux Distro right now and rename it myself and run the scan. Will post results in an hour here.
 
Scan is done. Click Here for the CBS.log file (MediaFire).

Line 7384 - "POQ 292 ends." is where it starts mentioning the issue.

P.S Do you know what the deal is with the mass spam here (it's at the end of the file as well):

Code: 
2015-12-14 23:11:13, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] 
2015-12-14 23:11:13, Info                  CBS    Session: 30488311_77690679 initialized by client WindowsUpdateAgent. 
2015-12-14 23:11:13, Info                  CBS    Session: 30488311_77690680 initialized by client WindowsUpdateAgent.
 
The important part of the CBS.log is this:
Code: 
2015-12-14 23:08:41, Info                  CSI    00000521 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-directshow-vfw-capture_31bf3856ad364e35_6.1.7601.17514_none_d88590af85321bf2\vfwwdm32.dll do not match actual file [l:24{12}]"vfwwdm32.dll" :
  Found: {l:32 b:s+ioGLGWjJKkmLFdjgQwpcvEqwjDuZtVifGmgQK7djo=} Expected: {l:32 b:UhSibYtEH3pVQU3Ck1r2x224yNVfhnfal9GZQ8addl4=}
2015-12-14 23:08:41, Info                  CSI    00000522 [SR] Cannot repair member file [l:24{12}]"vfwwdm32.dll" of Microsoft-Windows-DirectShow-VFW-Capture, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-12-14 23:08:41, Info                  CSI    00000523 Hashes for file member \SystemRoot\WinSxS\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7601.17514_none_5ec9dfb2784680fc\netfxperf.dll do not match actual file [l:26{13}]"netfxperf.dll" :
  Found: {l:32 b:ckKqPItROGeq8uHBr3J+W9jBcPGDp+Xta47tOVKRE7U=} Expected: {l:32 b:niYsPKziA2OjfK1uQ4+idHoFazyrvKIxyJ/1ZhBUS8Y=}
2015-12-14 23:08:41, Info                  CSI    00000524 [SR] Cannot repair member file [l:26{13}]"netfxperf.dll" of NetFx-FW_NETFXPERF_DLL, Version = 6.2.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-12-14 23:08:41, Info                  CSI    00000525 Hashes for file member \SystemRoot\WinSxS\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7601.17514_none_5ec9dfb2784680fc\netfxperf.dll do not match actual file [l:26{13}]"netfxperf.dll" :
  Found: {l:32 b:ckKqPItROGeq8uHBr3J+W9jBcPGDp+Xta47tOVKRE7U=} Expected: {l:32 b:niYsPKziA2OjfK1uQ4+idHoFazyrvKIxyJ/1ZhBUS8Y=}
2015-12-14 23:08:41, Info                  CSI    00000526 [SR] Cannot repair member file [l:26{13}]"netfxperf.dll" of NetFx-FW_NETFXPERF_DLL, Version = 6.2.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-12-14 23:08:41, Info                  CSI    00000527 [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2015-12-14 23:08:41, Info                  CSI    00000528 Hashes for file member \??\C:\Windows\System32\netfxperf.dll do not match actual file [l:26{13}]"netfxperf.dll" :
  Found: {l:32 b:ckKqPItROGeq8uHBr3J+W9jBcPGDp+Xta47tOVKRE7U=} Expected: {l:32 b:niYsPKziA2OjfK1uQ4+idHoFazyrvKIxyJ/1ZhBUS8Y=}
2015-12-14 23:08:41, Info                  CSI    00000529 Hashes for file member \SystemRoot\WinSxS\x86_netfx-fw_netfxperf_dll_31bf3856ad364e35_6.2.7601.17514_none_5ec9dfb2784680fc\netfxperf.dll do not match actual file [l:26{13}]"netfxperf.dll" :
  Found: {l:32 b:ckKqPItROGeq8uHBr3J+W9jBcPGDp+Xta47tOVKRE7U=} Expected: {l:32 b:niYsPKziA2OjfK1uQ4+idHoFazyrvKIxyJ/1ZhBUS8Y=}
2015-12-14 23:08:41, Info                  CSI    0000052a [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:26{13}]"netfxperf.dll"; source file in store is also corrupted
2015-12-14 23:08:41, Info                  CSI    0000052b Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-directshow-vfw-capture_31bf3856ad364e35_6.1.7601.17514_none_d88590af85321bf2\vfwwdm32.dll do not match actual file [l:24{12}]"vfwwdm32.dll" :
  Found: {l:32 b:s+ioGLGWjJKkmLFdjgQwpcvEqwjDuZtVifGmgQK7djo=} Expected: {l:32 b:UhSibYtEH3pVQU3Ck1r2x224yNVfhnfal9GZQ8addl4=}
2015-12-14 23:08:41, Info                  CSI    0000052c [SR] Cannot repair member file [l:24{12}]"vfwwdm32.dll" of Microsoft-Windows-DirectShow-VFW-Capture, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-12-14 23:08:41, Info                  CSI    0000052d [SR] This component was referenced by [l:198{99}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7601.17514.WindowsFoundationDelivery"
2015-12-14 23:08:41, Info                  CSI    0000052e Hashes for file member \??\C:\Windows\System32\vfwwdm32.dll do not match actual file [l:24{12}]"vfwwdm32.dll" :
  Found: {l:32 b:s+ioGLGWjJKkmLFdjgQwpcvEqwjDuZtVifGmgQK7djo=} Expected: {l:32 b:UhSibYtEH3pVQU3Ck1r2x224yNVfhnfal9GZQ8addl4=}
2015-12-14 23:08:41, Info                  CSI    0000052f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-directshow-vfw-capture_31bf3856ad364e35_6.1.7601.17514_none_d88590af85321bf2\vfwwdm32.dll do not match actual file [l:24{12}]"vfwwdm32.dll" :
  Found: {l:32 b:s+ioGLGWjJKkmLFdjgQwpcvEqwjDuZtVifGmgQK7djo=} Expected: {l:32 b:UhSibYtEH3pVQU3Ck1r2x224yNVfhnfal9GZQ8addl4=}
2015-12-14 23:08:41, Info                  CSI    00000530 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:24{12}]"vfwwdm32.dll"; source file in store is also corrupted
This is what I needed to create a fix. And these [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE] lines are normal, they occur on every Windows system. Follow the instructions below please.

myjIXnC.png
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 SFCFix.zip and move the archive to your Desktop;
    Note: Make sure that the file is named SFCFix.zip, do not rename it.
  • Save any work you have open, and close every programs;
  • Drag the SFCFix.zip archive file over the SFCFix.exe executable and release it;
    mMabJGT.gif
  • 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;
SFCFix.zip
 
Yes please :)

EndqYRa.png
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
    Spcusrh.png
    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;
    Code: 
    sfc /scannow
    Note: There's a space between "sfc" and "/scannow";
  • Once the scan is complete, enter the command below and press on Enter
    Code: 
    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.
 
Came up with no errors on the terminal!
Sigh, it bothers me that this log fills up with space so quickly, in one day it jumped up 1.3 MB, imagine what size it will be in one year if it kept going like that? (Already about 474 MBs, what my original file was about!). It disappoints me that Windows doesn't rotate this log or keep it trimmed.

None the less, here is the CBS.log
 
The log gets compressed once it reaches a certain size, so you gain back the space :) It transforms itself in cbs.persist.log. You can delete these if you want. SFC returned a clean CBS.log, was there anything else? :)
 
Sounds good, I'm glad that is in place, I was worried for a second!

Nope, I am good now, thank you so much for your assistance! Have a great Christmas and New Year :) (We are going to switch to Windows 10 soon, so if anything goes wrong, I'm sure to come to here!).
 
No problem, you are welcome! :) Have a great Christmas and Happy New Year to you too MrOats! :)
 
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