This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sector-based initial encryption of drive C: failed. Reason: -2144272202 (0x803100B6)

Hello there,

We have recently installed Safeguard, and it is pushing to our Windows 7 test machines fine, but when we push it to a Windows 10 device we get that error in the title with ID: 3508. Has anyone else run into this? And if so, how were you able to solve it?

Thank you in advance!

-J

This thread was automatically locked due to age.

0 FormerMember over 6 years ago

Hi Justin,

A very happy new year to you!

When you say you're "pushing" this out do you mean you have a deployment script setup via something like SCCM, LanDesk etc? If so, you'll need to be aware that your Windows 7 machines are likely using SafeGuard Disk Encryption (proprietary) whereas Windows 10 will be using SafeGuard Native Device Encryption (BitLocker) and the two are initialised by slightly differently commands.

Can you post a screenshot showing the 3508 error message? Also, does enabling Bitlocker manually start the encryption successfully?

I would also suggest taking a look at this article which may help further https://community.sophos.com/products/safeguard-encryption/f/sophos-safeguard-products/5789/sector-based-initial-encryption-of-drive-c-failed-reason-1354
Cancel
Vote Up 0 Vote Down

Cancel