Tech Support > Operating Systems > New AdShield setting interferes with Windows Update for IE6sp1
New AdShield setting interferes with Windows Update for IE6sp1
Posted by Kent W. England [MVP] on June 30th, 2003


Folks;

I posted a difficult problem some time ago and found no resolution. It
turns out that a new version of AdShield 3.0.5.0, a BHO popup/ad
blocker, is interfering with the WUv4 home page. The new setting that
causes the problem is to block delayed popups that use a timer in the
script. The resolution is to put http://v4.windowsupdate.microsoft.com/
in the Exclusion List. The option to block delayed popups is off by
default.

Following is the (modified) troubleshooter item that matches this
symptom:

Microsoft Windows Update Troubleshooter:
http://v4.windowsupdate.microsoft.com/troubleshoot/

"Checking for the latest version of the Windows Update software..."

Problem Description:

When you're using the Windows Update Web site you receive a dialog box
that states:

"Checking for the latest version of the Windows Update software...

Depending on your connection speed, this might take a minute. To
ensure that you're able to view Windows Update when this verification
is complete, select Yes in any "Security Warning" dialog boxes that
appear."

or

Depending on your connection speed, this might take a minute. During
this time, you may receive one or more security warnings. Review each
security warning to ensure that the content is signed by Microsoft,
and then click Yes to install the software."

The update process freezes at this point.

Resolutions:

This may be caused by a third-party firewall product called Zone Alarm.
Try disabling this program and opening the Windows Update site again. Be
sure to enable your firewall again when you are done.

-- add --

This may be caused by a third-party ad blocker called AdShield. Put
http://v4.windowsupdate.microsoft.com/ in the Exclusion List to avoid
this problem or disable the "Block delayed pop-ups" feature.

--
Kent W. England, Microsoft MVP for Windows



Posted by David Herman \(507119\) on June 30th, 2003


I'll give that to Lin's team to add. Thanks,

--
David Herman
BetaID: 507119


"Kent W. England [MVP]" <kwe@mvps.org> wrote in message
news:Oi8XdMsPDHA.2832@TK2MSFTNGP10.phx.gbl...


Posted by Jonathan Woodard [MSFT] on July 1st, 2003


Thank you for posting this solution! We're updating the article ASAP.

--
Thanks,
Jonathan (Microsoft)

This posting is provided "AS IS" with no warranties, and confers no rights.
--

"David Herman (507119)" <big_dave@hotmail.com> wrote in message
news:eauGStuPDHA.3192@tk2msftngp13.phx.gbl...


Posted by Kent W. England [MVP] on July 2nd, 2003


You're welcome. In return if you or someone else could explain to me via
email what part of the WUv4 page is triggering the block (which is only
supposed to block delayed popups), I'd appreciate it very much.

--
Kent W. England, Microsoft MVP for Windows



"Jonathan Woodard [MSFT]" <jonwood@online.microsoft.com> wrote in
message news:ei5LKOBQDHA.2248@TK2MSFTNGP11.phx.gbl...

Posted by Vikas Sahdev [MSFT] on July 2nd, 2003


Hi Kent,
I would be glad to assist you here. Can you tell me
is this the first time you are visiting the windows update
site ?

There is no delayed popup on the site initialization.
Infact the only pop-ups which appear during the
initialization are the client control certificate popups
and that too only the first time anybody comes to window
update site.

So if you already have the control bits installed on your
system ( meaning that if you accessed the site
successfully earlier anytime), there should be no popups
on the site initialization and Adshield should not
interfere with the site experience.

Thanks



Disclaimer: This posting is provided "AS IS" with no
warranties, and confers no rights. "Use of included script
samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"





Similar Posts