Luckily, Microsoft gave us a quick and easy way of repairing Windows XP, and it is already on the CD, ready for you to use in case you need it.
Steps to Repairing Windows XP 1. Put your Windows XP Install CD into your CD-ROM drive. 2. Reboot your computer. 3. Let your system boot off of the CD. 4. Let the Setup go through the first part of the Installation procedure. 5. When you come to the screen in which it says "Welcome to Setup." press Enter to Setup Windows XP, do not press R as this will just start recovery console.
6. Press F8 to agree to the End User License.
7. Let the Setup search your system for previous versions of Windows. 8. When the Setup is finished searching your system, select your Windows XP Installation and press the R key on your keyboard to start the Repair Procedure.
This is the part that might scare the you-know-what out of you. The Setup will delete all major system files and then replace them with new copies.
You will have to download all of the updates from Microsoft Windows Update again because it replaces the files.
Don't worry, your user data is still intact. Nothing has been lost, nothing has been deleted. Your data is safe, just the OS has been repaired, so relax.
There is nothing to worry about as long as you follow the steps to repairing Windows XP.
Did you upgrade your RAM all at once? If not, make sure that you have the same type, brand, and model RAM modules.
Every RAM module has a memory controller on-board. The memory controller tells the computer how to talk to it, and sometimes, another memory module doesn't talk the same way that the other module does, thus the system gets confused since it is getting mixed signals on which way to talk to the RAM.
Windows could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
That means the System Registry Hive has become corrupted.
There are two ways to get back up and running. The easy way which doesn't always work, and then there is the hard way.
Easy Way --- Note that this doesn't always work. When you are booting your system, press the F8 key during the start of the bootup sequence, meaning after it does the Power On Self Test.
Once you press the F8 key, you will be taken to a Menu. Select "Boot Using Last Known Good Configuration".
It will now attempt to load Windows XP using a past set of configuration files.
If that doesn't work, there is the next step....the hard way.
Hard Way Boot your system with the Windows XP Install CD, let the system boot into the Setup. Once in the Setup, choose to run the Recovery Console.
You will now be presented with a screen similar to good old DOS.
First, we will recover the System Hive.
Now, type in the following commands with pressing Enter after each line.
•The first thing you want to do is make an Emergency Repair Disk (will be referred to as ERD here on).
•Creating an ERD is a simple process, you can follow these steps.
•Make a backup copy of the windows\repair directory. Drag it with the right mouse button to a backup folder, and choose "Copy Here." Then rename the copied directory as the current date.
•You should now backup the registry. To do so, follow these steps.
•Once you receive the success message, click OK, and place the file in a safe place for future use.
•Now put in your Windows XP disk and reboot.
•It will run like a normal setup and when it gets done it will ask you if you want to install or repair.
•Click repair then choose repair with recover manually (have the ERD in the floppy drive now).
•It will come up with a DOS screen and you will see a C:\Windows, option should be to enter 1.
•It will ask you for root password and then type "fixmbr" to repair your mbr.
•Type help for more commands if you need to fix something else.
First, try a repair of Windows XP first. Documentation of how to repair Windows XP can be found here.
If that doesn't work, go into the Command Line Recovery Console and run the following commands.
bootcfg /rebuild ---- Rebuilds Boot.ini This scans all system hard drives for installations of Windows and allows you to add them to the boot.ini file.
If the XP install is the primary partition, you can run the "fixboot" to reinstall the boot loader of the partition.
You can also use the "fixmbr" if the XP partition is the primary booting partition.
System Restore can be used to remove any system changes that were made since the last time you remember your computer working correctly. System Restore does not affect your personal data files so you won’t lose changes made to these files. Windows XP creates "restore points" every day, as well as at the time of significant system events (such as when an application or driver is installed).
You can also create and name your own restore points at any time. Creating a restore point can be useful any time you anticipate making changes to your computer that are risky or might make your computer unstable. If something goes wrong, you select a restore point and Windows XP undoes any system changes made since that time.
Below is a detailed list of what is\is not restored: Restored:
•Registry •Profiles (local only—roaming user profiles not impacted by restore) •COM+ DB •WFP.dll cache •WMI DB •IIS Metabase •Files with extensions listed in the portion of the Monitored File Extensions list in the System Restore section of the Platform SDK
Not Restored:
•DRM settings •SAM hives (does not restore passwords) •WPA settings (Windows authentication information is not restored) •Specific directories/files listed in the Monitored File Extensions list in the System Restore section of the Platform SDK •Any file with an extension not listed as in the Monitored File Extensions list in the System Restore section of the Platform SDK •Items listed in both Filesnottobackup and KeysnottoRestore (hklm->system->controlset001->control->backuprestore->filesnottobackup and keysnottorestore) •User-created data stored in the user profile •Contents of redirected folders
This will enable a new version of IE6 to be downloaded and will place the IE6 into your Change/Remove applet in the Control Panel.
Now when you click on this program and click on the Change/Remove option, you will be able to add component or choose repair as in the older Windows OS's.
In Windows XP, the TCP/IP stack is considered a core component of the operating system; therefore, it is not possible to uninstall TCP/IP in Windows XP. However, the TCP/IP stack can be reset to the state when the OS was first installed.•Go to Start Menu -> RUN •Type "command" click OK•In the new window that pops up type this "NETSH INTERFACE IP RESET LOG.TXT" (less quotes), then press enter.•Reboot, if you like.More detailed information can be found in this MSKB article:
How to Perform an In-Place Upgrade (Reinstallation) of Windows XP This is a common method for repairing a pretty toasted system. It reinstalls the operating system but leaves all your software settings pretty much intact. It is a lot faster then re-installing the operating system and all your software. Make sure you read the link on how this can cause a loss of data and program settings!
When to Reinstall Windows XP Service Pack 1 This is a common question. With NT service packs had to be reinstalled just about any time you did anything to the system. Is this the case with XP?
Recovery Console ---------------- Recovery console is to an NTFS XP system like a boot floppy is to WIN9X. Here are a few articles giving you some helpful info about the feature. RC is not something you want to discover at the time you really need it. It is best configured while everything is working. Then you can forget about it.
BootVis.exe Tool This is a performance trace visualization tool for use with Windows XP systems. This version of BootVis.exe is compatible with final release of Windows XP (build 2600) and resolves a compatibility issue when using third-party IDE drivers.
A: When you get your accounts and passwords set up to your satisfaction, use the instructions found in MSKB Article # 305478 to create a password reset disk for a computer that is not a domain member in Windows XP.
The instructions for making a password reset disk for a computer in a domain in Windows XP can be found in MSKB Article # 306214.
Make a couple of sets, put them in two different 'safe' places and sleep better, knowing that you have these on hand should you need them. One word of caution, these disks can be used by anyone to bypass passwords. If you require high security, be sure to keep these disks in a secure location. How often these disks need to be made is dependent on how often you change or add passwords.
Below is a series of Microsoft Knowledge Base articles that will help you understand how drive letters are assigned and what you can do to keep yours like you want them.
Recovery Console is a DOS-like interface that allows one to access their system files when booting into WINXP is no longer possible. From the Recovery Console prompt one can often repair their system or sometimes recover files. For a complete description of the Recovery Console read this article. Description of the Windows XP Recovery Console
Setting the group policy to allow floppy access and access to non-system folders from within Recovery Console can significantly enhance your data recovery abilities. This must be done before disaster strikes! It takes a minute to do and can save hours of work. Read this article for instructions. HOW TO: Add More Power to Recovery Console By Using Group Policy in Windows XP Professional
File permissions are the system's way of telling you what you can and cannot do with a file or folder. They are governed by Access Control Lists (click for definition).
There are two ways of setting file permissions. You can do it the graphical way or the command-line way.
To do it graphically, you must have Simple File Sharing disabled from the View tab of Folder Options (Professional only) or be in Safe Mode (either). Right-click on the object of your choice and click Properties. Then go to the Security tab. Here you are presented with a list of users and groups and a small list of permissions. More permissions are available when you click Advanced.
Some rules of thumb:•Stick to the main security screen unless you're absolutely sure of what you're doing•Deny takes precedence over allow, so do not deny groups anything unless you are absolutely sure of what you are doing. If you deny something to the Users group, you deny that permission to everyone who is authenticated. Use even more diligence with denying everyone anything. •If no ruling is made on a permission to allow or deny, the system defaults to denying access.•Check yourself by using the Effective Permissions tab in the Advanced dialog.
XCACLS filename [/T] [/E|/X] [/C] [/G user:perm;spec] [/R user [...]] [/P user:perm;spec [...]] [/D user [...]] [/Y]
Description: Displays or modifies access control lists (ACLs) of files.
Parameter List: filename Displays ACLs.
/T Changes ACLs of specified files in the current directory and all subdirectories.
/E Edits ACL instead of replacing it.
/X Same as /E except it only affects the ACEs that the specified users already own.
/C Continues on access denied errors.
/G user:perm;spec Grants specified user access rights.
Perm can be: R Read C Change (write) F Full control P Change Permissions (Special access) O Take Ownership (Special access) X EXecute (Special access) E REad (Special access) W Write (Special access) D Delete (Special access)
Spec can be the same as perm and will only be applied to a directory. In this case, Perm will be used for file inheritance in this directory. By default, Spec=Perm. Special values for Spec only: T Valid for only for directories. At least one access right has to follow. Entries between ';' and T will be ignored.
/R user Revokes specified user's access rights.
/P user:perm;spec Replaces specified user's access rights. Access right specification as same as /G option.
/D user Denies specified user access.
/Y Replaces user's rights without verify.
NOTE: Wildcards can be used to specify more than one file. More than one user can be specified. Access rights can be combined.
Basically, if you want to give user "Bob" full access to dummy.exe without being asked if you are sure, here is the command: xcacls dummy.exe /G Bob:F /Y /C
If you want to deny Bob execute rights to dummy.exe, run xcacls dummy.exe /D Bob:X /Y /C
Warning: XCACLS is a powerful and extremely dangerous tool. Use it at your own risk. This tool is not in any way supported by Microsoft.
For an example on how Xcacls is used, see this thread from the Microsoft Help forum.
We have more then one member complain about missing CDROMs/DVDs from their XP system. A look in Device Manager shows an exclamation mark next to their drive(s). Microsoft attributes one of the causes of this to the removal of CD recording software, particularly (but not exclusively) EZCD Creator. Microsoft has a knowledgebase article referring to this problem. and offers a solution that seems to work in most cases.
Windows XP's Powertoys are indeed very powerful (particularly TweakUI), but sometimes changing settings in TweakUI may cause the icons to take a much less colorful, and quite ugly look, a la Windows 95 or NT.
Now this doesn't always happen, and if it doesn't, then you needn't worry. However, if it does, there are two simple ways to fix them.
First you can try the Repair icons feature within TweakUI itself. Its procedure flushes the cache and reload the icons. This can be done as seen in the screenshot here:
If that does not work, don't despair. This probably means that the registry settings for the icons was changed.
A .reg fix can be downloaded from Kellys Korner or you can attempt to do it yourself.
If you choose the latter, simply go open up Regedit ( Start -> Run -> regedit ), then nagivate to
If you are having trouble with any of the following:•How do I repair or reinstall the GUEST ACCOUNT?•Cannot access Internet Explorer from GUEST ACCOUNT after changing default browser to Mozilla.•Deleting and repairing a corrupt GUEST ACCOUNT.•I deleted the GUEST ACCOUNT from the C:\ drive, and now the GUEST ACCOUNT can not be used!To restore the default GUEST ACCOUNT in Windows XP, follow these steps:•Log on as Administrator•Go to Start > Control Panel > User Accounts.•Turn Guest Account off.•Go to Start > right click on My Computer > in System Properties go to Advanced tab > User Profiles > click on Settings > highlight Guest Account > click Delete button > click OK.•Close System Properties.•Go back to Start > Control Panel > User Accounts•Turn Guest Account on.•Log off as Administrator•Log on as GuestThe screen will go black for a few moments while Windows recreates the Guest Account. Wait until the log on screen appears.
When the log on screen appears, click Guest, and a new Guest Account will be in place.
The network service svchost.exe is in charge of running basic network chores, one of which is loading and resolving entries for the DNS cache. Normally this is fine and the process will not interfere with anything. But if svchost is running for extended periods of time and consumes 50-100% of your CPU, it becomes a hassle and will not allow you to use the internet until it's done. If you have access to reliable DNS servers, disabling DNS caching can put an end to svchost's reign over your internet connection. To disable DNS caching:•Type services.msc into the run command (which can be found in the start menu)•In the services.msc window, scroll down to DNS Client. Right-click on it and select properties.•Click on stop then change the startup type to manual and click apply.Now you'll need to ensure you have your DNS servers setup.•Go to the control panel, click on network connections, then right-click on the active connection and select properties.•Select TCP/IP and press properties.•Now enter your ISP's DNS servers or enter the IP address of your router if it has the capability of obtaining DNS information.
While trying to install or run an application, your system displays the error: WINDOWS\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications.
If you get an error naming the AUTOEXEC.NT as not being suitable, it is an indication the AUTOEXEC.NT file in the WINDOWS\SYSTEM32 folder is missing or corrupt.
A backup copy of the AUTOEXEC.NT file is kept in the WINDOWS\repair folder.
To fix the error, copy the AUTOEXEC.NT file from the WINDOWS\repair folder and paste it into the WINDOWS\SYSTEM32 folder.
There are occasions where file and folder ownership (permissions) are lost. This can occur when you reinstall the operating system or when moving drives from one machine to another. Fortunately, Microsoft has provided detailed instructions on taking ownership back.
Note - this article applies to both Home and Pro versions. In either system. you must be logged on to the computer with an account that has administrative credentials.
•If you are running Microsoft Windows XP Home Edition, you must start the computer in safe mode, and then log on with an account that has Administrative rights to have access to the Security tab.•If you are using Windows XP Professional, you must disable Simple File Sharing. By default, Windows XP Professional uses Simple File sharing when it is not joined to a domain.
Help! Why are my CD-ROM drives not showing in My Computer? Why are there yellow exclamation marks by the CD-ROM drives in Device Manager?
One of the reasons why this can happen is because the drivers that allow the CD-ROM drives to work in Windows XP have become corrupted.
The first thing to try is this Registry File. Remove the devices in Device Manager and reboot. The CD-ROM drives should work now.
If not, try these steps. Warning! These steps are not for the faint at heart.
Open the Device Manager and right-click on the CD-ROM drive that has a yellow exclamation mark by it.
Go to the Driver tab and click on the Driver Details button.
You should now have this window...
Look at each of the driver files that are being used for the CD-ROM drive, specifically the ones that aren't made by Microsoft. For instance, in the screen shot above is just one example of a device driver that isn't made by Microsoft. Copy all of the file names of the drivers that aren't made by Microsoft, you will need them for the next step.
Open up RegEdit and find all instances of those file names that you copied down in the last step. Delete any and all references that contain those file names.
Next, go into the Device Manager and delete the CD-ROM devices. Now, go to Add New Hardware and let it search for new devices. It should reload the CD-ROM devices minus the third-party device drivers, only the Microsoft supplied ones.
When you open Add/Remove Programs applet and click an application entry, you may notice that the Change, Remove (or Change/Remove) buttons may be missing, thus leaving only the application name entry there.
Here is a method to make Windows show the Remove, Change (or the Change/Remove button together) buttons in the listing.
RESOLUTION
•Click Start, Run and type REGEDIT. This starts the Registry Editor. Navigate to: HKEY_LOCAL_MACHINE \SOFTWARE \Microsoft \Windows \CurrentVersion \Uninstall \
•In the right-pane, do the following:
Double-click NoRemove (REG_DWORD) and set it to 0 Double-click NoModify (REG_DWORD) and set it to 0
If NoRemove is set to 1, the Remove button will be unavailable If NoModify is set to 1, the Change button will be unavailable
Final result is you'll get the Change and Remove buttons back (or, the Change/Remove button together).