MSE installs just fine when run in Win7 compatibility mode. Why people would choose XP mode is beyond me, but... Tested eicar.org - it worked! Why would one want to install AV on a pre-beta? WHY NOT?!?!?!?!?
can i install mse 2.0 on Windows 8 Build 7955 - Milestone 2 (original installer) & run without problem?
MSE runs properly on all builds.Just install in compatibility mode for win7(only while installing).After installed,no problem at all.
MSE broken on 7989 I know there's an antivirus thread already but nobody's posted there in over a month so... I installed 7989, activated by phone, installed MSE, and redpilled it. MSE will not start on bootup. it displays a message that the program's service stopped and it is no longer monitoring my system. there's a big red button to start the service, so I clicked it. It used to work, but no longer does. I have to go into computer management and restart it manually. It is set to start automatically in computer management, and is listed as a startup program in msconfig. I even set it to continue trying to start the service if it fails over and over again. I realize it's not a crucial problem and I can fix it manually but it's just a pain to keep starting it. Any ideas?
Why is the service not starting automatically though? makes no sense. I'll have to look into it later. Anyone care to check their event log to see if there's any clues as to why the service won't start?
EventID 7023 The Microsoft Antimalware Service service terminated with the following error: %%-2147024891 answers.microsoft.com/en-us/protect/forum/protect_start/event-id-7023-the-microsoft-antimalware-service/abceffd9-4b39-47d2-94a3-7cc6eaec96f5
Paranoid a bit? MS don't care that they get some extra beta testers, nobody ever got in trouble for that.
I did install in win7 compatibility. I checked the event log, I'm not getting that. And if I was, wouldn't setting the service to continue attempting to start after multiple failures fix it? I have an idea, I'm going to try to set it to a delayed automatic start and see if that fixes it. I'll post what happens.
I won't let you change it to delayed start, already tried. I also tried playing with all the relevant .exe's compatibility settings to no avail.