Vista startup problems

Remove From My Forums. Asked by:. Archived Forums. Windows Vista Setup. For deployment issues, please use the Windows Vista Deployment and Imaging forum. Sign in to vote. Hi all, I have installed Vista RC1 3 days ago, it was working fine until yesterday. Can someone please help? Tuesday, October 10, AM. Ask a question. Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. Hey guys, my computer lost power during startup and ever since i havent been able to start, i get the logo and the white text screen come up fine, then i get a screen that offers me two choices: Start windows with startup repair.

Saturday, March 8, PM. Yes it worked before Cant find an option to go into safe mode And i didnt get any cds with my computer when i broughtit. Tuesday, March 11, PM. Turn the computer on or Restart the computer Start tapping the F8 key. If you begin tapping the F8 key too soon, some computers display a "keyboard error" message. You must clarify this before you continue.

If the problem has always occurred, go to Step 5. If Windows Vista was performing acceptably after it was installed, and the startup performance problem only began to occur sometime after Windows Vista was performing acceptably, you can use the Reliability Monitor tool that is included with Windows Vista.

This tool lets you examine the events that occurred around the time that the problem began so that you can determine any relationship between the event and the issue.

To do this, you must determine approximately when the issue began to occur. When you determine the approximate time, you can examine the events that occurred around that time. Click Start , type reliability in the Start Search box, and then press Enter. Click Reliability and Performance Monitor in the Programs list. If you are prompted for an administrator password or for confirmation, type the password, or provide confirmation.

In the line graph that appears, you will see a representation of the reliability of the computer. Each vertical bar represents a day, and the height of the line for that day is determined by the events that occurred on that day. If any errors or warnings occur, the line will go down, and if no events or only informational events occur then the line will start to go up.

To use this tool to troubleshoot a performance issue that began sometime after Windows Vista was installed, follow these steps:. After finding out the approximate day that the problem began, select that day in the Reliability Monitor tool. Read the Information, Warning, and Error events that occurred on the day that the problem began, and on the two days before the problem began. At this point, you must use the data that you have collected to start to troubleshoot why the problem might have occurred.

Some possible examples of how to troubleshoot this problem are listed here. In the following examples, the most likely result is that you have to contact either the software or hardware vendor for more troubleshooting advice:.

If you see that the problem started the day that a driver update was installed, you have to determine whether there is a newer driver than the currently installed driver. Then, you have to install the newer driver to see whether that driver resolves the problem. If no driver update is available, use Device Manager to roll back the driver that was installed.

If you see that the problem started after the installation of a new piece of hardware, disable or unplug that hardware, and then test to see whether the problem still occurs.

If no updates are available, uninstall the program to test whether the problem continues to occur. If the problem still occurs after you address any of the changes that you identified in the Reliability Monitor, you must contact the computer manufacturer or the hardware vendor to determine whether the computer or hardware that is installed supports Windows Vista, or whether there are any updates that must be installed to make the computer compatible.

A common cause of poor system performance is that there is an application or a service that constantly stresses the hard disk.

This can cause other components that are running to be deprived of the resources that they require in order to function correctly and at an acceptable speed. One potential example of this kind of application is the indexer for Windows Search. This is because the indexer service only accesses the hard disk when the indexer service determines that another component of the system is not already accessing the hard disk, and the hard disk is idle.

In an older computer that has a slower hard disk, the hard disk may be unable to react quickly enough to new requests for disk access from other system components. This will cause system performance to decrease. To test To test whether the indexer service is causing performance problems, disable the Windows Search service so that indexing no longer occurs. Before you do this, you have to determine whether the indexer has completed indexing the system. To check the status of the indexer service, follow these steps:.

Click Start , and then type index in the Start Search box. In the Programs list, click Indexing Options. At the top of the window that appears, you see either Indexing complete or Indexing Speed is reduced due to user activity.

If you see Indexing Speed is reduced due to user activity , the indexer has not yet completed indexing the user documents and the e-mail messages on the system. If you see Indexing complete , the system has completed indexing the user documents and the e-mail messages on the system.

However, the indexer remains active so that it can index any new documents or e-mail messages that appear on the system. In either case, you can test to see whether the indexer is the cause of the performance issue by disabling the Windows Search service.

To disable the Windows Search Service, follow these steps:. In the Programs list, click Services. Click Stop to stop the service, and then click OK. Now, try to reproduce the performance issue to see whether the problem still occurs. Then, consider the following scenarios. In this scenario, the performance issue no longer occurs. Additionally, you find that the indexing process had not completed.

In this scenario, the likely cause of the performance issue is the Windows Search service. We recommend that you turn the service back on and leave it running to enable the index process to be completed.

The system will continue to be slow during the initial indexing phase.