[Research] Win 10 in S mode - detection on mozilla.org #6367
Description: Currently mozilla.org is unable to detect visitors to the site that are using Windows 10 in S mode to do so. This project
Problem statement: Users of Win 10 in S mode are unable to install Firefox, being limited to installs only via the Microsoft app store. This limits a large potential set of Firefox users.
UA string from a Levono laptop I obtained running Windows 10 S, running Microsoft Edge:
Firefox install flow:
Searched for "Download Firefox"
After ignoring all the Edge messaging in the search results, I clicked the moz.org link and downloaded as normal. Once the download had completed, I double clicked the installer .exe, which was then blocked by this message:
Because I wanted to install Firefox, I clicked the "See how" link, which then opened this screen:
This screen told me absolutely nothing about what I wanted to know. In frustration, I tried double clicking the Firefox installer again. This time, I got a different message:
This time, clicking the "See how" link took me to somewhere more useful:
I can only assume the first message I got was because it was the first time I had tried to install another browser.
Install flow for Chrome:
Searched for "Download Chrome"
Again, some pretty agressive messaging for Edge. I ignored it, and went to download Chrome:
Google does not detect Windows 10 S in any way, much like mozorg. There is no specific messaging shown to Edge users:
Double clicking the Chrome .exe installer results in the same message shown to Firefox:
Comparison between user agent strings:
Window 10 Pro:
Windows 10 S:
Conclusion: there is no identifiable difference, so using UA sniffing to identify Windows 10 in S mode is not going to be possible.
moved this from In Progress
to In Review
in Websites Durable Team Project Sprint Board
Jan 4, 2019
The Firefox product team have reached out to Micorosoft directly on this. There is a proprietary API in Edge that may give us the information we need:
"I believe you are looking for 178 or 179 in the “unlocked” value."
I'm going to try and test this out on a device and report back. It's currently not clear if this API will still work when Edge moves to Chromium.
I've tested the above out on a laptop running Windows 10 Pro in S mode, in Edge 17 and I see the following:
On a regular Windows 10 VM I see the following:
Notes of interest:
The value returned is from https://docs.microsoft.com/en-us/windows/desktop/devnotes/wldp-windows-lockdown-mode