Jump to content
Posted 04 March 2006 - 06:59 PM
Posted 05 March 2006 - 02:12 PM
Posted 05 March 2006 - 03:50 PM
Can you tell me what Operating System you are running, i.e XP, 2000 etc...
Posted 05 March 2006 - 04:20 PM
Posted 05 March 2006 - 05:28 PM
Hi again and thanks for the infomation.
If you read a number of the topics in the link below you'll see that there aren't many answers - most people are suspecting this bug will be fixed after an update so be sure to look around and find when the next update/patch is released. Perhaps it is a good sign that lots of people have the same problem that you have, and it shows it's not your computer but the program.
Hope that helped somehow
Posted 06 March 2006 - 03:51 AM
Posted 08 March 2006 - 02:41 PM
Posted 11 March 2006 - 04:24 PM
There are two users on the computer and we are using fast switching. I add this information because last evening a Windows Defender scheduled scan was run, and ended successfully in the user's profile from which it was scheduled, but the "program shutdown" notice, which is the subject of this thread, appeared in the 2nd user's profile (who was logged on at the time of the scan). Again, the subject spyware program came up as questionable in the 2nd user's profile, and I allowed it. However, today the subject program is still shown as "not classified" in the Software Explorer, Currently Running Programs category. The spyware program inserts a "run once" loader in the startup menu at log-off, and I am beginning to wonder if this somehow negates its previous status in Defender, and the process of classification starts all over again. If so, this still does not excuse the program shutdown we are experiencing.
Posted 11 March 2006 - 04:56 PM
Posted 21 April 2006 - 01:21 PM
1) Defender continues to question the program which inserts a "run once" value in the registry when you log off, no matter how many times you "allow." This requires you to "allow" it every time you boot up. To eliminate this inconvenience until future updates solves the problem, I have unchecked the "Notify when changes have been detected to software not yet classified."
2) With two users logged on, when scheduled scans are run from one user's profile, the scan is run successfully but the 0x8050800f error appears in the second user's profile. The scan, itself, does not seem to be affected, so maybe it is just shutting off a duplicate run in the second user's profile. We will have to wait for future updates to address this problem.
0 members, 0 guests, 0 anonymous users