R
randolindso
I just did this and it works, even after reboot, etc. My hat's off to you,
Lori Ann
Lori Ann
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
T
TopGun
Thank you so much for the tip.
Worked like a charm.
Just installed Yahoo Toolbar and ran it.
But I wonder if it works because of some malware that it removes or
something else
I had only 7 tracker cockies, all of them "legal" I mean from places I visit
from time to time.
When I started Defender after the Yahoo scan, it didn´t say "you have not
done a search for x days ect......" It´s seems like Defender thougth that it
had done a search
when actually Yahoo had done the search.
Anyway it worked
Worked like a charm.
Just installed Yahoo Toolbar and ran it.
But I wonder if it works because of some malware that it removes or
something else
I had only 7 tracker cockies, all of them "legal" I mean from places I visit
from time to time.
When I started Defender after the Yahoo scan, it didn´t say "you have not
done a search for x days ect......" It´s seems like Defender thougth that it
had done a search
when actually Yahoo had done the search.
Anyway it worked
T
Trifon
I got the same issue as well. I found out today when I logged in. Last
upadate and scan occured on the 28/01/2010. Yesterday I did not switched on
my pc.
Today when I looged in, Windows Defender produced this error code and
stated, that the last scan took place on the 26/01/2010, which is not true.
The internet is full of people having the same issue exactly with Windows
Defender and MS Essentilas. At the MS Answers site, they provide some
solution for the MS Essentials, but nothing is on for WinDef.
I believe that this clearly a Microsoft issue, and has nothing to do with
ous pcs or viruses or settings, etc.
Somone has to inform the MS Protection Center guys to fix it ASAP. I would
recomend for all of us to stay put and wait. Do not change anything on your
ps's settings.
Thanks alot.
Trif.
Athens.
upadate and scan occured on the 28/01/2010. Yesterday I did not switched on
my pc.
Today when I looged in, Windows Defender produced this error code and
stated, that the last scan took place on the 26/01/2010, which is not true.
The internet is full of people having the same issue exactly with Windows
Defender and MS Essentilas. At the MS Answers site, they provide some
solution for the MS Essentials, but nothing is on for WinDef.
I believe that this clearly a Microsoft issue, and has nothing to do with
ous pcs or viruses or settings, etc.
Somone has to inform the MS Protection Center guys to fix it ASAP. I would
recomend for all of us to stay put and wait. Do not change anything on your
ps's settings.
Thanks alot.
Trif.
Athens.
T
Trifon
Well WinDef is running now, a quick scan. With no new updates, or any
additional settings adjustments.
I just thought I'd let you know.
All the best.
Trif.
additional settings adjustments.
I just thought I'd let you know.
All the best.
Trif.
M
MickeyWickets
There's a get-around on the MSE forum and both my Defender and Sec.Trifon said:Well WinDef is running now, a quick scan. With no new updates, or any
additional settings adjustments.
I just thought I'd let you know.
All the best.
Trif.
Essentials are now working;-
The 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.
Start MSE and try a scan.
If you are not comfortable with the above steps, please open a support case
for help.
To open a support case, start here:
https://support.microsoftsecurityessentials.com/
-steve
D
dillulive
Thanks to loriAnn, randolindso & Steve (Stephen Boots).
Actually, the problem was solved by doing same that mentioned in
http://social.answers.microsoft.com/Forums/en-US/msescan/thread/a5810b32-5470-46aa-8be4-634f06064131
Mine was problem with defender of vista. Though, in the above it was given
for MSE, I tried the same after refering the post of randolindso. It
successfully worked.
Yet, I don't know the reason, why the problem solved now, whilst earlier,
defender was running smoothly without things which were done now. Any how
problem was solved, and working smoothly even after restarting/rebooting.
Actually, the problem was solved by doing same that mentioned in
http://social.answers.microsoft.com/Forums/en-US/msescan/thread/a5810b32-5470-46aa-8be4-634f06064131
Mine was problem with defender of vista. Though, in the above it was given
for MSE, I tried the same after refering the post of randolindso. It
successfully worked.
Yet, I don't know the reason, why the problem solved now, whilst earlier,
defender was running smoothly without things which were done now. Any how
problem was solved, and working smoothly even after restarting/rebooting.
H
Hoody
man u gota be kiddin me, this has been posted several times now. it doesn't
work.......,
I got this same stuff from MS , tried it, and still the error comes back
after a reboot.
I already said this thing can just be closed down for a while till there is
an "actual" fix. and that this IObit360 thing integrates into the OS and
replaces WD with no problem.
work.......,
I got this same stuff from MS , tried it, and still the error comes back
after a reboot.
I already said this thing can just be closed down for a while till there is
an "actual" fix. and that this IObit360 thing integrates into the OS and
replaces WD with no problem.
R
Richard M
Thanks for the post - running CHKDSK sorted me out.
T
Trifon
The same thing keeps happening. Last week , it happened again a couple of
times and it corrected it self.
Today, the same thing again. WInDef won't run, giving the same error code.
I think that the Microsoft guys are very good in taking our money, and when
troubleshooting is involved they sleep all day long.
In that case they sleep, the whole week. Please somebody wake them up please.
FIX WINDOWS DEFENDER!!
times and it corrected it self.
Today, the same thing again. WInDef won't run, giving the same error code.
I think that the Microsoft guys are very good in taking our money, and when
troubleshooting is involved they sleep all day long.
In that case they sleep, the whole week. Please somebody wake them up please.
FIX WINDOWS DEFENDER!!
H
Hoody
Well homes I know this can be a real PITA when this keeps goin, anyway I got
mine to run again even after reboot.
I did "both" these and ran a manual windows update, seems MS has now started
sending out the smaller updates again instead of this 12mg thing. Try both
these things.
the first is from MS I got in one of their emails, where you create a small
..reg file and runit by opening it with registry, the other I did was that
"profilelist" thing, by editing the reg. Funny thing though is I can't seem
to find that key now in my reg at all (vista) under /windows NT/current
version. But you can do a find and see if you have it, than do the reg thing.
==============================================
The problem lies in corrupted registry settings for the program. If you have
a similar problem to mine (Defender in Vista seemingly installed, but getting
a "can't initialize" error), try the following (originally posted here by
cdninja)
Step 1: Back up Registry ==================
1. Click Start, type "regedit" (without quotation marks) in the search bar
and press Enter.
2. In the Registry Editor, click File menu, and click Export.
3. In the Save In list, select the folder where you want to save the backup.
4. In the File Name box, and type a name for your backup file, such as
"Options" or "Backup".
5. Click Save.
Step 2: Create and Run the Registry File ==================
1. Click Start, type "notepad C:\register.reg" (without quotation marks) in
the Search bar, and then click OK. Choose Yes when you are prompted to create
a new file.
2. Copy the following texts between the star marks and then paste them into
the opened Notepad window:
************************BEGIN**************************
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend]
"DisplayName"="@%ProgramFiles%\\Windows Defender\\MsMpRes.dll,-103"
"ErrorControl"=dword:00000001
"Group"="COM Infrastructure"
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
6b,00,20,00,73,00,65,00,63,00,73,00,76,00,63,00,73,00,00,00
"Start"=dword:00000002
"Type"=dword:00000020
"Description"="@%ProgramFiles%\\Windows Defender\\MsMpRes.dll,-3068"
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00
"ObjectName"="LocalSystem"
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,\
00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\
65,00,00,00,53,00,65,00,42,00,61,00,63,00,6b,00,75,00,70,00,50,00,72,00,69,\
00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,73,00,\
74,00,6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,\
00,00,00,53,00,65,00,44,00,65,00,62,00,75,00,67,00,50,00,72,00,69,00,76,00,\
69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,68,00,61,00,6e,00,67,\
00,65,00,4e,00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,00,76,00,69,00,\
6c,00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,69,\
00,74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,\
00,00
"FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Parameters]
"ServiceDllUnloadOnStop"=dword:00000001
"ServiceDll"=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,\
00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,\
20,00,44,00,65,00,66,00,65,00,6e,00,64,00,65,00,72,00,5c,00,6d,00,70,00,73,\
00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Security]
"Security"=hex:01,00,14,80,04,01,00,00,10,01,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,d4,00,07,00,00,00,00,00,28,00,ff,01,0f,00,01,06,00,00,00,00,00,\
05,50,00,00,00,b5,89,fb,38,19,84,c2,cb,5c,6c,23,6d,57,00,77,6e,c0,02,64,87,\
00,0b,28,00,00,00,00,10,01,06,00,00,00,00,00,05,50,00,00,00,b5,89,fb,38,19,\
84,c2,cb,5c,6c,23,6d,57,00,77,6e,c0,02,64,87,00,00,14,00,fd,01,02,00,01,01,\
00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,\
05,20,00,00,00,20,02,00,00,00,00,14,00,9d,01,02,00,01,01,00,00,00,00,00,05,\
04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,\
00,28,00,15,00,00,00,01,06,00,00,00,00,00,05,50,00,00,00,49,59,9d,77,91,56,\
e5,55,dc,f4,e2,0e,a7,8b,eb,ca,7b,42,13,56,01,01,00,00,00,00,00,05,12,00,00,\
00,01,01,00,00,00,00,00,05,12,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Enum]
"0"="Root\\LEGACY_WINDEFEND\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
*************************END***************************
3. After you paste the above commands, please close the Notepad window.
Choose Yes when you are prompted to save the file.
4. Save the file as a REG file of any type (defenderfix.reg was what I
called the file, but any name will do, just make sure the file is a REG file,
and not a TXT file)
5. next double click on the new file.
6. When you receive a message box asking "Are you sure you want to add the
information in the REG file to the registry", choose "Yes"
7. You will receive another message box saying "Information in the REG file
has been successfully entered into the registry", please click "OK" to
confirm.
8. Restart the computer.
Its as far as I can see the end user can go with this
So far like I said mine seems to be working again.
mine to run again even after reboot.
I did "both" these and ran a manual windows update, seems MS has now started
sending out the smaller updates again instead of this 12mg thing. Try both
these things.
the first is from MS I got in one of their emails, where you create a small
..reg file and runit by opening it with registry, the other I did was that
"profilelist" thing, by editing the reg. Funny thing though is I can't seem
to find that key now in my reg at all (vista) under /windows NT/current
version. But you can do a find and see if you have it, than do the reg thing.
==============================================
The problem lies in corrupted registry settings for the program. If you have
a similar problem to mine (Defender in Vista seemingly installed, but getting
a "can't initialize" error), try the following (originally posted here by
cdninja)
Step 1: Back up Registry ==================
1. Click Start, type "regedit" (without quotation marks) in the search bar
and press Enter.
2. In the Registry Editor, click File menu, and click Export.
3. In the Save In list, select the folder where you want to save the backup.
4. In the File Name box, and type a name for your backup file, such as
"Options" or "Backup".
5. Click Save.
Step 2: Create and Run the Registry File ==================
1. Click Start, type "notepad C:\register.reg" (without quotation marks) in
the Search bar, and then click OK. Choose Yes when you are prompted to create
a new file.
2. Copy the following texts between the star marks and then paste them into
the opened Notepad window:
************************BEGIN**************************
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend]
"DisplayName"="@%ProgramFiles%\\Windows Defender\\MsMpRes.dll,-103"
"ErrorControl"=dword:00000001
"Group"="COM Infrastructure"
"ImagePath"=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,\
74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,73,\
00,76,00,63,00,68,00,6f,00,73,00,74,00,2e,00,65,00,78,00,65,00,20,00,2d,00,\
6b,00,20,00,73,00,65,00,63,00,73,00,76,00,63,00,73,00,00,00
"Start"=dword:00000002
"Type"=dword:00000020
"Description"="@%ProgramFiles%\\Windows Defender\\MsMpRes.dll,-3068"
"DependOnService"=hex(7):52,00,70,00,63,00,53,00,73,00,00,00,00,00
"ObjectName"="LocalSystem"
"ServiceSidType"=dword:00000001
"RequiredPrivileges"=hex(7):53,00,65,00,49,00,6d,00,70,00,65,00,72,00,73,00,6f,\
00,6e,00,61,00,74,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,\
65,00,00,00,53,00,65,00,42,00,61,00,63,00,6b,00,75,00,70,00,50,00,72,00,69,\
00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,52,00,65,00,73,00,\
74,00,6f,00,72,00,65,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,\
00,00,00,53,00,65,00,44,00,65,00,62,00,75,00,67,00,50,00,72,00,69,00,76,00,\
69,00,6c,00,65,00,67,00,65,00,00,00,53,00,65,00,43,00,68,00,61,00,6e,00,67,\
00,65,00,4e,00,6f,00,74,00,69,00,66,00,79,00,50,00,72,00,69,00,76,00,69,00,\
6c,00,65,00,67,00,65,00,00,00,53,00,65,00,53,00,65,00,63,00,75,00,72,00,69,\
00,74,00,79,00,50,00,72,00,69,00,76,00,69,00,6c,00,65,00,67,00,65,00,00,00,\
00,00
"FailureActions"=hex:80,51,01,00,00,00,00,00,00,00,00,00,03,00,00,00,14,00,00,\
00,01,00,00,00,60,ea,00,00,01,00,00,00,60,ea,00,00,00,00,00,00,00,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Parameters]
"ServiceDllUnloadOnStop"=dword:00000001
"ServiceDll"=hex(2):25,00,50,00,72,00,6f,00,67,00,72,00,61,00,6d,00,46,00,69,\
00,6c,00,65,00,73,00,25,00,5c,00,57,00,69,00,6e,00,64,00,6f,00,77,00,73,00,\
20,00,44,00,65,00,66,00,65,00,6e,00,64,00,65,00,72,00,5c,00,6d,00,70,00,73,\
00,76,00,63,00,2e,00,64,00,6c,00,6c,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Security]
"Security"=hex:01,00,14,80,04,01,00,00,10,01,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,d4,00,07,00,00,00,00,00,28,00,ff,01,0f,00,01,06,00,00,00,00,00,\
05,50,00,00,00,b5,89,fb,38,19,84,c2,cb,5c,6c,23,6d,57,00,77,6e,c0,02,64,87,\
00,0b,28,00,00,00,00,10,01,06,00,00,00,00,00,05,50,00,00,00,b5,89,fb,38,19,\
84,c2,cb,5c,6c,23,6d,57,00,77,6e,c0,02,64,87,00,00,14,00,fd,01,02,00,01,01,\
00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,\
05,20,00,00,00,20,02,00,00,00,00,14,00,9d,01,02,00,01,01,00,00,00,00,00,05,\
04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,\
00,28,00,15,00,00,00,01,06,00,00,00,00,00,05,50,00,00,00,49,59,9d,77,91,56,\
e5,55,dc,f4,e2,0e,a7,8b,eb,ca,7b,42,13,56,01,01,00,00,00,00,00,05,12,00,00,\
00,01,01,00,00,00,00,00,05,12,00,00,00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WinDefend\Enum]
"0"="Root\\LEGACY_WINDEFEND\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001
*************************END***************************
3. After you paste the above commands, please close the Notepad window.
Choose Yes when you are prompted to save the file.
4. Save the file as a REG file of any type (defenderfix.reg was what I
called the file, but any name will do, just make sure the file is a REG file,
and not a TXT file)
5. next double click on the new file.
6. When you receive a message box asking "Are you sure you want to add the
information in the REG file to the registry", choose "Yes"
7. You will receive another message box saying "Information in the REG file
has been successfully entered into the registry", please click "OK" to
confirm.
8. Restart the computer.
==============================================Trifon said:The same thing keeps happening. Last week , it happened again a couple of
times and it corrected it self.
Today, the same thing again. WInDef won't run, giving the same error code.
I think that the Microsoft guys are very good in taking our money, and when
troubleshooting is involved they sleep all day long.
In that case they sleep, the whole week. Please somebody wake them up please.
FIX WINDOWS DEFENDER!!
Its as far as I can see the end user can go with this
So far like I said mine seems to be working again.
T
Trifon
Well Hoody,
Thanks for the suggested solution man. It's bit too much for me. By the
way what about the second solution. You didn't mention it. The one with the
"ProfileImage" key.
I think that could work. By the way I also started having issues with the
System Restore in Vista. Check out my other (new) thread. I think that
WinDef and SR problems are related.
Thanks.
Trif.
Thanks for the suggested solution man. It's bit too much for me. By the
way what about the second solution. You didn't mention it. The one with the
"ProfileImage" key.
I think that could work. By the way I also started having issues with the
System Restore in Vista. Check out my other (new) thread. I think that
WinDef and SR problems are related.
Thanks.
Trif.
H
Hoody
OK here's the 2nd deal I was talkin about, that profile thing, I lifted this
from the site and reposted it here. It talks about XP and MSE, but there's an
update at the bottom that mentions defender and vista.
This can be a real PINT for a lot of people who don't know what this is all
about as it is, never mind those that can't even find this stuff on the web.
===============================================
You need to open the regedit program, click on edit, and click on find, than
a box will popup, there you can type in profilelist, or try profileimagepath
and see what comes up.
I found it one time but now for some reason can't (vista) but no matter like
I said mine seems to be workin now.
================================================
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.
Start MSE and try a scan.
If you are not comfortable with the above steps, please open a support case
for help.
To open a support case, start here:
https://support.microsoftsecurityessentials.com/
-steve
UPDATE 2/1/10:
Over the weekend I noticed that this issue has also been reported for
Windows Defender and that the error is not apparently limited to XP users.
I don't know if it also affects ForeFront. I have not seen any reports by
OneCare users. The common factor is that the core antimalware engine is used
by all of these products. In the case of MSE, the engine was updated around
January 21st and the first reports of this error appeared. A new engine was
released at the beginning of last week and this resolved it for most users.
The registry fix above was provided to me by Microsoft and seems to work for
all MSE users with the problem. As far as I know, in MSE it has only been
reported by XP users.
In the Defender newsgroups, apparently people discovered this post and tried
it on XP, Vista, and Windows 7 PCs not running MSE, but running Defender and
reported that it worked.
I checked the Registry on a few Vista and Windows 7 machines and all of my
profilelist branches include the referenced "profileimagepath" entry,
pointing to an actual path in the value for the entry. However, the actual
path doesn't seem to be an issue - just the existence of that key. So, if you
are here because you found this via a search or were linked from another
location, give the above steps a try if you are encountering the error with
XP, Vista, or Windows 7 for any of the above products that use the same
antimalware engine and definitions.
I assume that the Microsoft Antimalware team is working to develop another
update to mitigate the issue, but until then the above solution appears to
work well.
from the site and reposted it here. It talks about XP and MSE, but there's an
update at the bottom that mentions defender and vista.
This can be a real PINT for a lot of people who don't know what this is all
about as it is, never mind those that can't even find this stuff on the web.
===============================================
You need to open the regedit program, click on edit, and click on find, than
a box will popup, there you can type in profilelist, or try profileimagepath
and see what comes up.
I found it one time but now for some reason can't (vista) but no matter like
I said mine seems to be workin now.
================================================
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.
Start MSE and try a scan.
If you are not comfortable with the above steps, please open a support case
for help.
To open a support case, start here:
https://support.microsoftsecurityessentials.com/
-steve
UPDATE 2/1/10:
Over the weekend I noticed that this issue has also been reported for
Windows Defender and that the error is not apparently limited to XP users.
I don't know if it also affects ForeFront. I have not seen any reports by
OneCare users. The common factor is that the core antimalware engine is used
by all of these products. In the case of MSE, the engine was updated around
January 21st and the first reports of this error appeared. A new engine was
released at the beginning of last week and this resolved it for most users.
The registry fix above was provided to me by Microsoft and seems to work for
all MSE users with the problem. As far as I know, in MSE it has only been
reported by XP users.
In the Defender newsgroups, apparently people discovered this post and tried
it on XP, Vista, and Windows 7 PCs not running MSE, but running Defender and
reported that it worked.
I checked the Registry on a few Vista and Windows 7 machines and all of my
profilelist branches include the referenced "profileimagepath" entry,
pointing to an actual path in the value for the entry. However, the actual
path doesn't seem to be an issue - just the existence of that key. So, if you
are here because you found this via a search or were linked from another
location, give the above steps a try if you are encountering the error with
XP, Vista, or Windows 7 for any of the above products that use the same
antimalware engine and definitions.
I assume that the Microsoft Antimalware team is working to develop another
update to mitigate the issue, but until then the above solution appears to
work well.