This content has been marked as final. Show 14 replies
is it missing (or corrupt)? or is Windows confused about the fact?
perhaps you have some naughty software removing drivers, like system restore wink
The error message indicates that safeboot.sys (should be c:\windows\system32\drivers\safeboot.sys) is corrupted or missing, and Windows cannot be started.
Windows boot manager
Info: windows failed to load because a critical system driver is missing, or corrupt
We can get past pre-boot screen, but windows won't boot normally. Blank screen, no further errors.
When booting into Safe Mode, that's when we're presented with the above error message.
System Restore is switched off on all of our machines, so I think we can eliminate that. We've never seen anything like this before. We have SafeTech and WinTech disks in case we need to perform a recovery. Not sure that this will help though from what the gentleman above said.
Just let me know if you need any further infomation.
Thanks in advance for any advice or suggestions. :)
Well, we have a resolution... even though it is a bit of a mission to complete.
This is how we done it...
1. You'll need to get the safeboot.sys file off a working system onto a USB stick. (we used a file from the same version of SafeBoot... not sure if it'd work with a newer or older version.)
2. Use the SafeTech CDs to boot up on the affected machine. (Go->Programs->SafeBoot WinTech)
3. Authorize using the Daily Code.
4. Authenticate yourself against SBFS. (Or however you want really, that's just how I did it.)
5. Mount the USB drive. (Disk->Mount Drive)
6. Copy the file across to c:\windows\system32\drivers etc... (may be different if you're on different OS. We're using Vista.)
I appreciate I've been very brief there, so if you need any elaboration on any of the above points just let me know and I'll go into further detail.
it would indicate from your fix that windows was right - the file was missing (or corrupt) - did you check which before copying the file over?
you might want to get the client log from this machine to see if the client decided to remove the .sys file for some reason.
Yeah, the file was still there when we copied the new one across so there'd obviously been some corruption to the safeboot.sys file.
Not sure why this occured... any thoughts?
you'd need to diff the file with the original and see what had actually changed. The client log though is a good place to start looking.
I'm a bit puzzled on point 2 - what are these safetech CDs of which you speak? On our safeboot server theres a "programs/safeboot admin tools" , but no mention of wintech.
Is this an optional extra or something?
I asked my tech guys to try this, but no go. The weird thing is after they reinstall the OS on the laptop, the same error occurred. The laptop getting this error has the error "e0030009 - Error creating Endpoint Encryption File System host file" appearing in the log file as well.