Preparing for Insider Preview Builds of Windows 11 - ***UPDATED 6/28***

你觉得这个可信吗？工程师，我在西瓜视频看的

The Intel graphics driver using the internal GPU of some Intel processors should not be blocking: on my system I have disabled this GPU in the UEFI BIOS because I use another PCI graphics board (nVidia) which is fully compliant to DirectX 12.1 and WDDM3.

However it seems that Windows 11 wants to use (experimentally?) a new security mechanism for virtual Based security (VBS), which is still not in any other Hyper-V implementation successfully implementing VBS (notably for HVCI, and that works since Haswell/Broadwell, i.e. Gen3/Gen4 for Intel): MBET (mode-based execution "technology?"): it is an extension of the NX (no-execution) support which allows conditional execution of memory pages shared by different processes (some processes will be allowed to execute it, others won't, depending on various factors checked by the hypervisor, without requiring to create two virtual pages descriptors, with or without the NX bit).

Without MBET, there's a simple workaround, that does not require allocating two pages of memory and synchronizing them, it just requires two descriptors pointing to the same physical memory. This is rarely needed: most of the time (for example in JIT compilers), you first compile the code into writable non-executable memory, then changes the descriptor of that page to set it to readonly executable mode (possibly this may require allocating a new page and copying the content using a system call that will check the security of this request and updates the necessary caches of descriptors): the initial writable memory is no longer needed and can be freed. With MBET, the transformation, can be made in situ, and a JIT compiler could even modify the code on the fly, provided that there's no other context currently executing that code: this requires getting an exclusive lock on that page but this would fail if there are other active processes (or threads, or fibers) owning a active descriptor to that page, so the system call should still make a copy in that case and return a new page descriptor.

MBET is just a small optimization which offers a very small performance boost in very exceptional cases.

On Intel and AMD processors this MBET capability is repported by some processor flag that you can check using Systinternal's "Coreinfo.exe" tool.

Microsoft should document which processor flags are needed and why it chooses to exclude processors that don't have it, and why it chooses to not implement any workaround. For me it's sufficient to have support for the NX (no execute) bit in page descriptors. The rest is adaptable in JIT compilers or by program loaders in the OS, e.g. for thunks used by dynamic library loaders, or for "sandbox testing and emulation" used by security scanners and antimalwares.

So for me, any PC that can successfully run Hyper-V 2019 (with VBS and HVCI enabled and running) *should* support Windows 11 (Hyper-V 2022 for now is still in development inside the Insider program for Windows Server 2022). And this includes PCs that already run Windows 10 with its updated builtin Hyper-V version where VBS and HVCI were also enabled and running.

Almost all new UI features in Windows 11 come in fact from the early development of Windows 10X (abandoned recently, but taken as a base, it was released for a single unique model of Microsoft tablet with a dual screen), even if they have been improved (for larger use than just on a tablet, so that Windows 11 can drop the "tablet mode" of Windows 10 with a unified UI) and continue to be tested in Windows 11 Dev channel.

You all forget that you're an Insider. The bugs will be fixed in future updates. Share the bugs through the Feedback Hub app.

I only bought my Surface Laptop about a year ago. Intel® Core™ i7-7660U CPU @ 2.50GHz 16GB Ram I've check TPM and version 2 is active.

And yet I still get the same message

i can't open windows defender