Mine does not take 3 minutes to turn on, it's usually less than 1 minute. It may be slowed because of other apps starting??? I do not recall your system specs. I would think that less than ideal system specs combined with other apps starting may be a part of the slow start. Just guessing here Dick as I do not seem to have nearly as slow start with MSE as you are experiencing.

Glad you found the problem. Since Winpatrol is another anti-malware app, it may be conflicting with MSE. The old adage is to not use 2 security apps in real time, either 2 AV or 2 AM apps. I keep other anti-malware apps available for manual scanning, but only run one in real time, and at present that is MSE. (For those of you wondering, I restored to an Image with MSE, nixing the Avast AV/AM for now. Not having the BSOD so my feeling is something else caused them, not MSE)

I haven't used Winpatrol in a long time but I expect it uses a service. Assuming you're using Windows 7 or Vista, type Services.msc. Scroll down until you find the WinPatrol service and double click on it. In the Startup Type dropdown list, select automatic (delayed start). This will start WinPatrol shortly after boot. I wasn't able to find Microsoft's definition of shortly.

Hi Jerry:
Unless my tired. old eyes missed it, I don't see any service that WinPatrol uses on my W7 system.
What I did do, though, is to uncheck the WinPatrol option for having it auto-start.
I then pinned its execuatable to my taskbar; and once my system is booted up, and MSSE is green, I manually start
WinPatrol.
Ted,
I have no connection to WinPatrol, but I see it as much, much more than just another anti-malware app.

Zig:
It does have that feature, but I was not using it.
Not having WinPatrol auto-start, and then starting it from the task bar when MSSE comes up "green"
has done the trick for me.
Thanks for the response.
Ted:
I hope I didn't come across as "bitchy".
I didn't want someone who reads this thread later, and doesn't know much about WinPatrol, to think of it as "only" an
anti-malware app.

No, you did not sound that way at all. I did not know much about Winpatrol before and did not explain myself well in my post. It did seem obvious to me after you reported that holding off on Winpatrol until after MSE started fixed your problem. It does appear that Winpatrol was competing with MSE for resources during startup, and we do know how important it is to get our AV apps started ASAP. As long as you can manually start Winpatrol after MSE is running, you should not have a problem. I do not have a lot of experience with delay starting apps. Perhaps I will play with this a little and see what happens. Of course, I will create an Image before "play time"

The Following User Says Thank You to Medico For This Useful Post:

I have my MSE installation taskbar icon come up red, but only on occasion, it quickly turns to green again thereafter.
My boot drive is the Revo PCIe SSD. Unsure if the Revo is even related to this anomaly.

Event viewer shows it to be related to...

Event Veiwer:

Side by Side
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Kernel-EventTracing/Admin
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D