MSE v1.0.1959 out.

Well, I'm using latest MSE build and I'm not really experiencing an issue with Windows Updates being set off by MSE every time definitions come out.
It updates itself every day here.
Using Windows 7 Ultimate x64.

 

I'm not seeing it on every system either. I have two similar systems running the same version with the same settings, and it only does it on 1.

 

Not here. MSE doesn't depend upon the Windows Update setting anymore. This occured only with the MSE beta and Win 7 RC. MSE only uses the BITS and WU services to download it's updates.

 

Exactly.
The only time I noticed Windows Update prompting me for anything regarding MSE, it was to update the program in question, but that's it.

 

Another unhappy group of users on a Mircosoft Forum having the same problem as me:

http://social.answers.microsoft.com/Forums/en-US/mseupdate/thread/2ca1e4ac-8add-4134-9675-66ac49a186fe

 

after way to many issues myself over time and with my customers systems i NO longer recc mse to any of them.

 

What issues were you having Z?

 

no issues here.

HOWEVER...MSE was not able to detect or remove the malware XP Internet Security 2010...a pretty rough hombre as far as viruses/malware are concerned. I had to shoe-horn PC Doctor 2010 on the machine (would have used malwarebytes, but the malware was blocking it) to get rid of it.

Big hole when widespread malware goes completely undetected. but MSE + PC Doctor/Malwarebytes seems like a good combination.

 

Actually, like all malware, this one is pretty harmless if you run your computer in a reasonable configuration (meaning that, of course, you are logged in as a Standard User, not as an Admin and, of course, you have UAC turned on). Simply delete the Trojan it deposits in your AppData folder, delete the bogus filetype associations for executables, and Bob's your uncle. Of course, if you are one of those people who run as Admins with UAC turned off, you deserve whatever hits you.

I have the same issue on our home machine. The previous version downloaded updates automatically itself, but the new one goes through a Windows Update prompt. Not a huge deal, but quite annoying.

 

misc ones. stability on one system, another system crashed, etc .... i just got tired of dealing with it. i use nis2010 and avast internet security 5 and i have no issues with either one of them

 

Same here too ever since upgrading to the new version. However, I noticed that if you wait for MSE to update the definitions itself, the Window Update prompt will go away quietly.

 

I've noticed this as well. When I go into Updates Installed there's several entries for MSE Definitions.

I wonder if this is how MS wanted it or if it is a "bug" after all?

 

This is not a bug. MSE's definition updates showed up in installed updates from day 1, because MSE uses Windows Update services.

 

No... going through the "Previously Installed Updates" the MSE definitions don't start showing up until the day after I installed the newest version.

 

I don't know what you mean by previously installed updates, but when I open Windows Update > View update history, MSE's definition updates showed up ever since I had started using the MSE beta, final with Windows 7 RC, RTM, etc.

 

I've never had a MSE definition update appear in WU until the latest version. I've been running it on multiple systems for over 6 months.

 

Open WU > View update history. Each MSE definition update will be listed. This is not the same as you are talking about.

 

That's what I meant. Previously Installed Updates = Update History.

Not a SINGLE MSE entry until I updated to the latest version.

Why would I make that up?

 

I am seeing the MSE entries in 3 different machines with Vista and Win 7, all 64-bit.

 

Yeah, I see entries on my Mother-In-Law's desktop which has Vista 32bit, but they don't start appearing until the day of the new version of MSE was installed over the old version.

When I get home this weekend I will take a screen to show you I'm not making it up, because again, why would I?

 

I was not saying that you were making it up, but tried to tell you that was not really a bug.