StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PODetecting Visual Studio license type / distribution channel
text
Body
copied!<p>There is plenty of information throughout the net on how to detect Windows license type and distribution channel using PID (that can be found in <code>HKLM\SYSTEM\Setup\Pid</code> registry key) and ProductID (that can be found in <code>HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion</code>).</p> <p>However, there is quite little information on how to detect what kind of licensing is used to install other Microsoft products.</p> <p>Namely, what i need to determine is which ones were installed using MSDN subscription license, and which were installed using other license types.</p> <p>I've managed to find some info on Office flavors by analyzing product GUID (found in <code>Uninstall</code> registry branch):</p> <ul> <li><a href="http://support.microsoft.com/kb/230848">Office 2000</a></li> <li><a href="http://support.microsoft.com/kb/302663">Office XP</a></li> <li><a href="http://support.microsoft.com/kb/832672">Office 2003</a></li> <li><a href="http://support.microsoft.com/kb/928516">Office 2007</a></li> <li><a href="http://support.microsoft.com/kb/2186281">Office 2010</a></li> </ul> <p>However, all those articles only distinguish between these release types:</p> <ul> <li>0 Volume license</li> <li>1 Retail/OEM</li> <li>2 Trial</li> <li>5 Download</li> </ul> <p>Furthermore, i could not locate any feasible information about other products. Namely, Visual Studio... (which is the one i am interested in the most).</p> <p>To clarify: I do <strong>not</strong> need to obtain a <strong>license key</strong> (which i already found several ways of detecting while seeking for the information i need), my interest is solely in detecting what kind of <strong>license type</strong> was used to install the application.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload