Main Forum > General Computer Support
propsys.dll error ... Solved !!
Boggin:
That doesn't bode well that an offboot sfc is unable to repair all files.
As the CBS.log is quite large and takes some trawling through, Windows has kindly provided a command whereby only the files it is unable to fix can be displayed.
Open a command prompt as an admin then copy & paste the following command -
findstr /c: "[SR]" %windir%\Logs\CBS\CBS,log >"userprofile%\Desktop\sfcdetails.txt
exit (to close the command window)
That command will put a file named sfcdetails.txt onto the desktop which you can attach and Shane will be able to advise on it.
If the system is irreparable then you're probably looking at a Repair or Clean install unless you can copy any corrupt files from the install disk.
A tutorial for that if you need it is at the end of OPTION THREE in http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Repair Install tutorial http://www.sevenforums.com/tutorials/3413-repair-install.html
With either of the installs you will need to back up your drivers folders from C:\Windows\System32 and have the product key at hand.
Belarc Advisor is a program which will list all product keys. http://www.belarc.com/free_download.html
Being in the UK, I'm 8hrs ahead of the Post time stamp.
Did you try the restore points ?
shawie60:
--- Quote from: Boggin on November 20, 2014, 02:41:38 pm ---That doesn't bode well that an offboot sfc is unable to repair all files.
As the CBS.log is quite large and takes some trawling through, Windows has kindly provided a command whereby only the files it is unable to fix can be displayed.
Open a command prompt as an admin then copy & paste the following command -
findstr /c: "[SR]" %windir%\Logs\CBS\CBS,log >"userprofile%\Desktop\sfcdetails.txt
exit (to close the command window)
That command will put a file named sfcdetails.txt onto the desktop which you can attach and Shane will be able to advise on it.
----> actually tried this earlier using findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt" (you'd missed the % out before userprofile but np) the thing is i've done it a number of times and the text file is always empty. That's why I finished up posting the original. So I'm open to suggestions as to why etc or how to cure it ...
If the system is irreparable then you're probably looking at a Repair or Clean install unless you can copy any corrupt files from the install disk. --- > considered these earlier but i was covering my bases to try and avoid that if possible.
A tutorial for that if you need it is at the end of OPTION THREE in http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html
Repair Install tutorial http://www.sevenforums.com/tutorials/3413-repair-install.html
With either of the installs you will need to back up your drivers folders from C:\Windows\System32 and have the product key at hand.
Belarc Advisor is a program which will list all product keys. http://www.belarc.com/free_download.html
Being in the UK, I'm 8hrs ahead of the Post time stamp.
Did you try the restore points ? ---> as I mentioned before for some reason the only restore points available are the ones I've made prior to trying anything. Not sure why there arnt earlier ones. Another point is I installed Aomei backup when i installed the system originally to make a scheduled backup periodically. That together with the scheduled virus scans had stopped. (one of the reasons I ran a full virus scan over the system initially) Anyways i really appreciate your advice and time. if anything else comes to mind please let me know. Obviously if i find out how to rectify this (or what caused it) I'll post and let you know.
many thanks
--- End quote ---
Boggin:
The reason I missed your earlier replies is because I'm not used to seeing them in the Quote and apologies for missing the % out.
I'm not sure why that desktop file isn't being created from the command.
Going back to your Post #3 regarding replacing the file, I've covered that in my last post which you could try - but I had problems with Permissions when following the sevenforums tutorial to replace a file I once had problems with.
Shane who has a greater understanding of system files, will be back sometime today and will advise you of the best course of action after going through the CBS.log - probably.
Shane:
shawie60, you are not doing the forum quotes properly, so your answer is in with the quote and I cant tell which is yours lol
But have you ran a chkdsk on the drive yet to see if it finds and corrects any files system problems? I know you said you did but did you run it and have it check for bad sectors?
chkdsk c: /r
Shane
shawie60:
--- Quote from: Shane on November 20, 2014, 11:45:20 pm ---shawie60, you are not doing the forum quotes properly, so your answer is in with the quote and I cant tell which is yours lol
But have you ran a chkdsk on the drive yet to see if it finds and corrects any files system problems? I know you said you did but did you run it and have it check for bad sectors?
chkdsk c: /r
Shane
--- End quote ---
apologies guys I thought it would make it easier addressing each reply in turn, obviously not, and yeah Shane scanned for both (usually do just to be thorough) even though the system is just over a year old .. I usually use chkdsk c: /f /r
glenn
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version