Windows XP Won't Start - Corrupted hal.dll File

[DrewWilson]

Hey all,

I booted my XP machine this morning and it showed this message:

Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll.
Please re-install a copy of the above file.

Is this a simple matter of inserting the Windows XP CD or is there more I need to know about this particular problem?

Thanks.

[Mels_Smileys45]

I don't actually know but I would try inserting the XP disc and using the "repair" option. It surely won't hurt to try this first

[mountain_rage]

Wow gold and wedding invitations!!! Oh my I feel like a princess!!!

For those confused, there was a wow gold + wedding invitation spam post just above this one.






No, really there was...

[DrewWilson]

I was wondering why I couldn't get the repair program running. Seems like I need an additional CD for the repair thing. Currently working my way around getting one.

[Excrement_Cranium]

hal.dll?


What are you doing Drew? This is highly irregular.


*edit*

http://pcsupport.about.com/od/findbyerrormessage/a/missinghaldll.htm

[RACKnRAIL]

My ex had this same problem once with the exact same .dll in her computer.

I used the XP disk, as suggested, but I copied the file in DOS and pasted it in the sys32 folder. It worked for me.

Edit: I remember what I did now. I used a win98 CD to boot into dos and from there I copied/pasted the hal.dll into the sys32 folder. Like I said, it worked flawlessly.

It's beyond me as to how it became corrupted though.

[mountain_rage]

My ex had this same problem once with the exact same .dll in her computer.

I used the XP disk, as suggested, but I copied the file in DOS and pasted it in the sys32 folder. It worked for me.

Edit: I remember what I did now. I used a win98 CD to boot into dos and from there I copied/pasted the hal.dll into the sys32 folder. Like I said, it worked flawlessly.

It's beyond me as to how it became corrupted though.

Does 98 read NTFS??? I remember needing a dos variant to copy a file into my xp system. Now if I remember correctly linux still can't write to ntsf? If it can then you could use a linux boot disc. There's also a command prompt in xp but I cant remember for the life of me whether its a alternate boot or if its found on the xp pro install disc.

[RACKnRAIL]

Does 98 read NTFS??? I remember needing a dos variant to copy a file into my xp system. Now if I remember correctly linux still can't write to ntsf? If it can then you could use a linux boot disc. There's also a command prompt in xp but I cant remember for the life of me whether its a alternate boot or if its found on the xp pro install disc.

It doesn't have to read NTFS, since you don't have to install win98, therefore you are not reading NTFS from FAT32. All you are doing is booting into DOS from the Win98 CD, then you can remove the boot CD and insert the XP disk and copy the file from the location then simply paste it into sys32 folder. These are simple DOS commands, if you remember DOS.

Also, if he can't boot XP, as he mentioned, he can't use XP's command prompt.

[mountain_rage]

RnR you lost me, although some people still use fat 32 in XP most don't, so the system is likely NTFS. Unless I'm mistaken here, the version of the dos operating system on the 98 disc cannot read/write to a NTFS file system unless modified. Now if I remember correctly the files on the Xp disc are fat 32 so that fine, but the files system of his harddrive are NTFS, so how does he write to it?

[DrewWilson]

hal.dll?


What are you doing Drew? This is highly irregular.


*edit*

http://pcsupport.about.com/od/findbyerrormessage/a/missinghaldll.htm

The last thing I did on the computer was install the latest version of Java (not deinstalling the previous version)

I'm 99% convinced it was that... exactly how that would cause this particular DLL file to get corrupted is unclear to me though.

[mountain_rage]

Sometimes these errors are unrelated to the user and due to hardware failure, such as a corrupt sector on the h/d.

[Mels_Smileys45]

Sometimes these errors are unrelated to the user and due to hardware failure, such as a corrupt sector on the h/d.

From what ive read this is a likely cause.

[mountain_rage]

Wonder how hard it would be for Microsoft to build some redundancy into these essential system files, if they don't already.

[RACKnRAIL]

RnR you lost me, although some people still use fat 32 in XP most don't, so the system is likely NTFS. Unless I'm mistaken here, the version of the dos operating system on the 98 disc cannot read/write to a NTFS file system unless modified. Now if I remember correctly the files on the Xp disc are fat 32 so that fine, but the files system of his harddrive are NTFS, so how does he write to it?


I am not making this up. I am talking from a real experience. My ex's computer was in fact formatted to NTFS. Like I said, I used a Win98 CD to boot into DOS, but what I think I may have done was, copied the missing file on a floppy first, and then with simple DOS commands copied it into the sys32 folder. I do remember it was as simple as pie and it worked. There are other methods I just read on Google, but this one worked for me.

There is lots of info on how to fix this on google, as it would appear a not so uncommon problem, and not necessarily due to hardware issues.

I just found this method googling. I am not saying to use this method. I am just pointing out that there seems to be several ways of repairing the issue.


Boot from Windows xp CD and choose R to enter the recovery console

at the prompt, type
Attrib -H -R -S C:\Boot.ini
DEL C:\Boot.ini
BootCfg /Rebuild
Fixboot

If that does not work, reboot again and enter the recovery console

type

expand d:\i386\hal.dl_ c:\windows\system32\hal.dll.

(this assumes you have a single harddrive and your cd-rom drive is D:

Substitute d: for the drive letter of your CD if it is different

[Excrement_Cranium]

Bah, you guys suck. I slide in a perfect 2001: A Space Odyssey riff, and it gets completely missed!!!

:)

[DrewWilson]

Oops, yeah, missed that. Heheh. :)

[DrewWilson]

Fuck.

I got the repair CD, booted from the C drive and it went into the repair program. I tried hitting 'R' once the options went up, but it went back to the corrupted HAL.DLL file.

So I restarted the computer and now, at best, I get to the repair program and get an "unexpected error" message. Looks like I lost my main box and am looking at getting a new desktop. :(

Craaaapppp

[RACKnRAIL]

If your using the boot CD and not your C drive you should reach command prompt.

Then at the prompt, type
Attrib -H -R -S C:\Boot.ini
DEL C:\Boot.ini
BootCfg /Rebuild
Fixboot

If that does not work, reboot again and enter the recovery console

type

expand d:\i386\hal.dl_ c:\windows\system32\hal.dll.

(this assumes you have a single harddrive and your cd-rom drive is D:

Substitute d: for the drive letter of your CD if it is different

[DrewWilson]

I'm presuming I won't lose any of my files by doing this, correct?

If I'm not losing stuff that I put on there, I may as well give that a shot. :)

[Feather]

why did no one offer the idea of using system restore point or did I miss something

[RACKnRAIL]

I'm presuming I won't lose any of my files by doing this, correct?

If I'm not losing stuff that I put on there, I may as well give that a shot. :)

No, you are simply trying to repair the corrupted boot file.

Are your files on a partition or on C drive?


why did no one offer the idea of using system restore point or did I miss something


You would have to be able to boot up into windows to do that.

[Feather]

there is a way to do it from command prompt



Running System Restore from a command prompt

If your computer won't boot Windows normally and won't boot into the Safe Mode GUI, you can still access System Restore. Start by booting the system using the Safe Mode With Command Prompt option. After you log on, type the following command line at the command prompt:

%systemroot%\system32\restore\rstrui.exe

Press [Enter], and System Restore will run as it normally does. You can follow the steps in the wizard to perform a restore operation.

[RACKnRAIL]

there is a way to do it from command prompt

Yes, which I have already explained. He needs to boot to a CD!!

As I mentioned I had this exact same problem before. It can be repaired.

[RACKnRAIL]

there is a way to do it from command prompt



Running System Restore from a command prompt

If your computer won't boot Windows normally and won't boot into the Safe Mode GUI, you can still access System Restore. Start by booting the system using the Safe Mode With Command Prompt option. After you log on, type the following command line at the command prompt:

%systemroot%\system32\restore\rstrui.exe

Press [Enter], and System Restore will run as it normally does. You can follow the steps in the wizard to perform a restore operation.

No hal.dll , no safemode.

[Feather]

It should boot into safemode command prompt
It doesnt load any of the gui or anything but bare essentials

not trying to step on toes just offer another solution

[RACKnRAIL]

I'll let Drew tell ya.

I am quite sure he cannot boot into anything. CD booting only.

[DrewWilson]

So, with that string of commands, every space means hitting enter I'm presuming? (forgive me for being a little meticulous with the details, I want to make sure I don't screw this up completely)

I'll run by what I see when I load up the computer normally:

Screen turns on.

Great big Dell logo with the little option menu telling you you can hit f12 for options. There is that usual brief moment a simple little loading bar is going across the screen.

Everything on the screen vanishes.

Text appears telling me I have a missing or corrupted hal.dll file.

About the only things I can do is hit F12 to go into where I want to boot from or check out the BIOS. That's pretty much the only thing I can do without a CD at this point.

However, I am optimistic that there is no corrupted bits on the actual hard disk because I have a legit copy of Norton Internet Security Boot CD. I can boot from that CD and I get a few command prompt options from the CD, so I don't think it's necessarily the result of a crapped out hard disk, otherwise, I'm pretty sure I wouldn't even get to the Dell loading screen.

About the only way I can see getting a new hal.dll file is from the boot CD. I haven't tested this, but I might be able to get into the command prompt. However, if I don't have the boot CD to fix the file in the first place, I'm not sure what good it'll do to get into the DOS prompt portion (which is accessible when I get to the boot options) Then again, I have never had such a system failure before, so I'm pretty much shooting around in the dark when it comes to this.

The only thing I know is a few basic DOS prompts like 'help' (use to be 'h' if I'm not mistaken) and .dir.

At this point, the only thing I'm hoping to do is repair this file, get in, get everything backed up (including family photo's that only exist on this machine at this point >,< )

I'm going to do RackNRails suggestion first. Seems to be simply replacing a file in DOS prompt from CD - a work around from loading the whole CD which seems to take issue with a peripheral bus driver for some reason. I'm going for complete backing up of everything so if the computer craps out again, I have everything. I have no idea how many years it has left, but it has been around since about 2002-ish, so it's getting up there age-wise to begin with.

On a side note, I already had someone (who has a computer science masters degree) tell me at this point that the only thing left to do is to take the computer out to the back and shoot it, so there will be a bit of a silver lining if this all works - internet ppl on ZeroPaid proved a comp expert wrong. ;) Though pride is one of the last things on my mind at this point because there are more important things to worry about right now like family photo's and rediculously complicated passwords for two FTP sites - though getting my 100+ gig mp3 music collection back would be damn nice too.

Edit: Oh yeah, and the obligatory Space Odessey reference...

http://flowstate.homestead.com/files/hal9000.gif

[w31n3r]

just Follow RnR's advice on this one, he's spot on.

the fact that your friend is a computer genius is reason enough for him to say what he said. when you have an intricate understanding of why shit hit the fan, explaining it to a (possibly perceived) n00b is the shittiest job in the world. they'll just screw up some more and come back and bug you for days when it could be a 5 minute job. it's easier to just say "format>reinstall". i do it all the time, and i'm no genius.

as an alternate, if you're really worried about your data, heres what you can do:

1. download miniPE (http://torrents.thepiratebay.org/3669864/MiniPE_DigiWiz_2k5.09.03_release_-_23-2-2007.3669864.TPB.torrent) (knoppix is fine too, but windows users feel more comfortable with miniPE)
2. boot from disc, from there copy all your important data stored in c: drive assuming that thats where windows is kept. this includes documents and settings where a lot of people keep their music and photos. you can copy stuff you want to keep in a folder on another drive.
3. double check you haven't left anything behind.
4. boot from you OS disc and reinstall windows formatting ONLY the c: drive.

of course RnR's method will take you 2 minutes to accomplish if done right. good luck.

[DrewWilson]

GRrrr... I feel like an idiot. How do I get into command prompt on boot?

I did this once and I don't remember how I did it. I hit F8 and selected "Safe Mode with Command Prompt" but I go into the same HAL.DLL error. It puts a blue option on the bottom that says what I want, but it's as if I'm booting normally which, of course, causes the damn error.

I'm kicking myself for holding off this long in favor of real life. >,<

[DrewWilson]

Leave it to me to figure it out after posting that. LOL.

OK, I got into DOS prompt with the C:\WINDOWS> prompt line

I typed in "Attrib -H -R -S C:\Boot.ini" and I get the following error:

"The parameter is not valid. Try /? for help"

I type in attrib /? and get this:

"Changes attributes on one file or directory.

ATTRIB -R|+R|-S|+S|-H|+H|-C|+C filename

+ sets an attribute.
- clears an attribute.
R Read-only file attribute.
S System file attribute.
H Hidden file attribute.
C Compressed file attribute

To view attributes, use the DIR command."

So I type in DIR and the only thing that got close to it was "BOOTSTAT.DAT"

So I find the command "cd .." to get to the main hard drive.

I'm still posting, but thought I'd get a quick update right away.

[DrewWilson]

OK, I got to the parent directory, but when I hit "dir" to find a boot.ini file, I didn't see it. Any idea where the Boot.ini file is? (I'm gonna Google it myself right now after I post this)

[DrewWilson]

Looks like it's suppose to be there, but I can't see it :\

[lion7718]

"boot.ini" file is hidden..un-tick hidden files & hidden system files...
you should now see it under "C" (Root)

[RACKnRAIL]

"boot.ini" file is hidden..un-tick hidden files & hidden system files...
you should now see it under "C" (Root)


He should be able to see it from command prompt with those attributes.

If this doesn't work, I don't have an easy answer. I copied mine directly from a floppy to the sys32 when it happened to me.



Boot from your XP Setup CD and enter the Recovery Console
Run "Attrib -H -R -S" on the C:\Boot.ini file
Delete the C:\Boot.ini file
Run "Bootcfg /Rebuild"
Run Fixboot

[DrewWilson]

Is there a way to safely see if the Boot.ini file is even there? I've tried the DIR command, but didn't see it. Reason I ask is because if it was somehow deleted, maybe I can skip straight to the "Run Bootcfg /Rebuild" step. Either that or I'm not understanding the "invalid parameter" error message. Help said that the attrib command is a valid command.

The only other thing i can think of is, should I just be going "ATTRIB -H C:\Boot.ini", then "ATTRIB -R C:\Boot.ini", then "ATTRIB -S C:\Boot.ini" instead of doing all three at once because I'm guessing it's three different attributes that I'm changing.

Edit: Or is it possible that the attributes are already set this way which is why I'm getting an "invalid parameter" error?

[DrewWilson]

Well, it's been a long time since I updated this, but there has been a new development. Someone I know is visiting in town and has a spare hard drive with Windows XP installed. Swapped out the hard drives so the blank Windows drive is set to master and the original C drive is set to slave (left it unplugged while we worked with a single drive since that was the easiest).

Apparently, there were issues with the installation, so we let the Windows CD reformat the blank drive and re-install Windows again (wtf? Whatever...) After a fresh install, we keyed in the existing key in the sticker on the side of the tower and got it to boot up (after all the installation crap it went through)

We then shut the computer down once we knew it was working properly and plugged in the original C drive as slave. I was worried there would be a conflict, but it seems that it just reads the files as back-up files as long as the drive is set to slave.

The files are all accessible, so I plugged in my 500MB external USB hard drive and started dumping everything onto the external. It'll take a few days since I have two hard drives worth of stuff, but so far, things are working out nicely.

Just thought I'd update this thread with a note saying that I've resolved the issue finally (only took 2 fncking months to fix the problem, but it's a solution nevertheless!)

Edit: Oh yeah, the network cable to the machine was disconnected so it can't communicate with Microsoft in any way shape or form.