- CheckMates
- :
- Products
- :
- Harmony
- :
- Endpoint
- :
- Re: Encryption stuck at Verify Setup
- 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
Encryption stuck at Verify Setup
All laptops Windows 7 and Window 10 stuck at Verify Setup new installs as well as client upgrade error log shows:
20170803 154628,871-0400 I FDE_srv.exe:1d24 StateMachine ------====== ACTION RESULT ======------
20170803 154628,871-0400 I FDE_srv.exe:1d24 StateMachine * Phase: Deployment
20170803 154628,871-0400 I FDE_srv.exe:1d24 StateMachine * Action: Wait for User Acquisition
20170803 154628,871-0400 I FDE_srv.exe:1d24 StateMachine * Result: Success
20170803 154628,871-0400 I FDE_srv.exe:1d24 StateMachine ------===========================------
20170803 154628,873-0400 I FDE_srv.exe:1d24 VerifySetupAction Database does not contain any preboot drivers.
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine ------====== ACTION RESULT ======------
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine * Phase: Deployment
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine * Action: Verify Setup
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine * Result: Error
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine * Error Code: 2001
20170803 154628,873-0400 E FDE_srv.exe:1d24 StateMachine * Message: Could not enforce preboot. No user would be able to logon to the system
Checkpoint support has been unable to help so any ideas would be appreciated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From looking at the SR, it looks like TAC has a pretty good idea what the issue is.
There are a couple of symptoms that have the same solution as the one TAC offered:
- "FDE Step 2 error" when machine is booting
- After inserting new HDD to an encrypted system, BSOD occurs after initial reboot
Basically:
- FDE Preboot will support MBR or GPT partitions, but not both at the same time
- If your system has BIOS, then you need to use all MBR partitions
- If your system uses UEFI, then you need to use all GPT partitions
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Our Win 10 machines are GPT and Win 7 are MBR. It is even failing when we update a Win7 with older version of encryption on it.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like a tricky one for sure.
That said, the issue seems the issue is progressing in the TAC.
If things get stuck, please reach out privately and I'll see what I can do.
Short note (unrelated to this thread): When you respond via email to a thread on CheckMates and you don't remove your signature, that becomes part of the public post.
I removed the signature as it had your personal contact details, which I'm guessing you'd prefer not to share with the world
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This problem occurs time by time. Some times you just reinstall same system, and next time you stuck with this error.
On first look: you have all checks done. Win10 + GPT, 2 users, UAC disabled, etc. And even then it stucks.
