Microsoft Now pushing on the old part: Virtualization -Acided Security Das (VBS) and Windows Uwp Map Control and Related API have heavy names. There are tasks behind this that users do not look directly, but contact the developers.
Microsoft now calls these tasks End Windows Website for FunctionsVirtualization-based security slave, English virtue-based security enclaves (Visual should not be confused with basic scripts that briefly share VBS), provide a software-based “worldable performance environment” (TEA). It is behind isolated address space and virtualized machines that are code and data in areas protected from “general” programs and kernel codes. Encryption functions are often introduced in such tea, they can also provide TPM function. Processors and operating systems usually provide such areas, for example on ARM-based Android smartphones; Microsoft also keeps such areas First.
Security ceremony fly out of old Windows functions
Microsoft will soon throw this function with Windows 11 23H2 and Old -Windows Server 2022 and before the operating system versions. They are available for Windows 11 24h2 and Windows Server 2025 and more recent versions. Developers may have to update SDK and visual studios. Anyone who uses the old Windows version on the customer side and requires these functions for software, should plan updates of the Windows operating system in the future.
Two weeks ago, Microsoft announced “Microsoft UWP Map Control” and “Windows Maps Platform API”. It is behind the support for card apps, in which Microsoft has merged the system “bing maps for enterprise” and the “Azure Maps” under the roof of the latter service. Whoever depends on the Windows UWP map control in his program code, should look for replacement based on Azure maps within a year. But Replacement resource website for closed tasks is connected to Microsoft For developers, a blog on the requests, code examples and two maps services to change.

However, Microsoft also maintains every declaration for old tasks. In early April, Microsoft explained that the end of the driver synchronization in the WSUs – planned on April 18 of this year – is now being pushed on a long bench. Reaction from customers has shown that this function is still unavoidable for island operations, ie ships such as in separate networks, such as ships.
(DMK)
