Microsoft explains how win32 apps run on Windows 10X

Although Microsoft’s new Windows 10X operating system focuses primarily on UWP and web applications, the company is well aware of the importance of traditional Win32 to older users. So when the new operating system is released, Microsoft indicates that Windows 10X will enable support for Win32 applications in a special container. Now, thanks to the information WalkingCat shares on Twitter, we have a deeper understanding of the bottom layer of the operating system.

Microsoft explains how win32 apps run on Windows 10X

Video screenshot (from: Microsoft, via Neowin)

For Win32 applications, Microsoft will use container technology similar to the Windows Linux subsystem. Each Win32 application can run on the same container, which supports almost all Win32 applications.

However, due to containerization, Win32 applications will not be able to modify system files or the registry, so users of some software may run into some trouble, especially if they cannot be manually installed by executable files (such as driver software).

Microsoft explains how win32 apps run on Windows 10X

Even so, Win32 support makes it relatively easy for most traditional applications to use on Windows 10X because some content is shared with the host operating system (such as the path structure of the folder is the same as you expect).

In addition, users can share files between hosts and containers, but not private application data. Because common hardware (such as keyboards, mice, graphics, audio, etc.) all have “shortcuts” to the host, they work fine.

Users can enable privacy-sensitive hardware, such as webcams and microphones, at their discretion, which is equally effective in containers. If you allow access to win32 applications, each Win32 application can access the hardware.

Microsoft explains how win32 apps run on Windows 10X

Microsoft also mentioned the adaptation of the Windows 10X system tray, which means that users may not be able to see some icons of the Win32 app because it is no longer part of the new system.

The good news is that Microsoft hasn’t removed the API associated with the system taskbar icon, so trying to use this feature for a Win32 application won’t crash or have other problems (just don’t see the icon).

Finally, there are existing MSIX and native containers that provide a more powerful installation and unloading experience, a higher level of trust, and optimal performance than Win32 containers.

Of course, applications that are compatible with MSIX containers can also run in regular Win 32 containers.