Update problem

  • Thread starter Thread starter StormFX
  • Start date Start date
S

StormFX

I keep getting the same update. From 5731 to 5735.

It will install with no problem. Then next day or
whenever I update agian I ge the same update file.Just
wanted to let your guys be aware of this problem.
 
Storm,
Give the MS site a try , and see about getting build 615, released 7/18.

Ron Chamberlin
MS-MVP
 
Nope. Did that. Fixed the gcUnCompress.dll a while
back. Now the update problem is back again, this time
5737 won't stick (keeps saying it has 5735, downloads and
install 5737, then it still says it has 5735 and it does
it again. Over and over. Every single frigging time you
click "check for updates.")

I have the .615 build. And 5735 definition file. Looks
like I'm stuck with that one until Dec. 31.

I'm going back to Lavasoft.
 
So sad. It's happening to me too. (5735 to 5737 over and over.)

I'm not going back to Lavasoft, though, because I use both.
 
Kerry said:
Now the update problem is back again, this time
5737 won't stick (keeps saying it has 5735, downloads and
install 5737, then it still says it has 5735 and it does
it again. Over and over. Every single frigging time you
click "check for updates.")
Click to expand...

You must empty your Temporary Internet Files (or any other web cache) before
attempting a definitions update.
 
Walterius said:
So sad. It's happening to me too. (5735 to 5737 over and over.)
Click to expand...

You must empty your Temporary Internet Files (or any other web cache) before
attempting a definitions update.
 
You must empty your Temporary Internet Files (or any
other web cache) before
attempting a definitions update.
Click to expand...

Temp Internet Files had nothing to do with it. It was
the Spynet/Akami synch issue you illustrated in a
separate thread.

Three computers; all with the same 5735/5737 def update
problem for two days; Cleared cache on 1 but not on other
2; Def updates worked on ALL THREE after Trish's post
late last night that 5737 Defs were now available.

NOT a local web cache issue.
 
Back
Top