Error 0x8050800c after KB915597 (def. file 1.75.4.0)

  • Thread starter Thread starter randolindso
  • Start date Start date
R

randolindso

I downloaded and installed KB915597 and now Windows Defender won't scan.
I've been researching it and have found there have been like problems in the
past few years. I've tried the recommended fixes: uninstall/reinstall
Defender and run chk dsk, but to no avail. System restore will take me back
to the point where the Defender scan worked, but as soon as I reinstall the
update it's the same problem again. Am I the first to have this old problem
with this new KB update? Any ideas would be appreciated. FYI...
 
randolindso said:
I downloaded and installed KB915597 and now Windows Defender won't scan.
I've been researching it and have found there have been like problems in the
past few years. I've tried the recommended fixes: uninstall/reinstall
Defender and run chk dsk, but to no avail. System restore will take me back
to the point where the Defender scan worked, but as soon as I reinstall the
update it's the same problem again. Am I the first to have this old problem
with this new KB update? Any ideas would be appreciated. FYI...
Click to expand...
 
randolindso said:
I downloaded and installed KB915597 and now Windows Defender won't scan.
I've been researching it and have found there have been like problems in the
past few years. I've tried the recommended fixes: uninstall/reinstall
Defender and run chk dsk, but to no avail. System restore will take me back
to the point where the Defender scan worked, but as soon as I reinstall the
update it's the same problem again. Am I the first to have this old problem
with this new KB update? Any ideas would be appreciated. FYI...
Click to expand...
 
0x8050800C The system state prohibits the scan from running in a specific
user context.

Restart the computer, and retry the scan

<http://support.microsoft.com/kb/891717>


Right-click My Computer, and choose Manage. Click on Disk Manager. In the
right pane, is the partition type for the drive that contains the C: volume
"basic" or "dynamic"?

If it is dynamic, this error is a known bug, If you are in the U.S. or
Canada, I'd recommend calling Microsoft:
1-866-pcsafety
This is a toll free call (and the help is free too!) for security update or
malware infection issues.
If you are elsewhere in the world, the same free help is available, but the
phone call may not be free.
Call the nearest number for paid Microsoft
support in your part of the world.


If it is a basic partition, other users with this error have found that
running a chkdsk scan on the partition has eliminated this error.

No joy...... then
Run the Microsoft Windows Malicious Software Removal Tool

The very first thing you should do is to find out if there is any
malware resident.

Not sure by your post if this is XP or Vista. Besides the specific
edition of Windows installed, what Service Packs have been applied so far ?

In the meantime, see if you can download MBAM, install, update it, and
then run a Quick scan: <http://www.malwarebytes.org/mbam.php>
Click the ' Download free version ' button.
Once it's downloaded you may need to change it's name to *anything*
other than mbam-setup to get it installed.

Once it installs allow it to attempt to update. If it can not, then do a
Quick scan anyway. Allow it to remove what it detects.

*IF* it can not install and the system was able to update last month,
then try running the Microsoft Malicious Software Removal tool IF you've
previously allowed Windows Update to install it.

In Vista, click the Start orb, type in mrt in the Start Search field.
Then *right* click mrt.exe and choose Run as administrator.
In XP, click Start > Run > enter mrt in the Open field and then click OK
or press Enter.
When MRT opens click Next, then put a mark next to Full scan.

Click Next again. The scan will take awhile to complete but *should*
allow the installation of MBAM and/or allow you to have the system
scanned by an online scanner.

<http://www.superantispyware.com/onlinescan.html>

<http://onecare.live.com/site/en-us/tryscanner.htm>


If the MRT has never been installed nor updated, then I doubt you'll be
able to download and install it as the latest 'versions' of malware are
acutely aware of the MRT.
-=-


Good luck
-=-
 
First of all...thanks for the quick responses. "C" is a basic partition. I
had already checked that. The system is xp home, sp3, using IE7. The
Malicious Software Removal Tool shows no abnormalities. Likewise Avast 5,
Super Antispyware, a2, Malwarebytes. I'm looking into your other suggestions
now. Thanks again, and any and all ideas are welcome. I've never had any
trouble with updates before, up to and including last month, and nothing's
really changed on my system, so I'm really thinking it's the update. But I'm
puzzled that no one has had that particular problem with it.
 
Now I've done everything suggested to me. Just ran MRT and everything
checked out fine. I'm getting a little paranoid about this. Still don't see
where any other users have this problem with this particular update. I think
I'll try reverting back to good state (pre KB915597), run regshot, reinstall,
then regshot again. Have used this tool a couple times, but it's pretty deep
for me.
 
OK I also started getting this insane problem when I updated to the latest
def. There's nothing wrong with the unit, its clean, and ALL items on when WD
was working are still on. The problem has to be with these new updates since
Jan 22. I just did another update to the latest one from MS auto update and
still WD gives me this error.

I have tried a reg fix I found, but that did nothing, I had restored my
image already to see if a manual install would work, but it also failed to
correct WD, it still gave me the same error code 0x805800c

I may end up re installing my image backup again, and just disable any
updates to this WD until or unless I and others get an answer on this.

I would even remove this program, but when I tried it said it was part of
the OS. I even downloaded the installer from MS, but it wouldn't install,
said it was already installed.

So I tried all I could, now need an answer from some one who may know.

BTW: I know what folder WD is in, where are these def located?
 
I now have a before-after comparison in regshot. There seems to be a few
changes in the software distribution folder, among others. I'm not sure what
it all means, not being an expert user, but I think it might be significant.
Would that regshot comparison be helpful to anyone? If so, can I copy and
paste it here, or is that something I shouldn't do? I'm not sure on the
correct protocol in newsgroup posting. Also, there seems to be a new
definition file now- it's 1.75.94.0. I've currently got it installed with
same results. I've also found another current post with similar
problems...http://social.answers.microsoft.com...y/thread/196a1746-de4b-44f3-bc8e-f933bb12feac
 
I have been tracking this issue with at least 12 of my end user PC's to date.
we have tried all the methods mentioned here as well as reverting back to
known good. none worked. at one point we did get one to seemingly get
repaired by replacing all the reg keys and file locations with ones from a
known good and running system but as soon at it took the next def update it
broke again.

Definitions are in the All Users directory "C:\Documents and Settings\All
Users\Application Data\Microsoft\Windows Defender\Definition Updates"

There doesn't seem to be a rhyme or reason to why some of our PC's are now
displaying this issue while others that are from the same image and got the
same updates are not.
 
randolindso said:
I downloaded and installed KB915597 and now Windows Defender won't scan.
I've been researching it and have found there have been like problems in the
past few years. I've tried the recommended fixes: uninstall/reinstall
Defender and run chk dsk, but to no avail. System restore will take me back
to the point where the Defender scan worked, but as soon as I reinstall the
update it's the same problem again. Am I the first to have this old problem
with this new KB update? Any ideas would be appreciated. FYI...
Click to expand...


Hi randolinso;
I have just got Defender to run!!!
I enabled my Yahoo toolbar and ran Yahoo anti-spy after it updated itself.
The anti-spy found 41 objects which I then deleted an tried Defender, and it
now works! However, my security essentials doesn't yet but will try re-start
and then try it. Hope this helps you, Cheers. Mike.
 
MickeyWickets said:
Hi randolindso;
I have just got Defender to run!!!
I enabled my Yahoo toolbar and ran Yahoo anti-spy after it updated itself.
The anti-spy found 41 objects which I then deleted an tried Defender, and it
now works! However, my security essentials doesn't yet but will try re-start
and then try it. Hope this helps you, Cheers. Mike.
Click to expand...

Update - Security essentials scan is now working after Defender scan
finished OK with the latest definitions!
 
well first off its "XP" your talkin bout, and 2nd MS Essential Security,

I and others are talkin bout Windows Defender., and Vista.

I did a search for that key in Vista and came up blank.

Other than that, for some reason at times I can seem to get the thing to
scan but on a restart or cold start, its back to the same error.

I already did the MS thing and have my email back, but as usual its more
involved as it needs to be. I have the ability to follow it but don't see
why, the average user shouldn't need to monkey around with this stuff, its
NOT their computer thats messed up, its NOT the program in question, it the
new UPDATE of the definitions, which is a MS problem.

I'm not gona hack into the update and mess with the code, its not my job.

This is something MS needs tol follow up on and "FIX" their damned updates
for "Windows Defender" not MSES.
 
Wow! Thanks for all the replies. I read a post somewhere in a forum about
an xp user with the same problem and he said that, after Defender ran an
automated scan, the on-demand scanner worked ok without the error. I tried
it and it did work. Have no idea why. This is obviously not a fix, but if
it works, and more importantly, keeps working after the next kb update, I
guess you'd call it a workaround until Microsoft fixes it. Thanks for all
the response.
 
This issue cropped up for Microsoft Security Essentials users late
last week. The common factor was that the engine for MSMPENG (which is
used by MSE, ForeFront,, OneCare, and Defender) was updated along with
definitions. It only affected XP users and not everyone. An updated
engine was released early this week and this resolved it for many MSE
users, but not all.

Earlier today I was provided with a workaround by Microsoft for MSE
and it may well solve it for Defender, too. I posted it to the MSE
forums as a sticky here:
http://social.answers.microsoft.com/Forums/en-US/msescan/thread/a5810b32-5470-46aa-8be4-634f06064131

Here is the text of the post:

he majority of reported cases of the subject error were resolved with
the engine and definitions update released earlier this week, but
there have been some reports that this did not fix the problem for all
users of MSE on XP that are experiencing the error when trying to
perform a scan.

I just got word that a confirmed verified workaround for this issue
has been found if you are still encountering the error when trying to
perform a scan and you've confirmed that you have the latest engine
and definition updates.

As of 1/29/10, the engine should be: 1.1.5406.0

You can see the engine version by opening MSE and clicking the
downward triangle next to Help and selecting About Microsoft Security
Essentials.

The workaround is to edit the registry.
If you are not comfortable editing the Registry, please open a Support
case.
Note that editing the Registry incorrectly can cause your system to
become unusable.

In XP, go to Start/Run and type REGEDIT - then press Enter.
Navigate to

HKLM\software\microsoft\windows nt\current version\profilelist

You will see several branches.
Looking at an XP machine here, I see a bunch and they all begin with
"S-1-5-" and some have just 2 more digits, while some have a long
string of digits after that.
Open each key branch and you'll see several values within on the right
hand Regedit pane.
Look for a value called:

profileimagepath

If there is a value within the "S-1-5-..." branch, move on to the next
entry.
In any branch, if there is no value called "profileimagepath" then
add one.
Right click in the right hand pane blank space and select "New" and
then "Mult-string Value"
A new item will appear with the name "New Value #1", and it will be
highlighted. Overtype "New Value #1" so that it now reads
"profileimagepath"
Close Regedit.
Repeat the check and add the value for any other keys in the
"profilelist" branch so that all keys include at least a blank key
with the name "profileimagepath"

Close Regedit when done.

Reboot after closing Regedit.

Run a scan.

-steve
 
I've now read a few more responses in this newsgroup for the error and
see that it is not limited to XP users.

I checked my Vista and Windows 7 machines and they all have a key
named "profileimagepath" in each branch of the registry path noted
below.
So, in my opinion, it may be worth adding the new blank value to the
key branches if they do not exist on a Vista or Windows 7 machine
experiencing this issue.
You may want to back up the registry before making changes.
This article explains how to do this:
http://www.registrycleanergeeks.com/vista/registry-backup/

-steve
 
OK well for the time being I decided to elevate myself of this irritation
with this WD program I decided to just “turn it off†for the time being. You
can do this by opening Defender, and go to Options, than just scroll down to
the bottom of that setting page and un-check the two items related to using
defender.

I found the program called IObit360 will actually take the place of
Defender, and its function and integrate itself to the OS, so it doesn’t give
you that red shield telling you your system isn’t protected, or its not on.

I have gone through ALL the usual crap, including the “suggestions†from MS
via e-mail help. There’s no change, with this program or the error
(0x805800c). I sent MS help my opinion on it and the info they asked for.

I did get it to actually scan a few times, but as soon as you do a reboot
the problem is back when you try to do a scan again. This may be the same
deal with you if you check.

So for now I will do without this one anti-spyware program and use this
IObit360, along with a couple of others I use.

When I see people saying that its been “fixed†I’ll retry the thing.
 
Well guess what? I rebooted and tried the scan, per your suggestion, and the
error is back. Frustrating, isn't it? I don't know what else to do. I'll
just wait it out, I suppose, and see if M'soft comes up with a fix. I might
try to send them my opinion too- maybe if enough people do that it will catch
their eye. Is there a link or something to contact them about this. The
last time I dealt with them was on an update issue that dealt with registry
permissions in limited user accounts and their suggestion was to change the
limited accounts to admin...kinda left me with a pretty low opinion of that
particular support person.
 
Back
Top