0x8050800c

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

Guest

I'm getting this error after the scan (quick or full) scans about 26k files
objects:

"Windows Defender encountered an error: 0x8050800c. An unexpected problem
occurred. Install any available updates, and then try to start the program
again. (To check for updates, click Start, click All Programs, and then click
Windows Update.)"

Definitions are fully updated, and the object it was showing on the scan
statistics when the error popped up is:

"HKLM\software\vgroup"

I just updated from Windows AntiSpyware to Windows Defender, and I didn't
have this scanning problem with the previous version. Any idea what might be
causing the problem?
 
I believe this one is seen by anyone with a dynamic disk partition (see disk
manager--right click My computer, choose manage, then click on disk manager.

--
 
The PC I encountered this on uses Windows 2000. I used Windows Update to
check if everything was up to date. Four items were found including a service
pak rollup, a GDI application, which Defender uses, and the latest definition
for Defender. After installation it worked fine. Might be worth a try to
check with Windows update.
 
I'm using Windows XP, fully updated.

Auburn said:
The PC I encountered this on uses Windows 2000. I used Windows Update to
check if everything was up to date. Four items were found including a service
pak rollup, a GDI application, which Defender uses, and the latest definition
for Defender. After installation it worked fine. Might be worth a try to
check with Windows update.
Click to expand...
 
They have a fix coded for this, which will be released as a part of an
update at some point--but I don't have a timeline for when it will be
released--it'll just be part of a normal update for the signatures. You
will, until that is released, be unable to complete a scan. However,
updates and real-time protection will be working correctly.

--
 
Interesting--so you were able to install--which meant that a GDIplus version
was already in place in system32 on that system--but it was old enough that
it predated the security rollup version...

Thanks.

--
 
I'm getting this error after the scan (quick or full) scans about 26k
files
objects:

"Windows Defender encountered an error: 0x8050800c. An unexpected problem
occurred. Install any available updates, and then try to start the program

again. (To check for updates, click Start, click All Programs, and then
click
Windows Update.)"

Definitions are fully updated, and the object it was showing on the scan
statistics when the error popped up is:

"HKLM\software\vgroup"

I just updated from Windows AntiSpyware to Windows Defender, and I didn't
have this scanning problem with the previous version. Any idea what might
be
causing the problem?
Click to expand...

My son was getting this error on his computer and we ran chkdsk on his
computer and it found errors on the drive and it fixed them. He ran another
scan and it finished the scan this time so you might want to try this and
see if it works for you.
 
Gary said:
My son was getting this error on his computer and we ran chkdsk on his
computer and it found errors on the drive and it fixed them. He ran
another
scan and it finished the scan this time so you might want to try this and
see if it works for you.
Click to expand...

Thanks--that's helpful. Do you know whether you son's disk partiton was
basic, or dynamic?

This is shown by right-clicking My Computer, choosing Manage, and then Disk
Management--look at the notations under Disk0 or Disk1 in the lower right
pane.
 
Thanks--that's helpful. Do you know whether you son's disk partiton was
basic, or dynamic?

This is shown by right-clicking My Computer, choosing Manage, and then
Disk
Management--look at the notations under Disk0 or Disk1 in the lower right
pane.
Click to expand...

It was basic.
 
Thanks--that's useful.

I believe that at this point, this error is expected on a dynamic partition,
but not expected on a basic one. So--users seeing this error on a basic
partition should do a chkdsk, as you did--excellent troubleshooting!

--
 
Thanks--that's useful.

I believe that at this point, this error is expected on a dynamic
partition,
but not expected on a basic one. So--users seeing this error on a basic
partition should do a chkdsk, as you did--excellent troubleshooting!
Click to expand...

What was happening was it would stop on a certain file and about ten seconds
later the error would appear. I new something wasn't right here so that is
when I ran chkdsk. People who turn there computer off by the power button or
the power goes off when the drive is being written to will have drive errors
most likely. It is good to run chkdsk once in a while to check for errors.
 
Thanks--that's interesting--this behavior is pretty similar to the way this
error works for users with dynamic partitions --the scan appears to hang on
a particular file name consistently.
--
 
I believe this one is seen by anyone with
a dynamic disk partition (see disk manager
--right click My computer, choose manage,
then click on disk manager.
Click to expand...

NO dynamic disks here and I get the same error
 
OK--One user with a basic partition reported that running chkdsk both fixed
errors on the partition, and corrected this error on scan. However, another
user reported no errors, and no change to the error--so my statistical
sample seems insufficient at this point!

--
 
Back
Top