Fix for 0x8050800c and other issues

[Mike Treit [Msft]]

Please be aware that with the latest signature and engine update (released
this evening) we have provided a fix for the 0x8050800c error that a number
of people were hitting, as well as various other fixes for a variety of
issues.

Please ensure that you have updated to the most recent signature and engine
version. You can force an update by opening the Windows Defender UI and
clicking the down-arrow next to the help button, then selecting About
Windows Defender and finally clicking the Check for Updates button.

After the update complete, you should see the following version information,
which will confirm you are running with the latest updates:

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6

Once you are up-to-date, please spend some time testing the new code and as
always report any problems here in the newsgroups.

Thanks

-Mike

 

[plun]

Windows Defender Version: 1.1.1051.0

Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6

Hi

Still problem with the cleanup procedure after update.

Notifys "ON" and Advanced Spynet member

Path Found:
regkey:HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce\\wextract_cleanup0;runonce:HKLM\Software\Microsoft\Windows\CurrentVersion\RunOnce\\wextract_cleanup0;file:C:\WINDOWS\system32\rundll32.exe
Threat Classification: Unknown
Detection Type:

WD reset with a scan or to start a scan and directly stop it. OK.


regards
plun

 

[Guest]

FYI - Updated successfuly this morning to:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6

However, I don`t know whether or not the `other issues`you mention were
supposed to cure the error generated when following the home page warning
`You haven`t scanned your computer in 3 days` is displayed, you then attempt
to scan from the `Start Scan` button offered. If it was, I`m still receiving
the following error:

"Windows Defender encountered an error: 0x80070002. The system cannot find
the file specified."

Thanks

Stu

 

[Bill Sanderson]

Don't know whether you've spotted the text log file for mpcmdrun which is
presumably in %windowsroot%\temp

(or was on one Windows 2000 machine I found it on!)

--

 

[plun]

Hi Bill

Within "temp" junkyard ...........

Also ballon settings

No this is something else about nothing to reset for WD.

This must be the same for all users running with notifys "on" beacuse
this is the same reset functionality as with removals.

Error 0x80501001

regards
plun

 

[Guest]

I'm still receiving this error with the versions you listed. Is there any
other info we can provide to help identify the issue?

 

[Guest]

--
John Arnett

 

[Guest]

FYI Mike, Friday's fix 'broke' my Defender, i.e., it did NOT have the problem
until I installed the update (1.13.1282.6). Fully-patched, clean, secure XP
Pro SP2 system on which Defender had run without issue until now.
Uninstalled, reinstalled, several times (w & w/out reboot and in safe mode)
to no avail. New reinstall w/out allowing update and all is fine other than
Defender definitions are out of date (sys tray and Windows Update
notifications in addition to one at time of install). :-|

 

[Guest]

Please be aware that with the latest signature and engine update (released
this evening) we have provided a fix for the 0x8050800c error that a number
of people were hitting, as well as various other fixes for a variety of
issues.

Please ensure that you have updated to the most recent signature and engine
version. You can force an update by opening the Windows Defender UI and
clicking the down-arrow next to the help button, then selecting About
Windows Defender and finally clicking the Check for Updates button.

After the update complete, you should see the following version information,
which will confirm you are running with the latest updates:

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1186.0
Signature Version: 1.13.1282.6

Once you are up-to-date, please spend some time testing the new code and as
always report any problems here in the newsgroups.

Thanks

-Mike


Hi,

before appling the update i didn't seem to have a problem on my windows 2003
sp1 server after applying the update i get the 0x8050800c error when i do a
scan of my machine.

Marcof

 

[Guest]

I'm still getting this error.
I don't know if this helps but it falls over when scanning the dvdplay.exe
file (Media Player 10 file) in the system32 folder every time it happens.

 

[Mike Treit [Msft]]

Dave / Marcof - could you please send me an email so I can contact you
offline to investigate further?

Thanks

-Mike

 

[Guest]

Greetings,
I have the same error. Removed Defender and reinstalled without updates
results in a complete custom scan with no error. As soon as I update and do a
complete scan, it stops on DVDPLAY.EXE with the 0x8050800c error. Have not
seen the 0x80004003 error yet. System is a P4 2.4 ghz., XP-pro/sp2, build
2600.xpsp_sp2_gdr.050301-1519. 768 mb ram. 18gb SCSI u160 drive.
Thanks,
Dan>

 

[Mike Treit [Msft]]

Please see my earlier post 'Explanation of error 0x8050800c using engine
build 1.1.1186.0' that has an explanation for this issue.

Or to summarize, if your system drive is a dynamic disk this behavior is due
to a known issue that will be corrected in a forthcoming update.

If your system drive is not a dynamic disk, please let me know.

Thanks

-Mike

 

[Guest]

Will wait for the update as all of my drives are setup as dynamic types.
thanks<86 Systems>

 

[Guest]

Any idea how long an engine update will be - there are a lot of us with
dynamic disks out there. I only converted as Microsoft sold the idea of how
great it would be!!!!

 

[Guest]

Mike

My disk is configured as Basic. I have Version 1.1.1051.0, engin 1.1.1186.0
and sig 1.13.1282.6.

I still get the error at the dvdplay stage. Have yet to complete a quick or
scheduled scan.

 

[Bill Sanderson]

Have you done a chkdsk on the partition?

Do you get any event log messages relating to missing registry hives?

 

[Guest]

Have done a chkdsk now and it showed no problems.

 

[Bill Sanderson]

Don't know what's going on. The error should relate to difficulty
reading/opening registry hives.
--