Share via

Using smlgr with MAK keys on Windows 11 Enterprise

Van Fifty 20 Reputation points
2026-06-04T00:21:50.83+00:00

I was reading the following which applies to Windows 10 and would like to know if it also applies to Windows 11 Enterprise:

https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/dn502526(v=ws.11)

It mentions "slmgr.vbs /ipk <MultipleActivationKey>" it then states "If users install a MAK by using the UI, the MAK client attempts to activate itself over the Internet one time. If the users install a MAK key by using the Slmgr.vbs script, the MAK client does not try to activate automatically."

I would like to confirm, if a system is disconnected from the Internet and slmgr.vbs /ipk is used then the license will be associated with the OS but Windows 11 will not activate? Even after connecting to the Internet Windows will still not activate and the MAK count will remain unchanged.

To activate, one would need to connect to the Internet and then also invoke : slmgr.vbs /ato

This will then use up one MAK count and Windows 11 will be activated, correct?

If slmgr.vbs /ato is invoked multiple times after activation on the same activated system then the MAK count will remain unchanged?

Windows for home | Windows 11 | Licensing and activation
0 comments

Answer accepted by question author

Marcin Policht 91,150 Reputation points MVP Volunteer Moderator
2026-06-04T00:39:56.54+00:00

Yep - the behavior described in that Windows 10 / Windows Server documentation still applies to Windows 11 Enterprise when using a MAK (Multiple Activation Key). When you run:

slmgr.vbs /ipk <MAK-key>

you are only installing the product key into the licensing store. That alone does not activate Windows if the key was installed through slmgr.vbs. So in your scenario, on a system that is disconnected from the Internet will install the MAK into Windows 11 Enterprise, but Windows will remain in the unactivated state.

If the machine is later connected to the Internet, Windows still will not automatically activate merely because the MAK is present. The activation attempt is not automatically triggered simply due to connectivity being restored after a scripted /ipk installation.

Activation occurs when you explicitly invoke:

slmgr.vbs /ato

or otherwise initiate activation through the UI/API. At that point, Windows contacts Microsoft's activation servers, consumes one MAK activation from the pool, and activates the installation. After the system is already activated, running:

slmgr.vbs /ato

again on the same unchanged installation normally does not consume additional MAK activations. Microsoft activation servers recognize the existing activation state/hardware identity. Repeated /ato calls on the same installation are generally harmless and do not continually decrement the MAK count. Note though that substantial hardware changes or reinstallation/reimaging can cause the system to be treated as a new activation event, which can consume another MAK activation.

If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

hth

Marcin

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.