Member Avatar for KF4SQB

I've searched for and found other instances of my problem on here, but the answers given weren't helpful to me, so here goes:

I have an install of Windows XP Pro that failed to boot, with an "Operating System Not Found" error, after a software install. I've slaved the HDD with another running XP to run a virus scan, defrag, and check for errors. Virus scan came back clean (AVG 7.5 Free Edition, fully updated), and the Windows disk check utility didn't report any errors (I don't remember if it automatically reports or not. I miss the old DOS scandisk!). Apparently, the disk check did do something, because it then booted to a screen saying that "<windows root>\system32\hal.dll" was missing or corrupted, and advising me to reload it. I did that by booting into the recovery console with the XP CD. Then got a message that "<windows root>\system32\ntoskrnl.exe" was missing or corrupted, so I reloaded it, too. After that, I got a message that "Windows could not start because of an error in the software. Please report this problem as: Load needed DLLs for kernel." What I need to know is, which DLLs is it referring to, so that I can load them?

  • 2 Contributors
  • 1 Reply
  • 124 Views
  • 6 Hours Discussion Span
  • Latest Post Latest Post by dos_centavos

Dani AI

Generated

Brief summary and a focused recovery checklist (building on 's points).

The symptoms described by — an XP install that stopped booting after a software install, a slave-disk scan, CHKDSK activity and manual recovery-console file restores — point to either (a) broader corruption of core system files, (b) a damaged/incorrect boot area (MBR/boot sector/partition flag), or (c) a mismatch between restored files and the original XP build/service pack. A full reinstall will work, but there are intermediate steps that often recover the system while preserving data.

Practical next steps (in priority order):

  • Back up user data now (attach the drive to another machine, boot a Linux Live CD or Windows PE and copy the Users folder and any hidden application data). Image the drive if possible.
  • Verify BIOS sees the drive and check jumpers/cables/SATA mode — a drive that moves between systems or has wrong settings can show kernel-load symptoms.
  • Run the drive vendor’s diagnostic (SeaTools, WD Data Lifeguard, etc.) to rule out hardware faults or failing SMART attributes.
  • From the XP Recovery Console, repair disk and boot structures and attempt file restoration:
chkdsk /r
fixmbr
fixboot

If individual system files are still corrupt/missing, restore them from the same XP installation media (exact edition and service pack) using the Recovery Console expand syntax to copy from the i386 folder. Mixing files from a different SP, Home vs Pro, or another machine can make the problem worse.

If those steps fail, perform the XP in-place repair (boot from the XP CD, press R) — it replaces system files but keeps programs/data; afterwards reapply service packs, updates and drivers. If repair still fails or the disk has physical defects, a clean install after data backup is the final option.

Notes and cautions: SFC cannot be run offline on XP, so a repair install or proper expand restores are the reliable ways to fix multiple corrupted system files. Avoid copying single system files from arbitrary PCs — always use matching media.

Member Avatar for dos_centavos

At his point it sounds as though the entire XP Pro installation is totally shot. Can you boot to safe mode? Even though you were capable of restoring specific files from the recovery console you might want to list the contents of the system32 folder using the recovery console. This is where windows stores the majority of the OS. My system32 folder contains 2,413 files not to mention 262 sub folders that contain an additional 4,470 files. If the system32 folder is toast the best option you have available is to use another system to copy and save all of your user data and do a clean install of XP.

The other option available is to reinstall XP over the top of what you currently have using the repair option. The problem with this approach though is it does not clean up the registry and it overlays any maintenance you have installed on XP up to this point.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.