Windows Thread, file missing or corrupt after WDS deployment in Technical; We have created an image for a dell USFF 760 pc.
The image came down ok. When the pc came ...
-
13th May 2009, 10:56 AM #1
- Rep Power
- 11
file missing or corrupt after WDS deployment
We have created an image for a dell USFF 760 pc.
The image came down ok. When the pc came to startup is sais windows could not start because the following file is missing or corrupt: <windows root>\system32\hal.dll
please reinstall re-install a copy of the above file.
This is a fresh install of win xp. NON oem.
Its not a hdd issue, cos i tried another one.
I have also tried replacing the hal.dll, ntoskrnl.exe and ntkrnlpa.exe on the base image.
Any help much appreciated.
DG
-
-
IDG Tech News
-
13th May 2009, 11:28 AM #2 Are you trying to use the image on different hardware? The HAL generally throws up errors if the hardware is different, or if you were using the same system but with a single core CPU and then a dual core CPU.
You could trying performing a Windows repair, then creating a secondary image from this. It's possible large OEMs may use slightly varying components, despite the name/model being identical.
-
-
13th May 2009, 02:15 PM #3
- Rep Power
- 11

Originally Posted by
Michael
Are you trying to use the image on different hardware? The HAL generally throws up errors if the hardware is different, or if you were using the same system but with a single core CPU and then a dual core CPU.
You could trying performing a Windows repair, then creating a secondary image from this. It's possible large OEMs may use slightly varying components, despite the name/model being identical.
the hardware is identical
dell usff pc 760
Multi cpu
We think it may now be caused by a hidden partition dell use.
Dan
-
-
14th May 2009, 10:32 AM #4
- Rep Power
- 11
This error can be caused by a number of things after WDS.... but it is always hardware related. You are correct in assuming it is a hidden partition. I assume you, like me, always delete all the partitions before installing a WDS image? If you then install an image that had a seperate parition the boot.ini file will point to an incorrect partition and stupidly the Hal.dll error is the one that shows. All you need to do is rebuild the boot table. If you have a number of machines I advise you to either rebuild the boot table and resend the image to the server, or open up the image and put the correct boot.ini file i nthe root of your system drive.
To rebuild: Boot to your windows disk, press R for recovery console, type in bootcfg /rebuild, agree to replace, Identifier "Windows XP Professional" and then leave the options blank after. Beware this can often leave traces when loading windows so edit your boot.ini once in Windows and remove the old line.
That should do it
-
3 Thanks to Bobo:
adamchapman (3rd August 2009), dirtydog (6th November 2009), speckytecky (7th November 2009)
-
6th November 2009, 08:47 PM #5 
Originally Posted by
Bobo
This error can be caused by a number of things after
WDS.... but it is always hardware related. You are correct in assuming it is a hidden partition. I assume you, like me, always delete all the partitions before installing a
WDS image? If you then install an image that had a seperate parition the boot.ini file will point to an incorrect partition and stupidly the Hal.dll error is the one that shows. All you need to do is rebuild the boot table. If you have a number of machines I advise you to either rebuild the boot table and resend the image to the server, or open up the image and put the correct boot.ini file i nthe root of your system drive.
To rebuild: Boot to your windows disk, press R for recovery console, type in bootcfg /rebuild, agree to replace, Identifier "Windows XP Professional" and then leave the options blank after. Beware this can often leave traces when loading windows so edit your boot.ini once in Windows and remove the old line.
That should do it

legend - fixed my problem
-
-
16th December 2010, 08:16 AM #6
- Rep Power
- 0
Reason of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll DLL file or a hal.dll file that has been deleted or moved from its intended location. Please try to rebuild the boot.ini file by using Bootcfg.exe tool.
-
-
16th December 2010, 08:17 AM #7
- Rep Power
- 0
-
SHARE:
Similar Threads
-
By bmdixon in forum O/S Deployment
Replies: 9
Last Post: 6th July 2010, 11:39 AM
-
By Boon72 in forum Windows
Replies: 7
Last Post: 13th May 2009, 01:13 PM
-
By wesleyw in forum Office Software
Replies: 1
Last Post: 23rd April 2009, 06:52 PM
-
By networkdemon in forum Thin Client and Virtual Machines
Replies: 0
Last Post: 3rd September 2008, 08:54 AM
-
By flashsnaps in forum Windows
Replies: 14
Last Post: 5th February 2008, 01:20 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules