Windows can't activate using the MAK key error 0xC004F069

 

Resolving Windows Activation Issues with MAK Keys on Evaluation Versions



If you're encountering issues activating Windows using a Volume Licensing MAK key due to a previously installed evaluation version, follow these steps to resolve the problem.

Step-by-Step Guide to Activate Windows with a MAK Key

1. Uninstall the Current Product Key

Run the following command to remove the existing product key and place Windows into an unlicensed state:

slmgr.vbs /upk

After running this command, Windows may display an activation warning.

2. Remove the Product Key from the Registry

To ensure the previous key is fully deleted, execute:

slmgr.vbs /cpky

This step prevents any conflicts when entering the new key.

3. Install the New MAK Key

Replace <YOUR-MAK-KEY> with your actual key:

slmgr.vbs /ipk <YOUR-MAK-KEY>

This command installs the MAK key, replacing any previously installed keys.

4. Activate Windows

Once the new key is installed, activate Windows:

slmgr.vbs /ato

5. Verify Activation Status (Optional)

To confirm that Windows is properly activated, run:

slmgr.vbs /dlv

This command provides detailed activation status and licensing information.

Additional Issue: Evaluation Version Preventing Activation

If the MAK key still fails, it's likely that Windows is still in evaluation mode.

Check the Current Edition

Run the following command to identify the installed edition:

DISM /online /Get-CurrentEdition

If the output indicates an evaluation version (e.g., ServerStandardEval), you need to convert it to a full version.

Convert from Evaluation to Standard/Datacenter Edition

Use the following command to upgrade to the appropriate edition. Replace <YOUR-MAK-KEY> with your valid MAK key:

DISM /online /Set-Edition:ServerStandard /ProductKey:<YOUR-MAK-KEY> /AcceptEula

For Datacenter edition, replace ServerStandard with ServerDatacenter.

Restart and Activate

After conversion, restart the server and reattempt activation with:

slmgr.vbs /ato

This should successfully activate your Windows installation.




Popular Posts

Windows 11 24H2 Upgrade using Intune Feature Updates Policy

Image
How to Deploy Feature Updates Using Intune: A Step-by-Step Guide Microsoft Intune provides a streamlined method for managing Windows feature updates across your organization. In this guide, I'll walk through the essential prerequisites, policy creation steps, deployment, and monitoring process to ensure a smooth rollout of feature updates using Intune. 1. Verify Prerequisites Before you create a feature update policy, ensure the following prerequisites are met on the target devices: Device Enrollment : Devices must be enrolled in Intune, either as Microsoft Entra hybrid joined or Microsoft Entra joined . Supported OS : Devices must be running a supported version of Windows 10 or Windows 11 . Telemetry Settings : Devices must have the telemetry level set to Required . You can configure this via Devices > Windows> Configuration > Create Policy > Templates>  Device Restrictions > Reporting and Telemetry > Share Usage Data >Set as Required...
Read more

Deploying a Script through Intune to a Linux PC

Image
Can Intune Deploy Shell Scripts to Linux Devices? Yes! Just like deploying PowerShell scripts to Windows, Intune can also deploy shell scripts to Linux devices. In this blog, I'll walk you through the process of deploying shell scripts to Linux using Intune, making it easier to automate tasks and manage Linux endpoints efficiently. Prerequisites Before deploying a shell script via Intune, ensure the following requirements are met: 1. Intune and Microsoft Entra ID Your environment must have Microsoft Intune configured for device management. This setup enables secure enrollment and policy enforcement on Linux devices. 2. Linux Device Enrollment The Linux PC must be properly enrolled in Intune to receive policies and scripts. If the device is not enrolled, follow Microsoft's documentation on Linux enrollment in Intune. Deploying the Shell Script Once the prerequisites are met, follow these steps to deploy your shell script through Intune: Access Microsoft Intune Sign in to the ht...
Read more

Deleting Registry.pol and Forcing Group Policy Update Using a Batch File - Deploy through SCCM

  Deleting Registry.pol and Forcing Group Policy Update Using a Batch File - Software update cycle scan failures  In some troubleshooting scenarios ( specially software update cycle scanning errors)  , it is necessary to remove the Registry.pol file to reset Group Policy settings and force an immediate update. This guide outlines how to accomplish this using a batch script and deploy it via SCCM.  Step 1: Create a Batch File Script to Delete Registry.pol and Update Group Policy @echo off setlocal :: Define paths set "RegPolPath=C:\Windows\System32\GroupPolicy\Machine\Registry.pol" :: Check if the file exists and delete it if exist "%RegPolPath%" del /f /q "%RegPolPath%" :: Force Group Policy update gpupdate /force :: Notify user echo Group Policy has been updated successfully. pause Open Notepad. Copy and paste the script above. Save the file with a .bat extension (e.g., ResetGPO.bat ). Step 2: Deploy the Batch Script Using SCCM 1. Create an SCCM Packag...
Read more

Remove CCMCache, Windows.old, and Temp folders using Powershell script

Image
This PowerShell script automates the cleanup of: CCM Cache Files : Removes files older than 14 days from C:\Windows\ccmcache. Temporary Files : Cleans up files older than 14 days from the user’s temp folder ($env:Temp) and the system-wide temp folder (C:\Windows\Temp). Windows.old Folder : Deletes the Windows.old folder if it’s older than 14 days. This folder is typically created during a Windows upgrade and can take up significant disk space. The script also logs all actions to a log file (C:\TempCleanupLog.txt), making it easy to track what was deleted and troubleshoot any issues. # Define paths $ccmCachePath = "C:\Windows\ccmcache" $tempPath = "$env:Temp" $systemTempPath = "C:\Windows\Temp" $windowsOldPath = "C:\Windows.old" $logFile = "C:\TempCleanupLog.txt" # Change log file location if needed # Function to clean up files and directories older than a specific number of days function Clean-Ol...
Read more