Updating

  • Thread starter Thread starter -pk-
  • Start date Start date
P

-pk-

-----Original Message-----
My MSAS is not updating itself, nor am I able to maually
update it. I get an error that says unable to connect to
the itnernet. I have exausted all possible reasons that I
could think of. Any ideas out there?
.
Click to expand...

I am also getting this, it's possible that they are
updating their servers with a new update release.. or so
i hope.
 
This is one possible cause of the specific error message. And such updates
have recently happened towards the end of the week.

If you find this issue persists--i.e. your definition files are clearly way
out of date, going by the information in this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;892519

a fix which seems to work is to actually physically delete or rename the
files involved. This has had positive results in most cases I've had
feedback on so far--although I think it had no effect in one case.
 
Another issue is (known?) bug in the scheduler. In my setup I asked 10-AM.
My fire-wall logs shows 19:03 (some days but not all with an attempt to
update software if I understand welle the name of the process). I think you
must ensure you admin account is running for more than one day without
interrupt to be able to update.
I also noticed a side effect on timestamps (update time shown by MSAS isn't
MS-KB, isn't the one shown on properties and isn't the one shown for update
by the fire-wall log).
 
Just used the suggestions in the Updating Problem thread
under Networking and im getting the same conclusion with
tcpview, it's not even attempting to send anything.


I should probably mention that I was having proxy issues
before installing MS AntiSpyware. Other programs which
are having problems include Steam and Norton Quarantine.
Both programs fail to connect and by using a packet
monitor Norton Quarantine doesn't even try to send
anything (just like MSA); when using Steam I try to
update/refresh the server list and it trys sending pairs
of packets to destination 0.0.0.0:0

I have tried fixing this issue with these two programs
for about a month and it didn't start happening until I
removed a broswer hijacker called Search-Essentials (
se.dll ), 2nd Thought Trojan ( stcloader.exe ), & a few
other adcrap that came along with 2nd Thought. Also I
should probably say that 2nd Thought Trojan was detected
and removed once again about a week later with another
file name( hyperlinker3.exe ). Just yesterday I ran
Spybot Search & Destroy and it pointed me towards the
remains of Hyperlinker3/2nd Thought Trojan in the
registry and an MSA undectected file ../system32/lmdv.bin

I have already uninstalled all Networking related
programs, MS products (word, powerpoint, excel, access,
outlook, VisualStudio.Net, .NET Frame Work, etc.), along
with Norton and Steam. I even uninstalled the service
packs and reinstalled them. I have messed with proxies,
firewalls, routers, trying different ethernet cards,
changing TCP/IP properties, checking hosts file, checking
the registry/services/startup, etc. You say it I've
probably already tried it.

I was planning on just reinstalling Windows XP anyways
due to the constant spyware problems (of which I should
mention my less knowledgable brother, sister, or dad
installed) - The reason I haven't done this already is
because I wanted to help win the war on spyware and was
willing to help with Spynet submissions and other issues
such as these; However, i'm afraid that the time has come
and that I have lost this battle.. but nevertheless I
will be back :)
 
Jacques said:
Another issue is (known?) bug in the scheduler. In my setup I asked 10-AM.
Click to expand...

Hmm - I have scheduled scans set for 10 AM, and they happen at that time. I
have no idea when the scheduled update is set to--OK, daily at 9 AM. No
idea if that is working.
My fire-wall logs shows 19:03 (some days but not all with an attempt to
update software if I understand welle the name of the process). I think
you must ensure you admin account is running for more than one day without
interrupt to be able to update.
Click to expand...

I suspect there will be significant improvement in both the scheduling and
the aspects of the program that would do better as services in beta2.
I also noticed a side effect on timestamps (update time shown by MSAS
isn't MS-KB, isn't the one shown on properties and isn't the one shown for
update by the fire-wall log).
Click to expand...

I haven't tried to analyze where the timestamps come from--I don't even
understand why they are useful--perhaps in some legal sense in determining
which set of definitions were in effect at a given moment.... I go by the
definition numbers, or the files themselves.
 
I just spotted the se.dll in your message. Steve Dodson said that he had
some additional information for folks cleaning this one.

You might drop a line to Steve at:

(e-mail address removed)

and see whether what he has might help.

I take it you've done both a Winsock reset and a TCP/IP reset?
(netsh winsock reset)
(netsh int ip reset c:\resetlog.txt)
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357
 
If you click on the last item of main windows, named "Auto-Updater", you
have a blue windows last line is "manage ato-updater".
I found that very usefull for home users. You just need to choose day and
hour (avoiding known bugs of scheduler). I chosed scan at lunch time (1-PM)
so must have auto-update just before (hugh, I fall in 10-AM doubt).
After that, you let run the system for some days and look in firewall log...
that's all.
 
With new defs (5707 released this night) and new setting (11-AM), if my bug
description is correct, I suppose I'll have this new defs installed today
(as I changed schedule) at 11:00 with apparent date 14/04 (2 days bias) and,
tomorrow update process occuring at the time shown by MSAS.
 
That would make sense--we'll see. Then they'll release beta2 and we'll have
to find a different set of bugs!
 
Back
Top