Windows update hoses Activesync and Security Center reporting
Sam
functioning, complaining that it didn't have permission to login. I
tried uninstalling it and reinstalling... no difference. So I
uninstalled all of the new patches (not knowing which one was causing
the problem). ActiveSync works just fine again. Apparently they made
the system so secure that their own software couldn't access the
Outlook data.
While I'm on a rant, I also noticed that, after the updates, the
Security Center no longer recognized either my existing firewall or
antivirus software. I use the ZoneAlarm Security Suite and it was
recognized before. After I uninstalled the MS updates (see above) the
Security Center was once again happy. <sigh>
So, until they fix whatever they broke, it looks like I'll be
patchless for awhile.
Sam
Sam
I finally figured out that the problem was the Windows update
KB902400. Once this update was uninstalled, ActiveSync now works. No
problems with it recognizing my firewall or virus protection either. I
now have 6 out of the 8 patches installed. (I haven't reinstalled
KB896688 either since it has been reported to cause other problems).
Sam
PA Bear
Read this and you may want to rethink your decision:
SANS - Internet Storm Center - Cooperative Cyber Threat Monitor And
Alert System - Current Infosec News and Analysis:
http://isc.sans.org/diary.php?storyid=759
--
~PA Bear
Sam
wrote:
I do have 7 of the 8 updates successfully installed now. (I just put
in KB896688 without any problems) . The only one that's not been
installed is KB902400. Until I figure out how to synch my PDA, it will
have to stay off for now.
Sam
Sam
wrote:
>Sam wrote:
I'm doing some further testing to see what's going on. I've
reinstalled the KB902400 update and like clockwork ActiveSync refused
to synch.
However, I've noticed a bunch of Event Viewer errors. Maybe they'll
help figure out what's going on.
Event ID 8193 : Volume Shadow Copy Service error: Unexpected error
calling routine CoCreateInstance. hr = 0x80040206. [this error
appears three times]
Event ID 4609 : The COM+ Event System detected a bad return code
during its internal processing. HRESULT was 80070005 from line 44 of
d:\qxp_slp\com\com1x\src\events\tier1\eventsystemobj.cpp. Please
contact Microsoft Product Support Services to report this error. [this
error appears five times]
Event ID 5013 : Volume Shadow Copy Service error: Shadow Copy writer
Microsoft Writer (Bootable State) called routine
CVssWriterShim::Subscribe which failed with status 0x8000ffff
(converted to 0x800423f4).
Event ID 1802 : The Windows Security Center Service was unable to
establish event queries with WMI to monitor third party AntiVirus and
Firewall. [this error appears twice]
Any ideas as to what might be going on?
Sam
PA Bear
>>>> After installing the latest roundup of patches ActiveSync stopped
>>>> functioning, complaining that it didn't have permission to login. I
>>>> tried uninstalling it and reinstalling... no difference. So I
>>>> uninstalled all of the new patches (not knowing which one was causing
>>>> the problem). ActiveSync works just fine again. Apparently they made
>>>> the system so secure that their own software couldn't access the
>>>> Outlook data.
>>>>
>>>> While I'm on a rant, I also noticed that, after the updates, the
>>>> Security Center no longer recognized either my existing firewall or
>>>> antivirus software. I use the ZoneAlarm Security Suite and it was
>>>> recognized before. After I uninstalled the MS updates (see above) the
>>>> Security Center was once again happy. <sigh>
>>>>
>>>> So, until they fix whatever they broke, it looks like I'll be
>>>> patchless for awhile.
>>>>
I'd forward all of 'em (or this reply) to MS Product Support Services
(p...@microsoft.com), Sam, and reference this newsgroup thread (in archive:
http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/4be43a41c76c2d8f/5dcd34512df750c6?q=Windows+update+hoses+Activesync+and+Security+Center+reporting&rnum=1&hl=en#5dcd34512df750c6).
You may reference my name.
The last one concerns me most and may indicate a hijackware problem is at
least part of the overall problem. (See below.)
With 902400 installed, you might want to try the Clean Boot troubleshooting
technique to see if you're able to nail down a culprit other than the
update(s). See http://support.microsoft.com/default.aspx/kb/310353.
Checking for/Help with Hijackware
http://aumha.org/a/parasite.htm
http://aumha.org/a/quickfix.htm
http://aumha.net/viewtopic.php?t=5878
http://mvps.org/winhelp2002/unwanted.htm
http://inetexplorer.mvps.org/data/prevention.htm
http://inetexplorer.mvps.org/archive/tshoot.html
http://www.mvps.org/sramesh2k/Malware_Defence.htm
http://defendingyourmachine.blogspot.com/
When all else fails, HijackThis v1.99.1
(http://aumha.net/downloads/hijackthis.zip) is the preferred tool to use.
It will help you to both identify and remove any hijackware/spyware. **Post
your log to http://forums.spywareinfo.com/,
http://castlecops.com/forum67.html or http://aumha.net/viewforum.php?f=30
for expert analysis, not here.**
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE, Security, Shell/User)
Sam
wrote:
>Sam wrote:
Thanks for all your suggestions... I'll report this, as you suggest. I
don't think it's spyware/viruses though. I check for crapware pretty
regularly. Just to be sure, I did a full SpySweeper check and all it
found was 3 tracking cookies. I've also recently run AdAware and
Spybot.
Sam
Sam
wrote:
>I'd forward all of 'em (or this reply) to MS Product Support Services
>(p...@microsoft.com), Sam, and reference this newsgroup thread (in archive:
>http://groups.google.com/group/microsoft.public.windowsupdate/browse_frm/thread/4be43a41c76c2d8f/5dcd34512df750c6?q=Windows+update+hoses+Activesync+and+Security+Center+reporting&rnum=1&hl=en#5dcd34512df750c6).
>You may reference my name.
Just one last wrinkle... I tried to forward all this to
p...@microsoft.com and my mail got rejected:
><p...@microsoft.com>:
>131.107.3.123 does not like recipient.
>Remote host said: 550 5.1.1 User unknown
>Giving up on 131.107.3.123.
Any other places where I can send this information?
Sam
PA Bear
Lawrence Garvin [MVP]
I'm also wondering if there might be some sort of undetected conflict in the
COM fixes introduced by KB896688 and the COM+ fixes introduced by KB902400.
Maybe their coexistence is not coexisting?
I've seen responses that either of these updates being uninstalled has
'fixed' problems.
Personally, I have KB902400 installed without any noticeable issues
(although I'm not using ActiveSync).
It was the Cumulative Update that I'm holding off on, but I expect to do a
test install of it within the hour.
"PA Bear" <PABe...@gmail.com> wrote in message
news:ezggW5E0...@TK2MSFTNGP09.phx.gbl...
Lawrence Garvin [MVP]
l l . n e t
and I'll funnel through the WSUS group and see if they can help us.
"Sam" <ret...@home.net> wrote in message
news:9g0uk1l381m8he945...@4ax.com...
Sam
<onsitech...@news.postalias> wrote:
>
>I'm also wondering if there might be some sort of undetected conflict in the
>COM fixes introduced by KB896688 and the COM+ fixes introduced by KB902400.
>Maybe their coexistence is not coexisting?
>
>I've seen responses that either of these updates being uninstalled has
>'fixed' problems.
>
>Personally, I have KB902400 installed without any noticeable issues
>(although I'm not using ActiveSync).
>
>It was the Cumulative Update that I'm holding off on, but I expect to do a
>test install of it within the hour.
Except I had the same problem with KB896688 not installed. I actually
installed KB896688 a day after I figured out that KB902400 was the
cause of my problem.
Sam
Lawrence Garvin [MVP]
post with the details elsewhere in this newsgroup.
"Sam" <ret...@home.net> wrote in message
news:dr10l1pbbjc0ivsqe...@4ax.com...
PA Bear
KB909444 gave you information to resolve your problem, yes?
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE/OE, Security, Shell/User)
CC: MarieM
Sam
wrote:
>Sam, I understand from your reply to another thread in this newsgroup that
>KB909444 gave you information to resolve your problem, yes?
Correct. Changing the permissions of the C:\Windows\Registration
folder fixed the problem(s).
Sam