The other day my dad, my technology lever, mentioned in passing that he had read on the Internet that Windows 11 could not be used and that the operating system was not accepted.

Dad had a case. Now he’s more of an Apple user – I have him on the phone in order to support his technical needs, he uses an iPhone and an iPad. As his needs changed, his reliance on Windows devices decreased. In fact, its current Windows needs include non-Apple applications. (And because he’s a separate user, not a domain user, many of Windows 11’s authentication-related achievements won’t be available to him.)

Computerworld recently noted that the spread of Windows 11 is moving slowly along with it works on only 1.44% of all systems. It’s similar to what I see at home and in my office. At home I have one Surface Pro 7 computer that can run Windows 11. In the office I only have two computers that support Windows 11.

In fact, a lot of users I can’t run Windows 11. If it’s you and you’re wondering why you can’t run Windows 11, you can download Bytejeans a tool to know exactly why. This laptop that I use, for example, has a Trusted Platform Module that will support Windows 11. But its processor has no support based on virtualization (VBS).

Windows 11 ensures that VBS is enabled by default to support code integrity using a hypervisor. While you may argue that on a stand-alone workstation this protection may not be necessary, at the enterprise you want to make sure it is enabled. (This is not a new technologiesbut the mandate is new.)

VBS is required for Protect your Windows Defender credentialswhich protects the domain credentials on the network. As noted: “Credential Guard is a virtualization-based isolation technology for LSASS that prevents theft of credentials that can be used to transmit hash attacks. … After system build-up, attackers often try to retrieve any saved credentials for further lateral movement across the network. The main goal is the LSASS process, which stores NTLM and Kerberos credentials. Credential Guard prevents attackers from throwing away credentials stored in LSASS by running LSASS in a virtualized container that even a user with SYSTEM privileges cannot access. … The system then creates a proxy process called LSAIso (LSA Isolated) to communicate with the LSASS virtualized process. ”

Copyright © 2022 IDG Communications, Inc.

Previous articleSee Thomas Rhett’s sweetest family moments that are “memorable”
Next articleSales of used, clean electric cars reach a record high Business news