During installation a fresh copy of Windows XP, some of files can not copy to hard disk (driver.cab, spnike.dll, sprio600.dll, sprio800.dll, srgb.icm, streamci.dll and other files). How can I solve this problem? Please help me

There are several different ways that kernel.dll errors can show up on your computer. Here are some of the more common ways that you might see kernel.dll errors:

• "Kernel.dll Not Found"
• "This application failed to start because kernel.dll was not found. Re-installing the application may fix this problem."
• "Cannot find [PATH]\kernel.dll"
• "The file kernel.dll is missing."
• "Cannot start [APPLICATION]. A required component is missing: kernel.dll. Please install [APPLICATION] again."

Kernel.dll error messages might appear while using or installing certain programs, when Windows starts or shuts down, or maybe even during a Windows installation.
The context of the kernel.dll error is an important piece of information that will be helpful while solving the problem.

Cause of Kernell.dll Errors
Kernel.dll errors are caused by situations that lead to the removal or corruption of the kernel DLL file.
In some cases, kernel.dll errors could indicate a registry problem, a virus or malware issue or even a hardware failure.

How to Fix Kernel.dll Errors
Important: Do not download kernel.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of kernel.dll, it's best to obtain it from its original, legitimate source.
Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the kernel.dll error.

1. Restore kernel.dll from the Recycle Bin. The easiest possible cause of a "missing" kernel.dll file is that you've mistakenly deleted it.
   If you suspect that you've accidentally deleted kernel.dll but you've already emptied the Recycle Bin, you may be able to recover kernel.dll with a free file recovery program.
   Important: Recovering a deleted copy of kernel.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.
   
2. Run a virus/malware scan of your entire system. Some kernel.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the kernel.dll error you're seeing is related to a hostile program that's masquerading as the file.
   
3. Use System Restore to undo recent system changes. If you suspect that the kernel.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.
   
4. Reinstall the program that uses the kernel.dll file. If the kernel.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.
   Important: Try your best to complete this step. Reinstalling the program that provides the kernel.dll file, if possible, is a likely solution to this DLL error.
   
5. Update the drivers for hardware devices that might be related to kernel.dll. If, for example, you're receiving a "The file kernel.dll is missing" error when you play a 3D video game, try updating the drivers for your video card.
   Note: The kernel.dll file may or may not be related to video cards - this was just an example. The key here is to pay very close attention to the context of the error and troubleshoot accordingly.
   
6. Roll back a driver to a previously installed version if kernel.dll errors began after updating a particular hardware device's driver.
   
7. Run the sfc /scannow System File Checker command to replace a missing or corrupt copy of the kernel.dll file. If this DLL file is provided my Microsoft, the System File Checker tool should restore it.
   
8. Install any available Windows updates. Many service packs and other patches replace or update some of the hundreds of Microsoft distributed DLL files on your computer. The kernel.dll file could be included in one of those updates.
   
9. Test your memory and then test your hard drive. I've left the majority of hardware troubleshooting to the last step, but your computer's memory and hard drive are easy to test and are the most likely components that might cause kernel.dll errors as they fail.
   If the hardware fails any of your tests, replace the memory or replace the hard drive as soon as possible.
   
10. Repair your installation of Windows. If the individual kernel.dll file troubleshooting advice above is unsuccessful, performing a startup repair or repair installation should restore all Windows DLL files to their working versions.
    
11. Use a free registry cleaner to repair kernel.dll related issues in the registry. A free registry cleaner program may be able to help by removing invalid kernel.dll registry entries that might be causing the DLL error.
    Important: I rarely recommend the use of registry cleaners. I've included the option here as a "last resort" attempt before the destructive step coming up next.
    
12. Perform a clean installation of Windows. A clean install of Windows will erase everything from the hard drive and install a fresh copy of Windows. If none of the steps above correct the kernel.dll error, this should be your next course of action.
    Important: All the information on your hard drive will be erased during a clean install. Make sure you've made the best attempt possible to fix the kernel.dll error using a troubleshooting step prior to this one.
    
13. Troubleshoot for a hardware problem if any kernel.dll errors persist. After a clean install of Windows, your DLL problem can only be hardware related.
    

Applies To
The kernel.dll error message could apply to any program or system that might utilize the file on any of Microsoft's operating systems including Windows 8, Windows 7, Windows Vista, Windows XP, and Windows 2000.

Receiving a bad image checksum error message when upgrading a computer to Windows XP means that a Windows system file such as user32.dll is damaged. This error occurs when any damaged system file is encountered that isn't overwritten during Setup. The repair process for this error involves voiding the damaged dynamic link library file from the DOS command line prompt and replacing it with a new copy from the Windows XP disk.

Insert a clean Microsoft Windows Millennium Edition (ME) or Microsoft Windows 98 Edition startup disk into the computer, and hold the reset button on the front of the computer until the system commences rebooting. Navigate the Windows startup menu with the keyboard's directional keys and select 'Start Computer with CD-ROM Support'. Hit "Enter" to continue. Write down your CD-ROM's drive letter on a piece of paper. At the command prompt, type "Drive:" without quotes (Drive should be replaced with the drive letter on which Windows is installed), and press "Enter." Type "cd windows\system32" without quotes, and press "Enter." Type "ren user32.dll user32.old" without quotes and again press "Enter." This renames your damaged user32.dll file so it is not recognized by the system, but still physically exists as a backup if needed in the future. Eject the Windows ME or 98 disk, and insert the Windows XP disk. At the command prompt, type "extract CDROMDrive:\i386\user32.dl_ Drive:\windows\system32\user32.dll" without quotes, replacing CDROMDrive with the CD-ROM's drive letter that you made a note of earlier, and replacing Drive with the system's drive letter on which Windows is installed. Hit "Enter" to execute the command. This process extracts a new copy of the user32.dll file to your hard disk, from the Windows XP CD. The new file will be found in the Windows/System32 directory. Restart the system by holding the reset button on the front of the tower until reboot commences.

You may receive one of the following stop error messages while working on your Windows XP computer.
STOP: C0000221 unknown hard error
Path\File_nameSTOP: 0xC0000221 unknown hard error
C:\Winnt\System32\Ntdll.dll (or another specific file or driver)
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
Path\File_name
Note: The error message may be discussed in many different formats-blue screen or message box. It depends on when the corrupt file was detected.
Similarly, you may receive the following STOP messages when a critical system file fails to load on your Windows NT and Windows 2000 computer.
STOP: C0000221 unknown hard error
<path>\<file_name>STOP: 0xC0000221 unknown hard error
c:\winnt\system32\ntdll.dll
Note: Some other drive may also be given in the message.
On Windows 2000 the following error message may display:
STOP: 0xC0000221 STATUS_IMAGE_CHECKSUM_MISMATCH
<path>\<file_name>
You usually face this problem when an incorrect driver for one or more hardware is installed on your system. For instance, the error messages described above are displayed when you install a millions of instructions per second (MIPS) driver on a x86 system.
Cause of the Error
This error occurs if the file given in the error message is damaged.
Your Windows XP operating system checks the following files for integrity during system startup:

• All driver files, excluding the files that loaded using the system loader to start your system .
• All DLL (Dynamic Link Libraries) on the system. These include, Graphics Driver Interface (GDI), User, Ntdll, Crtdll, Shell, Kernel and several other DLL files on the system.
• On Windows NT and 2000 computers, all DLLs loaded in the Window server address space are also checked.

The problem may also occur if an Iomega Zip drive is connected to the same cable as your hard disk drive.
Resolution Method
You can resolve this issue by removing the corrupt driver from your computer and then reinstalling a fresh and healthy copy of the driver. You may need to use the Device Manager utility to remove the driver. It is recommended that you clean your registry with the help of a reliable tool, such as RegGenie to ensure that all entries related to the uninstalled driver are removed from the system. After you have completely removed the corrupt driver, restart your system and install a fresh copy of the driver on the system.
If this step does not resolve the problem, you may have to reinstall Windows XP.
It is recommended that you regularly clean your registry with the help of a registry cleaner tool and perform antivirus and antispyware scan using tools, such as Antivirus Plus and StopZilla to prevent such errors from occurring on your system.

GOOD LUCK :-)

take fresh copy of xp nd format the older os the problem is of missing files of xp .....

I see ..either teh installation didnt complete the loading of the files..or you didnt format the Hdd proper...try to reformat it in the NTFS normal mode...and change the installation cd ..cause in the proces there might have been a file it couldn't copy ..and skip it ...keep trying cause sometimes it does that ...if the server went fine ..this means that the HDD its ok ..and the problem is the installation disk ...with xp on ...

There's actually a number of reasons why these annoying little DLL errors happen, but the most common, is caused when new programs are installed over all old ones and the old ones are not completely uninstalled 100%, causing registry pile ups and of course, getting a .DLL error messages.

Another reason, is damage that's been done by malware/spyware/adware programs, attaching themselves to your PC and wrecking havoc, deleting crucial DLL files from your PC.

The hal.dll file is created during install from 5 other dlls. HAL is the Hardware Abstraction Layer and it's the interface between the system drivers and the actual hardware.

Copying hal.dll will not resolve the problem.

A lot of times the file will be reported missing due to corruption of the boot sector or of the file system

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll file or a hal.dll file that has been deleted or moved from its intended location.

Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged HDD.

Suggested remodies-

1. Restart the PC. The hal.dll error could be a fluke.

2. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.
Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.

3. Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.

4. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.

5. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.

6. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.

7. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.

8. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.

Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

Important: If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.

9. Replace the hard drive. Finally, if all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

10. Perform a new installation of Windows XP after installing the new hard drive.

I have not tried it - but HERE is a free program purporting to fix the error.


Thanks for using FixYa - a FixYa rating is appreciated for taking the time to answer your FREE question.

hi im josh in cebu phils. Friend if some files wont transfer during the installation. the problems are centered to your cd installer or your optical disk drive. try change the cd installer if it is too scratchy or if your cd is good.try to change your optical disk.try use the faster one sothat you may done easily. good luck hope i helped you.pls.vote me if it helps you so that i will know.thnks.

OK I managed to install XP on Targa Traveller on 1591!
With the CD of window XP it is necessary to make F6 for the starting up of the installation and to use a diskette with the pilots(drivers) SATA of NVidia nforce. Naturally the most practical are of incorporated the pilots(drivers) SATA into the CD Windows but I knew how to make;) link for the pilots(drivers) SATA:
Http://garlon.free.fr/Appli/NVidia /
If after the intallation of the pilots(drivers) at the beginning of the copies of file An error of copy of file (cann' t copy spin NVr dll) make Esc (65 files nvidia not copied) and continue the installation up to the restart.
I put out(switched off) the computer, removed the hard disk to put it in an external box usb on another computer I have to copy files dll to System32 or system32 / drivers, file .inf on file windows/inf and file .sys on system 32 or system32 / drivers
I restarted the computer and finished the installation links Pilots(Drivers) xp (I am not sure for Chipset drivers Chipset...you must verify)
http://fred.garlon.free.fr/Appli/Targa
Good luck

I had the same problem. What I did was instert my xp disk then when you load up go to install windows. It will eitehr ask you to install a new copy or repair your copy, repair..you will have to reenter your product code, but it will reinstallyour dlls without losing all of your information. OTherwise backup all info you want to a disk, format and reinstall a fresh copy.

Make sure you get rid of the virus first though.

clean cd. try agen, repartition it agen may be the wrong size. reformat it agen. windows xp cd in. hit continue each time. you could try a new hard drive, and get a new windows xp from ebay.
I only use AVG at http://avg.download-go.com/ its free and has never let me down.