: Finding different Windows XP Service Packs via User-Agent string I am planning to get rid of the SHA1 certificate signing algorithm in our certificates and switch over to SHA-256. Problem is,

@Kevin317

This MSDN article documents the nomenclature used for user agents. Appears the feature token can be used in conjunction with the platform token to make some determinations.


Feature tokens

Certain optional components can also modify the user-agent string; this next table shows common ones. Be aware that many other
applications also modify the user-agent string. Because of this, a
comprehensive list is not possible. If you find additional tokens in
your user-agent string, investigate them in more detail.


The table specifically notes SV1 as a signal for a specific service pack.

However, the document explicitly states that a comprehensive list is not available.

UserAgentString.com collects User-Agent strings but I do not see any correlation to SP versions.

I have not been able to find an official Microsoft reference for what feature tokens were added to the various service packs. But I do know this appears on their blog from time to time:

The IE7 User-Agent String

The Internet Explorer 8 User-Agent String (Updated Edition)

Perhaps with some digging you can find the others.

Vote Up Vote Down

@Ravi8258870

If this is possible, I think your only option is to dig into .NET CLR version history. I believe the different Service Packs could have been served different .NET CLR versions. Unfortunately the user agents doesn't show the last digits (1.1.4322.????).

If one can install any .NET CLR version on any Windows XP version. Then the answer is no. You can not tell Service Pack version from the User Agent string.

Vote Up Vote Down