Windows vista slow in shutting down

My opinion is that Vista sucks anyway. This isn't the only problem I've had with it by a long shot. Sure there has been some potentially cool advances and tools for master users. But Microsoft doesn't seem to get that the important thing is the user experience, not their vision of how you should interact with your own comptuter. So I'm moving to linux. I've built a kubuntu 8 beta with kde desktop server machine and I really like it. I have full control and can change what I want.

There are plenty of productivity programs in the open source world so I don't miss hardly a thing. I am probably soon going to partition this Vista laptop and setup ubuntu linux on it as my default OS and use Vista only for those rare things where I dont' have a choice program wise. I figure that if someone has to learn enough to make registry edits on Vista to make it work, why not just go for full control?????

Microsft said Vista was a work in progress. Why not then go to an OS where the progress has been much greater. Sunday, April 20, PM. It has explained all possible reason for vista slow working and shutdown. Thursday, June 26, AM. Dam windows vista is the main problem!!! Wednesday, March 3, PM. Try to reduce startup programs. Friday, February 18, AM. Ziegler 0. I take a look at the trace, maybe I see what's wrong with your Windows.

Proposed as answer by Andre. Hi, Well there has to be something in common. Poor ventilation, low power brown outs or fluctuating power. Look in the Event Viewer to see if anything is reported about those reboots. Windows Vista automatically restarts if your PC encounters an error that causes it to crash.

If you could give the Blue Screen info that would help. Such as the BCC and the other 4 entries on the lower left. Rob - Bicycle - Mark Twain said it right. How satisfied are you with this reply? Thanks for your feedback, it helps us improve the site. Cody C. In reply to Friendlytoo's post on February 16, Is the system crashing while in safe mode? On the following thread, SpirtX suggests several ways to test your memory for errors.

I'd highly recommend trying that:. This site in other languages x. If you installed Windows Vista on a computer that only meets the minimum hardware requirements, but the computer does not meet the recommended hardware requirements, you may be unable to make a noticeable improvement to the performance of Windows Vista unless you upgrade the hardware on the computer, or you disable some features of Windows Vista.

These features might include the search indexer or some visual effects. Computers that meet the minimum requirements are known as "Windows Vista Capable," and computers that meet the recommended requirements are known as "Windows Vista Premium Ready. This tool measures the performance of a computer, and the tool gives information about the performance in a way that is easy to understand for the end-user. The performance information about the computer is known as the "Windows Experience Index.

When you review the performance rating for the computer, you see an overall score and a sub-score for individual components in the computer. The overall score is determined by the lowest sub-score on the computer. Therefore, if the lowest sub-score for a component in the computer is 2. This is because the component with the lowest performance in the system is considered the bottleneck.

When you review this score, you can use this information to determine whether there is a component in the computer that is causing the startup performance issue. When you determine the Windows Experience Index for your computer, you can use this information to correctly set expectations about the level of performance that you can expect to achieve with the current configuration.

After you set the expectations, it is important to continue to troubleshoot the issue by proceeding with the next troubleshooting step. This is because, although the computer may have slower hardware, the computer may also have other issues with software configurations that can further decrease performance.

For guidance about how to make recommendations about computer performance that is based on the Windows Experience Index, visit the following Microsoft Web site:. If the drivers for the video card are not WDDM drivers, the sub-score will automatically be recorded as 1. When you have identified performance expectations by using the Windows Experience Index, go to the next troubleshooting step.

If a driver or an operating system component causes the performance issue, there may be an update that is available on Windows Update that addresses the issue. Visit Windows Update, and install any driver or operating system updates that are available.

To do this, visit the following Windows Update Web site. Frequently, Windows Vista can automatically detect any issues that are related to performance and can make recommendations about how to troubleshoot these problems.

When this happens, a warning is displayed in Control Panel. To access these warnings, follow these steps:. Click Start , right-click Computer and then click Properties.

In the Advanced Tools window, click the performance-related links to examine detailed information about the computer. After you click the links in the Advanced Tools window, follow the recommendations that appear.

When you have resolved all the issues that appear in this list, restart the computer to see whether the startup performance issue is resolved. If the problem continues to occur, go to the next troubleshooting step. When you troubleshoot a performance issue, it is important to determine whether the problem always occurred after you installed Windows Vista or if the problem began sometime after you installed Windows Vista.

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.