Microsoft: Old Windows loses virtualization-based security enclaves
Microsoft is cutting back on functions: Virtualization-based security enclaves are being removed, as well as features for maps displays.
(Image: Curt Bauer / Shutterstock)
The functions that Microsoft is now relegating to the scrapheap have unwieldy names: Virtualization-based Security Enclaves (VBS) and Windows UWP Map Controls and associated APIs. These are functions that users do not get to see directly, but with which developers have contact.
Microsoft is now naming these functions on the website for the discontinued Windows functions. The virtualization-based security enclaves (VBS) (not to be confused with Visual Basic scripts, which share the abbreviation VBS) provide a software-based "Trusted Execution Environment" (TEE). Behind this are isolated address spaces and virtualized machines that seal off code and data in protected areas from the "normal" program and kernel code. Encryption functions are often offered in such TEEs, and they can also provide TPM functions. Processors and operating systems usually provide such areas, for example on ARM-based Android smartphones; Microsoft also provides such areas.
Security function to be removed from older Windows functions
Microsoft will soon be removing this function from Windows 11 23H2 and older as well as from Windows Server 2022 and operating system versions prior to that. It will remain available for Windows 11 24H2 and Windows Server 2025 and newer versions. Developers may need to update the SDKs and Visual Studio to newer versions. Customers who are still using older versions of Windows and require these functions for their software must plan to update their Windows operating system in the foreseeable future.
Videos by heise
Two weeks ago, Microsoft announced the discontinuation of "Microsoft UWP Map Control" and "Windows Maps Platform APIs". Behind this is the support for map apps, whereby Microsoft wants to merge the "Bing Maps for Enterprise" and "Azure Maps" systems under the umbrella of the latter service. Anyone who relies on Windows UWP Map Control in their program code should look for a replacement based on Azure Maps within a year. On the replacement resource website for discontinued functions, Microsoft links helpful instructions for developers on how to switch, code examples and the blogs for the two Maps services.
However, Microsoft does not maintain every announcement for obsolete functions. At the beginning of April, Microsoft announced that the end of Driver Synchronization in WSUS – planned for 18 April this year – will now be postponed for the time being. Feedback from customers has shown that this function is currently still indispensable, particularly for island operation, i.e. in isolated networks such as on ships.
(dmk)
