Missing windows file, hal.dll.

  • Thread starter Thread starter --Ivan--
  • Start date Start date
I

--Ivan--

Hi

My computer displays the following msg

windows could not start because the folowin file is missin or corrupt,

<Windows root>\system2\hal.dll.

I ran chkdsk /r 3 times and didnt fix it,

any suggestions

thank you


(running xp pro)
 
--Ivan-- wrote (on Sat, 13 Jun 2009 20:07:01 -0700):
My computer displays the following msg

windows could not start because the folowin file is missin or corrupt,
<Windows root>\system2\hal.dll.

I ran chkdsk /r 3 times and didnt fix it,
Click to expand...

http://en.wikipedia.org/wiki/Hardware_abstraction_layer

Did you boot into Recovery Console mode and try running the system file
checker program (sfc.exe /scannow)?

http://support.microsoft.com/kb/314058

Unless you have a backup program that boots off the MBR in the hard
drive or using a bootable CD (so you can restore to a previously saved
image of the OS partition), you'll probably have to do an in-place
upgrade (i.e., Repair install).

http://support.microsoft.com/kb/315341
 
VanguardLH

This is not an area where my knowledge extends far but can you run
System File Checker in the Recovery Console? I have never used the
Expand command but might that be an area to explore?


--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
VanguardLH said:
--Ivan-- wrote (on Sat, 13 Jun 2009 20:07:01 -0700):


http://en.wikipedia.org/wiki/Hardware_abstraction_layer

Did you boot into Recovery Console mode and try running the system file
checker program (sfc.exe /scannow)?
Click to expand...


I don't have a problem, but since you mentioned SFC, I thought I would
ask about something I had wondered about: If your installation CD for
Windows XP is older than all the updates installed since the original
installation, what would happen if it finds a newer version file while
running sfc.exe /scannow? Will it advise you that a later version
already exists, or try to install the old version of that file?

And if you choose to install the old version of that file, is there a
way of knowing which updates are needed in order to bring it to the
latest version?
 
        I don't have a problem, but since you mentioned SFC, I thought I would
ask about something I had wondered about:  If your installation CD for
Windows XP is older than all the updates installed since the original
installation, what would happen if it finds a newer version file while
running sfc.exe /scannow?  Will it advise you that a later version
already exists, or try to install the old version of that file?

        And if you choose to install the old version of that file, is there a
way of knowing which updates are needed in order to bring it to the
latest version?
Click to expand...

I have an XP CD that is a few years old and always wondered what would
happen if I ever had to try to use it for something serious since I
now have SP3 installed...

I made a new bootable XP CD with SP3 slip streamed into it, so it is
as up to date as you can be (I reckon). At least it is better than my
old original.

I found an easy tutorial on how to create the new bootable
installation CD and it worked the first time I tried it. There seem
to be many methods and suggestions, but I am not into the - guessing
it should work, it might work, if it doesn't work, etc. I want
something I know will work.

So if I ever need to run sfc (never have so far), I will use my new CD
with SP3 built in and not worry about it copying old files onto my SP3
installation.

It does not seem logical to boot on an SP1 or SP2 CD to try to fix a
system with SP3 on it.

Even if you go out and buy a new XP CD, it will only have SP2 on it (I
think) and you will have to download and install SP3, so it made sense
to me to just make a new installation CD with SP3 built in. No more
downloading/installing SP3 (which of course always works perfectly).

If you need to expand anything from your CD, it is easy.

For example, if you need Task Manager (taskmgr.exe), find it on your
CD as taskmgr.ex_ the command would be something like:

expand d:\i386\taskmgr.ex_ c:\Windows\system32

Another good thing about making your own CD is that you can include
any other files you think you might like to have or already expanded
versions of files.

If you don't have Recovery Console installed on your system (you
really should consider it), but have previously installed SP3, you
will not be able to install RC from the CD because it is only SP 2 (or
1) - another good reason to have an installation CD with SP3 built in,
then install RC on your hard disk as a boot option.
 
Ken said:
I don't have a problem, but since you mentioned SFC, I thought I
would ask about something I had wondered about: If your installation CD
for Windows XP is older than all the updates installed since the
original installation, what would happen if it finds a newer version
file while running sfc.exe /scannow? Will it advise you that a later
version already exists, or try to install the old version of that file?
Click to expand...

If the installation CD is older I don't think that SFC will accept it,
it will prompt you to supply a CD with the same service pack as is
installed. Windows File Protection keeps a list of protected files and
their version numbers and I don't think that it would replace the files
with earlier versions. Copies of the files are usually stored in the
dll cache, if the files can't be found there then it looks in the
Service Pack files or the Windows CD.

And if you choose to install the old version of that file, is there
a way of knowing which updates are needed in order to bring it to the
latest version?
Click to expand...

You're not given any choice as to what to install or not install, other
than possibly being asked to supply the CD SFC does everything else
without user intervention. As far as I know there is no log of the
actions performed by SFC.

http://support.microsoft.com/kb/222193
Description of the Windows File Protection feature

http://www.updatexp.com/scannow-sfc.html
scannow sfc - LEARN how to use SFC.EXE (system file checker)

John
 
John

Thanks for confirming what I thought.

In the recovery console would not the user be able to replace the
missing hal.dll from the driver cache using the Expand command? Some
instructions would help Ivans if he comes back to read the thread he
started.




--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
try chkdsk /p

--
db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
- @hotmail.com
"share the nirvana" - dbZen

~~~~~~~~~~~~~~~~~~
 
It happens that Gerry formulated :
Some instructions would help Ivans if he comes back to read the thread he
started.
Click to expand...

He double posted, question already answered.

http://groups.google.com/group/micr...l/browse_thread/thread/e8f0fd4590f0fcfa?hl=en

Windows could not start because the following file is missing or
corrupt <windows root>\system32\hal.dll
http://www.google.com.au/search?hl=...dows+root>\system32\hal.dll&btnG=Search&meta=
Error Message: Windows could not start because the following file is
missing or corrupt
http://support.microsoft.com/kb/320252
 
Gerry explained on 14/06/2009 :
This is not an area where my knowledge extends far but can you run System
File Checker in the Recovery Console? I have never used the Expand command
but might that be an area to explore?
Click to expand...

This is not aimed at anyone in particular.

If the comp is still bootable, I put in my latest slipstreamed CD & do
this.

Reinstall WindowsXP and keep all your current installed applications
and settings ( including ms updates/hotfixes ):
Put your XP cd in the drive.
Start > All Programs > Accessories > Command Prompt or, Start > click
Run, type cmd and click OK.
Copy & paste > D:\I386\winnt32 /unattend
The above assumes D is your CD drive.
Press Enter.
If you have i386 on your drive, you can replace D: with the location of
it.
If the comp is unbootable, the unattend method is unavailable, you can
use your slipstreamed cd this way.
XP's No-Reformat, Nondestructive Total-Rebuild Option
http://www.informationweek.com/windows/showArticle.jhtml?articleID=189400897
 
Gerry said:
VanguardLH

Looks like the COMMUNITY SOLUTIONS CONTENT DISCLAIMER was needed!
Author: Jabez Ming Teik Gan MVP

SFC is not listed in
http://support.microsoft.com/kb/314058
Click to expand...

Yikes, I didn't scroll down far enough. Jesus! They're sticking in
posts from their webnews-for-dummies gateway to Usenet as though they
are Microsoft-supplied knowledgebase articles? Oh crap. Nothing should
be added to their support knowledgebase unless it has been okayed by a
Microsoft representative.
 
VanguardLH

Microsoft representatives are not infallible, when it comes to writing
Knowlege Base Articles <G>!

--


Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
 
I know, I've seen that article before. There is an error in it, SFC
can't be run from the Recovery Console.

John
 
Back
Top