Vista windows problem

The idea of doing incremental releases and upgrades of its software -- rather than a major shrink-wrapped release every years -- was a good concept. Microsoft just couldn't figure out how to make the business model work, but instead of figuring out how to get it right, it took the easy route and went back to an old model that was simply not very well suited to the economic and technical realities of today's IT world.

Microsoft either forgot or disregarded that fact when it released Windows Vista, because, despite a long beta period, a lot of existing software and hardware were not compatible with Vista when it was released in January Since many important programs and peripherals were unusable in Vista, that made it impossible for a lot of IT departments to adopt it. Many of the incompatibilities were the result of tighter security.

After Windows was targeted by a nasty string of viruses, worms, and malware in the early s, Microsoft embarked on the Trustworthy Computing initiative to make its products more secure. The other big piece of Trustworthy Computing was the even-further-locked-down version of Windows that Microsoft released in Vista. This was definitely the most secure OS that Microsoft had ever released but the price was user-hostile features such as UAC, a far more complicated set of security prompts that accompanied many basic tasks, and a host of software incompatibility issues.

In other words, Vista broke a lot of the things that users were used to doing in XP. Security isn't even that big of an issue because XP SP2 and above are solid and most IT departments have it locked down quite well. As I wrote in the article Prediction: Microsoft will leapfrog Vista, release Windows 7 early, and change its OS business , Microsoft needs to abandon the strategy of releasing a new OS every years and simply stick with a single version of Windows and release updates, patches, and new features on a regular basis.

Most IT departments are essentially already on a subscription model with Microsoft so the business strategy is already in place for them. As far as the subscription model goes for small businesses and consumers, instead of disabling Windows on a user's PC if they don't renew their subscription, just don't allow that machine to get any more updates if they don't renew.

Then users would have the choice of renewing on their own after that. Will your company eventually migrate to Vista? Take our poll. I've changed the way I charge my iPhone. You should, too. Time for a Linux smartphone? If you are connecting to the internet with a router, a firmware update may be required for the router.

I am using a router however, right now I'm replying to you from a computer on the same network which can connect to all microsoft websites. Thanks for trying to help though. Wednesday, April 9, AM. This error persists. Other computers can contact windows update just fine, but this unit will not Monday, April 13, AM.

Thank you, thank you!!!! Wednesday, October 13, PM. Monday, October 18, AM. Thank you, thank you! I just wish people who are smart enough to make the malicious bs would channel their intelligence in better ways!!!! Saturday, October 23, PM. Thank you for this info.

Thursday, November 18, PM. Tuesday, November 30, PM. Wednesday, January 5, AM. Yip all is fine updates, no viruses, no crashing, amazing, if u have the same problem this is defo the way to fix it, dont bother trying any other way cos ive already tried them, thank you charlie :. Thanks, worked great and updating now. Monday, January 24, PM. Thanks, The download has done as you said it would. I too will spread the word.

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. 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.

They were all entered and accepted prior to the crash. Office Office Exchange Server. Not an IT pro? Script Center.

Sign in. United States English. Ask a question. Quick access. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Windows Vista Setup. For deployment issues, please use the Windows Vista Deployment and Imaging forum. Sign in to vote. Hope this might help. Monday, February 12, AM.

Other symptoms that may be happening: failed software installs With no progress, I hit the internet and started to search. Hope this helps. Wednesday, February 14, AM. I haven't even had a chance to test your theory, but I'm certain you're right. Should have thought of it myself. Wednesday, May 30, PM. A new Tagan W power supply fixed the problem.

Numerous attempts at discussing with MS have prevailed with not a single email response. My advise to anyone thinking about Vista Sunday, June 3, AM. Thanks in advance.