Windows 11 OEM licence deactivated after 24h2 update

not practical with an estate of 2000 devices

and to the poor people who have had to buy another licence, maybe go back to MS for a refund and or class Action

2025 i got update and windows deactived

Windows 11 Pro Insider Preview 24H2 IS26200.5622

Windows: 1000.26100.121.0

As a quick solution, I was able to prevent Windows from updating to 24H2 from 23H2, but not disable the Windows updates for security reasons:

You can set Group Policy to stay on the desired Windows 11 revisions.

1 Open the Local Group Policy Editor (gpedit.msc).
2 Navigate in the left pane of Local Group Policy Editor.
Computer Configuration > Administrative Templates > Windows Components > Windows Update > Manage updates offered from Windows Update

3 In the right pane of Manage updates offered from Windows Update in Local Group Policy Editor, double click/tap on the Select the target Feature Update version policy to edit it

5 To Specify Target Feature Update Version

A) Select (dot) Enabled.

B) Perform the following steps under Options:​

• Type Windows 11 in the Which Windows product version would you like to receive feature updates for box.
• Type the version (ex: "23H2") you want to specify in the Target Version for Feature Updates box.

C} Click/tap on OK

(Copied from external site https://www.elevenforum.com/t/specify-target-feature-update-version-in-windows-11.3811/ )

Hi all, i have now created a solution. please note this is only applicable for enterprise users with intune

This is a powershell script to use intune detection and remediation

Just input your MAK key into the remediate script

Detect script

# Detection Script - Check Windows Activation Status

$LogFolder = "C:\Windows\Logs\ActivationRemediation"

$LogFile = Join-Path $LogFolder "ActivationDetect.log"

if (-not (Test-Path $LogFolder)) {

    New-Item -ItemType Directory -Path $LogFolder -Force | Out-Null

}

function Write-Log {

    param ([string]$Message)

    $Timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"

    Add-Content -Path $LogFile -Value "$Timestamp [DETECT] $Message"

}

Write-Log "Starting detection script."

try {

    $Activated = Get-CimInstance -ClassName SoftwareLicensingProduct |

                 Where-Object { $_.PartialProductKey -and $_.LicenseStatus -eq 1 }

    if ($Activated) {

        Write-Log "Device is activated. No remediation required."

        exit 0  # Compliant

    } else {

        Write-Log "Device is NOT activated. Remediation required."

        exit 1  # Non-compliant

    }

} catch {

    Write-Log "Exception during detection: $_"

    exit 1

}

Remediate script

# Remediation Script - Reapply MAK Key and Reactivate Windows

$MAKKey = "XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

$LogFolder = "C:\Windows\Logs\ActivationRemediation"

$LogFile = Join-Path $LogFolder "ActivationRemediate.log"

if (-not (Test-Path $LogFolder)) {

    New-Item -ItemType Directory -Path $LogFolder -Force | Out-Null

}

function Write-Log {

    param ([string]$Message)

    $Timestamp = Get-Date -Format "yyyy-MM-dd HH:mm:ss"

    Add-Content -Path $LogFile -Value "$Timestamp [REMEDIATE] $Message"

}

Write-Log "Starting remediation script."

try {

    Write-Log "Installing MAK key..."

    $ipk = cscript.exe /nologo C:\Windows\System32\slmgr.vbs /ipk $MAKKey 2>&1

    Write-Log "Key installation output: $ipk"

    Start-Sleep -Seconds 5

    Write-Log "Triggering online activation..."

    $ato = cscript.exe /nologo C:\Windows\System32\slmgr.vbs /ato 2>&1

    Write-Log "Activation output: $ato"

    Start-Sleep -Seconds 5

    $Activated = Get-CimInstance -ClassName SoftwareLicensingProduct |

                 Where-Object { $_.PartialProductKey -and $_.LicenseStatus -eq 1 }

    if ($Activated) {

        Write-Log "Activation successful."

    } else {

        Write-Log "Activation failed. License status still non-compliant."

    }

} catch {

    Write-Log "Exception during remediation: $_"

}

===================================

the scripts can be deployed and set to run very day or as little as every hr Just deploy to the relevant device group.

Hope this helps you out, sorry no solution for ppl with OEM licence issues