• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1091
  • Last Modified:

Windows Deployment Services - (File corrupt or missing \system32\hal.dll)

I'm trying to upload a xp image to WDS, and its getting created properly, but after I install the image on the exact same hardware, i get "File corrupt or missing \system32\hal.dll". I've been reading with alot of people trying to do this same thing, and the solution solution has been to delete the hidden partition thats like 32 mb in size, then it boots fine.
My problem is, I'm unsure if I'm doing this on the WDS server, or the XP image itself, and I'd like to automate this when our help desk staff pullls down the image. I've researched and found that what you're supposed to do is call a Diskpart script that deletes the hidden partition. Do I use imagex to do this? is these files being created on the XP image or in the system32 directory of WDS?
This is a similar script I've seen referenced all over the web:
DISKPART
SELECT DISK 0
CLEAN
CREATE PARTITION PRIMARY
EXIT
EXIT

Any help would be very appreciated.
0
khptech
Asked:
khptech
  • 4
  • 2
1 Solution
 
Tony MassaCommented:
I don't use WDS, but use the WIM imaging tools from WAIK, and I have to assign a drive letter and format the disk during the diskpart process.

I use diskpart /s mydiskpartscript.txt
Here's my diskpart script:

SELECT DISK 0
CLEAN
CREATE PART PRI
SELECT PART 1
ACTIVE
FORMAT FS=NTFS LABEL="Local Disk" QUICK
ASSIGN LETTER=C:
EXIT

Open in new window

Maybe that will help you somewhat
0
 
Tony MassaCommented:
It could be that you're not setting your new partition "ACTIVE"
0
 
Tony MassaCommented:
I re-read your post a little more carefully...  :)

Did you build your XP image from a fresh PC install?  If you formatted and used the entire disk in the process, you won't have a "hidden" partition.  
Are you using the WIM imaging format (IMAGEX) to capture the image?  If so, it is a file based imaging process and the diskpart script is run during the WINPE portion to clean, format the disk, set the C: drive as active before applying the WIM image.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
khptechAuthor Commented:
I'm using the Windows Capture Utility, the GUI option. Maybe I need to re-capture it, tmassa99? If I use ImageX for capturing the WIM, you're saying it will do this already for when it captures it automatically, without me adding any scripts, etc?
0
 
khptechAuthor Commented:
The hidden partition is only visible to me when I used diskpart to view the partitions, and when I deleted it using diskpart, the imaged workstation that first showed the hal.dll error, booted into Windows XP fine, so it was apparent that I need to rid of the hidden partition?
0
 
Tony MassaCommented:
I don't think you have to get rid of the hidden partition.  The disk clean part of the deployment because the capture utility does grab the WIM image of the reference computer.  
(When I tested WDS, I already had the captured WIM files)

This looks to be an excellent source to look at:
http://blog.augustoalvarez.com.ar/2010/04/21/deploying-windows-7-using-windows-deployment-services-wds-step-by-step-part-ii/
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now