Microsoft is optimizing the Chromium experience on Windows Core OS

Rumor has it that Microsoft has not given up on the so-called Core OS, a modular version of Windows 10 designed to accommodate devices of different sizes. In addition to cheap netbooks like Chromebooks, Core OS also works on dual-screen/folding devices, as well as HoloLens 2 extended reality headsets. Many see WCOS as a successor to Windows OneCore and the foundation for the development of Windows 10X.

Microsoft is optimizing the Chromium experience on Windows Core OS

A feature of Windows 10X is the ability to safely run Win32 applications in a sandbox environment to support most of the desktop applications that users love.

In other words, the container of Windows 10X runs smoothly with classic Win32 applications such as Chrome, Edge, and Slack, and the software runs in a different sandbox environment from the system, securely isolating them from the core components of the operating system.

Although Microsoft doesn’t seem ready to talk about WCOS’s future vision, it appears to be actively developing, even finding a reference to the operating system in Chromium Gerrit.

We found a reference to WCOS in a June 8 submission by Microsoft Edge engineers to Chromium Gerrit, but it hasn’t been the subject of much attention.

Microsoft is optimizing the Chromium experience on Windows Core OS

As shown in the figure, Microsoft seems to be optimizing the Chromium experience by fixing problems with App Containers to make it work better on WCOS.

Because on WCOS systems, the number of characters in the application container is limited to 50. However, Chromium currently provides an AppContainer name that is larger than 50 characters, so the development team modified the name of the sandbox process.

AppContainer is known to provide a secure sandbox environment for Win32 applications and to allow applications access to resources specifically awarded to them.

Thanks to the latest changes on WCOS and Windows 10X, it will be more difficult for an attacker to perform outside of the allocated resources.

Finally, Microsoft notes in the support ingress that the AppContainer environment for Win32 applications isolates it from accessing hardware, files, registration labels, and other core areas with special permission.