“Sorry, the Windows 7 RC is no longer available for download. If you’ve got the download and need a product key, they’ll be available until October 21, 2009.”

In other words, if you can retrieve the RC download via other (legal) means, a product key is still available through the Microsoft distribution site.

You can avoid this issue by downloading the public release candidate of Windows 7, which will be available until August 15, 2009.

• Smaller installer
• Better automatic driver installation (if you had third-party device issues with previous releases, this one may solve some issues)
• Better graphic performance (perhaps due to new drivers). Several users report a boosted WEI (Windows Experience Index) for various graphics cards and better frame rates in various games.
• Internet TV Beta 2.0 has been added to Windows Media Center

See all of our Windows 7 coverage.

Users also report the installation of new ATI graphics card drivers after the update.

If you are having problems installing Windows 7, see our previous coverage for a fix.

We’ve also published fixes for the following Windows 7 issues:

• Blank screen after installing
• Boosting Poor Disk Performance in Windows 7

Several users have reported that they can’t install Windows Vista SP2. This problem is more likely to occur if a pre-release edition of Windows Vista service pack 2 was installed prior to the final edition, but it is also happening to systems that only had SP1 (make sure you have SP1 installed before you attempt SP2 installation).

Fixes

There are three potential fixes for this issue:

Run CheckSUR First, download and run the System Update Readiness Tool (aka CheckSUR) for Windows Vista and Windows Server 2008. Running this tool, which takes 15 minutes or more on most systems, can resolve issues that prevent SP2 from installing. After running the tool, re-attempt installation of Windows Vista SP2.

CheckSUR is available through Windows Update (Click Start, then click Control Panel, and then click Security. Under Windows Update, click Check for updates) or this standalone download page.

Delete vLite key If you receive the message “Service Pack Installation Cannot Continue: One or more of components that the service pack requires are missing,” try deleting the file vLite key from the registry. To do this:

1. Click Start
2. In the search box (or in “Run”), type regedit then press enter.
3. Navigate to HKLM\Software\
4. Select vLite
5. Choose Edit and then Delete from the Registry Editor menu.
6. Restart your computer and try the Windows Vista SP2 update again

Try selective startup As a last resort, try running the Windows Vista SP2 update while booted in a selective startup mode. To do this:

1. Click Start then go to the Control Panel and select “System and Maintenance”
2. Go to Administrative Tools and select System Configuration
3. Click Continue (enter admin password if required)
4. Select the General tab then choose Selective startup
5. Uncheck “Load startup items”
6. Click the Services tab then check “Hide all Microsoft services” and select “Disable all”
7. Click Apply, then OK
8. Restart
9. Retry the Windows Vista SP2 update

Disable antivirus/spyware software during installation Directly prior to installation of Windows Vista SP2, disable all antivirus/anti-spyware software, then re-enable it after the update is complete. These programs can interfere with proper installation of the update and cause other problems.

In particular, some versions of ESET Smart Security and the ESET NOD32 Antivirus software have caused issues with the update. Disable or uninstall this program before installing Windows Vista SP2.

Can’t see license agreement; fix Some users are unable to properly view the Windows Vista SP2 license agreement, and therefore cannot proceed with installation. In most cases, this problem can be resolved with Chris Pirillo’s Vista Font Fix.

• Windows Search 4.0: “improved indexing and search relevance; helps find and preview documents, e-mail (including signed e-mail messages), music files, photos, and other items on the computer.”
• support for the 64-bit central processing unit (CPU) from VIA Technologies
• support for Bluetooth v2.1 and Windows Connect Now (WCN) Wi-Fi Configuration
• ability to record data to Blu-Ray Disc media

The new release is available through Windows Update or via the following download (standalone) links:

• Windows Vista/Windows Server 2008 SP2 32-bit edition
• Windows Vista/Windows Server 2008 SP2 64-bit edition

Unfortunately, many users are likely to encounter a variety issues, such as startup problems, application crashes, performance hiccups and more, after the update. Here’s a run-down of the best methods for preventing these issues and making your update experience a smooth one:

Backup First and foremost, a full backup should be performed prior to any major system update. Your best bet is to use a tool that can create a complete, bootable backup of your primary volume. If major problems ensue post-update, you will have working copy of your current applications and documents that can be put into use immediately. Acronis True Image is one such tool. Alternatively, you can use Windows Vista’s built-in backup tools.

Check for spyware Next, eliminate any spyware or malware that might interfere with the update process or create conflicts after your system is updated. Various free or inexpensive tools, including Ad-Aware and Spybot are available for this purpose.

Kill any unnecessary startup processes Eliminating any unnecessary startup processes, or removing all third-party startup processes, can reduce compatibility headaches that often follow major system updates. Launch the System Configuration utility by clicking “Windows” then entering “System Configuration” in the search bar and pressing return. Click on the “Startup” tab and remove any unnecessary items, then restart.

Disable antivirus/spyware software during installation Directly prior to installation of Windows Vista SP2, disable all antivirus/anti-spyware software, then re-enable it after the update is complete. These programs can interfere with proper installation of the update and cause other problems.

Update drivers Check manufacturers’ websites for the latest driver editions for any third-party devices that are connected to your system. Many manufacturers have already updated their drivers for basic compatibility with Vista SP2.

Disconnect any unnecessary devices Aside from your keyboard, mouse, monitor and network connectivity, virtually all external device should be disconnected from your system right before you install Vista SP2. Disconnecting these devices can preclude a variety of issues. Once the update is applied, you can reconnect the devices one by one and check for compatibility issues.

Uninstall any pre-release Vista updates If you installed the Vista SP2 release candidate or a prior beta, uninstall it right before running the final Vista SP2 update. Open Control Panel, click Programs, then click “View Installed Updates.” Look for the Microsoft Windows list, then right-click the beta or pre-release service pack and select uninstall.

Use the standalone updater Users have reported fewer problems when using full standalone Vista service pack updates instead of obtaining the updates through Windows Update.

Problems Installing If you have problems installing the update, see this article.

Feedback? info@windowsfixup.com.

We previously reported an issue in which certain games will not run with OpenGL capabilities under Windows 7 RC1. This issue is most likely to occur when User Account Control (UAC) is enabled.

Other users have reported problems wherein games do not recognize their 3D graphics cards and therefore refuse to run.

It appears that these issues, among others, have been fixed in the new release. This allows the usage of previously unplayable games, including Neverwinter Nights 2.

Most of the fixes appear to be due to enhancements made to DirectX in the new release.

Windows 7 build 7122 is currently available only to specific beta testers, but the release has leaked to various filesharing networks.

Fix for previous Windows 7 builds If you are running an older build of Windows 7 (including 7100, the RC1 release), you can use this fix, discovered by a poster to the Neverwinter Nights forums.

1. Download this file and keep it somewhere safe.
2. Navigate c:\windows\system32 or c:\windows\syswow64 depending on whether you are running Windows 32-bit or 64-bit.
3. Take ownership of the existing dxdiagn.dll file in that directory (for instructions on taking ownership of a file, see this article)
4. Rename the existing dxdiagn.dll file to dixdiagn.dll_backup
5. Put the dxdiagn.dll file you downloaded in step 1 into the same folder that the old file was in.

The gap between the private and public releases begs a nagging question: why is Microsoft withholding a significant update, which includes security enhancements relevant to all, in addition to functionality enhancements, from general users?

Not only does this delay keep the vast majority of systems vulnerable to exploits and deprive users of useful new features and performance enhancements, it also creates the potential for worse security exploits when the update is publicly released. Those with malicious intent will have likely already gained access to the final release, and found new methods of working around its more stringent security standards before users have even had a chance to update.

As written by “Colonel Michael,” a poster to Microsoft’s TechNet forums:

“It has been going on 2 weeks already since its release, and news articles are stating the probability that you will not release it to the public until June. The “leaked” product is already in the hands of those with malicious intent. By the time it reaches the large masses, the hacked computers, the zombie computers, will have already been updated with the “zombie fixes”. So when SP2 does get installed, the zombie masters will still maintain control of the computers”

What’s your take? Let us know in the comments below or at info@windowsfixup.com.

See our previous coverage on preparing your system for Windows Vista SP2 and what’s new in the release.

A follow-up post on Microsoft’s Windows Team blog reads:

“If the telemetry we receive from the Windows 7 RC meets our expectations in terms of quality, then we expect to hit RTM in 3 months or so”

See this page for our full Windows 7 coverage.

The tool’s documentation states its “report will let you know if your PC meets the system requirements, if there are any known compatibility issues with your programs and devices, and will also provide guidance on your upgrade options to Windows 7.”

Upgrade Advisor can run under Windows 7, Windows Vista or Windows XP Service Pack 2. It is available for download from Microsoft’s download center.