Windows

0

Users have reported problems with a number of programs after the update to Windows Vista SP2.

Microsoft provides a list of applications that will lose functionality (either partially or completely) after the update. Among them are a number of antivirus/anti-spyware tools, including:

  • Avira AntiVir
  • Spyware Doctor
  • Trend Micro Internet Security & Virus Buster
  • Spy Sweeper

Developers will be releasing updated versions of some of the aforementioned applications in the coming days, so stay tuned to manufacturers’ websites for new releases.

Filed under Viruses/Malware, Windows Vista by on . Comment#

0

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:

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.

5

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 . 5 Comments#

0

itunes-logoSeveral 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:

  1. Quit iTunes if it is open
  2. Navigate to the following directory: \Documents and
    Settings\username\My Documents\My Music\
  3. Open the iTunes folder
  4. Remove the following files: iTunes Music Library.xml and iTunes Library.itl. Put them in another location on your hard drive for safe-keeping.
  5. 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."
  6. 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.
0

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

0

chkdskSeveral 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 . Comment#

0

Some users have received a black screen when attempting to connect to various systems (primarily those running Windows Vista) via the Remote Desktop protocol (RDP). In some cases, the host machine may crash when this problem occurs.

Other users have reported receiving the error “atbroker.exe crashed” or “Transitions Accessible technologies between desktops has stopped working”

Fixes

Make sure updates are installed, not waiting It appears that, in some cases, this problem may occur when updates are downloaded, but not installed in Windows Update on the host machine (the one receiving the connection). Try installing any pending updates then restarting the system.

Uninstall drivers Try uninstalling any recently installed third-party drivers, or drivers that you installed right before the problem started to occur, then restart. To do this, click the Start button then navigate to Control Panel > System and Security > Device Manager. Right-click any recently installed third-party items and select “Uninstall” then restart. Some users have reported that the Logitech QuickCam driver may be to blame.

Update to Windows Vista SP2 Some Windows Vista SP2 beta testers have reported that updating to the new release resolves this issue. Unfortunately, SP2 is not yet publicly available, but is available in final form to TechNet subscribers.

Filed under Windows Vista by on . Comment#

2

vista-network-iconUsers have reported a variety of local networking issues under Windows 7. These include an inability to see or exchange files with Windows Vista or XP systems, inability of other systems on the LAN to see Windows 7 systems and more.

Fix

Some networking issues may be related to mismatched authentication settings. Make sure that local area network authentication settings are the same on all computers on the network. To check this setting on, click the start button, then enter secpol.msc in the search field (use “Run:” in Windows XP) and press enter.

Navigate to Local Policies > Security Options and find “Network Security: LAN Manager authentication level.”. Make sure it carries the same settings on all systems and the server, if one exists.

Alternative fix

Some users have also had success with temporarily turning off the Windows 7 firewall, allowing other machines on the network to be discovered, then turning the firewall back on.

To turn the firewall on or off, open the Control Panel then the click the Windows Firewall icon and modify the setting on the left.

Filed under Windows 7 by on . 2 Comments#

40

chromelogoSeveral users have reported an issue in which Google Chrome will not display Adobe PDF files in the browser. Users experiencing this problem may receive the error message: “The Adobe Acrobat/Reader that is running can not be used to view PDF files in a Web Browser. Please exit Adobe Acrobat Reader and exit your Web Browser and try again.”

Fix

This problem can generally be easily fixed by copying the Adobe PDF plug-in to the Google Chrome Plugins folder. You may need to create the Plugins folder yourself if one does not already exist. Follow these steps:

  1. Go to Program Files\Adobe\Acrobat(version number)\Acrobat\Browser
  2. Copy the file nppdf32.dll
  3. If you are using Windows XP, go to C:\Documents and Settings\(username)\Local Settings\Application Data\Google\Chrome\Application\(Version Number)\. If there is not a Plugins folder there, create a new folder with the name “Plugins.” Paste nppdf32.dll into the Plugins folder. Quit and restart Google Chrome and retry PDF access.
  4. If you are using Windows Vista or Windows 7, go to (username)\AppData\Local\Google\Chrome\Application\. If there is not a Plugins folder there, create a new folder with the name “Plugins.” Paste nppdf32.dll into the Plugins folder. Quit and restart Google Chrome and retry PDF access.

Failing the above, use an alternative reader. One good choice is the free Foxit Reader. It tends to use fewer resources than Adobe Reader, and works well in Windows 7.

4

(See more fixes here)

Early-access users who installed a pre-release version of Windows Vista SP2 are experiencing some issues with installation of the final release. Users may receive the message “Service Pack Installation Cannot Continue: One or more of components that the service pack requires are missing.”

Fix

Try deleting the file vLite key from the registry. To do this:

  1. Click Start
  2. In the search box, 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

Filed under Windows Vista by on . 4 Comments#

Partly powered by CleverPlugins.com