> ## Content Index
> Fetch the complete content index at: https://elevendecoded.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Fix Intune Not Working After Cloning a Windows 11 PC
- URL: https://elevendecoded.com/fix-intune-not-working-cloned-windows-11-pc/
- Published: 2026-10-24T14:33:00.000Z
- Updated: 2026-10-24T14:33:00.000Z
- Author: Md Fakharuddin
- Tags: Windows 11, Troubleshooting, Desktop Management

Intune stops [managing a cloned Windows](https://elevendecoded.com/reinstall-windows-11/) 11 PC because the device identity and enrollment data are duplicated from the original machine. This duplication causes Intune to reject the cloned device since it appears identical to the source. To fix this, you need to reset the device identity and re-enroll the PC in Intune, restoring unique device identification and management without losing data or security settings.

## Why does Intune stop working after cloning my Windows 11 PC?

When you clone a Windows 11 PC, the system image copies device-specific identifiers like the hardware hash and unique IDs used by Intune to recognize devices. Because these identifiers are duplicated, Intune cannot distinguish between the original and cloned device, causing enrollment conflicts. The cloned PC also retains cached management policies and tokens linked to the original device, resulting in authentication failures and broken management. Common symptoms include error messages like "Device not compliant" or the cloned device disappearing from the Intune console.

> **Symptom:**

```
Device not compliant
```

The underlying problem is that Intune's device identity and enrollment state become invalid or conflicted after cloning, breaking the trust relationship required for device management.

## How does cloning affect Windows 11 device identity and Intune enrollment?

Windows 11 and Intune rely on unique device identities created from hardware components and system data. Enrollment binds this identity to Intune via tokens and certificates stored locally. Cloning copies the entire system image, including these tokens and unique identifiers, resulting in multiple devices sharing the same identity. Intune expects each device to have a unique hardware hash and enrollment record. When clones share these, the Intune management server rejects them or fails to apply policies. In effect, cloning duplicates the device identity layer Intune depends on, causing management failures until you reset and re-register the device identity.

## How can I fix Intune enrollment issues after cloning a Windows 11 PC?

To restore Intune management on a cloned Windows 11 PC, you must remove conflicting enrollment data, reset device identifiers, and re-enroll the device. Here's how:

1. Log in to the cloned PC with an administrator account.
2. Disconnect the PC from Intune by removing the workplace or school account:

```text
Settings > Accounts > Access work or school > Select the connected account > Disconnect
```

Settings path

1. Remove existing device management data by deleting MDM enrollment information. Open an elevated PowerShell window and run:

```powershell
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\Enrollments" -Recurse -Force
Remove-Item -Path "HKLM:\SOFTWARE\Microsoft\EnterpriseResourceManager" -Recurse -Force
```

PowerShell (run as Administrator)

1. Reset the device’s TPM to avoid identity conflicts:

Clearing TPM deletes keys stored in it, such as those used for disk encryption. Confirm this is acceptable before proceeding.

```powershell
Clear-Tpm -Confirm:$false
```

PowerShell (run as Administrator)

1. If possible, run sysprep with the generalize option to reset system-specific data. This is best done before cloning but can be done now if preparing the device for future imaging:

```cmd
C:\Windows\System32\Sysprep\sysprep.exe /generalize /oobe /shutdown
```

Command Prompt (run as Administrator)

1. Restart the PC after completing the above steps.
2. Reconnect the device to Intune by adding the work or school account again:

```text
Settings > Accounts > Access work or school > Connect > Sign in with your organizational account
```

Settings path

These steps clear duplicate enrollment data and force Windows 11 to generate a new, unique device identity that Intune can manage properly. Avoid removing devices from the Intune portal before trying these local fixes, as they preserve device records and are less disruptive.

## How do I verify that Intune is working correctly after the fix?

After re-enrolling the device, verify Intune management is functioning:

- Open Settings and go to `Accounts > Access work or school` to confirm the device is connected and shows no errors.
- Run in an elevated PowerShell window:

```powershell
Get-MDMEnrollmentStatus
```

PowerShell

This should confirm the device is enrolled.

- Check the Intune portal to ensure the device appears with a new unique device ID and shows a "Compliant" status.
- Manually trigger a sync with:

```powershell
Invoke-DeviceAction -Action Sync
```

PowerShell

- Confirm deployed policies, configurations, and apps from Intune are applied successfully.

Watch for errors such as "Device not enrolled" or "Pending" status. If issues persist, repeat the enrollment steps or verify network connectivity. Successful verification means Intune now recognizes and manages the device uniquely.

## What can I do to prevent Intune problems when cloning Windows 11 PCs in the future?

To avoid Intune issues when cloning Windows 11 PCs, prepare the source machine properly:

- Always run `sysprep /generalize` on the source PC before capturing the image. Sysprep removes unique identifiers and prepares the OS to generate new identities at first boot.
- Do not clone a running, already Intune-enrolled PC without generalizing it first. Cloning without sysprep duplicates device IDs and enrollment data.
- Create clean reference images that have not been enrolled in Intune.
- After deploying cloned machines, immediately re-enroll them into Intune as new devices.
- Document your imaging and deployment processes to include clearing enrollment data and resetting TPM when appropriate.

Following these steps reduces duplicate device identities and keeps Intune management stable across deployments.

## Conclusion

If a cloned Windows 11 PC stops working with Intune, resetting the device identity and re-enrolling it usually resolves the problem. Disconnect the device from Intune locally, clear enrollment data, reset TPM if needed, and reconnect the device. Then verify that Intune recognizes the device and applies policies correctly. For future cloning, always use sysprep or a similar generalization process to prevent duplicate device identities and ensure smooth Intune management.

## Frequently Asked Questions

### Can I fix Intune issues on a cloned PC without re-enrolling?

Usually not. Because cloned devices share identical identifiers, you need to reset the device identity and re-enroll. Simply reconnecting the existing enrollment rarely restores proper management.

### Is sysprep required before cloning for Intune to work?

Yes. Sysprep removes unique system identifiers from the source machine. Without it, clones inherit duplicate IDs causing Intune enrollment conflicts.

### Will clearing TPM affect device security when fixing Intune issues?

Yes. Clearing TPM deletes stored keys used for features like disk encryption. Ensure this is acceptable in your environment before proceeding.