sfc /scannow is a windows function that looks though protected files to insure that they are the correct version and not corrupt. We have run though sfc /scannow and it did not fix the issue.

fltMgr.sys corrupt, how to replace?
Started by
avanti09
, Feb 18 2009 03:11 AM
#16
Posted 23 February 2009 - 08:53 PM

sfc /scannow is a windows function that looks though protected files to insure that they are the correct version and not corrupt. We have run though sfc /scannow and it did not fix the issue.
#17
Posted 23 February 2009 - 09:08 PM

Hi tuxman,
They determined that from the precise point where the system bluescreens, ie from the driver file that F-Secure needs to complete the update process. It installs, then during the dozen or so updates it does to be completely up-to-date, at the last one, which is I believe F-Secure Control Manager, that's where it bluescreens. And according to them, at that point is where F-Secure connects with (or whatever the term is) the fltmgr.sys driver.
Thanks,
They determined that from the precise point where the system bluescreens, ie from the driver file that F-Secure needs to complete the update process. It installs, then during the dozen or so updates it does to be completely up-to-date, at the last one, which is I believe F-Secure Control Manager, that's where it bluescreens. And according to them, at that point is where F-Secure connects with (or whatever the term is) the fltmgr.sys driver.
Thanks,
#18
Posted 23 February 2009 - 09:39 PM

avanti09,
Lets check to see if any files were not able to be repaired by sfc /scannow. To to do that.
1. Open an elevated command prompt.
2. Type the following command, and then press ENTER:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
Go ahead and post the results for sfcdetails.txt
Lets check to see if any files were not able to be repaired by sfc /scannow. To to do that.
1. Open an elevated command prompt.
2. Type the following command, and then press ENTER:
findstr /C:"[SR] Cannot repair member file" %windir%\logs\cbs\cbs.log >sfcdetails.txt
Note The Sfcdetails.txt file contains details from every time that the System File Checker tool has been run on the computer. The file includes information about files that were not repaired by the System File Checker tool. Verify the date and time entries to determine the problem files that were found the last time that you ran the System File Checker tool.
Go ahead and post the results for sfcdetails.txt
#19
Posted 23 February 2009 - 09:59 PM

Hi, I've tried that a couple times, and nothing happens. I don't even get another c prompt.
#20
Posted 23 February 2009 - 10:27 PM

If you do not get another c prompt then it is currently working on creating the log. Once you get the c prompt you will need to look for the sfcdetails.txt and paste the information here.
Similar Topics
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
As Featured On:






