How to Fix C00002E2 Directory Services Could Not Start - Blue Screen

Printer-friendly versionPDF version
How to Fix C00002E2 Directory Services Could Not Start - Blue Screen

There are several reasons you may get get this error. The most common being a corrupt Active Directory database (NTDS.DIT). I know this sounds detrimental, but it's actually easy to fix this blue screen.

*** This is the Active Directory Database we're talking about here, so make sure you have a good backup of the server, in case this doesn't work***

This Stop code is only seen on a system with Active Directory on it. You notice it when the server is booting. You'll get a blue screen and an error code, like the following:

STOP: c00002e2 Directory Services could not start because of the following error:

A device attached to the system is not functioning.

Error Status: 0xc0000001.

Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.

How to Fix C00002E2 Directory Services Could Not Start - Blue Screen 1

To begin, do as the message says, and boot into Directory Services Restore Mode. When the server powers on, press F8 before the OS begins to load. You should see a selection screen like this. Choose Directory Services Restore Mode:

How to Fix C00002E2 Directory Services Could Not Start - Blue Screen 2

Once in Directory Services Restore Mode, you can check if there is a problem with the database by running the following commands:


activate instance ntds


If there is a problem with it, you'll see something like this returned:

Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113

How to Fix C00002E2 Directory Services Could Not Start - Blue Screen 3

To fix, just rename all of the .log files located in C:\windows\ntds\ to .log.old, or anything else, so they can be recreated.

How to Fix C00002E2 Directory Services Could Not Start - Blue Screen 4

Now reboot the server. For most people, this fixed the database, and the server booted up. For others, it still blue screened after this. If you continue to get a blue screen, run the following command in Directory Services Restore Mode, and then reboot:

esentutl /p "c:\windows\ntds\ntds.dit"

Thanks for your post :)

Thanks a lot for this ^^

seriously. thank you.

thank you!!!

Thank you !!!

still didn't work for me

Worked like a charm!

Many, many, thanks. Although, in my case, I couldn't complete exactly like you did, your help was invaluable. Thanks again!

Thanks a million! Had to modify it a bit but the server is up!

hermano muchas gracias , tenia dias de tener este problema y lo solucione gracias a usted..un abrazo y gracias nuevamente!!

Muchas Gracias dias con este problema. solucionado gracias a usted

Thank you very much, very helpful got me out of a real tough situation.

Thanks alot it worked like charm for me

good luck

wonderful and good

Dude you saved me so much time. Seriously this was a life saver

Many thanks worked like a charm...

Very good! Saved me a lot of efforts!

This worked perfectly for me, thank you very much. :)

Thank you very much!

Today is my day to say thank you.
You did it to one more technician that was lost about this error.

BIG THANKS TO YOU and Keep sharing and spreading the knowledge.

Thanks for this. Helped when I storing an old SBS server in MAC Parallels.

Thanks!! I had to do both steps but finally got it to work!

works !!!, thank you sir

Brilliant, I was ready to throw the server out the window, this helpful advice from you saved the server AND my sanity. Thanks :-)

Boooom fixed it nice 1

thank you for this post

It is perfect.
Thank You

thanx, you bring me out of a infernal trouble

I've been doing monthly test restorations using Shadow Protect for years on all member servers but always ran into the issue of not being able to logon other than through DSRM on DC's. I found this site, followed the instructions and BOOM! Sure boosted my confidence in restoring a domain controller, when that restoration is on the only DC in the domain. Good job!

Thanks man! this work for me

Thank you!!!!!

Thank you sooo MUCH!!!!
In my case the first NTDS fix didn't work and it blue screened again.
But the second command fixed the issue and the DC came right abck up.

Again, thank you very much.

Muchas gracias desde Chile!!!
Thank you very much from Chile!!!

Worked like a charm!! Saved our bacon!

Worked perfectly! Thanks!!!

Perfect, thanks!!!

Thank you master!

First step worked in ma case :) Thanks so much.

Thank you! You saved me a significant hassle.

Had to do all to the last line using eseutil, rebooted and it worked! Your a champion

Huge thx. I love you :)

Thank you! Эта статья сэкономила мне кучу времени!!!

Worked a treat! Magnificent, thank you for your post.

Sos un maestro! muchas gracias!

THX :-)

Seriously. thanks a million!!

Obrigado, resolveu meu problema!

You know , You save my life. !!!!!!!!!! i do esentutl /p "c:\windows\ntds\ntds.dit" to get otu of this !!

Thank you.

hello, really, thanks a lot, this post save my job, we were 12 hours without services, Sql clusters down, shared folders down, 12 hours of investigation and just renaming those files like you said saved my life. thanks a lot once again.

You're welcome :)

Thanks buddy!

Gracias Hermano.

Me salvaste la vida...

Very good. Thanks man!

YOU R THE MAN!!! Saved me BIG TIME! Thanks mon fr: JA

Thank you!! Big help!!

You ARE the man!

Thank you very much.

After one month of hard work i solve my problem.


YES! More one success case, thank you a lot! It saved my head...

Post new comment