Unite Innovations

By

If you  are ready this article chances are you are encountering the dreaded 0x00002e2 boot error.

Windows Server Error 0x00002e2

Backup, Just In Case

Before trying any of these, make a backup if possible of the instance. In case something goes wrong you could always revert back to where you started from.

Try From Safe Mode

In this situation I would first try these steps –

  1. Reboot
  2. Press f8 for boot menu options
  3. Select Safe Mode with Command Prompt
  4. At the command prompt type SFC /scannow
  5. Once done reboot

Boot Using Windows Media

If you cant boot to the safe mode with command prompt, try booting from a window boot media or install media.

  1. Select Repair
  2. Select Command Prompt
  3. Then run SFC /scannow
  4. Once done, then reboot

You may have to change to the directory where the windows installation resides.

Still Boot To The Error 0x00002e2 Screen

If you still boot to the error 0x00002e2 screen then time to try something else.

  1. Reboot and press F8 for boot menu options
  2. Select Directory Services Repair Mode (DSRM).
    • Note: This mode is only available if the server has a DC to interact with NTDS database. During boot the server may repair itself or try to repair itself and reboot, leaving you to do steps one and two again.
  3. Log in using an administrator account.
    • It maybe necessary to log in using a local administrator account. This will be necessary, because the AD service will not or may not be running. Chances are the domain users will be unavailable for log in.
  4. Open command prompt
  5. Then change directories. Type cd c:\windows\NTDS
  6. Make sure to make a copy or backup of everything in this directory before you continue.
  7. Then type NTDSUTIL and press enter.
  8. Type activate instance ntds and press Enter.
  9. Type Files and press Enter.
  10. Type Info and press Enter. This command will shows you the location of the logs. In case the the server has more than one partition.
  11. Navigate to logs location and delete or rename or move the *.log.
  12. Then reboot.
  13. F8 again.
  14. Select Directory Services Repair Mode (DSRM) again.
  15. Once in DSRM again, defrag the database.
  16. Using the command prompt, type NTDSUTIL and press enter.
  17. Type activate instance ntds and press Enter.
  18. Type files and press enter
  19. Type info and press enter. This will help verify the servers NTDS directory. Make sure it reads C:\Windows\NTDS.
  20. Created a folder – C:\Windows\NTDS\Temp.
  21. Type Compact to C:\Windows\NTDS\Temp and press enter.
  22. Once complete, copy the newly created Ntds.dit file in the C:\Windows\NTDS\Temp folder over the old one in C:\Windows\ NTDS directory.
  23. Delete all the *.log files.
  24. Reboot normally and that should be it.

Once up and running I would recommend running a DCdiag to make sure everything is okay or to help spot some other issues. If these steps do not work, I would suggest restoring from a backup (If a backup is available.).