Going back to beta 1

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

hi
Running server 2003 network, with 40 Xp pro clients (updates checked daily)

We were using beta 1 quite happily, Beta 2 isnt too happy. All installs ok,
but its the defs which struggle (as ive read here, similar problems for me)

1. where can we redown load beta1?
2. Is it a problem to still run the old Beta 1?

Ive tried manually downloading the beta 2 update, but this didnt seem to get
some of my beta2 systems up to date. Some are fine.
3. Any other fixes for getting beta2 up to date, def wise?
4. and is there a URL for the update location? so i can check daily?

Thanks for your efforts on this forum

Simon Bratt
 
Updates within the program go via AutoUpdate--so be certain this is working
in your environment. It sounds as though it is.

You can manually update by going to Windows Update. In some cases, a manual
run to Windows Update, and applying all offered patches on an express scan
(with the exception of the WGA notification one) may put in a prerequisite
for automatic updates to work thereafter. The Windows installer 3.1 is
certainly required, and there seem to be others.

mpcmdrun.exe is a command-line executable in the Windows Defender folder
which both initiates scans and initiates checks for updates. You could
schedule this using task scheduler hourly, if you wished. However,
historically, updates have come out slightly more frequently than once a
week. This isn't an antivirus--there are sometimes definitions at
unexpected times, but rather infrequently.

Beta1 downloads appear to still be available at www.filehippo.com. I
wouldn't recommend going back--I believe that program will expire on July
31. Additionally, both the real-time protection, and the cleaning
capabilities are superior in Windows Defender. No further bug fixes will be
made to beta1.

The troubleshooting KB for definition updates is:

http://support.microsoft.com/kb/918355/en-us

However, there are additional possible remedies if that fails.

The mechanism by which updates are distributed means that the URL changes
with each update. Often, a user has posted these with a notice of the new
update--most recently on May 8 or 9th in this group, by Engel.

I know that they are working hard on the update issue--and I saw only a
handful of folks having problems on the last cycle, and none of my machines
had a problem (my home machine has had problems with the previous two update
cycles)

Personally, I think you are better off with the new program, and I'd monitor
..announcements and .signatures to see when new ones are released. In
offices I administer, I typically find that all machines have updated
automatically with no user interaction--and that's an excellent result.


--
 
Thanks Bill, ill stick with beta 2 then. I admit i didnt do an manual forcing
of windows updates. ill try that now
 
Yup thats great a forced windows update sorted them out, i hope the next
update will come automatically
 
Back
Top