ClipUp.exe License error

Saaglem

Active Member
Messages
246
Reaction score
68
Good day Mates. Trust you are all well.

I get a license registration error of missing clipup.exe eveytime I do a Win11 LTSC or IOT LTSC rip with NTLite. The file is there before the rip but after I've completed the iso then this file disappears. I've attached 2 presets, one with compatibilty enabled and one without, incase you want to view it.

If I remove the windows activation check mark in compatibility (Disabled preset), then NTLite delete the clipup.exe file and activation is not possible, unless you copy the file back into the system32 folder. If I enable the check box (Enabled preset) then it doesn't delete the file.

The file enables the function to register the OS. When I monitor the folder while NTLite is busy removing the items I can see it removes the file from system32 folder. Because it removes the files at random I cannot jump fast enough to see which one is the culprit doing it.

Just thought I everyone should know.

Cheers
 

Attachments

Hi,

did I understand this correctly:
- if you disable Windows Activation compatibility, Windows Activation is not protected?
That is expected, keep it enabled.

The component pulling that file is Easy Migration, will think about protecting that file with some other kept component in case people disable the compatibility.
Btw in the meantime you can add a file to the protection in the Compatibility - right side file list.
 
Yes, that's normal. You must keep the compatibility "Windows activation"
These compatibilities are used to protect the necessary files

EDIT : This clipup.exe file should only be needed to activate LTSC or IOT LTSC
With a Home or Pro, I don't have this file in System32 and no activation problems
And the "Activation" compatibility is checked
 
Last edited:
Nope, it is not protected.

It took me half a day to figure it out, but thats how we learn. I'll keep it enabled.

Thanx
 
Is your Windows activation using a digital license ?
No problem activating a Home or Pro without this file, and the digital license
 
Once my system is stable, registerd and tuned, I block the crap out of it. I've shared my firewall with NTLite before and I run it through an old knoppix VS. It evolves on communication and was a bit predictabile but got that sorted. It works great, a bit limited but I can do everything I want with it. I will have to rewrite some of it due to changes in win11.

Will see how windows sandbox evolve once copilot is in full swing. I'm already working on a AI firewall that might defeat the use of a sandbox. A bit stuck on the impersonateprevilidges but I'll get there.

Oh, system is running fine with only activation enabled, and yes, digital license. I am actually thinking of removing the file in system32 after registration.

BIG NOTE: DO NOT run the firewall on your machine untill you've changed some of it. It ONLY allow some ports to be used and works with the security file. You can view changes in the windows defender firewall ui.
1754132919432.png



Note: Most of the code in the power shell file was supplied by Roger Zander.

Thanx guys.

Cheers
 

Attachments

Last edited:
Yes, that's normal. You must keep the compatibility "Windows activation"
These compatibilities are used to protect the necessary files

EDIT : This clipup.exe file should only be needed to activate LTSC or IOT LTSC
With a Home or Pro, I don't have this file in System32 and no activation problems
And the "Activation" compatibility is checked
ClipUp is used by KMS activation methods. It's not required for retail Windows licenses.
 
ClipUp is used by KMS activation methods. It's not required for retail Windows licenses.
Yes, what I said in my edit, even though the KMS component is necessary for the proper functioning of Windows activation and the associated service (but can be removed after activation) and this file is not deleted with KMS component but another one

But Saaglem has an activation problem and isn't using KMS but a digital license (retail)
Or is there a digital license with the KMS too (I just use Retail and MAK) ?
 
ClipUp.exe is the Client Licensing Platform migration tool dating back to W8, which also handles Store app licenses. So it's not packaged under the KMS component. Without ClipUp.exe, ClpSvc can't receive those licensing requests that normally flow into it.

For legitimate KMS activation, a PC contacts a locally managed KMS server.

"Digital activation" only applies to retail keys or MAK licenses stored on MS back-end servers. KMS is self-managed, your site is allowed to administer the license pool on the local KMS server without having to report everything to MS. Those are two different workflows.
 
Gents. I actually use KMS to activate it. Without the clipup file it gives me the following error.

[REDACTED] Per forum rules, KMS activation scripts cannot be discussed here.
 
Last edited by a moderator:
Gents. I actually use KMS to activate it. Without the clipup file it gives me the following error.

[REDACTED] Per forum rules, KMS activation scripts cannot be discussed here.
So, you need this file for KMS activation (not using it, I hadn't looked)
The best thing is to protect this file in the compatibility menu of the Components page I think
 
ClipUp has nothing to do with KMS activation, or activation per-se
it only migrate downlevel genuine licenses (KMS, Retail, OEM..) to Digital License

e.g. before Win 7-8.1 keys support were removed in 2023, genuine Win 7-8.1 key can be installed on Win 10, and ClipUp will convert it to compatible HWID-based license
 
Back
Top