I need serious computer help

[Fire Yoshi]

Just the other day, I tried to update my oooold computer to the next service pack(Windows XP Service Pack 2.)  After the update finished, it asked me to restart my computer, did so.  After I tried logging back on, a black screen came up that said one of the files needed to start is either missing or corrupt.  How do I get my computer to log on again?

[TheRedFox8]

Ah. I encountered many problems like that. Give me the exact error message and I'll see what I can do for you.

It usually involves inserting the Windows CD and doing some console commands.

[Fire Yoshi]

Ah. I encountered many problems like that. Give me the exact error message and I'll see what I can do for you.

It usually involves inserting the Windows CD and doing some console commands.

"Windows could not start because of the following file is missing or corrupt:

System32DriversNtfs.sys"

[TheRedFox8]

Okay, try this.

To resolve this problem, replace the missing or corrupted Ntfs.sys file:[list type=decimal]

[*]Use the Windows XP startup disks or the Windows XP CD to restart your computer.

[*]When the "Welcome to Setup" screen appears, press R to select the To repair a Windows XP installation using Recovery Console, press R option.

[*]Type the number of the Windows installation that you want to access from the Recovery Console, and then press ENTER.

[*]    Type the administrator password when you are prompted, and then press  ENTER. If no administrator password exists, just press ENTER.

[*]At the command prompt, type the following commands (press ENTER after each command):cd windowssystem32drivers

ren ntfs.sys ntfs.oldNote This step renames the corrupted Ntfs.sys file to Ntfs.old. If the Ntfs.sys file is not found, the file is missing.

[*]At the command prompt, type the following command, and then press ENTER:copy cd:i386ntfs.sys drive:windowssystem32driversWhere cd is the drive letter for the CD-ROM drive that contains the Windows XP CD, and drive is the drive where you installed Windows XP.

[*]Remove the Windows XP CD from your CD-ROM drive, type quit at a command prompt, and then press ENTER to quit the Recovery Console.

[*]Restart the computer.

[Fire Yoshi]

Okay, try this.

To resolve this problem, replace the missing or corrupted Ntfs.sys file:[list type=decimal]

[*]Use the Windows XP startup disks or the Windows XP CD to restart your computer.

[*]When the "Welcome to Setup" screen appears, press R to select the To repair a Windows XP installation using Recovery Console, press R option.

[*]Type the number of the Windows installation that you want to access from the Recovery Console, and then press ENTER.

[*]    Type the administrator password when you are prompted, and then press  ENTER. If no administrator password exists, just press ENTER.

[*]At the command prompt, type the following commands (press ENTER after each command):cd windowssystem32drivers

ren ntfs.sys ntfs.oldNote This step renames the corrupted Ntfs.sys file to Ntfs.old. If the Ntfs.sys file is not found, the file is missing.

[*]At the command prompt, type the following command, and then press ENTER:copy cd:i386ntfs.sys drive:windowssystem32driversWhere cd is the drive letter for the CD-ROM drive that contains the Windows XP CD, and drive is the drive where you installed Windows XP.

[*]Remove the Windows XP CD from your CD-ROM drive, type quit at a command prompt, and then press ENTER to quit the Recovery Console.

[*]Restart the computer.

Alright, I have two problems withdoing that.

1. My computer didn't come with a windows XP disc...I don't think at least.  I read the user manual for my computer (which is a Compaq) and it said that this computer doesn't come with a recovery disc, or something.

2. Whenever I try runnung the recovery console, it asks for my password, just like you said.  I put my password in, and it says it's not valid.  Is the password it asks for the one you use to log in?  Because I tried typing that in, it just says that the password is invalid.  I even tried passwords that I had in the past, nothing.

[TheRedFox8]

So first thing is to figure out some way to get those Windows files or burn your own recovery disc. You need that file to copy. Remember, you need ANY Windows XP disc, not just the one that comes with any given computer. Maybe you can borrow one from a friend.

As for the password, just try hitting enter. There is a difference between the computer's Administrator (the one used to log into safe mode) and YOUR administrator account.

Hope that works for something.

[FoxMcCloud]

So first thing is to figure out some way to get those Windows files or burn your own recovery disc. You need that file to copy. Remember, you need ANY Windows XP disc, not just the one that comes with any given computer. Maybe you can borrow one from a friend.

As for the password, just try hitting enter. There is a difference between the computer's Administrator (the one used to log into safe mode) and YOUR administrator account.

By default the Administrator account in Windows XP is disabled, if you are able to enable it you can use a free Program that we security professionals use.

Also I believe that there is no password for safe mode. Your best bet is to boot into safe mode, then do a system restore.

Okay, try this.

To resolve this problem, replace the missing or corrupted Ntfs.sys file:[list type=decimal]

[*]Use the Windows XP startup disks or the Windows XP CD to restart your computer.

[*]When the "Welcome to Setup" screen appears, press R to select the To repair a Windows XP installation using Recovery Console, press R option.

[*]Type the number of the Windows installation that you want to access from the Recovery Console, and then press ENTER.

[*]    Type the administrator password when you are prompted, and then press  ENTER. If no administrator password exists, just press ENTER.

[*]At the command prompt, type the following commands (press ENTER after each command):cd windowssystem32drivers

ren ntfs.sys ntfs.oldNote This step renames the corrupted Ntfs.sys file to Ntfs.old. If the Ntfs.sys file is not found, the file is missing.

[*]At the command prompt, type the following command, and then press ENTER:copy cd:i386ntfs.sys drive:windowssystem32driversWhere cd is the drive letter for the CD-ROM drive that contains the Windows XP CD, and drive is the drive where you installed Windows XP.

[*]Remove the Windows XP CD from your CD-ROM drive, type quit at a command prompt, and then press ENTER to quit the Recovery Console.

[*]Restart the computer.

If you can get to a Command Prompt, you can do this:

You don't have to boot into repair mode to do so. If you can find any XP disk, then go to

Start -> Click Run -> After you click run, type in CMD.

A Black console screen will run type in the command  sfc /scannow

EDIT: I found this fix, it MIGHT work

Above all, try running a checkdisk if you can get to command prompt in safe mode. Administrator might have no password. Just hit enter to see if it works

That will run a checker so that you check OS Integrity.

Once you are able to boot into the safe mode

Do Start -> Run -> Type in CMD -> type in CHKDSK /R

This will do a repair on the hard-drive, and might fix your ntfs.sys error

2nd Edit: After more research

Did you have anymore data after the ntfs.sys? For example Page_fault_in_nonpaged_area?

[TheRedFox8]

Or you could do that, yes. I just remember my method worked before.

It was on my dad's computer, both parents were gone, and I restarted his computer because I plugged a keyboard back in. Something like this happened and I nearly panicked. Luckily I was able to fix it :P

[FoxMcCloud]

Interesting, I have never seen a keyboard cause an error like this, then again in all my years of computer repair and diagnosing, I still always see something new in the field. Thank the lord for Certifications and training to help people with this kind of stuff

Fire Yoshi is lucky to have us both :D

[Fire Yoshi]

By default the Administrator account in Windows XP is disabled, if you are able to enable it you can use a free Program that we security professionals use.

Also I believe that there is no password for safe mode. Your best bet is to boot into safe mode, then do a system restore.

If you can get to a Command Prompt, you can do this:

You don't have to boot into repair mode to do so. If you can find any XP disk, then go to

Start -> Click Run -> After you click run, type in CMD.

A Black console screen will run type in the command  sfc /scannow

EDIT: I found this fix, it MIGHT work

Above all, try running a checkdisk if you can get to command prompt in safe mode. Administrator might have no password. Just hit enter to see if it works

That will run a checker so that you check OS Integrity.

Once you are able to boot into the safe mode

Do Start -> Run -> Type in CMD -> type in CHKDSK /R

This will do a repair on the hard-drive, and might fix your ntfs.sys error

2nd Edit: After more research

Did you have anymore data after the ntfs.sys? For example Page_fault_in_nonpaged_area?

It won't let me do a system restore, it just brings me back to that error message when I try doing so.  And about the disk, my friend has a Windows XP disc, but it's for service pack 2, and it's for a DELL computer.  Mine is a Compaq.  Does this matter?

[FoxMcCloud]

It won't let me do a system restore, it just brings me back to that error message when I try doing so.  And about the disk, my friend has a Windows XP disc, but it's for service pack 2, and it's for a DELL computer.  Mine is a Compaq.  Does this matter?

No it does not matter, you will be able to use the disk on the Compaq. And even though it is a Service Pack 2 Disk, your computer is updated to Service Pack 2, so you should be all set.

[TheRedFox8]

Interesting, I have never seen a keyboard cause an error like this, then again in all my years of computer repair and diagnosing, I still always see something new in the field. Thank the lord for Certifications and training to help people with this kind of stuff

Fire Yoshi is lucky to have us both

The keyboard didn't cause the error. I restarted the computer because the keyboard wasn't hot-swappable (it won't instantly work when you plug it in). It gave me the error after I restarted.

And FireYoshi, he means by doing system restore AFTER you boot to safe mode using the Windows XP disk. Just restore it to a day before you installed SP2 since that seemed to cause the problem and try it again. If it breaks again, well... I don't know what to say :P

[FoxMcCloud]

Gotcha, ok. Darn PS/2 Keyboards

Hope our attempts to help you work. I have a final to go to, but I should be back later to help you out even more

[DZComposer]

If ntfs.sys is corrupt, he'll never get to safe mode or system restore without a Windows disc. That's the driver that tells Windows how to read NTFS partitions.

I would just do a repair install. If ntfs.sys is corrupt, no telling what else is. It will save you time, and if your source disc has SP2 on it, you'll be there when it finishes, as opposed to doing a System Restore which would leave your at SP1. Of course if you're on XP, you should be at SP3, so there's still that to do.

To repair install, tell the Windows Disc that you want to install Windows. It will then tell you it found an installation and will ask you if you want to repair it. Say yes. It will then re-install all of your Windows files.

If it DOESN'T give you that option, then it means your filesystem is likely hosed and a reformat would be your best option. I doubt that's the case, though, because if your filesystem were hosed it wouldn't even get to ntfs.sys.

[Fire Yoshi]

fireyoshibrett@hotmail.com

That's my email, one of you please add me to you contact list so we can instant message eachother while I do this.  It'll be a lot safer, I think.

[TheRedFox8]

If ntfs.sys is corrupt, he'll never get to safe mode or system restore without a Windows disc. That's the driver that tells Windows how to read NTFS partitions.

I would just do a repair install. If ntfs.sys is corrupt, no telling what else is.

And that is why we are telling him to boot using the disk. It's either that or trying to work with the Recovery console where you have to type in very specific commands that you don't know if it will even work.

I believe my dad had this problem before and we tried EVERYTHING. He ended up with a clean OS install. It didn't delete everything (just killing the registry and stuff like that), but it was a pretty tough blow, nonetheless.

[Fire Yoshi]

Okay I'm really confused...it's not recognizing any of those commands that you two are telling me to put in.  Could someone please just add me to their contanct list so you can guide me through this?  I already put my email on an earlier post(14)  I have a disk now btw

[DZComposer]

DO A REPAIR INSTALL. (and a Barrel Roll )

If one file is corrupted, it is likely many more are. Digging around in recovery console will waste time, and doing a system restore when you have a SP2 disc is taking a step backwards.

Here's a video tutorial on repair install. It's easy:

KNOQ0sCYY8s

EDIT: they neglected to mention that you need to press "F8" to get past the license agreement.

There are a few steps they don't show, but these steps consist of clicking "Next."

I can't IM from where I am right now, sorry.

[Fire Yoshi]

DO A REPAIR INSTALL. (and a Barrel Roll )

If one file is corrupted, it is likely many more are. Digging around in recovery console will waste time, and doing a system restore when you have a SP2 disc is taking a step backwards.

Here's a video tutorial on repair install. It's easy:

KNOQ0sCYY8s

EDIT: they neglected to mention that you need to press "F8" to get past the license agreement.

There are a few steps they don't show, but these steps consist of clicking "Next."

I can't IM from where I am right now, sorry.

Alrighty then! It's copying the files right now, I'll edit this post once it's done.

[TheRedFox8]

Have fun with it. Don't freak out if it appears you lost everything. Unless you formatted the hard drive, everything's still there :P

[DZComposer]

Provided no install issues arise, and on the speed of the computer, you should be back up and running in 20-45 mins.

The repair install is a powerful tool. So long as the disk partition isn't hosed, it can fix many Windows boot issues.

Note that it is no replacement for a reformat if one is needed. It preserves all files and registry entries, meaning any malware will also still be there. Also some tasks like rebuilding the boot sector and/or MBR takes less time in recovery console. A repair install will fix those things, but you turn a 10 min job into a 30+ min one.

[Fire Yoshi]

A screen came up that's showing that I'm going to be installing windows.

Collecting information

Dynamic Update

Preparing Installation

Installing Windows

Finalizing intallation

Is this right?  I sure hope this doesn't delete everything I have. ^^;

[DZComposer]

That's normal. So long as you didn't format (and you'd know if you did because it would have told you that is what you were doing with a big ALL CAPS warning that you would lose data), you won't lose anything. So, if you followed the video, you're fine.

The reason it is called a "repair install" is because you are actually re-installing windows, but without destroying the registry or data on the drive.

Some windows may pop up at some point. You can usually take all the defaults (just hit next), but read them to be sure that's what you want. It's all non-techie stuff like what language you want to use and the date/time.

In rare cases, there will be a program you use that will need to be re-installed, but that is very rare. I've only seen it once.

[Fire Yoshi]

That's normal. So long as you didn't format (and you'd know if you did because it would have told you that is what you were doing), you won't lose anything.

I'm pretty sure I didn't format anything, and it doesn't say anything about doing so...

I need to go to work now, so I'm just going to let it go on it's own while I'm gone.  I hope it doesn't do anything bad in the mean time. :/

[DZComposer]

If it didn't say you were formatting, then you didn't format. You'll be fine.

You may have to click through the language and date/time windows, so if you get back and find it not finished with a window on-screen, that's likely what it is (failed installs tend to either just reboot or BSOD).