Activation troubleshooting

Superfly said:

MS messed-up with Win 10 MAK's - they are supposed to be removed (I posted before about that before.. I need to search for the post .. I think in the ShowKey thread).. it's all gone wonky..

I almost posted this there. Kind of wondering if they changed how MAK's activate with 1809. I can't really test it, as all my PC's already have multiple DL's for Enterprise. In VM I guess? I've never ever setup a VM install.
This is the first time I've ever installed LTSC. It didn't really appeal to me. But with all the bugs lately I thought I'd give it a go and see if its actually usable. No forced upgrades twice a year.

EDIT: Calling it quits for tonight. I'll chack back tomorrow. Take care. =)

alphanumeric said:

I almost posted this there. Kind of wondering if they changed how MAK's activate with 1809. I can't really test it, as all my PC's already have multiple DL's for Enterprise. In VM I guess? I've never ever setup a VM install.
This is the first time I've ever installed LTSC. It didn't really appeal to me. But with all the bugs lately I thought I'd give it a go and see if its actually usable. No forced upgrades twice a year.

EDIT: Calling it quits for tonight. I'll chack back tomorrow. Take care. =)

No prob, bud.. thanx for your input.. nice to get someone else getting the same issue.. I was bewildered... LOL

alphanumeric said:

I almost posted this there. Kind of wondering if they changed how MAK's activate with 1809. I can't really test it, as all my PC's already have multiple DL's for Enterprise. In VM I guess? I've never ever setup a VM install.
This is the first time I've ever installed LTSC. It didn't really appeal to me. But with all the bugs lately I thought I'd give it a go and see if its actually usable. No forced upgrades twice a year.

EDIT: Calling it quits for tonight. I'll chack back tomorrow. Take care. =)

See here.. ShowKeyPlus - Page 95 - Windows 10 Forums

Thanks all, this thread made for a very interesting read

Superfly said:

See here.. ShowKeyPlus - Page 95 - Windows 10 Forums

I'll run showkey on that PC latter on today and post the results in the other thread. Or here if you want. The activation screen showed the PID and the last five of the product code. I didn't check but I assumed it matched the MAK key I used. I will double check that latter on.

Superfly said:

FYI for those wondering why Windows will suddenly get de-activated.

The Scheduled Task that checks licencing is SvcRestartTask - it is triggered daily.

It runs "C:\WINDOWS\system32\sppsvc.exe" as a service.

Code:

Enables the download, installation and enforcement of digital licenses for Windows and Windows applications. If the service is disabled, the operating system and licensed applications may run in a notification mode. It is strongly recommended that you not disable the Software Protection service.

Therefore, any "non-enforcement" eg. a non-reply from the Activation server would have the same effect as the service not running at all.

Well after deleting the task Windows went nuts (both SPP and Clip) see the event log errors below.

Activation was unaffected, however

Code:

ToolVersion: 10.0.17763.1
LicensingStatus: SL_LICENSING_STATUS_LICENSED
LicensingStatusReason: 0x4004F401
LocalGenuineState: SL_GEN_STATE_IS_GENUINE
LocalGenuineResultP: 1
LastOnlineGenuineResult: 
GraceTimeMinutes: 0
TotalGraceDays: 0
ValidityExpiration: 
ActivePartialProductKey: KD782
ActiveProductKeyPid2: 00342-50527-80868-AAOEM
OSVersion: 10.0.17763.2.00010100.0.0.048
ProductName: Windows 10 Pro
ProcessorArchitecture: x64
EditionId: Professional
BuildLab: 17763.rs5_release.180914-1434
TimeZone: South Africa Standard Time(GMT+02:00)
ActiveSkuId: 2c293c26-a45a-4a2a-a350-c69a67097529
ActiveSkuDescription: Windows(R) Operating System, OEM_DM channel
ProductUniquenessGroups: 55c92734-d682-4d71-983e-d6ec3f16059f
ActiveProductKeyPKeyId: 03f72807-7684-0de5-c18f-ed07cfc7a7a8
ActiveProductKeyPidEx: 03612-03425-052-780868-02-2057-17763.0000-2672018
ActiveProductKeyChannel: OEM:DM
ActiveVolumeCustomerPid: 
OfflineInstallationId: 099631283945135237840496505694061969675891980664222330018234885
DomainJoined: false
ComputerSid: S-1-5-21-2898950816-864432406-675651644
ProductLCID: 2057
UserLCID: 7177
SystemLCID: 2057
CodeSigning: SIGNED_INFO_PRS_SIGNED
ServiceAvailable: true
OemMarkerVersion: 0x00020001
OemId: DELL  
OemTableId: CBX3   
OA3ProductKey: *****-*****-*****-*****-KD782
ActivationScenarioCode: 
ProductKeyCode: 
Manufacturer: Dell Inc.
Model: Latitude E5470
InstallDate: 20180924185653.000000+120
Result: PASS
TamperedItems: 
ServerProps: 
OA3xOriginalProductId=00342-50527-80868-AAOEM
OA3xOriginalProductKey=*****-*****-*****-*****-KD782
SessionId=LicensingDiag
TimeStampClient=2018-12-01T11:27:38ZsttgnhtxBu5ajNizfDf+FpaJhYtmRmesoZsOOJT7Ps9kPhUn+mYeMUNl4+9K+96c0dIBrw1nTpUmp9hsw6vaqmKAPZ6DDzjH/1LmCZTaqN8RDQBH5te0icLamAxiTvkqbdb1PcuzcZFKKxs5Mt2247HK2G0rjyS896xKLUYL00s=
 
--------- SPP Event log data ---------
Failed to schedule Software Protection service for re-start at 2118-11-07T11:27:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:26:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:26:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:25:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:25:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:24:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:24:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:23:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:23:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:22:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:22:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:21:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:21:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:20:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:20:29Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:19:59Z. Error Code: 0x80070002.
Failed to schedule Software Protection service for re-start at 2118-11-07T11:19:29Z. Error Code: 0x80070002.

.... it goes on for billions of entries 

--------- Clip Event log errors ---------
License install failed for license type: 1
Result code: 0xC03F6601
License install failed for license type: 1
Result code: 0xC03F6601
License install failed for license type: 1
Result code: 0xC03F6601
License install failed for license type: 1
Result code: 0xC03F6601
License install failed for license type: 1
Result code: 0xC03F6601
License install failed for license type: 1
Result code: 0xC03F6601

... also a billion such entries

.. and yup, MS are in 2118 already... LOL

Hi Superfy,

cant check on my IP build, but is there another trigger in the Windows Activation Technologies,
(on W7 it triggered KB971033, ie the 90 day rule)

Roy

hawkman said:

Hi Superfy,

cant check on my IP build, but is there another trigger in the Windows Activation Technologies,
(on W7 it triggered KB971033, ie the 90 day rule)

Roy

Not sure Roy, I will need to dig a bit... I doubt there will be >1 trigger tho'...

BTW... How's things going with Win 7 activation? Is @NoelDP still being kept busy? LOL

It was humbling him handing me the mantle at Eight Forums..

Send him my best - he was an inspiration to me (and you I'm sure)

To test the theory that VL media installations activate with the VL key rather than a DL.

I installed Pro VL and got the default VL key...



Then changed to MAK key - it then activated with a DL anyway

My only install that doesn't / didn't activate with a DL is Windows 10 Enterprise LTSC 2019. Activated with a MAK key.
MAK and Retail keys are all I have access to via MY Visual Studio Enterprise subscription. I have no way to activate VL media via KMS.