Several users have reported an issue in which they cannot run chkdsk on their systems, as the tool reports that it cannot continue because of corrupt files.
Fix
Try inserting the Windows Vista installation or recovery disc that came with your computer and rebooting from the disc. A few screens into the installation process (or accessible as an option in another menu) you should be given the ability to run a command prompt. At the command prompt, enter the command:
- chkdsk c: /f
then press enter. Run the tool repeatedly until no errors are reported.
(Note: if your system does not automatically boot from the Vista disc, you need to change the boot device in BIOS. To do this, boot from the installation disc, insert the disc, then restart, and while the computer is restarting, continually press the appropriate key [F12 on most systems, F1, F2, F10, the Delete (del) key or the Escape (ESC) key on others -- consult your user's manual or perform a Google search for your specific model] then select CD/DVD/CD-RW as the boot drive.)
Filed under Windows Vista by on May 15th, 2009. Comment. 
The latest build of Windows 7, build 7122, resolves some significant issues affecting a number of games under previous iterations of Windows 7.
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.
- Download this file and keep it somewhere safe.
- Navigate c:\windows\system32 or c:\windows\syswow64 depending on whether you are running Windows 32-bit or 64-bit.
- Take ownership of the existing dxdiagn.dll file in that directory (for instructions on taking ownership of a file, see this article)
- Rename the existing dxdiagn.dll file to dixdiagn.dll_backup
- Put the dxdiagn.dll file you downloaded in step 1 into the same folder that the old file was in.
Filed under News, Windows 7, games by on May 18th, 2009. 2 Comments.
Several users have reported an issue in which Windows 7 freezes when connected to wired (Ethernet) networks, but not when connected to wireless (WiFi) networks.
As described by Bryan Archambeault, a poster to Microsoft’s TechNet forums:
“So, as I mentioned above, I brought a wireless access point with me to the office today. I hooked up my laptop with the wired connection after having run it at home without any problems, and within 5 minutes, it locked up. I hooked up the wireless access point, removed the wired cable from the laptop, rebooted, and it’s now been working flawlessly since I came in this morning – about 5 hours ago.”
Another poster adds:
“I have been experiencing the same freezing problems with my T61p at work but at home where I have the wireless hub I haven’t experienced anything.”
It appears that, in some cases, this issue may be due to Cisco PIX hardware.
If you are experiencing a similar problem, please let us know at info@windowsfixup.com.
Filed under Windows 7 by on May 18th, 2009. 1 Comment.
We previously reported on some Windows 7 installation issues, including a problem in which the installer states “Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information” (see a fix for that issue here). However, users are now reported a host of other installation issues, including one in which the installer freezes during the “expanding files” phase and another in which the screen goes blank near the end of the installation process.
Fixes
For freezes that occur during the “expanding files” stage, bad memory may be to blame. See our article on checking for bad RAM and replace any problematic modules, then re-try installation.
For an issue in which the screen suddenly goes black, try turning your monitor off then back on again. It appears that the Windows 7 installer may lose communication with the graphics card or the monitor during installation, and powering your display off then back on can re-establish communication and allow you to continue with the on-screen prompts for installation.
Filed under Windows 7 by on May 19th, 2009. Comment.
Several users have reported a problem in which various media, including video, music and podcasts cannot be added to the iTunes library under various versions of Windows.
Fix
In some cases this issue can be resolved by recreating your iTunes media library. This can be accomplished via the following process:
- Quit iTunes if it is open
- Navigate to the following directory: \Documents and
Settings\username\My Documents\My Music\ - Open the iTunes folder
- Remove the following files: iTunes Music Library.xml and iTunes Library.itl. Put them in another location on your hard drive for safe-keeping.
- Launch iTunes and navigate to the "File" menu then select "Import." Find the file iTunes Music Library.xml from the previous step and click "Choose."
- Failing the above, quit iTunes and navigate to \Documents and Settings\username\My Documents\My Music\ and delete all files in the "iTunes" folder. Next, launch iTunes again and re-select "Import" from the "File" menu. Locate and re-import all of your music and other media.
Filed under Windows 7, Windows Vista, Windows XP, iTunes by on May 20th, 2009. Comment.
Several users have reported a problem in which Windows 7 RC1 systems either cannot connect to wireless networks or display the message low connectivity or no connection when attempted to the network. In some cases, using Windows 7′s built-in “fix” routine can resolve the issue, albeit temporarily.
Fix
Updating to the latest set of Broadcom wireless drivers, for systems that use Broadcom chipsets, resolves this issue for most users. In particular, users have had success with driver version 5.10.79.7, available here.
You may also want to run Windows Update to check for the latest drivers for wireless hardware from other manufacturers.
Filed under Windows 7 by on May 21st, 2009. 5 Comments.
Users have reported an issue in which Adobe Reader does not function properly under Windows 7. In particular, users report problems with intra-browser viewing of PDFs, noting that they sometimes get a blank pop-up with an Adobe title and an OK or hangs in the browser when attempting to view PDFs. The problem is most likely to occur in Internet Explorer 8.
Use an alternative reader
Several users have been able to quickly an easily work around this issue by installing and using an alternative PDF reader. One good choice is the free Foxit Reader. It tends to use fewer resources than Adobe Reader, and works well in Windows 7.
Filed under Windows 7 by on May 21st, 2009. 4 Comments.
Several users have reported an issue in which Netflix online streaming does not work properly in Internet Explorer 8 under various versions of Windows, or under Windows 7 in various browsers (including Internet Explorer 8). In some cases streaming works, but screensavers are not automatically disabled, the stream incorrectly uses low bandwidth, or other functionality is missing. In other cases, streaming does not work at all.
Fixes
Try compatibility mode In the IE 8 toolbar, click on the small icon that looks like a page broken in half, next to the refresh button (pictured below). This invokes “Compatibility View,” which can fix the Netflix issue.
Source: Microsoft
If the issue persists and you would like to downgrade to Internet Explorer 7, follow the instructions in this Microsoft Knowledge Base article.
Use the beta Netflix player The Netflix beta player, which is based on Silverlight, works better under Windows 7 for a number of users.
Filed under Internet Explorer 8, Windows 7, Windows Vista, Windows XP by on May 21st, 2009. 1 Comment.
After a long period of exclusive availability to TechNet and MSDN subscribers, Windows Vista and Windows Server 2008 SP2 has finally been released to the general public. The new release includes:
- 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.
Filed under News, Windows Server 2008, Windows Vista by on May 26th, 2009. Comment.
(See all of our Windows Vista SP2 coverage)
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:
- Click Start
- In the search box (or in “Run”), type regedit then press enter.
- Navigate to HKLM\Software\
- Select vLite
- Choose Edit and then Delete from the Registry Editor menu.
- 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:
- Click Start then go to the Control Panel and select “System and Maintenance”
- Go to Administrative Tools and select System Configuration
- Click Continue (enter admin password if required)
- Select the General tab then choose Selective startup
- Uncheck “Load startup items”
- Click the Services tab then check “Hide all Microsoft services” and select “Disable all”
- Click Apply, then OK
- Restart
- 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.
Filed under News, Windows Server 2008, Windows Vista by on May 26th, 2009. 64 Comments.