Newest signature will not install

[Guest]

Until today, I have had no problems with Defender updating its definition
file, but the latest file (1.14.1408.8) will not install. I just keep
getting the error message that the update was not successful, and I have no
idea why. Anyone else have this problem or a solution.

I also don't know why there are never any programs listed on the "allowed
programs" page. Is this by design, a problem with the beta version, or what?

Thanks.

 

[Bill Sanderson MVP]

First thing to try is the resolution steps in this KB article:

http://support.microsoft.com/?kbid=915105

 

[Guest]

Sorry, I have just tried the procedures in kbid=915105 and the result is the
same. There is a funny quick message in WD tray icon stating error 0x80240022
and instructing to insert some ??? diskette with ??? serial number into ???
drive.

There must be something wrong with the Definition Update file.

 

[Guest]

I have exactly the same problem.

Just finished a Windows Update to the newest defenition and upon reboot I
tried a manual defention update and got the error as you describe below.
Looks like bad code to me !!

 

[Guest]

It would seem that this is still not fixed, as of 4/26. The KB article does
not work.

 

[Guest]

Just an update. I uninstalled Defender and reinstalled after downloading
again from the Defender website (because I'd read there were two versions of
Beta2). After the install, Defender went out and got the latest update and
installed it successfully. We'll see if there is a problem with the next
update that is not tied to an initial install, but for now I have the latest
definition file.

 

[Steve Dodson [MSFT]]

This is a new issue:

Can you send me:
c:\windows\windowsupdate.log
MSI install logs
http://support.microsoft.com/?kbid=223300

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

 

[Guest]

With regard to error code 0x80240022 as seen in the system tray when you try
to manually check for signature updates from within Windows Defender, the
event viewer for system events reveals 4 error entries not seen before.

(a)
Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error was
The referenced assembly is not installed on your system.

(b)
Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error
message: The referenced assembly is not installed on your system.
..

(c)
Generate Activation Context failed for
d:\f570ccbf49ab023e81e08b8c8bf1\SigStub.exe. Reference error message: The
operation completed successfully.
..

(d)
nstallation Failure: Windows failed to install the following update with
error 0x80070643: Definition Update 1.14.1408.8 for BETA Windows Defender
(KB915597).

Note that while the system tray gives error code 0x80240022, system log entry
(d) shows error code 0x80070643.

So the question is, what has changed recently that there is now a problem with
Windows Defender updating itself? Looks like an updated runtime file is
missing.
Does this problem only affect signature updates, or is the ability to update
the
software now also broken? If that's the case, it would make it difficult to
update
the software to fix problem!

Otherwise, Windows Defender, nice work, Thanks Steve.

This is a new issue:

Can you send me:
c:\windows\windowsupdate.log
MSI install logs
http://support.microsoft.com/?kbid=223300

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

It would seem that this is still not fixed, as of 4/26. The KB article
does
not work.

 

[Guest]

I have an install problem several times in the past. The only way I got
around it was to uninstall and reinstall. I guess when all else fails, "brute
force" will work. I would prefer to not have to do this, obviously. I look
forward to a resolution to this issue.

Thanks.

 

[Richard Hay]

I am amazed at the number of installation failures I see in these NG's. I
have never had a failure for signature or Defender updates.

(Knocks on wood!).

 

[Bill Sanderson MVP]

Updates are not broken. I looked at all my office machines hoping to find
some broken ones to gather log files from, and haven't found any--my
personal machine at home is broken, but none of the machines in offices I
administer is, at the moment.

I would think about deleting the manifest file, based on those log messages,
but you might want to wait for Steve Dodson who can say whether that really
makes sense.

--

With regard to error code 0x80240022 as seen in the system tray when you
try
to manually check for signature updates from within Windows Defender, the
event viewer for system events reveals 4 error entries not seen before.

(a)
Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error
was
The referenced assembly is not installed on your system.

(b)
Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error
message: The referenced assembly is not installed on your system.
.

(c)
Generate Activation Context failed for
d:\f570ccbf49ab023e81e08b8c8bf1\SigStub.exe. Reference error message: The
operation completed successfully.
.

(d)
nstallation Failure: Windows failed to install the following update with
error 0x80070643: Definition Update 1.14.1408.8 for BETA Windows Defender
(KB915597).

Note that while the system tray gives error code 0x80240022, system log
entry
(d) shows error code 0x80070643.

So the question is, what has changed recently that there is now a problem
with
Windows Defender updating itself? Looks like an updated runtime file is
missing.
Does this problem only affect signature updates, or is the ability to
update
the
software now also broken? If that's the case, it would make it difficult
to
update
the software to fix problem!

Otherwise, Windows Defender, nice work, Thanks Steve.

This is a new issue:

Can you send me:
c:\windows\windowsupdate.log
MSI install logs
http://support.microsoft.com/?kbid=223300

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

It would seem that this is still not fixed, as of 4/26. The KB article
does
not work.

:

I have exactly the same problem.

Just finished a Windows Update to the newest defenition and upon
reboot I
tried a manual defention update and got the error as you describe
below.
Looks like bad code to me !!



:

Sorry, I have just tried the procedures in kbid=915105 and the
result
is the
same. There is a funny quick message in WD tray icon stating error
0x80240022
and instructing to insert some ??? diskette with ??? serial number
into
???
drive.

There must be something wrong with the Definition Update file.
--
MW


:

First thing to try is the resolution steps in this KB article:

http://support.microsoft.com/?kbid=915105

--

Until today, I have had no problems with Defender updating its
definition
file, but the latest file (1.14.1408.8) will not install. I
just
keep
getting the error message that the update was not successful,
and I
have
no
idea why. Anyone else have this problem or a solution.

I also don't know why there are never any programs listed on the
"allowed
programs" page. Is this by design, a problem with the beta
version, or
what?

Thanks.

 

[Bill Sanderson MVP]

I'm keeping a low profile, 'cause I'm busy with actual work, rather than the
volunteering I do here, and also, I don't have a solid answer to the update
issues at the moment, but here's my set of prioritized steps for the current
issue:

1) be sure you are up to date on critical updates via Windows Update.
2) If you are not on the 1347 UI version posted April 12th at the download
center, download and install that.
3) Try 915105--although this doesn't seem to work for the current issues, I
suspect there is still a mix of causes involved, and it will work for some.

I'm going to quit my list there--there are other things I could try, but I
think I'd rather wait and see if we get some clearer guidance before telling
everyone in the world to try the cleanup tool, or removing and reinstalling,
etc. I'd rather sit tight for a bit than go overboard on advice that may
have downsides.


--

With regard to error code 0x80240022 as seen in the system tray when you
try
to manually check for signature updates from within Windows Defender, the
event viewer for system events reveals 4 error entries not seen before.

(a)
Dependent Assembly Microsoft.VC80.CRT could not be found and Last Error
was
The referenced assembly is not installed on your system.

(b)
Resolve Partial Assembly failed for Microsoft.VC80.CRT. Reference error
message: The referenced assembly is not installed on your system.
.

(c)
Generate Activation Context failed for
d:\f570ccbf49ab023e81e08b8c8bf1\SigStub.exe. Reference error message: The
operation completed successfully.
.

(d)
nstallation Failure: Windows failed to install the following update with
error 0x80070643: Definition Update 1.14.1408.8 for BETA Windows Defender
(KB915597).

Note that while the system tray gives error code 0x80240022, system log
entry
(d) shows error code 0x80070643.

So the question is, what has changed recently that there is now a problem
with
Windows Defender updating itself? Looks like an updated runtime file is
missing.
Does this problem only affect signature updates, or is the ability to
update
the
software now also broken? If that's the case, it would make it difficult
to
update
the software to fix problem!

Otherwise, Windows Defender, nice work, Thanks Steve.

This is a new issue:

Can you send me:
c:\windows\windowsupdate.log
MSI install logs
http://support.microsoft.com/?kbid=223300

--
-steve

Steve Dodson [MSFT]
Windows Defender Beta Lead
MCSE, CISSP
http://blogs.technet.com/stevedod
--

This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.

It would seem that this is still not fixed, as of 4/26. The KB article
does
not work.

:

I have exactly the same problem.

Just finished a Windows Update to the newest defenition and upon
reboot I
tried a manual defention update and got the error as you describe
below.
Looks like bad code to me !!



:

Sorry, I have just tried the procedures in kbid=915105 and the
result
is the
same. There is a funny quick message in WD tray icon stating error
0x80240022
and instructing to insert some ??? diskette with ??? serial number
into
???
drive.

There must be something wrong with the Definition Update file.
--
MW


:

First thing to try is the resolution steps in this KB article:

http://support.microsoft.com/?kbid=915105

--

Until today, I have had no problems with Defender updating its
definition
file, but the latest file (1.14.1408.8) will not install. I
just
keep
getting the error message that the update was not successful,
and I
have
no
idea why. Anyone else have this problem or a solution.

I also don't know why there are never any programs listed on the
"allowed
programs" page. Is this by design, a problem with the beta
version, or
what?

Thanks.

 

[Guest]

I had the same problem. Now that 1410 has been released, however, the
problem has gone away.