|
Windows Troubleshooting Tips and Links
When you are experiencing a computer related problem there
oftem seems to be an empty pit in your tomach as you wonder
whether the computer problem you are experiening is fixable
or not and what it may take to resolve the problem. I have
included some of my favorite links and excerpts from sites
that I hold in high regard and hope that you may find
some solace in the suggestions that these excerpts and links offer.
Page Under Construction Information is listed here for educational
and reference to other web sites with helpful information to help
solve problems with the Windows operating systems. Techniques
should only be used by qualified technicians. Use at your own risk.
One of the many new features in the Windows Vista operating
system is a utility called the Startup Repair Tool. What makes
this new tool stand out among its brethren is that is designed to
intercede at the first hint of an operating system startup problem.
When a startup problem is detected, the Startup Repair Tool will
launch an automated, diagnostics-based troubleshooter that requires
little if any user intervention and will resuscitate an unbootable system.
http://articles.techrepublic.com.com/5100-10877_11-6131173.html
"Must have" Utilities
The basic premise of this page is not to host all of the hundreds
of the Windows 2000 Utilities and shareware that's available,
just award winning software which we've personally used and
a few smaller utilities that we've think are essential. For
more award winning utilities, check out site
http://www.mcsetoolkit.com
http://labmice.techtarget.com/Utilities/default.htm
http://www.smartcomputing.com
Windows 2000 Information and Resources on the Internet
http://www.infosyssec.net/infosyssec/win2000.htm
The Security Portal for Information System Security Professionals
http://www.infosyssec.net/index.html The most comprehensive
computer and network security resource on the Internet for
Information System Security Professionals- Says Yahoo Editors
PC Crashes are caused mainly of the following:
1. Inappropriate Software drivers for a new hardware or inappropriate hardware
2. Virus attacking the Windows operating system
3. Corrupted Windows Registry If you have recently installed a new device,
for example, a new TV PCI adapter, check to see if the software drivers you
have installed are appropriate to your particular hardware configuration.
You will be able to tell if it is the one causing the crash if after you remove
the new hardware physically, your computer stops crashing. To resolve
this, you have to check with the hardware vendor what appropriate software
driver for your PC is. They could have an updated driver for you to download
to fix a bug to the software driver. A virus, spyware, or trojan attack can
also be the cause of a computer crash.
These viruses commonly attack the Windows Operating System core files
like the ntdll.dll and ntoskrnl.exe files. Viruses come from clicking on an
unknown link or opening an attachment from an e-mail.
Always keep your anti-virus definition files updated to be able to detect
and clean the latest PC virus infections. Windows Registry corruption
is also a common cause of PC crash. Frequent installation and un-installation
of programs and corrupted software drivers lead to corrupted Windows Registry.
The Windows registry, stored on your PC in several files, records
the relationships or links between hardware, memory space, and addressing.
If these links are broken, your PC will malfunction, hang or crash.
A good Registry Cleaner tool is needed to automatically restore these
links. Manual registry cleaning using regedit is not recommended since
setting those data type and values manually is also one of the main
causes of invalid links in the registry. Recommendations to fix and
prevent computer crashes:
. Install new hardware with the latest software drivers from the
hardware vendor. Check hardware compatibility with your existing PC.
. Always keep updated on Microsoft Patches to prevent security
vulnerability attacks on the Windows core operating system.
. Run Registry Cleaner tool regularly, at least once a week, to
clean any errors on the registry.
. Always keep your Spyware removal tool and anti-virus software updated
of latest spyware and virus definitions. Regularly scan your PC
and remove spywares and viruses. Getting the debugger
The debugger is free and available from Microsoft's Web site.
At the site, scroll down until you see the heading, "Installing Debugging
Tools for Windows." Select the link, "Install 32-bit version."
and then select the most recent non-beta version and install it.
The most recent versions are about 12M-byte downloads.
You can do the installation on a PC without restarting it
(Don't be surprised if the site has changed somewhat.
Microsoft keeps improving the debugger with releases at least once per year.).
http://www.networkworld.com/news/2005/041105-windows-crash.html?page=2
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
Debugging Tools for Windows - Overview You can use Debugging Tools
for Windows to debug drivers, applications, and services on systems
running Windows NT 4.0, Windows 2000, Windows XP, Windows Server 2003,
Windows Vista, and Windows Server codename "Longhorn," as well as
for debugging the operating system itself. Versions of the Debugging Tools
for Windows package are available for 32-bit x86, native Intel Itanium, and
native x64 platforms.
The latest release of Debugging Tools for Windows is available for download
from the web. You can also install the package from the Windows DDK,
Platform SDK, or Customer Support Diagnostics CD. Accessing the
Recovery Console Even though the Recovery Console is part of Windows 2000,
It isn 't installed by default--probably because it consumes an extra 74MB
of hard disk space. If you need access to the Recovery Console, you have a
couple of choices. Before the system ever crashes, you can install it directly
through the Windows 2000 graphical user interface.
If a crash has already occurred, you can install the Recovery Console
by booting from the four Windows 2000 startup disks and following the prompts.
(Of course, if the crash has already occurred and you don't have enough
free hard-disk space to install the Recovery Console--or if the hard disk is
too badly damaged to install or access the Recovery Console--you can always use
ERD Commander Professional to get in and clean up the hard disk.
It works directly off floppy disks and doesn't have to be installed to the hard disk.)
To install the Recovery Console on a functional Windows 2000 system, follow these steps:
1. Close any open programs and open a Command Prompt window.
2. Insert your Windows 2000 CD and navigate to the I386 directory (or
the Alpha directory, if you're using an Alpha system).
3. Enter the following command to install the Recovery Console: [code]
WINNT32 /CMDCONS 4. If the system has already been damaged,
boot your computer from the first setup disk. If you don't have these disks,
you can easily create them on any PC by using the disk images stored on
the Windows 2000 CD.
5. Once your system boots, follow the prompts as if you're installing Windows
2000 until you reach the point at which where Setup asks if you want to repair
an existing installation. Enter "R" to begin the repair process.
6. You'll be asked if you prefer to use the Recovery Console or the emergency
repair disk. Select the Recovery Console option and continue to follow the
prompts to install the Recovery Console. Once you've installed the
Recovery Console, you can access it by rebooting your PC and
selecting the Recovery Console command from the boot menu.
As I mentioned earlier, you'll have to enter the Administrator password
before you 'll be able to use the Recovery Console. Once the Recovery Console
loads , you 'll be presented with a standard DOS screen.
Most of the usual DOS commands work in this environment; however,
some new commands are available, as listed in the sidebar "Recovery
Console Commands". You can put these commands to work as you fix Windows 2000.
http://www.enterprisenetworkingplanet.com/netsysm/article.php/623601
--> --> How to Create Windows 2000 Emergency Repair Disks -->
How to Create Windows 2000 Emergency Repair Disks
The following instructions will help you to create the disks that, in the event
of a severe system crash, will help you to repair or restore your Windows 2000 system.
For the best protection, please create both boot disks and emergency repair
disks. How to Create Windows 2000 Emergency Repair Disks
1. Click on Start -> Accessories -> Accessories -> System Tools -> Backup
2. On the Tools menu, click Create an Emergency Repair Disk.
3. Follow the instructions that appear on your screen. Important
. You will need a blank 1.44 MB floppy disk to create an Emergency Repair Disk (ERD).
. The repair process relies on information that is saved in
the systemroot\Repair folder (systemroot being your Windows 2000 directory).
You must not change or delete this folder. Notes
. Choosing Also back up the registry to the repair directory will save
your current registry files in a folder within your systemroot/repair folder.
This is useful if you need to recover your system in the event your hard disk has failed.
. Additional information on the repair process is available from Microsoft
through the Microsoft Help and Support web page.
1. Create a backup copy of your current BIOS. Before you install a new
or changed BIOS, save the old version. Every Flash tool includes an option
such as "Save current BIOS as" (see Screenshot D).
With the help of a backup, you can always get your system up and
running again if a new version or changes to settings cause problems.
2. Change only one setting at a time. When running the BIOS Setup
program, make changes carefully, one at a time, and in small increments
where applicable.
Restart you PC after each change and take it on a test drive under
Windows to make sure things work properly.
This is the only safe way to determine what impact individual
settings changes have on your PC.
3. Run stress tests or benchmarks. Running your system under heavy or full load
is the best way to determine whether or not aggressive settings cause problems
when the PC is put to work. For this purpose, parallel use of massively networked
applications such as online games, video editing, or 3D benchmarks such
as 3DMark 2005 work best.
4. If all else fails, try a cold boot. If the PC won't boot after pressing the Reset
button, turn off the computer and wait a minute or two before turning it back on.
Use the switch on the power supply, not the buttons on the front of your PC.
5. Erase the CMOS. When the PC won't boot any more after you make
BIOS changes, you won't be able to access the BIOS Setup program to
back those changes out. Should this happen, you'll need to erase the
CMOS memory in which the BIOS settings reside. Follow the instructions
for clearing or resetting CMOS from your motherboard (or system) manual.
In some cases, this requires moving a jumper to bridge contacts that are
designed to send a "Clear CMOS" instruction to that memory. This may
mean actually moving a physical jumper block on the motherboard,
or may require flipping a DIP switch. Remember to remove that jumper
after you 've cleared the CMOS. Another possibility is removing the
CMOS battery and unplugging the PC from the wall. This may take
several hours to work reliably, however. hich can wreak havoc on your system.
http://searchwincomputing.techtarget.com/tip/0,289483,sid68_gci1063916,00.html
By: Daniel Petri
How can I easily control what applications will run when my computer starts?
If you want to edit the startup locations manually, just
look at the following REGISTRY keys:
HKU\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Run HKU\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce HKLM\Software\Microsoft\Windows\CurrentVersion\Run HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx HKCU\Software\Microsoft\Windows\CurrentVersion\Run HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce
You should also look in the startup folders for all users and the current version.
If you're using Windows 9X or ME, you have the MSCONFIG utility to control what loads in your Startup Group, as well as from various places in the Registry.
Windows XP brings back MSCONFIG as a native tool and that version of MSCONFIG will work great in Windows 2000. You can download the XP version of MSCONFIG from HERE (64kb).
To make your life easier, take a look at 3 cool freeware applications that can easily help you do what you want.
AutoRuns
From Sysinternals. This applet shows you what programs are configured to run during system bootup or login. These programs include ones in your startup folder, Run, RunOnce, and other Registry keys. You'll probably be surprised at how many executables are launched automatically.
You can download it from HERE (v1.2, 32kb)
Startup Control Panel
A nifty control panel applet that allows you to easily configure which programs run when your computer starts. It's simple to use and, like all my programs, is very small and won't burden your system. A valuable tool for system administrators! Startup Control Panel is compatible with all modern versions of Windows, including Windows 95, 98, 98SE, ME, NT 4.0, 2000, and XP.
You can download it from HERE (v2.7, 66kb)
StartupMonitor
A small utility that runs transparently (it doesn't even use a tray icon) and notifies you when any program registers itself to run at system startup. It prevents those utterly useless tray applications from registering themselves behind your back, and it acts as a security tool against Trojans like BackOrifice or Netbus.
Download it from HERE (v1.02, 60kb).
http://www.petri.co.il/configure_auto-starting_applications.htm
How to Remove Startup Programs
by Mitch Tulloch
08/22/2006
The longer you own a Windows PC, the slower it boots up. This is because you will likely install numerous applications on your computer over time. Some of these applications will be boxed software purchased from Office Depot or Staples, but most will probably be applications you've bought online after downloading free trial versions for evaluation. The problem is that many programs you buy from stores or download from the Internet will install programs or services that start up automatically whenever Windows starts. So after a while, starting Windows also means starting lots of other stuff that runs in the background, out of sight. If your computer has lots of memory, you might not notice too much of a startup delay. And of course some applications are justified in automatic startup--antivirus programs and third-party firewalls being a good example. But a lot of applications start up programs or services when they really aren't needed, and those are the culprits you probably want to ferret out and eliminate.
Of course, if you bought your computer "fully loaded" from a computer store or online direct-sales company, you're likely going to experience slow startup from day one. That's because PC vendors tend to load up the computers they sell with tons of extras, including system management tools, CD-burning utilities, paint programs, photo-processing tools, and lots of other stuff you may never even use. It can be quite a revelation for ordinary users when they compare the startup time for a freshly installed XP machine with their own "fully loaded" machine. Wow--makes you want to go straight to Add or Remove Programs, start selecting things, and click Remove, Remove, Remove. Unfortunately, sometimes removing these things can leave behind programs or services that still start up whenever Windows boots. Where do they hide?
Finding Startup Programs
Programs and services that start whenever Windows boots do so in various ways. The simplest way is for the installation routine to create a shortcut to the program within the Startup folder for the current user (or for each user on the machine). To open your own Startup folder, click Start, then Run, and type the following:
%userprofile%\Start Menu\Programs\Startup
The Startup folder common to all users on the machine can be found by opening this path:
%allusersprofile%\Start Menu\Programs\Startup
When I try these two paths on my main Windows XP machine, my Startup folder is empty, but the common Startup folder has a shortcut to a power-monitoring utility from the vendor of the Uninterruptible Power Supply (UPS) attached to my machine. Note that program shortcuts in the common Startup folder automatically run when any user logs on to your computer, so if I delete this shortcut, my UPS probably won't work as designed. Better leave it alone.
Registry keys are another common way to launch programs or services at startup. Here are some registry keys you can examine to see what programs are starting automatically, followed by their description:
HKLM\Software\Microsoft\Windows\CurrentVersion\Run
Values for this key are programs that start every time any user starts your computer. I just checked this key and found 12(!) different programs listed. Finding out what these programs are can sometimes be tricky. A value named DVDLauncher is likely just what it says it is, but what about a value named igfxpers? A good way to find out is to search for such values in ProcessLibrary.com, which tells me that igfxpers.exe is "a process installed alongside NVidia graphics cards [that] provides additional configuration options for these devices. This program is a non-essential process, but should not be terminated unless suspected to be causing problems." Aha! If I delete this registry value, my video card might not work, so better leave it alone, too.
Another registry key to examine is:
HKCU\Software\Microsoft\Windows\CurrentVersion\Run
This is similar to the previous one, but the difference (HKCU instead of HKLM) means that programs listed here as values will only be launched for the current user (me), not for all users. I find only two programs listed here, Windows Messenger (which I want to start up whenever Windows starts) and ctfmon.exe, which ProcessLibrary.com tells me has to do with the Microsoft Office Language Bar. I don't use that feature of Office so I'm tempted to delete this registry value, but a better approach would be to rerun Setup for Microsoft Office and remove this feature from my machine. Searching the Microsoft Knowledge Base tells me more.
Similar to the previous key is this one:
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows\Run
This key isn't present on my machine, so there's nothing to worry about here. Just above it is this key:
HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows
Examine the value named Load here, because any programs listed in this value will run when any user logs on to your machine.
There's more--here are four places where programs that only need to run once can be found:
HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKCU\Software\Microsoft\Windows\CurrentVersion\RunOnceEx
My machine has the first two keys but not the others, and the keys have no values except Default. This makes sense however, because after a program listed here runs, the registry value associated with launching it is deleted. You can find more info about these keys here, here, and here.
Here is one more key to examine:
HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
Within this key are a number of values. The two of interest to us, called Shell and Userinit, specify the default Windows shell and the user shell, respectively. Malicious spyware can replace these values with different ones; in one situation I've heard of, you try to logon to your machine but are immediately kicked out and presented with the logon box again. Nirmal Sharma, a Microsoft Most Valuable Professional (MVP) has written a Community Solutions KB article concerning this issue and how you can fix it by remotely connecting to the affected machine's registry. A Community Solutions article is a KB article contributed by a member of the MVP community rather than Microsoft's own PSS team. These solutions aren't supported by Microsoft, but they're often terrifically helpful. To find more Community Solutions articles, try googling (oops, try using Google to search for) the string "Community Solutions Content Disclaimer" while restricting your search to the support.microsoft.com domain.
If your computer belongs to a domain, then your network administrator has the power to add startup programs to your machine. These policies are found here:
* Computer Configuration\Administrative Templates\System\Logon
* User Configuration\Administrative Templates\System\Logon
Three relevant policies can be found in each of these two locations:
* Run These Programs At User Logon. Programs listed here obviously run every time Windows starts, in addition to any startup programs already listed in your own machine's registry.
* Do Not Process The Run Once List. If your administrator enables this policy, then any programs found in your RunOnce registry keys won't run when Windows starts on your machine. Enabling this policy is generally a good idea, as it helps prevent malware from launching on your machine.
* Do Not Process The Legacy Run List. If your administrator enables this policy, then any programs found in your Run registry keys won't run when Windows starts. Enabling this policy is also a good idea, as it helps prevent malware from running on your machine.
Home users can also configure these policies manually on their machines, provided they are logged on with an account that has administrator credentials. Here's how: click Start, then Run, and type gpedit.msc. This opens the Group Policy Editor and lets you edit your Local Computer Policy. Navigate to the appropriate place as specified above, and configure each policy as desired. Be careful, though: if your machine came "fully loaded," disabling the Run list may prevent some of your hardware or software from running properly. Use these policies on a home computer at your own risk; the main reason they're there is for network admins to maintain greater control over Windows workstations on their network, not for home users to start fiddling around with them.
When you configure a policy like Run These Programs At User Logon, the list of programs you specify gets written to special sections of your registry, namely:
HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run
A malicious program could also write something to these registry keys, even if Group Policy is not being used on your network.
Still another registry key to which setup programs sometimes write is:
HKLM\Software\Microsoft\Windows\CurrentVersion\ShellServiceObjectDelayLoad
Values here indicate DLLs that are loaded during startup to add special capabilities to the Windows shell. If you find anything here other than CDBurn, PostBootReminder, SysTray, and WebCheck, you may have malware on your machine.
Another way startup programs can run on a computer joined to a domain is if a startup or logon script runs when your computer starts or when you log on to your machine. Ask your network administrator about this if you're curious; it's not something that home users need to worry about. Then there's your Scheduled Tasks folder--it's possible to create per-user tasks that schedule a program to run every time your computer boots, but you'll only find these kinds of tasks in the Scheduled Tasks folder in your administrator account. Ordinary users can also schedule tasks to run every time they log on to the computer, and these tasks generally run hidden in the background.
Dealing With Startup Programs
In addition to finding startup programs manually using the steps I've listed above, you can also use tools like your System Configuration Utility (click Start, then Run, type Msconfig.exe, click OK, and select the Startup tab) or a third-party tool like Autoruns from Sysinternals. Once you've found all this junk though, how do you get rid of it?
Removing items from your Startup folder (or the common Startup folder) is generally safe, but deleting values from your Registry should be done only as a last resort. In fact, sometimes deleting a registry value won't even work--as soon as you run the application associated with the startup program, the deleted registry value may get automatically re-created!
The best way to proceed is to first try to see if the application itself lets you remove the feature or component that's starting up every time Windows boots. You might need to rerun your application's Setup program to do this. If this fails, then (and only then) should you consider deleting a registry value (but always back up your registry before making any changes to it).
And next time you buy a computer, don't ask for one that's "fully loaded," but instead consider buying a "bare metal" machine (one with no operating system) from your local "white box" vendor (or a used computer store like Geeks.com). Then buy a shrink-wrapped copy of Microsoft Windows (whatever the latest version is) and install it yourself. Your machine will fly; startup will be much faster than you're used to. Then, install only those applications you need; avoid downloading and installing every tool under the sun from shareware sites on the Internet. If you must do this, have a separate "junk" machine just for this purpose so your main machine doesn't get cluttered.
Finally, here a few more sources of information on the topic of startup programs:
* How To Manage Windows Startup
* Configure Auto-Starting Applications
* How to Modify the List of Programs that Run When You Start Windows XP
* Restore Your Computer's Performance with Windows XP
Mitch Tulloch is the author of Windows 2000 Administration in a Nutshell, Windows Server 2003 in a Nutshell, and Windows Server Hacks.
Return to the Windows DevCenter.
http://www.windowsdevcenter.com/pub/a/windows/2006/08/22/how-to-remove-startup-programs.html
Resources for troubleshooting startup problems in Windows XP
View products that this article applies to.
Article ID : 308041
Last Review : March 22, 2008
Revision : 5.2
This article was previously published under Q308041
On This Page
INTRODUCTION
This article describes how to troubleshoot startup problems in Windows XP. After you follow the articles or steps in each section, try to start your computer to determine if the problem is resolved. If you still cannot start your computer, continue to the next section of the article.
Back to the top
MORE INFORMATION
You receive an error message when you start your computer
If you receive an error message when you start your computer, follow the steps that are described in the following two sections. If you do not receive an error message when you start your computer, go to the "Your computer stops responding when you try to start Windows XP" section.
Configure Windows not to load the file or the service that is mentioned in the error message
If the error message refers to a file or service, the file or service may be listed on one of the tabs in the System Configuration Utility (Msconfig.exe). If the file or service is listed, turn it off by following the procedure that is outlined in the article below. If the file or service is not listed, continue with the next troubleshooting step in this article.
For additional information about how to turn off a file or service by using the System Configuration Utility, click the following article number to view the article in the Microsoft Knowledge Base:
310353 (http://support.microsoft.com/kb/310353/) How to perform a clean boot in Windows XP
For additional information about how to turn off services by using Computer Management, click the following article number to view the article in the Microsoft Knowledge Base:
310602 (http://support.microsoft.com/kb/310602/) How to disable a service or device that prevents Windows from starting
Contact the manufacturer of the faulty service for more assistance.
Note For more information about the file or service that is causing the problem, contact a Microsoft Product Support Services professional for help. For information about how to contact a Support Services professional, visit the following Microsoft Web site:
http://www.microsoft.com/support (http://support.microsoft.com/?scid=http%3a%2f%2fwww.microsoft.com%2fsupport)
If the original equipment manufacturer (OEM) of your computer installed Windows XP for you, call them for help with this issue.
Determine if a new program was recently installed on your computer
If you recently removed a program or a Windows component from your computer by deleting it manually, related information that is still on your computer may be causing the problem. To remove the program or component, first reinstall it, and then use the Add or Remove Programs tool, or follow the manufacturer's instructions.
To remove a program from your computer, follow these steps:
1. Click Start, click Control Panel, and then click Add or Remove Programs.
2. In the list of programs, click the one that you want to remove, and then click Change/Remove.
3. Click Yes when you are prompted with the question "Do you want to remove the program?"
If the program is not listed in the Add or Remove Programs tool, contact the manufacturer to obtain instructions for removing it.
Back to the top
Your computer stops responding when you try to start Windows XP
If your computer stops responding when you try to start Windows XP, see the articles that are listed in the following sections, or follow the steps in the following sections.
Start your computer in Safe mode
For additional information about how to troubleshoot Windows XP by using Safe mode, click the following article numbers to view the articles in the Microsoft Knowledge Base:
315222 (http://support.microsoft.com/kb/315222/) A description of the Safe mode boot options in Windows XP
For information about how to disable a service or a device that prevents Windows from starting, see article 244905 in the "Recommended Knowledge Base articles" section.
Use Device Manager to determine if the problem is related to a device driver
You can use Device Manager to examine and change software-configurable devices. If your hardware device uses jumper pins or dip switches, you must configure the device manually.
For additional information about how to troubleshoot device conflicts by using Device Manager, see article 310126 in the "Recommended Knowledge Base articles" section. For additional information about how to troubleshoot unknown devices that are listed in Device Manager, see article 314464 in the "Recommended Knowledge Base articles" section.
Use the System Restore tool to restore the operation of Windows XP
You can use the System Restore tool to return your computer to a previous working state. System Restore takes a "snapshot" of critical system files and some program files and stores this information as restore points. You can use these restore points to return Windows XP to a previous state.
For additional information about how to use the System Restore tool, see article 305084 in the "Recommended Microsoft Knowledge Base articles" section.
For additional information about System Restore, click Help and Support on the Start menu. In the Search box, type system restore, and then click OK.
Use the Last Known Good Configuration tool to restore the operation of Windows XP
If Windows does not start, try to restore operation of Windows XP by using the Last Known Good configuration. To do this, follow these steps:
1. Start the computer, and then press the F8 key when Windows begins to start. The Windows Advanced Options menu appears.
2. Use the ARROW keys to select Last Known Good Configuration (your most recent settings that worked), and then click OK.
3. If a start menu appears, use the ARROW keys to select Microsoft Windows XP, and then click OK
Windows XP starts your computer by using the registry information that was saved at the last shutdown.
Perform an in-place upgrade to repair your installation of Windows XP
Try to repair your installation of Windows XP by doing an in-place upgrade. Running the Setup program from the Windows CD-ROM frequently repairs a damaged Windows installation.
For additional information about how to perform an in-place upgrade of Windows XP, click the following article number to view the article in the Microsoft Knowledge Base:
315341 (http://support.microsoft.com/kb/315341/) How to perform an in-place upgrade (reinstallation) of Windows XP
Confirm that your CMOS/BIOS settings are correct
Confirm that your CMOS/BIOS settings are correct.
Warning This procedure may involve changing your CMOS settings and changing your BIOS. Incorrect changes to the BIOS of your computer can result in serious problems. Microsoft cannot guarantee that problems resulting from changes to your BIOS can be solved. Change your CMOS settings at your own risk. Incorrect or corrupted CMOS and BIOS settings can cause startup problems or shutdown problems.
Microsoft cannot provide specific instructions for changing your CMOS and BIOS settings because they are specific to your computer. For information about the correct CMOS and BIOS settings for your computer and how to check and change these settings, see your computer documentation or contact the manufacturer of your computer.
Note An insufficiently charged or damaged internal battery may corrupt the CMOS or BIOS settings.
Confirm that your hard disk or file system is not damaged
Confirm that your hard disk or file system is not damaged. Start your computer from the Windows XP CD-ROM, load Microsoft Recovery Console, and then use the Chkdsk command-line utility. This may solve your problem.
Important We recommend that advanced users or administrators use the Recovery Console. You have to know the Administrator's password to use the Recovery Console.
For additional information about how to check and repair a damaged hard disk by using Chkdsk, see the "Using the Recovery Console" and "Using the Recovery Console command prompt" sections in the following article:
307654 (http://support.microsoft.com/kb/307654/) How to install and use the Recovery Console in Windows XP
Note If the Chkdsk command reports that it cannot gain access to your hard disk, you may have a hardware failure. Examine all cable connections and any jumper settings on your drive. For more assistance, contact a computer repair professional or the manufacturer of your computer.
If the Chkdsk command reports that it cannot fix all hard disk problems, your file system or Master Boot Record (MBR) may be damaged or no longer accessible. Try appropriate Recovery Console commands such as Fixmbr and Fixboot, contact a data recovery service, or repartition and reformat your hard disk.
Important For more help, contact your computer manufacturer or a Microsoft Product Support Services professional.
Allow only qualified personnel to repair your computer. Computer repair that is performed by non-qualified personnel may nullify your computer's warranty.
If you repartition and reformat your hard disk, you lose all the information on the disk.
Back to the top
After an upgrade, programs that previously loaded during startup no longer start
After you upgrade your computer from Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition to Windows XP, the programs that previously loaded during the startup process may not be listed in the notification area (at the far right of the taskbar), and they do not start automatically when you start your computer.
For additional information about how to resolve this issue, see articles 298427 and 303561 in the "Recommended Knowledge Base articles" section.
Back to the top
REFERENCES
Recommended Knowledge Base articles
For additional information about how to troubleshoot startup issues in Windows XP, click the following article numbers to view the articles in the Microsoft Knowledge Base:
242518 (http://support.microsoft.com/kb/242518/) Long pause during Windows startup process
244905 (http://support.microsoft.com/kb/244905/) How to disable a service or device that prevents Windows from booting
249000 (http://support.microsoft.com/kb/249000/) Windows Advanced Options boot menu missing at startup
252448 (http://support.microsoft.com/kb/252448/) How to create an MS-DOS network startup disk in Windows 2000
266169 (http://support.microsoft.com/kb/266169/) How to troubleshoot problems with standby mode, hibernate mode, and shutting down your computer in Windows 2000
298427 (http://support.microsoft.com/kb/298427/) How to restore the disabled startup programs after an upgrade from Windows 98 or Windows Millennium Edition
300886 (http://support.microsoft.com/kb/300886/) A description of the Restore Startup Programs option that is used when you upgrade to Windows XP
303561 (http://support.microsoft.com/kb/303561/) Windows XP shortcuts in the Startup group do not work when you first start the computer
306084 (http://support.microsoft.com/kb/306084/) How to restore the operating system to a previous state in Windows XP
310126 (http://support.microsoft.com/kb/310126/) Troubleshooting device conflicts with Device Manager
314464 (http://support.microsoft.com/kb/314464/) How to troubleshoot unknown devices that are listed in Device Manager in Windows XP
244601 (http://support.microsoft.com/kb/244601/) How to troubleshoot unknown devices that are listed in Device Manager in Windows 2000
Back to the top
How to use the Microsoft Product Support Services Web site to find a solution
If you cannot resolve the problem by following the steps in this article or by viewing the recommended Knowledge Base articles, you can use the Microsoft Product Support Services Web site to find a solution to your problem. Some of the services that the Microsoft Product Support Services Web site provides include the following:
. Searchable Knowledge Base
To search technical support information and self-help tools for Microsoft products, visit the following Microsoft Web site:
http://support.microsoft.com/search?ln=en-us&sd=gn (http://support.microsoft.com/search?ln=en-us&sd=gn)
. Frequently asked questions
To view product-specific frequently asked questions and support highlights, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[ln];winxpfaq&product=winxp (http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;winxpfaq&product=winxp)
. Microsoft Product Support newsgroups
To contact your peers and Microsoft Most Valuable Professionals (MVPs), visit the following Microsoft Web site:
http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx (http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx)
. Software and software updates
To find software and software updates at the Microsoft Download Center, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/search.asp (http://www.microsoft.com/downloads/search.asp)
. Other support options
To ask a support question by using the Web, to call Microsoft Product Support Services, or to provide feedback, visit the following Microsoft Web site:
http://support.microsoft.com/kb/308041
Troubleshooting Tools and Strategies
Problems which prevent the computer from completing startup or shut down can be frustrating. However, there are several techniques that you can use to isolate and solve these problems.
Startup Problems
If a computer fails to complete the Windows 2000 startup process, note whether any new hardware or software has been added since the last startup. If so, remove the new component to see whether this resolves the problem.
If nothing has been added or changed on the system, restart the computer in Safe Mode. If successful, you might be able to resolve the problem from within Safe Mode. Starting Windows 2000 in Safe Mode can help you resolve issues that occur when you start Windows 2000 normally, including (but not limited to):
.
Setup freezes during the first restart.
.
Error messages are displayed.
.
The system stops responding.
.
You lose functionality.
Starting Windows 2000 in Safe Mode bypasses the current configuration and loads a minimal configuration, enabling only basic Windows 2000 device drivers and system services.
If the startup failure does not occur in Safe Mode, you might have a conflict with hardware settings or system resources; incompatibilities with Windows programs, services, or drivers; or registry damage.
In Safe Mode, use the following tasks to find a startup problem. Many of these steps require changes to system configuration files. The changes are to isolate the conflict that is causing the problem and are not intended to be permanent. For more information about Safe Mode, see Safe Mode earlier in this chapter.
To troubleshoot startup problems in Safe Mode
1.
To enter Safe Mode, restart the computer, and then press F8 when the screen displays the prompt For troubleshooting and advanced startup options for Windows 2000, press F8.
2.
On the Windows 2000 Advanced Options Menu, select Safe Mode , and then press ENTER. Determine whether the startup failure is resolved. If not, check for hardware problems such as defective devices, improper installation, cabling, or connector problems. Remove any newly added hardware to see whether the problem is resolved.
If you cannot complete the startup process and you suspect your computer might have corruption in the registry, restart the computer, press F8, and on the Windows 2000 Advanced Options Menu , select Last Known Good Configuration . Press ENTER.
3.
If you can complete the startup process in Safe Mode, start System Information. Open the Run dialog box, and then type:
msinfo32
For more information about System Information, see System Information earlier in this chapter.
4.
Within System Information, check the Conflicts/Sharing section under Hardware Resources and the Problem Devices section under Components for known issues. Address any issues found by reconfiguring or disabling the devices in conflict, and then restart the computer.
If you disabled a device to resolve the problem, check that the device is listed on the HCL and that it was installed correctly; or check it on another computer to see whether the device might be defective. Try using Windows Update to see whether any updated drivers are available. If not, try visiting the manufacturer's Web site to see whether an updated driver is available.
5.
If there were no conflicting devices reported in System Information, under Software Environment, check the Startup Programs section for programs that are automatically started when the computer is started. Disable these programs and restart the system.
note-icon
Note
Links to startup programs can be in a variety of places, including in the registry under the following subkeys:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce
Also look for startup programs in C:\Documents and Settings\ logon_name \Start Menu\Programs\Startup and in C:\Documents and Settings\All Users\Start Menu\Programs\Startup. If the user is a member of the local administrators group, check C:\Documents and Settings\Administrator\Start Menu\Programs\Startup.
If the problem is resolved by disabling the startup programs, re-enable them one at a time, and restart the computer each time to determine which program causes the startup failure.
6.
If disabling the Startup Programs does not resolve the problem, check the boot log file, %systemroot%\Ntbtlog.txt. Rename this file to indicate that it is a Safe Mode boot log file, and compare its contents to a recently saved boot log file from a normally started session. If a normal boot log does not exist, create one by restarting the computer, pressing F8 at the Starting Windows screen to display the Windows 2000 Advanced Options Menu , selecting Enable Boot Logging , and then pressing ENTER. The normal boot log file can indicate which driver file did not load properly.
note-icon
Note
Some startup problems occur so early in the startup process that they prevent the system from saving the boot log file to disk.
Examine the Safe Mode version of the boot log file to see which drivers were not loaded. This list of skipped drivers is a good starting place to look for the driver that is causing the startup process to fail.
If the problem is a Stop message (also known as a blue screen), see the troubleshooting tips in the chapter Windows 2000 Stop Messages in this book.
Top of pageTop of page
Shutdown Problems
The Windows 2000 shutdown process involves sending messages to the installed devices, system services, and applications to notify them that Windows is preparing to shut down. The system waits for responses from open applications to make sure that they shut down properly, and save unsaved data to disk. Each running device, system service, and application usually respond to the shutdown message, indicating that it can be closed.
Typical causes for problems with Windows 2000 shutdown include:
.
Device drivers not responding correctly, if at all.
.
System services not responding or sending busy request messages to the system.
.
Applications not responding, particularly 16-bit Windows programs.
To resolve problems with shutdown, try the following suggestions:
.
Check that the system properly shuts down in Safe Mode. If so, check the boot log file. Note the services that were disabled under Safe Mode, stop them one at a time in normal mode, and then shut down to see whether the system works properly. After the problem driver or service is identified, if the file is corrupted, either reinstall it, search for an update, or uninstall it until the problem can be resolved.
.
Press CTRL+SHIFT+ESC to start Task Manager and see which applications are currently running. Manually quit the applications before shutting down to see whether that resolves the problem.
.
Check with your computer manufacturer to be sure that you have the latest BIOS update for the system.
If the problem occurs immediately after a change to the system, such as installing or upgrading applications, system services, or hardware with device drivers, undo the last change made to the system and test the system.
http://www.microsoft.com/technet/prodtechnol/windows2000serv/reskit/prork/pref_tts_eznd.mspx
Backup and Restore
With today's use of e-mail you almost can't afford to lose a single e-mail so let alone your entire mail archive. This guide is all about backing up and restoring your Outlook Data. It describes various methods and explains which method is best to be used in which scenarios.
Locating the pst-file
Relocating the pst-file (optional)
Backup pst-file
Restore pst-file
Export pst-file
Import pst-file
Backing up individual items
Backing up an Exchange mailbox
Restoring the Exchange mailbox
Tools
Locating the pst-file
Before you can make a backup you'll need to know what to backup first. In the case of Outlook in a home environment all data is stored in a single file with a pst-extension. The pst-file is also known as Personal Folders and is able to store several mail, contacts, journal, notes and calendar folders. More about pst-files can be found here.
You can locate your pst-file by using one of the following methods;
Make sure you include hidden and system files and folders when searching for pst-file
By default it is located in
C:\Documents and Settings\%username%\Local Settings\Application Data\Microsoft\Outlook\
For Windows Vista the default is
C:\Users\%username%\AppData\Local\Microsoft\Outlook\
You can also locate the file by using
Rightclick the root folder (probably Outlook Today)-> Properties-> button Advanced-> field Filename
Relocating the pst-file (optional)
I assume lots of you have already relocated the My Documents folder to a more convenient location by right clicking it on the Desktop-> Properties-> tab Target. I've got mine set to D:\My Documents so I won't have to rescue my data in the (worst) case that I have to reformat my C:\ drive. As I see the pst-file to be data just like a Word file I like to have it where I keep all my important documents; in the My Documents folder. In the My Documents folder I have a folder called My Outlook where I store the file in.
To configure Outlook with a new pst-file location do the following;
Make sure Outlook is closed
Go the the location of your pst-file
Copy it to the new location (D:\My Documents\My Outlook)
Rename the file in the old location to .old
Start Outlook; after a warning message it will prompt you to locate the pst-file. Use the Browse button to direct it to the location you've set in step 3
You're done! If all is successful and desired you can delete the renamed pst-file in the old location. You might need to recreate some "move to folder" Wizard Rules to update the new location.
Backup pst-file
Backing up the pst-file is quite easy; you just copy the pst-file to your safe location when Outlook is closed. A safe location can be one of the following;
another physical hard drive in your machine
another physical hard drive in another machine
an external hard drive
a USB memory stick
a Flash memory card
a CD-R(W)
a DVD+/-R(W)
a backup tape
Restore pst-file
A backup is worthless if you can't restore it. So we first test the back-up. Testing the backup when knowing that the original still works is a lot less stressful then as well.
To restore your pst-file copy the file to the location where you want to work with it like D:\My Documents\My Outlook\Temp. If you restored from CD/DVD make sure you uncheck the "Read Only" file attribute by right clicking the file and choose Properties. Now open Outlook and connect to the file by choosing File-> Open-> Outlook Data File... You can now check if the backup was successful and you made sure you backed up the right file.
In the case of a real disaster the original pst-file would be missing or beyond repair. When the pst-file is missing Outlook would have prompted you for the pst-file location. You then need to close Outlook and restore the file from backup to D:\My Documents\My Outlook as described above. Then start Outlook again and if prompted browse to the location of the pst-file.
When the pst-file is beyond repair Outlook will start with the message that it can't be opened and that you need to run the Inbox Repair Tool (scanpst.exe). If scanpst.exe can't fix the pst-file either rename the corrupted pst-file to .old and you would now be in the situation that the pst-file went missing.
Export pst-file
It's a general misconception that an export of your mail is a good backup. This misconception gets even bigger if you run the export and see that the default name of the file to export to is backup.pst. The reason that it isn't a backup is because you will lose data during an export even if you configure the export to export all the folders and subfolders. The following data gets lost during an export;
custom forms
custom views
Wizard Rules
folder properties like AutoArchive settings
An export of your pst-file to another pst-file can be seen as a selective backup since during the export you can choose what data you want to backup. This is handy if you see no need in backing up the entire pst-file like the Sent Items folder or the Funny Forwards folder (who doesn't have one of those?) which can get quite big over time and you might consider them as not important enough to backup.
Let's say you only want to export your Inbox and your Contacts folder;
Choose File-> Import and Export...
Choose Export to a file
Choose Personal Folder File (.pst)
Select the Inbox and press Next (we do the Contacts folder later)
Set the file location to D:\My Documents\My Outlook\Backup\export.pst
Press Finish and you'll be prompted to set properties for the export.pst file
In the Name field type a descriptive name like "Export June 2004"
Press OK to start the export
To export the Contacts folder as well repeat step 1 to 4 and this time select the Contacts folder
If the save location is not set to the path you've set in step 5 browse to it
Press Finish to export the Contact folder
Close Outlook and copy the exported file to your safe location as described in Backup pst-file
Import pst-file
Importing a pst-file can only be done in a working Outlook situation like when you've reinstalled your machine, configured Outlook and now want to restore your Inbox and Contacts. Importing a pst-file can be done in two different ways; automatically through a wizard or manually by dragging and dropping. Before importing restore your pst-file; Copy the file to the location where you want to work with it like D:\My Documents\My Outlook\Temp. If you restored from CD/DVD make sure you uncheck the "Read Only" file attribute by right clicking the file and choose Properties.
Restore through the Import and Export Wizard
Choose File-> Import and Export...
Choose Import from another program or file
Choose Personal Folder File (.pst)
Browse to the location where you've restored the pst file (D:\My Documents\My Outlook\Temp)
Set the options to "Include subfolders" and "Import items into the same folder in:" and select the folder that is listed as your Outlook Today folder set in the dropdown list
Press Finish to complete the import
Restart Outlook and remove the export.pst file from the Temp directory if desired
Restore manually
Choose File-> Open-> Outlook Data File...
Browse to the location where you've restored the pst file (D:\My Documents\My Outlook\Temp)
You'll now see an additional set of folders added to your folder list which you can expand. Expand the list and select the Inbox folder
In this folder select the messages you want to restore to the original Inbox folder
Drag & drop them to the default Inbox folder
Do the same for the Contacts folder. You might want to set your view to a list view so you can easily select and move the items. To change the view choose View-> Arrange By-> Category
Now that the importing is complete right click the pst-file added in step 2 and choose Disconnect
Restart Outlook and remove the export.pst file from the Temp directory if desired
Backing up individual items
Sometimes it's more convenient to backup a single item. Think about account login information you receive by e-mail. Backing up this way is very easy. You can choose File-> Save as... and then choose in which format you want to save the message. If you want to be able to open them on just about any system you can choose the txt or htm format. To easily save several messages in the Outlook format (msg) you can select those messages and drag & drop them out of Outlook into an Explorer window. When you save them in the msg-format any attachments that might have been included in the message are saved within the msg-file as well.
Backing up an Exchange mailbox
Backing up an Exchange mailbox is the task of the Exchange administrator. Since this is managed on the Exchange server it's beyond the scope of this article. However in some cases it's good to have a backup for yourself as well. This is especially true if you are a mobile user and you synchronise with the Exchange server so you'll have your messages available when you are not connected to the Exchange server. If you are not able to connect to the Exchange server for a long time but you'll have to make sure you can always reach your e-mail you might want to export your messages as well. This way you'll have a backup of the mailbox in case something happens to the off-line mailbox. See the Export section for more info on how you can export certain folders.
Restoring the Exchange mailbox
Restoring the Exchange mailbox is also a task of the Exchange administrator. Here I'll describe how you can use the exported pst-file when the off-line mailbox gets lost or scanost.exe can't repair it and you won't be able to connect to the Exchange server for a while.
For Outlook 2002/2003
Go to Control Panel-> Mail-> button E-mail Accounts-> button Next
Cancel all password prompts you might be getting from the Exchange Account
Now press the button New Outlook Data File...
With Outlook 2003 choose whether it's an Outlook 97-2002 or Outlook 2003 pst-file (in the example we've created an Outlook 2003 file but it doesn't matter which one you choose when you add an existing pst-file)
Browse to the location where you've restored the pst file (D:\My Documents\My Outlook\Temp)
You'll get a details overview; press OK
Now set the default delivery location to the pst-file you've just added by using the dropdown list
Start Outlook and see that it adds the other default Outlook folders in case you haven't exported these
Cancel all security prompts you might be getting from the Exchange account
For Outlook 2000
Go to Control Panel-> Mail
Press Add...
Browse to the location where you've restored the pst file (D:\My Documents\My Outlook\Temp)
You'll get a details overview; press OK
Cancel all password prompts you might be getting from the Exchange Account (Work Offline)
Press the Delivery tab
Now set the default delivery location to the pst-file you've just added by using the dropdown list
Start Outlook and see that it adds the other default Outlook folders in case you haven't exported these
Cancel all security prompts you might be getting from the Exchange account (Work Offline)
Tools
Outlook Add-in: Personal Folders Backup
The Personal Folders Backup download creates backup copies of your .PST files at regular intervals, in Outlook 2000 and later versions, making it easy to keep all of your Outlook folders safely backed up.
Backup script
I created this batch in order to be able to schedule Outlook pst-file backups by using Scheduled tasks in Windows. Since I always have my Outlook open a simple copy to backup isn't possible without an "open file backup" service.
ABF Outlook Backup
ABF Outlook Backup is a backup and synchronization tool for MS Outlook. It allows you to backup and restore your messages, address book, settings, accounts, message rules, junk email lists, signatures, and even your Internet favorites.
If you decide to order use "ABF-1HTJ8" to get a discount.
http://www.howto-outlook.com/howto/backupandrestore.htm
|
|
Return
to top of page