Multi-OEM/Retail Project {MRP} - Mk3

The Reason Code database is now at an eye watering 375 codes and descriptions , took some tracking down most of them!

I think it covers a very large proportion of errors that can occur in the Software Licensing/Activation side.

Considering 90%+ should not occur, so they never be seen in normal circumstances - unless you are tampering with the WAT or other License files.

They are added to the next version of MRP and QT.

 

The Query Tool v34 has been uploaded and first post password has been updated.

Quick Summary

Added more License Reason Codes/Text (376 now). Most may never be seen but they are there for those odd occasions.

On the display screen the Reason Code and Text is now on separate lines, the saved report they are on one line. This is to allow for extra wording without messing up the display version.

Other minor code tweaks.

 

If there was a problem in the KMS side, a Reason Code would of been displayed with a possible cause of failure. The code/texts shown are for a Genuine KMS system but they might get displayed for the 'MDL Solutions' in some circumstances.

Such as:

Code:

RPC Server unavailable. Firewall settings are not configured on the KMS host.
DNS Name does not exist. The KMS client cannot find KMS SRV RRs in DNS.
No records found for given DNS query. The KMS client cannot find KMS SRV RRs in DNS.
The count reported by your Key Management Service {KMS} is insufficient.
The Key Management Service {KMS} is not enabled.
The Key Management Server {KMS} is not activated. KMS needs to be activated.
The specified Key Management Service {KMS} cannot be used.
Virtual Machine Found. The Key Management Service {KMS} is not supported in this mode.
The Key Management Service {KMS} determined that the requested timestamp is invalid.
The Key Management Service {KMS} could not be contacted.

 

The method i obtain the OEM / RETAIL / VOLUME_KMS-MAK is done via a slmgr.vbs /DLI call and parse the result with a FINDSTR i could not find another way that was reliable.

Code:

CScript slmgr.vbs /dli >"ChanActType.txt"
findstr /I "\<RETAIL\>" "ChanActType.txt" >nul
IF NOT ERRORLEVEL 1  SET "RETOEMKMSMAK={Retail}"

findstr /I "\<OEM_DM\>" "ChanActType.txt" >nul
IF NOT ERRORLEVEL 1  SET "RETOEMKMSMAK={OEM_DM}"

Others:
VOLUME_KMSCLIENT, VOLUME_MAK, OEM_COA_NSLP, OEM_SLP, OEM_COA_SLP

The reason codes only are for 'errors' as such. Why m$ decided to use one for a store/DL is a puzzle as all other codes/text are for problems.

I had the DL text originally showing about a store license but changed it as all info i found mentioned a Digital License which is what is shown on the Activation screen in the Settings App. I just kept it all same wording.

Reason Code 0000000 is from what i can gather about a valid Product key.

 

For Servers there is a whole new set of codes, for shutdown, BSOD's etc, which for the QT/MRP use is not required and i not want to spend another x days finding all those out which in most cases won't be necessary anyway. Plus those that know/maintain Servers would most likely understand those so i have decided not to pursue that side.

Some standard reason codes don't have any actual text as such just some cryptic wording, those i had to word in a different way to make sense to the average person.

Such as:
0xC004D00C
SL_REMAPPING_SP_PUB_API_TOO_MANY_LOADED_ENVIRONMENTS

0xC004D012
SL_REMAPPING_SP_PUB_API_BAD_GET_INFO_QUERY

The above reference to Software Licensing and Security Processor!

 

You need to login to view this posts content.

 

I found that website by pure luck (or accident not sure which ), yes a LOT of codes, and i still don't think they cover every code m$ has within the OS's.

It is a complicated area as you can see , some are covered by slmgr /dli others are reason codes it took me a while to get the system i have in place to work as it does, i know it not perfect but it does work 95%+ of the time as it should.

Yes the Store/DL is a strange one. If you buy say a App from the M$ Store technically you can check that app's license which will return the 4004F401 (store license) for it, not sure how it can be done but in theory that is what would get returned.

The OS isn't really a App but it can be worded as a Store Licence (if the key was bought via that), or a Digital License if upgraded from a valid previous OS (7/8.x), m$ certainly like to make things overly complicated. Either that or it just a sloppy forethought process and a 'bodge' to get things to 'work' - who knows.

I am guessing the 'Store License' wording was changed because of the changes at the end of the year about the 'free' upgrade that still works as after the time is up then only a purchased license from the Store, (or retail bought from a shop)/Pre-installed OEM MSDM computer will be the normal way to obtain a genuine version.

 

I fully agree, but so far this has been a challenge i have not 'mastered' (yet) , I don't give up easy, i may have a rest for a while, but i return with a vengeance and beat the living of it until i find a way.

 

It may not be a simple registry key change! It may even be a file that is downloaded that is checked/changed which indicates to the OS what type of license is installed/used. Or even a combination of the two.

I think some of the information could be found within the Windows setup files as they seem to do some checks during installation (offline and online), more so with the latest insider builds (rs4). Sadly i not have the time or tools to check if this is the case.

I do know it now pre-checks the MSDM key even if i explicitly not insert the key ie if the OS installed is Pro and the MSDM key is for Home, in MRP i not insert the key (because it won't activate). M$ are changing things behind the scenes and getting a bit more clever!

 

CompositionED is not a reliable method as such as @s1ave77 found out, so we use a WMIC method to obtain the correct information, as License switches ie just changing a key can cause some confusion in the results. That is why the QT can put up a message that a possible License switch has occurred.

ProWS is a odd ball one at the moment as using just the key to change from say Pro does not give the full WS 'experience', converting Home to ProWS via DISM does change it and the CompositionID will say ProfessionalWorkStation. As it is not a General Release as such as in a ISO (you have to 'create' it), i have not continued with much about it, my test pc has a DL for ProWS obtained via the Insider (old version) then upgrading etc.

When it becomes available in the main ISO's and updates work for it then i will do more tests on that version. For now its not a priority.

 

As we have gone off topic i will just say again, the license switch using just the key does not always give a 100% ProWS system!

See the ProWS thread and you can see some have found this out. https://forums.mydigitallife.net/threads/discussion-windows-10-pro-for-workstations.74909/