This is a read-only archive. No new posts or registrations. Privacy Page Still need help? Ask the volunteers at Geeks to Go, free.
Software

system restore led to missing files in system32

6 min read

This thread's last reply is from . Advice, software, and links below may be out of date — treat specific steps and download links with caution.

The other day my neighbor's sound drive went missing on his Windows XP, so he followed the directions in his manual on how to perform a system restore. However, after that, his laptop wouldn't even load XP anymore because at the startup screen, it said that he was missing a file called "c:/windows/system32/hal.dll." So I went over to his house and tried to fix it using my spare windows XP OS CD. After the CD loads, i typed in 'R' for the 'repair windows installation' option. (the other option was to load windows xp from the CD but i was afraid that would erase all his data). Then the screen led us to an MS DOS command prompt, and we tried to copy the hal.dll file from the F: drive (my CD) onto his C: drive. that was successful so we restarted, but then another file was missing..this time 'c:/windows/system32/ntoskrnl.exe.' so we did the same thing–copying the file. but after restarting once again, we got the error message that said 'unable to load something something kernel. please contact your support representative' i can't remember the exact wording of it unfortunately. he suggested we try to copy the entire system32 folder from the CD into his C: drive. so we renamed 'c:/windows/system32' to 'c:/windows/system31' and then tried to copy F:/windows/system32 directory. however, there was an error that said that the "copy" command could not be used to copy an entire directory. so we tried "xcopy" but then the error said "xcopy" is not a supported command. So now, we are stuck and before resorting to rebooting everything, I was wondering if anyone else had suggestions on where to go from here. Any help would be appreciated. Thank you.
Hi appledale,

Your thread seems to have been missed, our apologies to you.

I suggest your friend may like to try the following with either the OS CD that hopefully came with the computer, or borrowing yours which is quite acceptable for this SFCScan.

Backup/archive/copy

To be on the safe side I strongly recommend that before doing anything at all you check that your back up/archive/copy of all your important data, drivers, files, settings, work, etc is 100% up to date accurate and reproducible, (even if your back up is even only a day or so out of date, it's worth updating it now.)
Also don't forget to check that you have all your application Installation CD's to hand together with the product keys (including those for Windows itself)

Windows Protected System File Checker SFC
  • Start
  • Run
  • type:sfc /scannow (note the space between the c / )
  • Have your Win XP installation disc handy as if damaged files are found they will need to be copied across from your disc, if SFC can't find correct copies elsewhere.
Windows XP Installation disc not available or wrong Service Pack- SP1 when SP2 or SP3 is needed

There are work- arounds to this problem but the easiest, by far is to borrow one and use that. It is perfectly OK to do this, for the purposes of running SFC,and if you ask around all your friends, you are likely to find someone who will be able to help you out.


SFC no disc, no friends able to help.

Well you will need to do it the harder way and as a registry edit will be required it is essential that you back up your registry before you do anything else. Then in the event of trouble it will be easier to repair your registry. Download ERUNT from here and take a moment to familiarise yourself with the programme and how to repair your registry with it if it should become necessary. At the same time it would be wise to create a System Restore point, post back here if you need instructions on how to do this.

For the alterations needed to run SFC If you go here you will find detailed instructions on the copying of files and the system changes you need to make. When you have followed all the instructions, reboot you machine and try to run SFC again, and please let us know how you go.

Below is the correct method for doing a System Restore, but the above scan is most important to replace any corrupt .dll files in your friends OS

System Restore Point facility

Go to:

  • Start
  • All Programs
  • Accessories
  • System Tools
  • System Restore follow the onscreen directions.
Try to put your system back to a date before your troubles started, see how you go.

Note 1

Using this facility will normally preserve documents and data created by you in your My Documents folder, but some data files left on the desktop for example are at severe risk of being lost. For this reason it is recommended that before doing anything at all, you check that your back up/archive/copy of all your important data, files, settings, work, etc is 100% up to date accurate and reproducible, (even if your back up is even only a day or so out of date, its worth updating it now.)

Also don't forget to check that you have all your application Installation CD's to hand together with the product keys (including those for Windows itself)

Note 2

It is always important to have System Restore, protecting your boot drive (usually Drive C:) unless your trusted adviser specifically recommends turning it off for a short while.

Keep us posted on your progress.

best regards,
Thanks for the reply :) But I haven't had the chance to try out your suggestions just yet because we aren't even able to load the windows desktop screen. After the computer boots up, we just get a black screen and an error message. Are there ways to do the SFC scan wihthout being able to load the start>run command?
In your initial post, you said you copied the file from the CD. I don't know how you did this but you can't just copy it, you need to use the EXPAND command as follows:

EXPAND
expand source [/F:filespec] [destination] [/y]
expand source [/F:filespec] /D
Use this command to expand a file. In the command syntax, source specifies the name of the file to be expanded and destination specifies the folder for the new file. If you do not specify a destination, the command uses the current folder by default. You cannot include wildcard characters.

You can use the following options:
/y Do not prompt before overwriting an existing file.
/f:filespec Identifies the files to be expanded.
/d Do not expand; display only a directory of the files in the source.
If the source contains more than one file, you must use the /f:filespec parameter to find the specific files to be expanded. You can include wildcard characters.

The destination can be any folder in the system folders of the current Windows installation, in the root of the drive, in the local installation sources, or in the Cmdcons folder. The destination cannot be removable media, and the destination file cannot be read-only. Use the attrib command to remove the read-only attribute.

Unless you use the /y option, the expand command prompts you if the destination file already exists.


Ditto for ntoskrnl.exe. Both are in the \I386 folder of the CD. So if your CD is D: then

expand -r d:\i386\hal.dl_ C:\windows\system32
expand -r d:\i386\ntoskrnl.ex_ C:\windows\system32
Oooh, sorry I think i worded the whole copy thing wrong. What we did exactly was after inserting the CD, and pressing 'R' for repair windows installation, the MS DOS command prompt appeared and asked us if we wanted to boot from the C: drive, D: drive, or F: drive. So first, we typed in something like 'cd D:' (and if i'm not mistaken, that means go into drive D), then we did 'cd windows' and after that 'cd system32.' so were in the location D:/windows/system32, and then my neighbor typed in a command(i can't remember exactly..) that listed all the contents of the location we were in. so we scrolled down and found the file hal.dll. so then we typed in 'copy D:/windows/system32/hal.dll' and then 'cd C:/windows/system32.' and somehow he managed to 'paste' the copied file into the C: drive folder (i can't remember the exact paste command either). after that, we restarted the laptop and no more hal.dll problem, this time the ntoskrnl.exe problem instead. we did the same thing, but after another restart, we got the error message that told us to find a system representative. i hope this makes a little bit more sense. But I will definitely try the Expand command and will let you know how that works. Thank you for the help!!

Still having this problem?

This topic is from the What the Tech archive and can't take new replies. Geeks to Go is an active, free help community run by volunteers. Post your question there and a person, not a bot, will work through it with you.

Ask on Geeks to Go →