Windows 10 1703 Build, NOT booting after turning off/decrypt the Bitlocker encryption

Swadesi

Active member
Joined
May 18, 2017
Posts
36
Hi, I have turned on the Bitlocker on my VAIO S13 laptop last night, which has Windows 10 ~ 1703 Build. And couldn't boot it this morning, but I do have an access to command prompt via advanced options, where I was able to turn off the bit locker and decrypt the drive and see all my contents.

However, I still couldn't be able to boot it at all, including safe mode.

I would highly appreciate your help on this, instead of resetting my laptop.

Thanks, Dave R
 
As part of my troubleshooting, I turned off the Windows 10 automatic repair, and it prompted me with this error:


File: \Windows\System32\ntoskrnl.exe
Error code: 0xc0000221


Please advice. I would highly appreciate your help!
 
Hi Swadesi. :welcome:

Run bcdedit on the system partition and see if device and osdevice, under OS loader section, are set to partition=C: (obviously, only if you have installed your system in c:. If you installed it in z:, you must use z:).
 
Last edited:
Hi Swadesi. :welcome:

Run bcdedit on the system partition and see if device and osdevice, under OS loader section, are set to partition=C: (obviously, only if you have installed your system in c:. If you installed it in z:, you must use z:).

Thanks, I already checked it and both says "C:" which is correct in my case!
 
This is a summary of an article on microsoft (docs), written by Don Marshall (MS employee?) here (click):
  • If a specific file was identified in the bug check message as being corrupted, you can try replacing that individual file manually.
  • Disabling memory caching of the BIOS might also resolve this error.
  • If the error occurred immediately after RAM was added to the system, the paging file might be corrupted or the new RAM itself might be either faulty or incompatible.
  • Run the Emergency Recovery Disk (ERD) and allow the system to repair or replace the missing or damaged driver file on the system partition.
  • Disk errors can be a source of file corruption. Run Chkdsk /r to detect and resolve any file system structural corruption.
  • You can also run an in-place upgrade over the existing copy of Windows.
 
Thanks Xilolee, hoping we could resolve this error with your input/lead. I will keep you posted shortly
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top