Main Forum > General Computer Support
propsys.dll error ... Solved !!
Boggin:
Does chkdsk /f report the same file as corrupt in the chkdsk/Wininit log in Event Viewer ?
Those reports tend to make for easier reading.
Just wondering if leaving %userprofile%\Desktop out and just using findstr /c: "[SR]" %windir%\Logs\CBS\CBS.log >sfcdetails.txt would produce the edited file straight to Notepad.
The CBS.log was reporting a number of errors regarding the Windows Update Agent, so running the applicable System Update Readiness Tool may help with that. http://windows.microsoft.com/en-US/windows7/What-is-the-System-Update-Readiness-Tool
Not sure if updating the AMD drivers would help, but the latest Win 7 AMD graphics drivers installed from the auto detect was giving me a red hue for my HD6310 and I had to roll those back - although as your friend's is probably a newer build, you may not have that problem.
shawie60:
--- Quote from: Boggin on November 21, 2014, 02:53:24 am ---Does chkdsk /f report the same file as corrupt in the chkdsk/Wininit log in Event Viewer ?
Those reports tend to make for easier reading.
Just wondering if leaving %userprofile%\Desktop out and just using findstr /c: "[SR]" %windir%\Logs\CBS\CBS.log >sfcdetails.txt would produce the edited file straight to Notepad.
The CBS.log was reporting a number of errors regarding the Windows Update Agent, so running the applicable System Update Readiness Tool may help with that. http://windows.microsoft.com/en-US/windows7/What-is-the-System-Update-Readiness-Tool
Not sure if updating the AMD drivers would help, but the latest Win 7 AMD graphics drivers installed from the auto detect was giving me a red hue for my HD6310 and I had to roll those back - although as your friend's is probably a newer build, you may not have that problem.
--- End quote ---
left out the %userprofile% and it made no difference I'm afraid. tried removing the original CBS.log from the logs folder and created a new one but still no joy, the txt file is empty. On a plus note there isnt as much info (basically 1 day) to wade through so I've included it here. Where exactly would I find the Wininit log in Event Viewer?
thanks glenn
Shane:
Well looking at the log shows that the backup oif the file is also corrupt.
--- Quote ---2014-11-21 11:24:40, Info CSI 00000328 Hashes for file member \??\C:\Windows\SysWOW64\propsys.dll do not match actual file [l:22{11}]"propsys.dll" :
Found: {l:32 b:g+OtbrV42A81wuBA60VuAa1TgpnRTXJqy6dD69WFWns=} Expected: {l:32 b:nf2cWLkCV8NNUrcVbB0lZr4y7nvUaZ3eFkpfGQ7E1Eo=}
2014-11-21 11:24:40, Info CSI 00000329 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-propsys_31bf3856ad364e35_7.0.7601.17514_none_2da67fa978cc211f\propsys.dll do not match actual file [l:22{11}]"propsys.dll" :
Found: {l:32 b:g+OtbrV42A81wuBA60VuAa1TgpnRTXJqy6dD69WFWns=} Expected: {l:32 b:nf2cWLkCV8NNUrcVbB0lZr4y7nvUaZ3eFkpfGQ7E1Eo=}
2014-11-21 11:24:40, Info CSI 0000032a [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\Windows\SysWOW64"\[l:22{11}]"propsys.dll"; source file in store is also corrupted
--- End quote ---
So lets find out if it is actually corrupt by comparing the hash from yours from one of my installs in vmware. What is the file version and size for the file on your system? I will then compare it to one of mine. I can also post a good file and have you manually replace it and we can see. :wink:
Shane
Shane:
OK I checked and these files off my windows 7 64 bit system match the hash that your sfc is looking for.
So you will want to replace each x86 one with the one from here and any x64 one with the other one I included as well. Right now the log only shows that the x86 version in the syswow64 folder is the one that is messed up. You can also use these files to compare to the ones you have :-)
Shane
Boggin:
And this is how to view the chkdsk/wininit report in Event Viewer http://www.sevenforums.com/tutorials/96938-check-disk-chkdsk-read-event-viewer-log.html
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version