Solved

Windows Server 2012 Automatic Repair Loop

Posted on 2014-02-25
4
3,686 Views
Last Modified: 2014-05-28
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?
0
Comment
Question by:dtssupport
  • 3
4 Comments
 
LVL 38

Expert Comment

by:Adam Brown
Comment Utility
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.
0
 

Author Comment

by:dtssupport
Comment Utility
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.
0
 

Accepted Solution

by:
dtssupport earned 0 total points
Comment Utility
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.
0
 

Author Closing Comment

by:dtssupport
Comment Utility
Resolved the issue on my own through various troubleshooting processes.
0

Featured Post

6 Surprising Benefits of Threat Intelligence

All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

Join & Write a Comment

In my previous 24 VMware Articles (http://www.experts-exchange.com/ARTH_1864316.html?arthOrderBy=3&arthSort=1#arth), most featured Intermediate VMware Topics. My next series of articles concentrated on topics for the VMware Novice;   If you would…
The reason that corporations and businesses use Windows servers is because it supports custom modifications to adapt to the business and what it needs. Most individual users won’t need such powerful options. Here I’ll explain how you can enable Wind…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
In this Micro Tutorial viewers will learn how to use Windows Server Backup to create full image of their system. Tutorial shows how to install Windows Server Backup Feature on Windows 2012R2 and how to configure scheduled Bare Metal Recovery backup.…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now