AboutChromebooks’ new WSL statistics roundup correctly identifies the 16.8% professional figure and the corresponding 15.9% personal-use figure. Stack Overflow’s results page says 31,569 respondents answered its operating-system question. The crucial qualification is in Stack Overflow’s methodology: its 2025 sample was recruited primarily through Stack Overflow-owned channels, making it a self-selected group tilted toward people already engaged with the site.
For Windows developers and IT administrators, that still makes the result useful. It shows that WSL is a routine part of the toolkit for a substantial minority of a large, technically engaged developer sample. What it does not show is how many corporate endpoints have WSL enabled, how many run WSL 2 rather than WSL 1, or whether those users are active beyond an initial installation.
The 16.8% figure is a developer-workflow signal
Stack Overflow puts Windows at 49.5% for professional use in the same 2025 operating-system results, while Ubuntu reaches 27.7% and WSL reaches 16.8%. Those categories cannot be interpreted as mutually exclusive slices of a single desktop market. A developer can use Windows as the host OS, Ubuntu in WSL for a project, and native Linux elsewhere during the same working week.
That overlap is the point of WSL. It is a compatibility and development layer that allows Windows users to run Linux distributions and command-line tools alongside Windows applications. Counting WSL separately gives it visibility that conventional operating-system market-share reports cannot provide, but it also means WSL should not be added to Windows or Ubuntu percentages to create a combined “Linux developer” number.
Stack Overflow’s wording for the operating-system question refers to the primary operating system in which respondents work, while its published presentation breaks results into personal and professional use. The public results make clear that WSL is treated as a distinct response category, but they do not provide the cross-tabs needed to answer the more useful question for Windows shops: how many respondents use both Windows and WSL on the same machine.
That missing intersection matters. A claim that “one in six developers use WSL” is defensible only when it is completed with “among respondents to this survey.” A claim that one in six developers have moved from Windows to Linux is not supported by the survey at all.
Microsoft has activity metrics, not adoption telemetry
Microsoft’s strongest recent public indicator is about project contribution, not user count. In its June 2 Build 2026 announcement, Microsoft said that community contributions to WSL had grown to more than 200 pull requests per month after the project was open-sourced at Build 2025.
That is meaningful evidence that WSL has become a more active open-source project. It suggests the codebase is receiving external engineering attention at a pace that matters for bug fixes, features, distribution integration, and the long-term maintainability of the Store-delivered WSL package. It is also consistent with Microsoft’s effort to position WSL as part of a broader Windows development stack alongside Windows Terminal, WinGet configurations, container workflows, and local AI tooling.
It is not evidence of 200 new users per month, let alone of broad enterprise deployment. Pull requests measure proposed source changes; a small number of organizations or individual contributors can create a large share of them. GitHub stars, forks, open issues, watchers, and release counts have the same limitation. They describe attention around the repository, not installed copies of WSL.
AboutChromebooks’ repository snapshot also needs a date correction. Its timeline describes WSL 2.7.10, published on June 26, 2026, as the most recent build in the sequence. Microsoft’s public GitHub releases page has moved on: WSL 2.7.11 appeared on July 24, and newer 2.9-series pre-releases, including 2.9.9, were published on August 25. The June 2.7.10 release can still be cited as a historical release, but it is no longer a current-project marker.
Microsoft has not published a public WSL install base, active-device count, or distribution split. The GitHub data and the Build pull-request claim should therefore be read as evidence of project momentum, not a substitute for adoption telemetry.
The Windows addressable base is broad, but it is not a WSL count
StatCounter’s July 2026 desktop figures put Windows at 71.18% of sampled worldwide desktop pageviews, and Windows 11 at 68.93% of those Windows pageviews. That tells us WSL has access to an enormous Windows desktop population. It does not tell us how many of those systems have virtualization enabled, are eligible under organizational policy, have the Microsoft Store available, or have a developer who needs Linux tooling.
Microsoft Learn lists Windows 10 version 2004, build 19041, or later, and Windows 11 as the baseline for the streamlined wsl --install experience. Microsoft’s documentation also says the command enables the required Windows features, installs the latest Linux kernel, selects WSL 2 as the default for new installs, and installs Ubuntu by default.
The practical implication is that compatibility is no longer the dominant barrier for most modern Windows desktops. Administration is. In an unmanaged home environment, enabling WSL is usually a developer choice. In a managed enterprise, it may involve virtualization policy, endpoint-security controls, Microsoft Store restrictions, proxy configuration, local-admin permissions, and rules governing imported Linux distributions and virtual hard disks.
StatCounter’s figures should also be handled carefully. The company measures web pageviews from its tracking network, not device inventory. Its desktop market-share tables are a useful broad indicator of the Windows opportunity, but they cannot establish WSL penetration or enterprise readiness.
Ubuntu’s default position has operational consequences
Ubuntu is central to the WSL story because Microsoft’s default installation path deploys Ubuntu unless the user specifies another distribution. Administrators can change that choice, and users can install or import other distributions, but the default matters because it shapes the first Linux environment many Windows developers encounter.
Canonical has leaned into that position. It announced general availability of Ubuntu Pro for WSL on December 2, 2025, describing a supported and managed Ubuntu offering for Windows environments. The product is aimed squarely at organizations that need security maintenance and administrative control around developer Linux instances, rather than informal local setups.
For IT teams, the relevant question is no longer merely whether developers use WSL. It is whether the organization knows which distributions are present, who owns their package and kernel update path, whether developer workloads can reach internal services, and where source code is stored. A WSL distribution is local developer infrastructure with its own userspace packages, credentials, SSH keys, language runtimes, and dependency chain. Treating it as a consumer app creates blind spots.
Microsoft’s Build 2026 announcement of WSL containers adds to that administrative pressure. Microsoft said the planned feature would give Windows a built-in way to create, run, and interact with Linux containers, with policy-based enablement and management promised for enterprises. The company described it as coming to public preview, rather than as a generally available capability. Organizations should not build production policy around the announcement alone, but it indicates why WSL’s governance model is becoming more important.
The defensible 2026 conclusion is modest: WSL is visibly established in the workflows of a meaningful portion of Stack Overflow’s developer sample, its open-source project is active, and Windows supports the standard installation path across most current desktop versions. There is still no public metric for how many people actually run WSL.
Until Stack Overflow publishes newer survey results with clearer overlap data—or Microsoft releases installation and activity telemetry—the 16.8% figure should remain what it is: a useful survey signal, not a global WSL market-share statistic.
