Thursday, April 2, 2015

Use Safe Mode to Troubleshoot Problems

It is very frustrating when your computer won't start correctly or when the process of starting it seems to take forever.  It is even more frustrating when you have ransomware or some other malicious program that loads with it and stops you from being able to fix the problem.  Fortunately, there is a way to start Windows with only the minimum files needed to run, called Safe Mode.  This can assist you with identifying and troubleshooting problems.

With Windows XP, Vista, and 7, press F8 while the computer is loading.  (You will probably have to hit it several times to make sure that you press it at the correct time.)  This will bring up a menu of options.  Search for "Safe Mode" or "Safe Mode with Networking" (this allows you to access other computers and the internet).  There is also a mode to start with the "Last Known Good Configuration."  This boots your computer in the same way it did the last time you successfully started it.

In Windows 8, Microsoft made it a little more difficult to access Safe Mode.  Because of the way Windows 8 boots, you can no longer press F8.  You can only access Safe Mode from within Windows.  (This doesn't help you if the computer won't boot, but Windows 8 is much better at recognizing boot problems and taking steps to help you.)  If you can get into Windows, hold down the Shift key while you click restart.  When the computer boots, you will be presented with a series of menus to click through to access Safe Mode.  Select "Troubleshoot", then "Advanced Options", then "Startup Settings".  Click on the Restart button, and you will finally be presented with the option to boot to Safe Mode.

If the computer loads fine in Safe Mode, then you know the problem is not with Windows itself, but with something that is starting alongside Windows.  If you want to troubleshoot, start by pressing Windows Key + R and typing "msconfig".  You can see all the programs that load at startup on the Startup tab, and you can begin shutting them off individually in order to find out what is causing the problem.

No comments:

Post a Comment