Question about Microsoft Windows XP Professional With Servise Pack 2 (e8503040) for PC

1 Answer

Windows installer not found

My friend has a windows xp service pack-2, and due to some boot error the window got corrupt. i want to restore it back to as it was earlier, since no possible solutions are working as per the dell help manual, plz suggets how to get back the laptop ( dell vostro a860n) to its original configuration.

Posted by on

  • Ariane
    Ariane May 11, 2010

    Im not sure i understand what is corrupt, do you mean you were trying to install sp2 and now nothings working and you want to take it off?



    If so you can use this method http://support.microsoft.com/kb/875350

×

1 Answer

  • Level 2:

    An expert who has achieved level 2 by getting 100 points

    MVP:

    An expert that gotĀ 5 achievements.

    Governor:

    An expert whose answer gotĀ voted for 20 times.

    Scholar:

    An expert who has written 20 answers of more than 400 characters.

  • Expert
  • 116 Answers

Does the Vostro have PCRestore (some business lines do not).

To verify see if there is a bar along the top that says WWW.DELL.COM just after the Dell logo during startup.

if it exists shut down the computer, power it up, hold the CTRL key and tap the F11 key a few times, it will bring up PCRestore for XP systems.

If you post the actual error we can probably fix it without reinstalling.

Posted on Feb 05, 2009

×

1 Suggested Answer

6ya6ya
  • 2 Answers

SOURCE: I have freestanding Series 8 dishwasher. Lately during the filling cycle water hammer is occurring. How can this be resolved

Hi,
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
goodluck!

Posted on Jan 02, 2017

Add Your Answer

Uploading: 0%

my-video-file.mp4

Complete. Click "Add" to insert your video. Add

×

Loading...
Loading...

Related Questions:

1 Answer

My windows XP has an error message when started. It says "MISSING NTLDR, PRESS CTRL, ALT, DEL TO RESTART" I tried restart with boot disk but nothing. Please help!?


How to Fix NTLDR Errors

  1. Restart the PC. The NTLDR error could be a fluke.
  2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.

    Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
  3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.

    Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
  4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.
  5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.
  6. 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 "NTLDR is Missing" error.
  7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
  8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.

    Try replacing the IDE cable cable if you suspect it might be faulty.
  9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
  10. 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.
  11. 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. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.

    If you can't gain access to your files to back them up, understand that you will

Jan 22, 2014 | Belkin Basic Wireless Router

Tip

Boot problems and their possible causes & resolutions


Symptoms:
Black screen
"Invalid Partition Table"
"Error loading operating system"
"Missing operating system"


Cause:
Corrupt Master Boot Record (MBR)

Resolution:
Boot into Recovery Console and run "fixmbr" to repair the MBR

--

Symptoms:
"A disk read error occurred"
"NTLDR is missing"
"NTLDR is compressed"


Cause:
Corrupt boot sector

Resolution:
Boot into Recovery Console and run "fixboot" to repair the boot sector

--

Symptoms:
"BOOT.INI is missing or corrupt"
"Boot device inaccessible"
"Windows could not start because the following file is missing or corrupt:
<Windows root>\system32\hal.dll"


Cause:
BOOT.INI missing, corrupt or out of date as a partition has been inserted

Resolution:
Boot into Recovery Console and run "bootcfg /rebuild" to repair the BOOT.INI

--

Symptoms:
"Windows could not start not start because the following file is missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM"


Cause:
Corrupt/missing system hive

Resolution:
1. Boot into Recovery Console and run "chkdsk C: /f" to check the system disk for errors and fix them, then reboot.
2. If the error continues and System Restore is enabled, copy the system hive from the last restore point into \WINDOWS\SYSTEM32\CONFIG
3. If the error continues, copy the system hive from \WINDOWS\REPAIR into \WINDOWS\SYSTEM32\CONFIG
4. If the error continues, perform a repair installation by booting from the Windows installation media


--

Symptoms:
"Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk, Check boot path and disk hardware."


Cause:
Boot volume (with Windows folder) is not accessible as defined in BOOT.INI

Resolution:
Check the boot volume is accessible

--

Symptoms:
Dual-boot 32-bit Windows and 64-bit Windows system reports "NTOSKRNL.EXE is corrupt" trying to boot into 64-bit Windows

Cause:
System volume contains an older boot loader than the boot volume requires - e.g. XP SP2 installed after XP x64

Resolution:
Copy NTDETECT.COM and NTLDR from XP x64 installation media to the root of the system volume

on May 03, 2010 | Computers & Internet

3 Answers

<windows root>\system32\hal.dll file is


Resolution

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.

Note: If repairing the boot.ini does correct the hal.dll issue but the problem reappears after a reboot and you've recently installed Internet Explorer 8 in Windows XP, uninstall IE8. In this specific situation, IE8 could be the root cause of your hal.dll problem.

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. Recover data from any bad sectors on your hard drive. If the physical part of your hard drive that stores any part of the hal.dll file has been damaged, you're likely to see errors like this.

7. 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.

8. 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.

9. 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, you should understand that you will lose them all if you continue with a clean installation of Windows XP.

10. Test the hard drive. 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 but you'll want to test it to be sure.

If the drive fails any of your tests, replace the hard drive and then complete a "new" installation of Windows XP.

Mar 09, 2011 | Microsoft Computers & Internet

2 Answers

My window xp2 is not installing window installer 3.1 help me


Windows Installer 3.1 Redistributable supports Windows 2000 with Service Pack 3 or later, Windows XP, Windows XP Service Pack 1, Windows XP Service Pack 2 and Windows Server 2003. Windows Server 2003 Service Pack 1 contains Windows Installer 3.1 and therefore can't be installed or upgraded by this redistributable.

Read the above, Windows Installer 3.1 already in in SP2. Why do you need to install it?

Jul 14, 2010 | Microsoft Windows XP Professional

2 Answers

The file <windows root>\system32\hal.dll.


Restart the PC. The hal.dll error could be a fluke.
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.
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.
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.
Note: If repairing the boot.ini does correct the hal.dll issue but the problem reappears after a reboot and you've recently installed Internet Explorer 8 in Windows XP, uninstall IE8. In this specific situation, IE8 could be the root cause of your hal.dll problem.
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.
Recover data from any bad sectors on your hard drive. If the physical part of your hard drive that stores any part of the hal.dll file has been damaged, you're likely to see errors like this.
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.
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.
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.

Feb 15, 2010 | Dell Latitude E5500 Laptop

1 Answer

Installed Windows Vista Service Pack 2 - now windows won't boot


first boot from the windows xp cd....
delete the existing partition in which windows was installed...create a new partition
do a fresh install of windows .....
this will solve all your problems

Dec 19, 2009 | Microsoft Windows Vista Home Premium with...

3 Answers

Windows XP won't start


for that you need winxp bootabler disk.
Tehn boot your computer with tht and go to recoverry console.
Then type in command prompt "chkdsk /r"
then press "y"
then it fixc error on harddisk.
Then after completing it restart your computer and boot with harddisk then it ok.

Jun 20, 2009 | Computers & Internet

2 Answers

Windows system 32 hal.dll error after restoring e-machine


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.

Apr 10, 2009 | E-Machines eMachines Desktop PC

3 Answers

Bootup failure


Cause:
  1. Keyboard issue
  2. Miscellaneous corruption
  3. Corrupt boot.ini file.
  4. Missing boot.ini file.
  5. Missing or corrupt ntoskrnl.exe file.
  6. Windows NT installed on a partition bigger then 7.8GB
  7. Corrupted hard disk drive or severely corrupted Windows.
Solution:Keyboard issue
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.
Miscellaneous corruption
Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.
Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.
Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.
Microsoft Windows NT and Windows 2000 users:
To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
  1. Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
  2. In the setup menu, type R to start the repair.
  3. When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file
If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
  6. You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
  7. Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB
If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the error message as shown below.
OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.
If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.
Corrupted hard disk drive or severely corrupted Windows
Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.
  1. Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
  2. Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
  3. In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
  4. Select the operating system you wish to fix, and then enter the administrator password.
  5. Once at the recovery console type chkdsk /r
  6. Once completed type exit and see if issue is resolved.

Dec 05, 2008 | Acer Aspire 3624WXCi Notebook

2 Answers

How do I...


NTOSKRNL.EXE is missing or corrupt.

Related errors:

Below is a listing of the full error message that may be related to this error.

Windows NT could not start because the below file is missing or corrupt:
C:\Winnt\System32\Ntoskrnl.exe

Cause:
Keyboard issue
Miscellaneous corruption
Corrupt boot.ini file.
Missing boot.ini file.
Missing or corrupt ntoskrnl.exe file.
Windows NT installed on a partition bigger then 7.8GB
Corrupted hard disk drive or severely corrupted Windows.
Solution:
Keyboard issue
This issue has also been known to be caused by a short in the ground wire in the keyboard cable. Make sure this is not the cause of your error by replacing the keyboard with a different keyboard or simply just disconnecting the keyboard from the computer.

Miscellaneous corruption
Before trying any of the below recommendations it's recommend that you attempt to load the last known good configuration. Additional information about doing this can be found on document CH000626.

Corrupt boot.ini file
This issue is often caused when the boot.ini is missing or improperly configured. This issue often arises after a user has recently added or removed an operating system on the computer or added or removed hard disk drives in the computer.
Make sure the line pointing to the operating system and it's drive and partition is properly configured in the [boot loader] and [operating systems] section. Additional information about boot.ini can be found on document CH000492.

Missing boot.ini file
Microsoft Windows XP users:
If the boot.ini is severely corrupted or missing a user running Microsoft Windows XP can rebuild the boot.ini to resolve this issue. Additional information about rebuilding the boot.ini can be found on document CH000648.

Microsoft Windows NT and Windows 2000 users:

To restore the original boot.ini file in Microsoft Windows NT or Windows 2000 you will need an ERD and follow the below steps. If you do not have an ERD you will be unable to follow these steps.
Boot the computer with your Windows NT three setup diskettes or the Windows 2000 setup disc.
In the setup menu, type R to start the repair.
When prompted for the ERD diskette insert the diskette and inspect the startup environment.
Missing or corrupt ntoskrnl.exe file
If the ntoskrnl.exe file is corrupt or missing this can also generate the error. To restore this file follow the below steps.
Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Type expand d:\i386\ntoskrnl.ex_ c:\windows\system32
You will then be prompted if you wish to overwrite the file type Y and press enter to overwrite the file.
Type exit to reboot the computer.
Windows NT installed on a partition bigger then 7.8GB
If you are running Microsoft windows NT 4.0 on a partition larger than 7.8GB this issue can occur if the boot files are located outside this limitation. When this error occurs your computer will have the

error message as shown below.

OS Loader v4.01
Disk I/O error status=00000001
Windows NT could not start because the below file is missing or corrupt: winnt\system32\Ntoskrnl.exe
Please reinstall a copy of the above file.

If your system partition is larger than 7.8GB you will need to delete the partition and recreate the partition to 7.8GB or less. Additional information about this issue can be found on Microsoft KB Q224526.

Corrupted hard disk drive or severely corrupted Windows
Attempt to check the hard disk drive for any errors by running the chkdsk error. To do this follow the below steps.

Insert the Microsoft Windows XP CD. Note: If you have a recovery CD or a restore CD and not a Microsoft Windows XP CD it is likely the below steps will not resolve your issue.
Reboot the computer, as the computer is starting you should see a message to press any key to boot from the CD. When you see this message press any key.
In the Microsoft Windows XP setup menu press the R key to enter the recovery console.
Select the operating system you wish to fix, and then enter the administrator password.
Once at the recovery console type chkdsk /r
Once completed type exit and see if issue is resolved.
If after trying all of the above steps you are still encountering the same issue it's likely that Windows is severely corrupted and it is recommended you attempt to reinstall Windows. Additional information about erasing the computer and starting over can be found on document CH000186.
Finally, if during the Windows installation you encounter errors it's likely that your hard disk drive is bad.

Oct 09, 2008 | Dell OptiPlex GX110 PC Desktop

Not finding what you are looking for?
Microsoft Windows XP Professional With Servise Pack 2 (e8503040) for PC Logo

74 people viewed this question

Ask a Question

Usually answered in minutes!

Top Microsoft Computers & Internet Experts

micky dee

Level 3 Expert

2644 Answers

Les Dickinson
Les Dickinson

Level 3 Expert

18381 Answers

Brian Sullivan
Brian Sullivan

Level 3 Expert

27725 Answers

Are you a Microsoft Computer and Internet Expert? Answer questions, earn points and help others

Answer questions

Manuals & User Guides

Loading...