Jump to content

Welcome to Geeks to Go - Register now for FREE

Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!

How it Works Create Account
Photo

fltMgr.sys corrupt, how to replace?


  • Please log in to reply

#16
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
How did they come to the conclusion that fltmgr.sys is corrupt?

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.
  • 0

Advertisements


#17
avanti09

avanti09

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
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,
  • 0

#18
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
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
  • 0

#19
avanti09

avanti09

    Member

  • Topic Starter
  • Member
  • PipPip
  • 11 posts
Hi, I've tried that a couple times, and nothing happens. I don't even get another c prompt.
  • 0

#20
anzenketh

anzenketh

    BSOD Warrior/Computer Surgeon

  • Technician
  • 2,854 posts
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.
  • 0






Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP