- CheckMates
- :
- Products
- :
- Harmony
- :
- Endpoint
- :
- Checkpoint FDE RAW partition no OS load
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Checkpoint FDE RAW partition no OS load
Hello to all,
We are the start of implementing FDE with Checkpoint and from 26 pc encrypted with preboot enabled we have 2 laptops that are not loading OS anymore after preboot authentification. We checked the disks and the partition that was encrypted its RAW (after preboot auth)
The common things are: Windows 10 Pro(1703 / 1709)
Endpoint client is 80.83
What can we do to try recovering the OS? Some hints and tips?
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also if anyone can point me how to collect the logs from that machine if it doesn't boot?
L.E: found the preboot tool
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So we did recover the data(with recovery media tool - decrypted the partition) and now Windows is still not loading giving us a blue screen with error "Page fault in non paged area"
Looking for advise
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you try to boot into Safe Mode to see if you can get to the OS? From my experience if we can get the data off the laptop by mounting the drive, but it can't boot to windows, we have just been rebuilding those laptops (imaging a new OS).
I would open up a case with TAC if getting the actual data off the laptop is not possible even though you decrypted the laptop.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Eventually, we will reinstall that laptop. The support told me that it was an issue with Fast Startup function from Windows.
We are still looking for possible scenarios on how to avoid this...
Any tips and tricks?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In our BIOS settings, we use the new UEFI BIOS instead of legacy. We have Fast Boot in the BIOS off (to correct the issue with usb mouse/keyboards in the preboot environment) and also Fast Startup in the Windows Power Options turned off (via GPO).
Since we turned off that fast startup in Windows, we haven't had that screenshot thats in the SK article you listed.
