Sorry for asking this question, as I have not searched the community but I need urgent assistence....
One of our collegue's came by the IT department with a laptop which only showed BSOD. No way to enter Windows.
On laptop Safeboot 5.2 is installed.
I managed to reinstall Windows on the C partitiion, leaving the D partition in tact.
But ofcourse, once Windows booted, the D partition can't be accessed.
So I reinstalled the Safeboot 5.2 client in the hope that I am able to access the D partition again.
However I am afraid that I will encrypt the D partition again (so encryption over encryption....).
Can someone tell me if that is the case ?
Will Safeboot/EEPC again encrypt the D partition ?
At this time, the C partition is encrypting and after that it will automatically continue with the D partition (hence my urgent question).
I already tried to recover D partition using BartPE bootable CD with Safeboot support, but after authenticating I tried to remove Safeboot.
Got error E0050001 saying Safeboot/EEPC was not installed. Found in Knowledge Base that EEPC needed to be reinstalled and after that removed.
I have access to EEM and I believe I can stop encryption.
I already marked D partition not to encrypt, so only C partition would encrypt (I think, as I never had this issue before).
What was intial error ? were you getting BSOD after Safeboot screen ? or safeboot screen was not there ? when you got laptop ?
EEPC Version ?
Initially Safeboot was working, only Windows got BSOD.
error was a stop error, I am not sure what stop error...I believe 7b
There was no possibility to get into Windows, not in Safe mode and not Last Known Configuration.
So I tried to repair Windows installation, but unfortunately it reinstalled Windows and not repair it.
We are using EEPC 5.2
1. STOP the current ecnryption.
2. Export Safeboot configuration file from EEM server (ofcourse old one)
3. Boot machine with WINTECH , (BARTPE)
4. RUN WINTECH TOOL
6. Wintech > Authenitcate from Database > select SDB file (copiend in STEP2)
6. GO > PRograms> A43 File managemetn utility
7. try to access D: Drive