Windows Startup Error “load needed DLLs for kernel”.

Original Title: I have a toshiba satellite that says load needed DLLs for kernel (xp)

It has a toshiba MK6021GAS the model is a toshiba satellite A35-S159


Question Info

Last updated June 23, 2019 Views 45,842 Applies to:
If you mean you are seeing a message like this:

Windows could not start because of an error in the software.
Please report this problem as :
load needed DLLs for kernel.
Please contact your support person to report this problem.

...and when you choose to boot in Safe Mode, the last thing you will see loading is:


then you will see the same message as before:

Windows could not start because of an error in the software.
Please report this problem as :
load needed DLLs for kernel.
Please contact your support person to report this problem.

The meaning is that this file is probably missing or corrupt:


Since that is one of the 3498 files that Windows File Protection cares about, it should never be missing.  If it really is missing, it was probably quarantined (effectively deleted) by your unspecified antivirus/antimalware application.

There are likely to be good copies of the file on your system here:


or here:


There is also one on my SkyDrive that you can download to a working machine and sneakernet it using a floppy or USB memory device to the afflicted machine and copy it to where it belongs.

Depending on your registry setup, you may not be able to access the floppy or USB stick once you get into the Recovery Console, but you will always be able to using a Hiren's BootCD (it has it's own registry), but try the easy stuff first.

The kdcom.dll is the same for SP2 and SP3 so somehow or another you need to boot on something to replace your missing or corrupted one.

You can create a bootable XP Recovery Console CD (no XP media required) and then when you do, you would enter a command like this:

copy c:\windows\system32\dllcache\kdcom.dll   c:\windows\system32

or (depending how SP3 was installed).

copy c:\windows\ServicePackFiles\i386\kdcom.dll    c:\windows\system32

Respond in the affirmative if asked to overwrite and existing file and you should see a message the one file(s) was copied.

Make yourself a bootable XP Recovery Console first since that is easy and something you can always use on some other rainy day.  If that doesn't get it for you, or the file is nowhere to be found on your system, you can download it from my SkyDrive, but try the easy stuff first.

Here is how to make a bootable XP Recovery Console CD (no XP media required):

If you have no bootable XP media (or are not sure what you have) create a bootable XP Recovery Console CD and be sure what you have (no XP media required).

This is not the same as any recovery disks that might have come with a store bought system.

You can make a bootable Recovery Console CD by downloading an ISO file and burning it to a CD.

The bootable ISO image file you need to download is called:


Download the ISO file from here:

Use a new CD and this free and easy program to burn your ISO file and create your bootable CD (do not install UniBlue or the Ask Toolbar - ever!):

Here are some instructions for ImgBurn:

It would be a good idea to test your bootable CD on a computer that is working.

You may need to adjust the computer BIOS settings to use the CD ROM drive as the first boot device instead of the hard disk.  These adjustments are made before Windows tries to load.  If you miss it, you will have to reboot the system again.

When you boot on the CD, follow the prompts:

Press any key to boot from CD...

The Windows Setup... will proceed.

Press 'R' to enter the Recovery Console.

Select the installation you want to access (usually  1: C:\WINDOWS)

You may be asked to enter the Administrator password (usually empty).

You should be in the C:\WINDOWS folder.  This is the same as the

C:\WINDOWS folder you see in explorer.

The Recovery Console allows basic file commands like: copy, rename, replace, delete, cd, chkdsk, fixboot, fixmbr, etc.

For a list of Recovery Console commands, enter help at the prompt or read about the XP Recovery Console here:

A good idea before starting things is to first verify the integrity of your file system using the chkdsk command.

From the command prompt window run the chkdsk command on the drive where Windows is installed to try to repair any problems on the afflicted drive.

Running chkdsk is fine even if it doesn't find any problems.  It will not hurt anything to run it.

Assuming your boot drive is C, run the following command:

chkdsk C: /r

Let chkdsk finish and correct any problems it might find.  

It may take a long time for chkdsk to complete or it may appear to be 'stuck'.  Be patient.  If the HDD light is still flashing, chkdsk is doing something.  Keep an eye on the percentage amount to be sure it is still making progress.  It may even appear to go backwards sometimes.

You should run chkdsk /r again until it finds no errors to correct.

Then enter the copy commands and see if you can replace the kdcom.dll file and see how things work after that.

27 people were helped by this reply


Did this solve your problem?

Sorry this didn't help.

Great! Thanks for marking this as the answer.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this response?

Thanks for your feedback.