Microsoft announced the exception of security facility VBS Enclaves today for the first versions of Windows 11 and Windows Server. VBS, based on virtualized-based security, the VBS Enclave was formally introduced by Microsoft in Windows Server 2019. Microsoft improved this feature by opening it for third-party application last year, for example, this feature.
Unholy declaration No clarification gives the convenience being removed from the old versions of the Windows 11 and Windows Server.
Description:
- VBS Enclaves are supported by Windows 11, version 24h2 and later, or Windows Server 2025 and later and later.
- The feature is left at Windows 11, version 23h2 and before, and Windows Server 2022 and before.
Comment: It has nothing to do with VBSCript, which Microsoft promoted in 2023.
VBS Enclaves explained
VBS Enclaves provide separate, safe environment for sensitive data on the Windows system. Only a few microsoft and windows-specific programs are confirmed at the time of writing. In addition to the Microsoft Azure SQL database, it is a recall feature and credential guard of Windows 11 that are also using it.
An advantage of VBS Enclave is that they do not have hardware dependence. As long as the VBS Enclaves feature is capable of a supported Windows PC, it should work fine.
What does demonstration mean
The demonstration does not mean that the facility is being removed immediately. This means that a specific feature in the future version of the operating system will be removed. Or, in this case, in the future updates for the affected operating system. In fact, most domestic users may not be affected at all. Why is it here?
Windows 11, version 23h2 reaches the end of support in this November. Not all previous versions of Windows 11 are now supported to consumers. Meaning, Microsoft will have to remove the facility between April 2025 and November 2025 to affect home users. It does not seem that this case is going to happen.
Microsoft does not give a reason to remove, which makes it more surprising. Since the expulsion does not affect most domestic users, it is the possibility of business and enterprise customers who are targeting Microsoft with the information of designation.
Microsoft’s Windows App Development website contains a possible explanation on safe enclaves documentation. ThereMicrosoft pairs the following notes: “Windows 11 Build 26100.2314 or later or Windows Server 2025 or later to use these APIs for VBS Enclave.
It is possible that Pedavanti affects the third-party app and they only reach API and not the first-sided apps. We asked Microsoft about this but has not heard back to this point. We will update the article when we receive an answer.
Thanks for reading..
