Windows is an old operating system and several core components of the operating system make it impossible for the platform to adapt to newer devices. Microsoft is aware of these issues and the software maker is working on a new and modular version of Windows 10 which would be far more flexible and lightweight.
This new operating system is allegedly called Windows Core OS – a modular version of Windows 10 streamlined for performance and security. The Windows Core OS is supposed to power the long rumored Surface Andromeda (dual-screen device) and the Surface Hub 2. According to reports, the company will not bring WCOS (Windows Core OS) directly to laptops, 2-in-1s, or desktops. Instead, it will arrive with the dual-screen Andromeda and the Surface Hub 2.
A new job posting on LinkedIn has given us a closer look at Windows Core development plans. The job post for a Software Engineering Manager was posted almost 11 days ago and it’s all about Windows Core OS.
“Do you love working on devices? Do you dream of integrating new software experiences with new hardware? If so the Device Platform team may be for you. The SiGMa Device Platform (DPlat) team owns the definition and delivery of Windows Core OS (WCOS), which is the OS shared across all new devices. DPlat also delivers the modern driver platform, including the tools to create & validate drivers along with driver flighting & services system for all versions of Windows. Finally, DPlat owns ensuring that Windows is a viable platform for key silicon partners, and for OEMs by doing hardware co-engineering during the development of new operating systems (e.g. WCOS) to ensure that version of Windows is ready for the ecosystem when it releases,” Microsoft explains.
According to the job posting, the 50+ person team is organized into the following teams:
- DnD: The Devices and Drivers team owns the Dev ice side PNP stack, driver installation and driver servicing, along with some aspects of device imaging.
- DDX: The Driver Developer Experience team owns the developer experience for writing drivers integrating with visual studio including eWDK, WDK, and ADK, and the tools for verifying driver behavior (including DV, DV TiP, DevFund/SysFund, and ST) .
- OneCore: The OneCore team Owns WCOS SKU and OS layering efforts (GameCore, Onecore/OnecoreUAP) APISets, Flexible Links, Windows Compositional Database (WCD), and driving cross org WCOS efforts, like state separation.
- HLK: The Hardware Lab Kit team owns the test harness and content coordination across all Windows SKUs along with coordination Hardware Dev Center for certification driver submission.
- DDC: The Differentiated Devices Co-engineering team owns enablement work between new device form factors and emerging versions of Windows (OneCore, WCOS, etc.) in order to inform the changes needed to support OEMs first use of the same emerging version. The team also drives first time SW/HW integration efforts of nascent versions of Windows running on innovative HW designs.
- QCC: The Qualcomm Co-engineering team works closely with Qualcomm on strategic initiative between QC and Microsoft. Supporting Reference platforms; fixing driver dependency issues; migrating driver packaging; fixing update issues
It’s worth noting that the Windows Core OS is not something that customers can use and it’s an internal platform only. The Windows-powered products that will be made using WCOS could be unveiled next year.