• Microsoft you have made this confusing

    Just bought a new workstation. HP small form factor (with the largest power brick ever) with a Windows 11 Pro downgraded to Windows 10 Pro so I KNOW it supports Windows 11. Joined it to the domain. Started to install Win11 as the first business rollout of 11.  I’ll use Fences program and corral icons so the user won’t be annoyed, and it will be like his Windows 10.

    So for grins I go and run the WhynotWin11 just to test.

    And it says the 12th generation i7-12700 is not supported.

    Huh?

    But it is clearly listed on this page as being supported.

    AND it states in the web sites it’s licensed for Windows 11. But as Microsoft still hasn’t fixed their “official” application to work in a domain I can’t use their official tool while the workstation is on a domain.

    Note that while Microsoft is now pushing 22H2 to “unmanaged” pcs (that means you, the huddled masses), I don’t consider it still quite ready for prime time.  The fix for the remote desktop not working (which impacts some but not all Windows 11) is in the PREVIEW release of KB5022360.  (This update addresses an issue that affects mstsc.exe. It stops responding while connecting to a RemoteApp and Desktop Connection.) So until that rolls into next month’s security update, 22H2 still isn’t ready for letting home users remote into their workstations.

    Microsoft when you start selling Windows 12 make this process easier of determining which ones are and are not supported?

    As a kind reminder – don’t forget to use either group policy, registry keys or incontrol to select the version you are on.