Windows Server 2012 Automatic Repair Loop

dtssupport
dtssupport used Ask the Experts™
on
We have two customers with Windows Server 2012 physical servers which had the exact same issue this morning. We use a remote monitoring and management product called GFI Max to manage these servers. Yesterday, we set the GFI Max agent to reboot the servers overnight. This morning both servers were stuck in an automatic repair loop. No matter what startup options we selected, it would just go straight to the light blue screen with the options Continue, Troubleshoot, and Turn Off Your PC. After trying every possible startup modification we could think of, finally the server booted up successfully after selecting "Disable Early Launch Anti-Malware Driver" from the Advanced Startup Menu.

Our issue is this:

Now every time we reboot the server, it goes to automatic repair and we have to choose "Troubleshoot" from the light blue screen, and select "Disable Early Launch Anti-Malware Driver" from the Advanced Startup Menu. What can we do to fix this?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Adam BrownSenior Systems Admin
Top Expert 2010

Commented:
I haven't worked with GFI Max before, but I've done a lot with systems like it in the past. Usually those Managed Services platforms will install a bunch of software on managed servers, and sometimes that software isn't fully compatible with the OS. Sounds like the pre-boot anti-malware stuff doesn't mesh with 2012 yet. You should be able to uninstall the Early Launch Anti-Malware software either directly on the servers or from the Max management console. That should fix the problem until 2012 is more supported by that feature.

Author

Commented:
As far as I've read, Early Launch Anti-Malware (ELAM) is a built-in feature of Windows Server 2012. Also, the Managed Anti-Virus from GFI Max (which is Vipre Anti-Virus) is installed on one of the servers, but not installed on the other server.
Issue was resolved but using the Symantec Clean Wipe tool and removing any let over remnants of the Symantec Endpoint Client that did not uninstall from the Server.

Author

Commented:
Resolved the issue on my own through various troubleshooting processes.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial