A number of users have reported an issue in which Windows 7 displays a message indicating that there is “no Internet Access,” accompanied by a yellow exclamation point warning sign, despite the fact that Internet access works properly in all applications.
Fixes
Disable link scanning in antivirus/malware software The number one cause of this issue is problematic link scanning functions in various antivirus/malware software packages. Try disabling any link scanning components, then restart and check for Internet access.
For example, you can disable AVG’s link scanner by clicking on the AVG icon in the task bar (lower-right hand corner) then selecting “Link Scanner” and unchecking the “Enable AVG Search-Shield” box.
Look for a similar Web “link scanner” or “web shield” component in your antivirus/malware package and temporarily disable it, then restart your computer and check to see if the problem still exists.
Disable then re-enable antivirus software In other cases, simply disabling then re-enabling antivirus software can resolve this issue.
Filed under Viruses/Malware, Windows 7 by on Aug 24th, 2009. 23 Comments. 
Under various versions of Windows, Windows Explorer may repeatedly crash either when certain actions are taken (e.g. right-clicking an item), after several minutes of use, or immediately after the system starts up. In some cases, the following error messages are displayed:
- “Windows Explorer has encountered a problem and needs to close”
The first thing you need to do, if this problem occurs as soon as your system starts up or whenever you click on any file or try to perform any other action, is download a copy of Universal Explorer, an alternative file viewer. This will at least allow you access to the system so that you can make changes and begin troubleshooting.
Next, begin with the following potential fixes:
Turn off DEP In some cases, Data Execution Prevention may be causing the crashes to occur. Turning this option off for Windows Explorer may leave your system more vulnerable to viruses and other malware, but may allow your system to function properly until you can find another workaround. To turn off DEP for Windows Explorer, follow these steps:
- Click the Start button
- Open the Control Panel
- Open System
- Select the “Advanced” tab
- Under “Performance,” choose Settings.
- Select the “Data Execution Prevention” tab.
- Select the option “Turn on DEP for all programs and services except those I select.”
- Click “Add…”
- Find Windows Explorer, which is generally located in c:\windows\explorer.exe and select it.
- Restart your system and check for persistence of the issue
Note that if Windows Explorer keeps crashing during the above steps, you can open the command line and type bcdedit.exe /set {current} nx AlwaysOff and accomplish the same effect.
Disable Shell extensions The site HelpWithWindows suggests that errant shell extensions may be to blame for Windows Explorer crashes, especially in cases wherein the issue occurs upon right-clicking certain files.
Download and install the tool ShellExView. It will show the description, as well as version details, company information, location, file name and more of any installed shell extensions and allow you to disable them.
Start by disabling all third-party shell extensions, then restarting your computer. If Windows Explorer doesn’t continue crashing, you know that a shell extension is to blame. Start re-enabling them one-by-one or in groups until you identify the culprit, then leave it disabled.
Switch antivirus software As we have noted, the presence of two overlapping antivirus or antimalware/spyware/firewall tools can cause various conflicts. Users should install one (and only one) strong anti-virus package and make sure it’s up-to-date.
In addition, certain antivirus packages can conflict with installed system software while other antivirus packages are not.
If you have already tried the aforementioned workarounds, completely remove or disable all antivirus/spyware software (Norton 360, ZoneAlarm, AVG, etc.). In fact, you may need to uninstall the packages–simply disabling may not work.
Next, re-install one and only one solid antivirus/spyware tool. If the crashes still occur, uninstall that package and try a different one.
Filed under Windows 7, Windows Vista, Windows XP by on Jun 23rd, 2009. 1 Comment.
Windows 7 RC1 breaks compatibility with some antivirus/anti-malware programs that were compatible with previous pre-release builds of the operating system. Users are reporting problems with:
- avast! Home Edition
- AVG Anti-Virus Free
- Symantec AV Corporate Edition
Some developers are already working on Windows 7 RC1-compatible updates to their antivirus programs. A post in the AVG forums, for instance, states “This is a known issue, and it is planning to be fixed in one of the future updates of AVG 8.”
Note, however, that some antivirus program error messages do not necessarily indicate that your system is unprotected. If, for example, you receive an error message indicating that that antivirus program is still on but is not properly reporting its status to Windows (as displayed below), you may still be protected.
In the meantime, we have compiled a list of antivirus applications that appear to be compatible with Windows 7 RC1.
Feedback? info@windowsfixup.com.
Filed under Viruses/Malware, Windows 7 by on May 5th, 2009. 3 Comments.
As we have noted, the presence of two overlapping antivirus or antimalware/spyware/firewall tools can cause various conflicts. Users should install one (and only one) strong anti-virus package and make sure it’s up-to-date.
One problem that can result from the presence of conflicting protection tools is an inability to connect to the Internet. This issue is typified by a persistent or sporadic inability to load web pages, generally accompanied by a never-ending “Connecting…” message in any given Web browser.
To resolve this issue, completely remove or disable all antivirus/spyware software (Norton 360, ZoneAlarm, AVG, etc.). In fact, you may need to uninstall the packages–simply disabling may not work.
Next, re-install one and only one competent antivirus/spyware tool and check for Internet connectivity.
Filed under Internet Explorer 8, Viruses/Malware, Windows 7, Windows Vista, Windows XP by on Apr 6th, 2009. 1 Comment.
April 1st is here, and early indications are that the much-ballyhooed Conficker worm is more bark than bite. Aside from a modest increase in junk mail that may be completely unrelated, users have yet to report any rise in infection or other adverse effects. Regardless, there is a drop-dead simple process you can use to protect against virtually any potential Conficker maladies, and the same process should be put in place under any circumstances to protect against other malware, viruses and other security threats. Here are the steps:
1. Make sure your Windows system has all pertinent updates Launch Internet Explorer and go to windowsupdate.microsoft.com. Install the ActiveX control if necessary, then use the “Express” option to download the latest and most important updates. That’s it–your system now has Microsoft’s latest Conficker protection mechanism installed. Microsoft may issue “zero-day” updates over the next few days, so check back regularly.
2. Install one (and only one) strong anti-virus package and make sure it’s up-to-date There a number of free, regularly updated anti-virus packages that do a fabulous job of protecting against worms like Conficker. Here’s a list:
Pick one and only one package and make sure it is updated frequently. Installation of multiple anti-virus packages can create conflicts that might actually weaken your system’s immunity and can create stability and performance issues.
As mentioned above, vendors may issue “zero-day” patches over the next few days to counteract any new variants of Conficker. Check the developer’s website or intra-application auto-update mechanisms regularly for the latest updates.
3. If you’re already infected, run this One of the nastiest elements of the Conficker worm is that it can disable antivirus and anti-malware tools, making it difficult to find and eliminate the worm after it’s been hatched. However, Microsoft offers a free OneCare system scan that is done over the Web, meaning it will be more likely to work if Conficker has crippled your software. Click here to access the scan.
–
If you’re still paranoid, you can rework your password to make it stronger and disable AutoRun.
Filed under News, Windows 7, Windows Vista, Windows XP by on Mar 31st, 2009. 1 Comment.
Determining whether or not malware is to blame for any given troubleshooting issue can be tricky. Some malware-caused issues manifest as simple application instability, slowness or seemingly random freezes. However, there are a few instances in which malware is a more-than-likely culprit. In this series of articles (“Signs That You Have Malware”), we’ll explore some of the tell-tale signs and reiterate the best methods for ridding your system of the infection.
Today’s sign: One or more flashing windows that suddenly pop up then disappear. Generally these windows are blank and cannot be closed, re-opened or otherwise manipulated.
Why it might be malware A constantly reappearing but non-functional window can be the result of an unwanted executable attempting to run.
How to get rid of it Start with Malwarebytes Anti-Malware, a shareware malware and spyware removal tool that can eliminate many types of unwanted executables.
Next, move on to Microsoft’s Malicious Software Removal tool. Microsoft releases an updated version of this tool on the second Tuesday of each month, and “as needed to respond to security incidents.” You can keep it up to date with Microsoft Update, Windows Update and the Microsoft Download Center
Finally, run a scan with a good anti-virus package. AVG is free, and comes highly recommended by users and experts alike. Just remember, stick to one good anti-virus package. Installing multiple anti-virus programs can actually weaken your protection and introduce performance and stability issues. The following anti-virus apps are also recommended:
Filed under Windows 7, Windows Vista, Windows XP by on Mar 31st, 2009. Comment.