# Secure Enclave issue after using Migration Assistant on macOS

**URL:** <https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456>\
**Category:** Pritunl VPN\
**Created:** [July 28, 2025, 2:10pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456 "2025-07-28T14:10:11Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Latorre](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/l/b5ac83/32.png) [@Latorre](https://forum.pritunl.com/u/Latorre)\
**Post date:** [July 28, 2025, 2:10pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456/1 "2025-07-28T14:10:11Z")

</div>

Hi,

We’re having an issue with the Pritunl VPN Client on new MacBooks with Device Authentication enabled.

We have two machines with the **same hardware and system version** , both fully updated. However, only the machine where we **used Migration Assistant** to transfer data and settings from an old Mac is having problems connecting to the VPN when Device Authentication is active.

The error mentions a **Secure Enclave** issue — it seems the Pritunl client can’t access or use the protected key properly.

On the other machine, where we did the **backup and migration manually** , everything works fine with the same user and Device Auth configuration.

### What we’ve tried:

- Reinstalled the Pritunl Client
- Removed and re-imported the VPN profile
- Updated the system

### Questions:

1. Can using Migration Assistant really cause issues like this with the Secure Enclave?
2. Have there been similar reports? Is there any recommended way to handle this situation?
3. Is there a safe way to restore Device Authentication to work correctly on the new Mac?

Thanks in advance for any help or guidance.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [July 28, 2025, 2:30pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456/2 "2025-07-28T14:30:09Z")

</div>

You will likely need to reset the Secure Enclave input. Run the commands below to clear the configuration file it is stored in then restart the service.

```auto
sudo rm -rf /Library/Application\ Support/Pritunl/pritunl-client.json
sudo launchctl unload /Library/LaunchDaemons/com.pritunl.service.plist
sudo launchctl load /Library/LaunchDaemons/com.pritunl.service.plist

```

---

<div class="post-metadata">

**Author:** ![Latorre](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/l/b5ac83/32.png) [@Latorre](https://forum.pritunl.com/u/Latorre)\
**Post date:** [July 28, 2025, 3:34pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456/3 "2025-07-28T15:34:43Z")

</div>

> [@zach](#):
>
> You will likely need to reset the Secure Enclave input. Run the commands below to clear the configuration file it is stored in then restart the service.

It worked! Thanks again, Zach!

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [July 28, 2025, 8:27pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456/4 "2025-07-28T20:27:11Z")

</div>

The next release will have a reset Secure Enclave in the menu to correct this issue in the future.

---

<div class="post-metadata">

**Author:** ![Latorre](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/l/b5ac83/32.png) [@Latorre](https://forum.pritunl.com/u/Latorre)\
**Post date:** [July 29, 2025, 3:45pm UTC](https://forum.pritunl.com/t/secure-enclave-issue-after-using-migration-assistant-on-macos/3456/5 "2025-07-29T15:45:29Z")

</div>

Perfect Zach!