Windows 7 Upgrades Hit by Endless Reboots, Other Snags -- Visual Studio Magazine

Microsoft Investigating Windows 7 Upgrade Troubles

By Kurt Mackie
10/29/2009

Microsoft is working on upgrade snags that some users have described when moving from Vista to Windows 7.

The complaints started late last week in the Microsoft Answers forum for Windows 7. Users appear to be experiencing two distinct problems, as described in this thread. In one case, Windows 7's installation process cuts short at 62 percent complete. The other problem involves an endless reboot, where the Windows 7 upgrade never completes.

The company is currently working on the reboot issue.

"Microsoft is continuing to investigate this issue, and we will post information on the existing threads in the Answers forum as it becomes available," the spokesperson explained in an e-mail. "Customers who had requested an alert when the answer is posted will be notified."

Disgruntled forum posters weren't the only ones experiencing the problem. A Microsoft employee encountered the reboot when upgrading to Windows 7 on a home PC, the spokesperson explained.

"Endless reboot" is a phrase that may jog some memories. Last year, some Vista users faced a similar reboot cycle when upgrading to Vista Service Pack 1. Microsoft has fixed that problem.

With regard to the incomplete upgrade problem with Windows 7, Microsoft does offer a workaround. The solution is described in a knowledgebase article, "KB 975253." Apparently a service, possibly the "Iphlpsvc" service, interferes with the upgrade to Windows 7. The workaround involves executing a detailed set of steps that may take the joy out of the upgrade process, especially for home users. Possibly, Microsoft may release an easier-to-apply solution.

"We are investigating using the Fix it technology to automate the steps outlined in KB 975253," the spokesperson explained. "Fix it" is Microsoft's online one-click patching service.

Finally, users could face another problem that may occur after a successful Windows 7 upgrade on machines that use solid-state drives (SSDs). The upgrade results in a storage system failure on certain machines using Intel SSD firmware, according to a report by Betanews.

The storage failure seems to be associated with "Trim command" technology, which helps SSDs keep track of file additions and deletions. Trim technology is specifically supported in Windows 7, according to the Engineering Windows 7 blog.

The Microsoft spokesperson indicated that the company is currently investigating the SSD storage failure problem and will post to the Microsoft Answers forum should more information become available.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.

Printable Format

comments powered by Disqus

Featured

Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.
Diving Deep into .NET MAUI

Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.
Copilot AI Boosts Abound in New VS Code v1.96

Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.
AdaBoost Regression Using C#

Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.
Versioning and Documenting ASP.NET Core Services

Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.