Internet Explorer 10 User Agent Strings On Windows 8 64bit

Question

I've been looking at Internet Explorer User Agent strings on Windows 8 64bit and according to its different usages and modes, its user agent string is as follows:

Application	Environment	32/64 bit	User Agent String
Internet Explorer	Metro	-	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0)
Javascript Application	Metro	-	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Trident/6.0;)
C#/VB Application	Metro	32bit	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
C#/VB Application	Metro	64bit	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0)
Internet Explorer	Desktop	32bit	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; WOW64; Trident/6.0)
Internet Explorer	Desktop	64bit(1)	Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.2; Win64; x64; Trident/6.0)
WPF Application	Desktop	32bit	Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.2; WOW64; Trident/6.0; .NET4.0E; .NET4.0C; Tablet PC 2.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 2.0.50727; Zune 4.7; InfoPath.3)
WPF Application	Desktop	64bit	Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.2; Win64; x64; Trident/6.0; .NET4.0E; .NET4.0C; Tablet PC 2.0; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET CLR 2.0.50727; Zune 4.7; InfoPath.3)

(1) Needs to be enabled for each security zone.

Analyzing the above table I conclude that:

1. Metro Internet Explorer is always a 64bit application on 64bit Windows 8.
2. Javascript Metro Style Applications don’t announce if they are 32bit or 64bit.
   1. They look like they are running on a 32bit Windows 8.
3. Desktop Internet Explorer retains the same behavior introduced with Internet Explorer 8.
4. Metro Style C#/VB Applications hosting the web browser (WebView control) exhibit the same behavior as Internet Explorer.
5. Desktop WPF Applications hosting the web browser (WebBrowser control) retain the same behavior introduced with Internet Explorer 8.
   1. This can be overriden by defining the document compatibility on the server or setting the browser emulation feature for the application on the client.

Any thoughts or findings on this?

---

Paulo Morgado