New Windows Update (Jun '05)

[Guest]

Have had no problems using Windows Update v5 since I configured Kerio
Personal Firewall to ignore applying it's rules to any domains connected to
windows update
(i.e. v5.windowsupdate.com, download.windowsupdate.com, go.microsoft.com,
heck - even *.microsoft.com & *.windowsupdate.com and quite a few others.)
To this, I even added said sites to my trusted sites list in IE6 (and,
dangerous or not, I give these sites in the Trusted Sites zone <i>carte
blanche</i> to do whatever, wherever, whenever.

My problem comes as I entered Windows Update this week to be greeted with a
new version of the software and, after installing and then selecting the
usual 'Custom' button I am faced with an error (0x800A0046) and told that I
should swith on 'Userdate Persistence' in the Security Settings.

Now, I may be reckless, allowing my 'Secure Sites' permission to do anything
but there is no way on Earth I am changing my 'Internet Zone' security
settings (which are *damn* tight) to allow this update.

Whats changed? Whats going wrong? Why do MS have to go and change things?

 

[PA Bear]

Windows version?

You may receive an error message when you search for available updates on
the Windows Update Web site or on the Microsoft Update Web site:
http://support.microsoft.com/?kbid=883821

0x800a0046 Windows Update error
http://www.updatexp.com/0x800a0046.html
--
Windows Update-specific newsgroup:
news://msnews.microsoft.com/microsoft.public.windowsupdate

~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE) & Security, AH-VSOP

 

[Guest]

XP SP2 - Bang up to date, (until this incident...)
Already tried these! Newsgroup was absolute last port of call before booking
hair transplants...
OKAY! Bit more like it! It would appear the shared experiences of the
unfortunate few on the newsgroups provide more insight.
I now have a couple or three ideas I need to try, (beginning with updating
Kerio Personal Firewall which MAY be involved and investigating WHO certain
services, such as BITS and Windows Update are logging on as...

Thanks for the pointers Robert!