The government is moving to require computer vendors to boot a Russian operating system as a secondary option, a proposal reported by Kommersant and tied to a draft decision from the Ministry of Digital Development. The plan envisions a layered boot sequence that would let a device start with an officially sanctioned Russian OS, while still allowing access to other software. In practical terms, this would affect how new devices are configured and presented to buyers, potentially reshaping what customers see as the default experience when they first turn on a machine.
Today, many imported computers ship with a foreign operating system preinstalled. Vendors occasionally resist installing Russian software directly, arguing it lacks the necessary official authorization. Yet legal counsel warns that under the forthcoming rules, sellers could be held responsible for breaches of terms and, in some cases, their inventory or property might be at risk of confiscation. The tension between commercial freedom and regulatory compliance could complicate how retailers and distributors approach pre-installations and post-purchase support.
Alexei Smirnov, who chairs the board of Basalt SPO, argues that such a mandate could help curb the distribution of devices with unauthorised or counterfeit Windows variants that do not receive timely security updates. He contends that ensuring a native operating system is present at the outset can bolster device security and trust in the supply chain. On the other hand, Anton Guskov, a representative from RATEK, cautions that mandatory pre-installation of Russian systems may drive up costs for manufacturers and could introduce technical challenges, including compatibility issues with certain hardware or software components and longer time-to-market for new models.
Back in November 2022, the Ministry of Digital Development highlighted three native operating systems as potential candidates for pre-installation: Astra Linux, Viola, and Red OS. All three are built on Linux foundations and are designed to run on a wide range of devices while offering localized support and updates. The choice of these operating systems reflects a broader policy objective to fortify national digital sovereignty, streamline maintenance, and potentially reduce reliance on foreign software ecosystems. The long-term impact on software innovation, system resilience, and user experience remains a topic of ongoing discussion among policymakers, industry players, and consumer groups.
In related industry commentary, past reporting raised concerns about the performance and repairability of certain widely used devices in school environments abroad. Specifically, there were observations about Chromebook laptops deployed in some U.S. schools that experienced rapid breakdowns and faced limited repair options. These observations feed into a broader debate about hardware longevity, total cost of ownership, and the role of vendor-supported software ecosystems in public education. As nations weigh their approach to domestic operating systems, the focus often returns to reliability, security updates, and the practical realities of maintaining devices across diverse settings.