Solved

Windows Server 2012 Automatic Repair Loop

Posted on 2014-02-25
4
3,855 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 39

Expert Comment

by:Adam Brown
ID: 39886356
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
ID: 39886413
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
ID: 40086587
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
ID: 40095115
Resolved the issue on my own through various troubleshooting processes.
0

Featured Post

Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
A procedure for exporting installed hotfix details of remote computers using powershell
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…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

777 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