Windows Server failure
Windows server is a group of operating systems released by Microsoft. It is corresponding to the home operating system. Since Windows server is designed to undertake more professional tasks, much worse error will appear when it goes wrong. For example, computer users might encounter such issues as system not booting, blue screen after system startup, unable to open any files after entering the desktop, unable to update the system, etc.
Generally speaking, all the problems are related to corrupted system file, damaged boot record and more, all of which could be caused by users’ mistaken operations and file incompatibility. So, here comes the question: what should we do when meeting such issues in Windows server 2012 R2/2008 R2/ 2016?
How to fix Windows Server 2012 R2/2008 R2/ 2016?
If your Windows Server is experiencing blue-screen or other crashes, or some other Windows features cannot work well, there are two windows server repair tools that might be able to help. And here we will focus on how to repair Server 2012 via the two different utilities.
#1: Common tool: SFC scannow
Before trying the SFC scannow server 2012 r2, we need to get a clear understanding of this tool. The SFC is “System File Detection” program, used under a command prompt. Besides, only the one with administrator rights can open and run this program. It is able to scan your Windows system files for corruption or any other changes. If a protected file has been detected to be covered by a wrong file, the SFC will automatically extract the correct file from the system backup to replace the incorrect version. Here is how to use it.
1) Put the Windows Server 2012 R2 installation disk into the CD drive, and then start the computer.
2) When the message “press any key to start from CD or DVD” shows up, press a key and Windows Setup screen will pop out.
3) Select language to install, time and currency format, keyboard or input methods, and click “Next”.
4) Hit “Repair your computer”.
5) Click the operating system you want to repair and click “Next”.
6) In the System Recovery Options dialog box, click “Command prompt”.
7) Type “SFC/scannow” in the command window and press Enter.
Then, the system will automatically scan the integrity of all protected system files and repair the incorrect one by itself. It will take about 5 minutes, so please be patient.
In addition to using the SFC command, you can also check and fix the system boot record, which can also be done in the command prompt window. You just need to input the following commands in turn and press enter after each:
bootrec / fixmbr
bootrec / fixboot
bootrec / rebuildbcd
After the scanning and repair process is finished, you can restart your computer and enter the desktop successfully.
#2: More convenient & professional solution: AOMEI Partition Assistant
If the SFC scannow does not repair Windows Server 2012 R2, you can try AOMEI Partition Assistant Server, a professional partition manager. It is compatible with Windows Server 2003, 2008 (R2), 2012 (R2), and 2016.
Back to the point, this tool could help you repair Windows Server 2012 R2 with most ease, so you can get rid of a hassle of entering the command prompt window and manually typing various commands.
Attention: since the system cannot boot normally, you need to create a bootable PE disk first via AOMEI Partition Assistant first.
To fix the Windows Server 2012 R2, do as following:
Step 1: Connect an empty USB drive (larger than 8GB) to a working computer, install and launch AOMEI Partition Assistant Server. Click Make Bootable Media in the left side and follow the wizard to create a bootable USB stick.
Step 2: Insert your bootable USB to your Windows Server 2012 which you need to fix, restart it and enter in BIOS to make the bootable USB as the first boot device, so your Server can boot successfully from it.
Step 3: Once logged in, you’ll see AOMEI Partition Assistant Server started automatically. Find the system disk partition, right click it and select Advanced-> Check Partition.
Step 4: Select the first way to check and fix the partition error, and click OK.
Step 5: Wait for a few seconds and minutes to complete the partition checking and fixing.
After this process, you can click the Partition Recovery Wizard to find the lost partition and recover it easily. Finally, disconnect the bootable media and restart your Server 2012R2.
1) The method above can also apply to fixing other Servers, like 2008 (R2), 2011, and 2016.
2) You can also try to rebuild MBR via AOMEI Partition Assistant, if the booting problem is caused by corrupted MBR.
3) It is highly advised to make windows server 2012 r2 backup to external hard drive after suffering the system boot failure, just in case something goes wrong again in future.
No matter using SFC scannow in Server 2012 R2 or AOMEI Partition Assistant, those two reliable ways are introduced to fix Windows Server 2012. Just choose the most suitable one according to your own situation. And the AOMEI Partition Assistant Server is a very versatile partition/disk management you will never want to miss. Besides solving the system boot failure, it is also able to fix “convert to GPT greyed out windows server 2012” issue even if the disk you want to convert is the system disk.