Legal downloads?

Hey there we go :). I’m going to side on the IoT core exemption coming into play here however anything outside of testing should probably still use a full license since this is full Windows and not IoT or otherwise not covered under the IoT core license agreement.

Probably. Interestingly, it does not activate until the internet is connected. Once I plug in the internet though, it self-activates. Which means that it might not be a platform-side exemption. I rather bet that it is telling Microsoft’s servers, “I’m running on a BCM2837 with the generic license key!” Microsoft servers then respond, “You’re on IoT Core, so you’re activated!”

However, there is one problem with this theory. Windows activation also sends the version of Windows you are running (e.g. IoT Core, Windows 10 Pro, Windows 10 for Workstations, etc.) Why MS servers are giving free pass to any version of Windows doesn’t quite line up.

Unless, of course, someone in Microsoft was experimenting with Windows 10 on a Pi before us. Maybe…

Interesting indeed… The only thing I can think of is that maybe their activation logic for IoT simply does not care about the reported version. MS engineers probably never intended on variation like this but they also partner with Qualcomm being a primary focus. It’s possible they will fix it eventually - they are aware now with your activation record at least.

Or not. I’m sure MS isn’t paying attention to every single activation.

Still, shout out to Microsoft: If you could leave it this way, that would be good! Better yet, if you could make Windows 10 run officially on the Pi, that would be great!

I activated Windows on mine with a MSDN key. Depending on how the UUID is constructed, this might have caused everybody to get activated…

Can you run wmic path win32_computersystemproduct get uuid in the command prompt and check what UUID is returned? Mine is 33695052-0000-0000-0000-000000000000 - if everybody gets this UUID, this would be why Windows is activating.

I ran it…

33695052-0000-0000-0000-000000000000

Which is exactly the same…

The Rearm count is 1001. And besides, MS wouldn’t allow more than a few Pis to be activated at once. If it really was just the UUID, how come nobody has come along and made a UUID changing tool for Windows?

My extended PID and activation IDs are very long and quite random looking. [My point is, it can’t be just a UUID. That’s too easy!]

Try slmgr.vbs /dlv in the command prompt. We can see if our IDs match.

BIOS UUID is one of the main things activation looks at (not the only thing - network card MAC is also checked, although I wouldn’t be surprised if that’s ignored for USB NICs).

Compared with your picture from above, my application ID and extended PID are the same, but activation ID is different. Note that I activated Windows 10 Pro N, however automatic activation doesn’t care about that (if you had regular Pro activated on a system, Pro N will activate if you install it without a key).

Weird…

But at the same time, this seems really… Windows Activation can’t be this easily fooled, especially not by accident. It’s too easy.


Somebody else just auto-activated. Build 17663.

Yes I activated 17134 then ran Windows update last night updates installed fine and have an activated win 10 Pro. Still has a stamp bottom corner “TEST MODE” so that might have something to do with it?

That is for drivers, not activation.

My mistake as in same area on screen as build info thought it was related… Same way unactivated Windows used to have an on screen nag in that area