by

Windows Server 2008 R2 Repair

Aug 21, 2019  Repair Windows Server 2008 R2 using Command Prompt In fact, the reasons for Windows Server 2008 R2 not booting can be various and complicated. Virus infection, bad boot sector, corrupted Master Boot Record (MBR), or missing system files etc can be the event that accounts for Windows Server 2008 R2 boot failure. Jul 24, 2019  For Windows 10, Windows 8.1, Windows 8, Windows Server 2012 R2 or Windows Server 2012 To resolve this problem, use the inbox Deployment Image Servicing and Management (DISM) tool. Then, install the Windows update or service pack again.

What situation should you repair Windows Server 2008 R2/2012/2016 R2?

Mar 24, 2017  ' Use Windows Server 2008 R2 installation DVD and booted the server from the DVD When you arrive at the windows with the button Install Now, choose Repair your computer so that you go to the recovery console On the recovery console, check the drive letter where the OS is installed. Restore or repair your server using installation media. Use the installation media from the server manufacturer to restore from a backup. Use the installation media to restore the server to default factory settings. To find out how to do this on your server, see the documentation from the server manufacturer. Windows Update not working on Windows Server 2008 R2. The Windows Update screen comes up and I click on Download Updates. I then get the bar scrolling across the screen and it says Downloading Updates but the counts never increase (0 KB total, 0% complete). I've tried several things found via Google to resolve this but so far nothing has worked. In order to download and install Windows 7 and Windows Server 2008 R2 SP1 you must currently have a Release to Manufacturing (RTM) version of Windows 7 or Windows Server 2008 R2 already installed. If you have previously installed a pre-release version of Windows 7 and Windows Server 2008 R2 SP1 on your machine, you must uninstall that version before installing SP1.

Aug 21, 2019  Stage 3 – Rebuild MBR for Windows Server 2008. You are in the main interface of AOMIE Partition Assistant Server. Right click the disk that needs repairing and choose Rebuild MBR. In the pop-up window, set the type of MBR for the current operating system (here Windows Vista/ 2008 is selected). You’ll return to the main interface.

Before learning how to repair windows server 2008 r2/2012/2016 R2 using command prompt, it is necessary to know in what situation should you repair it.

As we know, when there is some problem occurs to system, you can do some basic repair like startup repair, boot directory repair and windows directory repair. Sometimes, you may also meet hard disk corrupted issue, you can repair hard disk with “Bootrec /rebuildbcd” command.

Sometimes, when the error is too serious to recover from basic repair. For example, you cannot boot because of system failures. You can create a repair disk and choose an advanced way like system restore to repair it. One can easily fix the system error with this disc and get system back to life.

Unlike Windows 7, “Start-up Repair” & “System Restore” options are not available in Windows Server systems. Fortunately, you can still make use of Command Prompt to perform reparation.

You can create a repair disk which contains some system recovery tools. In this way, you are allowed to repair Server using command line even you are not within Windows.

How to repair Windows Server 2008 R2 using command prompt?

In this article, I will introduce two ways to repair Windows Server using command prompt. Repair Windows Server with built-in command prompt and repair Windows Server with AOMEI.exe.

Repair Windows Server with built-in command prompt

Take a first look at how to repair Windows Server 2008 R2 Operating System using the built-in command prompt. The built-in command line has some useful functions. You can run some basic repairs and run system restore with it.

Some examples to run some basic repairs with command prompt

Repair hard disk

Boot to the Windows Server 2008 and choose the repair in the lower left hand corner of the screen. Open a CMD prompt at advanced option.

  • Diskpart

  • List volume

  • Exit

  • D(your windows drive letter)

  • Bootrec /fixmbr

  • Bootrec /fixboot

  • Chkdsk /f /r

  • Y

If the problem is not solved, then you can repeat this MBR repair process again and use “Bootrec /rebuildbcd” command before “Chkdsk /f /r”

Repair boot files

Open CMD as above mentioned. From here you can run sfc and use the offline options.

  • Run sfc /offbootdir for offline repair specify the location of the offline boot directory

  • Run sfc /offwindir for offline repair specify the location of the offline windows directory

If you are still having issues, you could try to run a system restore with command line.

Run system restore with command prompt

As above mentioned, if the error is so serious that basic repair cannot work, you can run Windows Server 2008 R2/2012 R2/2016 system restore with command line. To do this, you need a system image backup first. Take a look at how to repair Windows Server 2008 r2 step by step.

Step 1. Boot the Windows Server with the installation disc if needed. At Windows Setup interface, click Repair your computer. Then choose Command Prompt in the System Recovery Options.

Step 2. At the prompt, type: wbadmin start systemstaterecovery –version:07/09/2017-13:29 –backuptarget:E: This means run system state recovery from system state backup at E drive created at 13:29pm in 07/09/2017.

Tips: You cannot restore system image to another computer with this method.

Repair Windows Server with AOMEI.exe

AOMEI Backupper Server is a reliable backup and restore software. You can either backup and restore the system from graphic users interface or command line. The best part is you can restore system to a dissimilar hardware.

Windows 2012r2 Repair

Besides, it supports both Windows system (Windows 7/8/8.1/10/XP/Visa) and Windows Server system (Windows Server 2003/2008/2008r2/2012/2012R2/2016). That is to say you can also repair Windows 7/8/10 from command prompt with AOMEI.exe. If you want to protect unlimited PCs and servers within your company, you may choose AOMEI Backupper Technician Plus. It offers unlimited billable technical services to clients. It also enables you to copy installation directory for portable version creation.

Repair

Let’s see how to repair windows server 2008 R2/2012 R2/2016 through AOMEI command prompt. Suppose you have already created a system backup. Before running a system restore, you can check if system image backup is intact and without error by using Check Image utilities.

Step 1. If you cannot boot PC, quickly create a bootable media with AOMEI. Boot machine from bootable media and it will bring you to the main interface of AOMEI Backupper Server. Open command line under Utilities tab.

Step 2. Navigate to AOMEI Backupper installation directory by typing the following command in command line: cd [installation path of AOMEI Backupper] and press Enter. For example: cd C:Program FilesAOMEI Backupper.

Tips: The drive letters might change under Windows PE environment.

Step 3. Run the following command to start restore: AMBackup /r /t [backup type] /s '[backup location path]' /d [destination location]. For example: To restore the system backup saved in D:system backup to disk 2.

AMBackup /r /t system /s “D:system backupsystem backup.adi” /d 2

If you want to restore to another computer, AOMEI command line still can do this for you. For example: Restore system in the image named 'system backup2.adi' to the partition 0 on disk 0 and perform a universal restore.

AMBackup /r /t system /s 'D:system backupsystem backup2.adi' /d 0:0 /x

If you are not familiar with command prompt or just want an easier way, you can create a Windows Server 2012 recovery disk with the graphic users interface of AOMEI Backupper Server. It can also help you repair your computer as long as you a have a backup created before.

Besides system restore, it is also a professional system backup and disk clone software. With it, you can migrate Windows Server 2016 to SSD or clone Windows Server 2008 R2 easily and without efforts. All in all, there are two methods to repair Windows Server 2008 R2 using command prompt, you can choose one based on your preference.

Both Windows Vista and Windows Server 2008 include the System File Checker (SFC) tool. Previous operating systems included this tool also. This discussion is specific to Windows Vista and Windows Server 2008. If you would like more information on previous operating systems see the following KB article: http://support.microsoft.com/kb/310747.

SFC scans and checks all Windows Resource Protected (WRP) resources. Windows Vista adds the following new functionality to the SFC tool:

  • Ability to scan a single file
  • Ability to scan a Windows installation offline

Common SFC Command Line Options

Here are some of the common commands you would use with SFC. Note you need to run SFC from a elevated command prompt

Scan entire system
SFC.EXE /scannow

Scan a specific file
SFC.EXE /scanfile=c:windowssystem32kernel32.dll

Verify. This scans all protected files but does not repair them
SFC.EXE /verifyonly

Help for Sfc.exe
SFC.EXE /?

One of the new features of SFC in Windows Vista/2008 is the ability to run SFC against a offline windows directory. This is most useful when you are unable to start Windows and suspect file corruption. Generally you should always try safe mode first before doing this to see if Windows can start. To use SFC in offline mode you do the following

  1. Boot from your Windows Vista or Windows Server 2008 DVD
  2. On the first screen of Setup choose Next
  3. In the lower left of the screen choose 'repair your computer'
  4. On the System Recovery Options screen choose your installation of Windows and then click next
  5. Click 'Command prompt'
  6. Type in the following command: SFC.EXE /scannow /offbootdir=c: /offwindir=c:windows
  7. When complete type in exit to see if Windows starts up now.

Advanced users may want to see what SFC is repairing on a system. When SFC runs it logs it’s actions to C:WINDOWSLOGSCBSCBS.LOG. You can find SFC specific entries by searching on [SR]. See http://support.microsoft.com/default.aspx/kb/928228 for more information.

Example of How SFC Can Fix Issues

Free helvetica condensed. The spectacle before us was indeed sublime.Apparently we had reached a great height in the atmosphere, for the sky was a dead black, and the stars had ceased to twinkle.

Windows Server 2008 R2 Repair Commands

The following is a example of how the system file checker was able to resolve a issue on my own computer. The issue I encountered was that When I would go into disk management my disks would show up but none of the information such as the type of disk, size, active/boot/system, healthy, etc… would show up. I checked the system event log and found the following

Active Directory

FMIFS.DLL is obviously a file used by disk management to display this information. If I look up the error code C1 it resolves to ERROR_BAD_EXE_FORMAT. So at this point I suspect that this file is corrupt. From within Windows I run the following command:

Windows Update 2008 R2 Fix

SFC.EXE /scannow

Windows Server 2008 R2 Repair Vss

It runs and says that it has repaired files. To verify I look in the C:WINDOWSLOGSCBSCBS.LOG and see the following entries

From this you can tell that SFC compared the hash for fmifs.dll and found it wasn’t correct. It restored the backup from c:windowsWinSxSx86_microsoft-

windows-fmifs_31bf3856ad364e35_6.0.6000.16386_none_54d7af8934ac24f1. After running SFC I was now able to open disk management and see my disk information.

Hopefully this helps explain how SFC can help you resolve problems on your computer and shows how Microsoft is committed to making Windows easier to fix when issues do occur.

Windows Update Repair Tool Server 2008 R2

Author:
Scott McArthur
Support Escalation Engineer
Enterprise Platforms Support