Update 'fix' also now fails to provide solution to installing new

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

Guest

Hi

For the last two sig# I have sucessfully removed the old sig# by going to
Start>Run> and typing 'Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}'
[without the quotes] to remove the old signature and then sucessfully
downloading and installing the new sig#

Now, at sig# 1.13.1276.16 I am notified that an update is available. It's
sig#1.13.1282.6. I cannot install this sig# using the standard WD[Beta2]
interface, or Windows Update. So, I tried the 'fix' as above in an attempt to
remove the old sig and download the new.

Event Viewer Applications confirms that the old sig has been removed. If I
go to C:\Documents and Settings\All Users\Application Data\Microsoft\Windows
Defender and look in the Defintions Update folder then the folder is empty.

If I look at the WD[Beta2] info it still lists sig# 1.13.1276.16

No matter how I try...deleting temp internet files, etc etc, rebooting and
all the methods I know to try a 'clean install' of the new sig# either by WD
or Windows Update, I cannot get past 'initialising update - update failed'

If I attempt to use more than once Start>Run> and typing 'Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}' [without the quotes] I am getting the
error message 0x80240022

Your help in getting out of this dead end appreciated.
 
i have been having a slightly different problme: the new sig of today
continuously auto downloads and puts an icon in the tray. When I executed
the install, it did update the sig - so says the Defender info screen.
However, the new update sig contiuously dowloads as the auto update feature
does not see thatthe update has occurred. Very frustrating situation -
Ican't stop the process!
 
Update............

I have now successfully installed sig# 1.13.1282.6

Having spent time studying Process Guard [PG] logs I can now see that PG was
blocking mpas-fe.exe

As soon as I 'allowed' mpas.exe the new signature installed [I had
previously removed the old sig# using the 'fix' method as mentioned further
up the thread.

I then ckecked PG logs for all the other signature install failures, and
there are no other listings for mpas-fe.exe........so I wonder if this is a
new .exe for the install?

I got the info for looking into mpas-fe when it was mentioned in this post
under Installation:

http://www.microsoft.com/athome/sec...&cr=US&r=e23dbd8f-cd66-4363-a118-7a12aba7c8a9

It will be interesting to see if adding mpas-fe.exe to the allow list in PG
will cure the signature update isues for me.
 
Thanks - that is interesting, and this isn't an executable that I've heard
of or seen before.
I can't spot the .installation post you referenced--can you give a date and
subject header?

--

julienfamilyman said:
Update............

I have now successfully installed sig# 1.13.1282.6

Having spent time studying Process Guard [PG] logs I can now see that PG
was
blocking mpas-fe.exe

As soon as I 'allowed' mpas.exe the new signature installed [I had
previously removed the old sig# using the 'fix' method as mentioned
further
up the thread.

I then ckecked PG logs for all the other signature install failures, and
there are no other listings for mpas-fe.exe........so I wonder if this is
a
new .exe for the install?

I got the info for looking into mpas-fe when it was mentioned in this post
under Installation:

http://www.microsoft.com/athome/sec...&cr=US&r=e23dbd8f-cd66-4363-a118-7a12aba7c8a9

It will be interesting to see if adding mpas-fe.exe to the allow list in
PG
will cure the signature update isues for me.

julienfamilyman said:
Hi

For the last two sig# I have sucessfully removed the old sig# by going
to
Start>Run> and typing 'Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}'
[without the quotes] to remove the old signature and then sucessfully
downloading and installing the new sig#

Now, at sig# 1.13.1276.16 I am notified that an update is available. It's
sig#1.13.1282.6. I cannot install this sig# using the standard WD[Beta2]
interface, or Windows Update. So, I tried the 'fix' as above in an
attempt to
remove the old sig and download the new.

Event Viewer Applications confirms that the old sig has been removed. If
I
go to C:\Documents and Settings\All Users\Application
Data\Microsoft\Windows
Defender and look in the Defintions Update folder then the folder is
empty.

If I look at the WD[Beta2] info it still lists sig# 1.13.1276.16

No matter how I try...deleting temp internet files, etc etc, rebooting
and
all the methods I know to try a 'clean install' of the new sig# either by
WD
or Windows Update, I cannot get past 'initialising update - update
failed'

If I attempt to use more than once Start>Run> and typing 'Msiexec /x
{A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}' [without the quotes] I am getting
the
error message 0x80240022

Your help in getting out of this dead end appreciated.
Click to expand...
Click to expand...
 
Back
Top