📎 AI Summary:
The thread discusses a Windows 7 user facing a system boot failure caused by a missing or corrupt driver (fltsrv.sys) after updates and repair mode failures. The original poster seeks help to resolve the issue without performing a full repair install, citing the challenges of reinstalling drivers and updates, but has a recent backup as a potential restore point. Responders suggest troubleshooting steps and links, with one mentioning Windows 7’s built-in Startup Repair as an alternative solution. Overall, the sentiment is seeking cautious troubleshooting options to avoid extensive reinstallation work.

Ninethe

Extraordinary Member
Member details
Joined
Nov 17, 2012
Messages
69
Thread Author #1
I ran into a problem booting 64-bit Windows 7 Pro on another computer. I'd applied the September updates, but since I use it so seldom, I stupidly failed to create a full backup, and so my most recent is from mid-July. :o

It was running perfectly when I last shut it down, but when I tried to boot the other day, it very, veryunfortunately dropped into system repair mode. That was so tragic because in all my years running Windows 7 (since it's release) on 9 different computers, Repair Mode has never done anything other than make my system worse! It's a horrible, horrible failure, because it tries to be "smart" but in reality it always makes the wrong decisions! :mad: But enough ranting...

I booted up another OS on that computer and confirmed that CHKDSK found no errors. I also confirmed that there was nothing wrong with the disk's MBR partition table. I tried to perform two system restores from two different restore points, but although both of them reported success, upon booting the infinitely evil Repair Mode ran both times. As part of it's diabolical plot to destroy operating systems, Repair Mode also apparently keeps whatever problems it supposedly finds to be Secrets of Satan, leaving us mere mortals with no clue as to how to overcome them (sorry, I guess I wasn't quite done ranting...)

Subsequently, I disabled Repair Mode in the BCD and booted again. Now that the Evil One did not run, I finally got an error message to work with...

Code:
File: \Windows\system32\DRIVERS\fltsrv.sys
Status: 0xc0000098
Info: Windows failed to load because a critical system driver is missing, or corrupt.

Would anyone be so kind as to help me deal with this issue?

I realize that one possible solution is a Repair Install. But I strongly and deeply wish to avoid that -- if at all possible -- because it's such an extreme PITA! Not only would I have to find and assemble all the latest drivers again (and believe me, some of them are exceedingly difficult to find again), but I'd have to re-download and re-apply all those Windows Updates, some of which damaged my system and had to be uninstalled again, but I don't remember which!

On the plus side, I do have that two month old full backup on an online disk (no recovery or restore tool needed), so I could potentially replace any missing or corrupt file from that backup.

What do you all think? I would be extremely grateful for your wisdom!!
 

kemical

Essential Member
Member details
Joined
Aug 28, 2007
Messages
36,163
Solution