Engine Update

[Guest]

How do I manually update the engine from 1.1.1441.0 to 1.1.1481.0?

 

[Bill Sanderson MVP]

Engine updates have been locked to definition updates--they come in the same
package. So--if you are on 1525.2 definitions, you should also have 1481
engine.

I think it would be very interesting indeed if you have current definitions,
but not that engine level.

 

[Guest]

I have the following:

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1441.0
Definition Version: 1.14.1525.2

 

[Dave M]

Yes, very interesting. Do you recollect being offline from 6/23/06 and
after the next signature updates on 6/27/06 when the definition updates
rolled over to 1.14.1511.3 ? Sounds like someone forgot to include this as
a possibility. But more importantly, what happens if Rob updates now via
the old engine and definition manual update for Signature v. 1.14.1508.5
and Engine v. 1.1.1481.0 using the link?:

http://au.download.windowsupdate.co..._d37281b0194bfdefa5e35921617aee90fbd14555.exe

Is that possible to do at this point?

 

[Guest]

I am behind a network policy that does not allow me to receive updates via
Microsoft Update. Therefore, I apply all my updates manually. I assume that
I missed the update that included the engine. I have gone back, found that
update, but it does not work. I believe it fails because my definition
version is more current that the one bundled with the engine update. Any
suggestions?

 

[Guest]

First exit WD; using Add or Remove Programs in Control Panel. Click WD and
click Change. Click Next, and then click Updªte. Reboot.

Let us know how it works ºut.

I am behind a network policy that does not allow me to receive updates via
Microsoft Update. Therefore, I apply all my updates manually. I assume that
I missed the update that included the engine. I have gone back, found that
update, but it does not work. I believe it fails because my definition
version is more current that the one bundled with the engine update. Any
suggestions?

 

[Dave M]

Hi Rob;
You should be able to get current by first un-installing and then
re-installing WD, and might even be able to do it through a repair install
using Add/Remove, although I'm not sure if that alone is enough. I'd wait
for a member of the WD testing team like Joe Faulhaber to respond, in order
to make sure they see your post. They might want to ask about your
installation... so I'm adding his name to the Subject. Ms needs to be
aware of this bug, so it would help I'd think if you could hold off for a
short time and see if they get back to you on this. Bill S. might want to
ring their bell also.

 

[Bill Sanderson MVP]

Thanks, Rob--I think you've helped us spot what is happening here.

Here's what I think I'd try:

go to a command prompt in \program files\windows defender

mpcmdrun -removedefinitions

Then--retry the update with the link that Dave M published.

If that fails, another possibility is:

mpcmdrun -removedefinitions -all

and then update using the direct link.

You can see the arguments and syntax of mpcmdrun by simply running it with
no argument--mpcmdrun, or mpcmdrun |more

This is uncharted territory, so you may want to wait for somebody with MSFT
to respond, but I'm not sure how likely that is.

--

I am behind a network policy that does not allow me to receive updates via
Microsoft Update. Therefore, I apply all my updates manually. I assume
that
I missed the update that included the engine. I have gone back, found
that
update, but it does not work. I believe it fails because my definition
version is more current that the one bundled with the engine update. Any
suggestions?

 

[Guest]

Thanks. I had to use "mpcmdrun -removedefinitions -all" before the update
would work.

Windows Defender Version: 1.1.1347.0
Engine Version: 1.1.1481.0
Definition Version: 1.14.1525.2

 

[Bill Sanderson MVP]

I'm glad that worked--there are full and delta updates, and that was the
complication you needed to work around.

I want to emphasize here for all the others reading these messages that this
is an unusual situation--this is actually the first legitimate use for those
commands that I've found--lurkers, please don't take this thread as a
prescription for routine maintenance.