The i7-7700K meet the minimun requierments to run Win11. But its not suported, Why?

Sixpiece 

"Otherwise it is the developers who suffer."

Enabling HypervisorPlatform, does not give you VM functionality, it is just an API. Hyper-V is not even remotely the same as HypervisorPlatform. Having the APIs and a fully functional program are entirely different things. Like I said, compare, and then make up your mind about which one you want. You have to work quite a bit to get the same thing (more complexity.) So of course you HAVE to research the costs of using open source software, over another alternative (it may or may not matter.) I use lots of free software, but I also use premium software as well (it depends on what it is.) If you've ever used any of these VMs, you would know right away that they just can't scale like you think they can (the free versions have hard-coded limitations.) Free ESXI has physical limitations, regardless of what you want to do with it (Google Search is your friend in this instance, but I guess that's outlawed in Europe for privacy reasons. Ok so whatever search engine you want to use, would probably be able to find a feature matrix comparison chart, etc, a lot of information to cross-reference with, to help you make an informed decision, etc.) If you improve your soft skills this will all make perfect sense to you.

The drawbacks of using free software are immediately noticeable, even if it's functionally comparable. It's laughable to compare that with the post-paid versions given how terrible the extensions are. Like I said though, that's the only drawback, which the extensions provide driver support. I mainly use that for Linux / Unix on Windows ironically. If I HAVE to use that with Windows, I disable most of the extensions because I don't want to have to generalize the image with sysprep, or go in and remove strange drivers from the driver store (it's still perfectly usable for any operating system.) If VM has amazingly good low-level hardware access in a Bare-Metal VM, most likely it's NOT going to be Hyper-V or the free version of VirtualBox. It's necessary to make effort to do cross-comparisons and research the costs (to see if the time investment is worth it.) I mean MOST VMs you get like Hyper-V and whatnot, are mainly used to provision images. They don't have to be really high performance, and they serve mostly to fill a gap, a functional need (ie. Provisioning 32-bit images with the ADK / AIK on a 64-bit host machine.) I'm sure Hyper-V might be useful for running a 64-core server with a ridiculous amount of containers  / virtualized Windows-only images, yet you would only be able to achieve that in a reasonable way on an entirely different SKU anyways (not Windows 10 pro obviously.)

Alberello

That Verge article is actually just quoting this Microsoft article (if you were wondering where it came from. My script is based on this too.)

"Ways to install Windows 11" -> https://support.microsoft.com/en-us/windows/ways-to-install-windows-11-e0edbbfb-cfc5-4011-868b-2ce77ac7c70e

SixpieceIf there are real issues, which are less common, then update your drivers, run this script, etc.

Set-ExecutionPolicy -ExecutionPolicy Bypass -Scope LocalMachine -Force
./sc config EventLog start=auto;./sc config UsoSvc start=auto;./sc config wuauserv start=auto;./net start EventLog;./net start UsoSvc;./net start wuauserv;
DISM /Online /Cleanup-image /Restorehealth;
DISM /Online /Cleanup-Image /StartComponentCleanup /ResetBase;
./SFC /SCANNOW;
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"};
Get-AppxPackage | Reset-AppxPackage;