britechguy Well-known member Joined Jun 2, 2016 Posts 772 Location Staunton, VA Jun 24, 2021 #1 That's pretty much it. Announced at "The Windows Event" today. Why a UI refresh warrants rebranding and a new version number eludes me, but much of what Microsoft chooses to do has that effect.
That's pretty much it. Announced at "The Windows Event" today. Why a UI refresh warrants rebranding and a new version number eludes me, but much of what Microsoft chooses to do has that effect.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,171 Location %systemroot% Jun 24, 2021 #2 britechguy said: Why a UI refresh warrants rebranding and a new version number eludes me, but much of what Microsoft chooses to do has that effect. Click to expand... Is it just a UI refresh? The kernel has probably significantly changed since the original Windows 10 build. Although, not sure why they're sticking with the Windows {number} naming convention?
britechguy said: Why a UI refresh warrants rebranding and a new version number eludes me, but much of what Microsoft chooses to do has that effect. Click to expand... Is it just a UI refresh? The kernel has probably significantly changed since the original Windows 10 build. Although, not sure why they're sticking with the Windows {number} naming convention?
britechguy Well-known member Joined Jun 2, 2016 Posts 772 Location Staunton, VA Jun 24, 2021 #3 @x BlueRobot, Of course there are other changes, including to the kernel, but there are other changes to the kernel with any major Windows 10 feature update. That goes along with how Windows As A Service works, introduced with the advent of Windows 10. We're both perplexed at why what used to be in the development stream as Windows 10, Version 20H2, now suddenly warrants a full Windows version number of its own. I'm sticking with, "marketing puffery."
@x BlueRobot, Of course there are other changes, including to the kernel, but there are other changes to the kernel with any major Windows 10 feature update. That goes along with how Windows As A Service works, introduced with the advent of Windows 10. We're both perplexed at why what used to be in the development stream as Windows 10, Version 20H2, now suddenly warrants a full Windows version number of its own. I'm sticking with, "marketing puffery."
philc43 BSOD Forum Moderator, BSOD Academy Instructor, BSOD Kernel Dump Expert Staff member Joined Jul 7, 2017 Posts 1,962 Location Cambridge, UK Jun 25, 2021 #4 Did you mean 21H2?
britechguy Well-known member Joined Jun 2, 2016 Posts 772 Location Staunton, VA Jun 25, 2021 #5 Yep. Typo.
xrobwx71 Administrator Staff member Joined Sep 27, 2019 Posts 2,608 Location Panama City Beach, FL Jun 26, 2021 #6 Download PC Health Check to see if your PC is compatible. So far, my Office PC at work is not. From what I've gathered, it's usually the requirement for TPM 2.0. I turned TPM 2.0 on in my BIOS/UEFI but it still says my processor is not compatible. I've also come across some TPM workarounds.
Download PC Health Check to see if your PC is compatible. So far, my Office PC at work is not. From what I've gathered, it's usually the requirement for TPM 2.0. I turned TPM 2.0 on in my BIOS/UEFI but it still says my processor is not compatible. I've also come across some TPM workarounds.
Tekno Venus Senior Administrator, Developer Staff member Joined Jul 21, 2012 Posts 7,199 Location UK Jun 26, 2021 #7 xrobwx71 said: but it still says my processor is not compatible. Click to expand... 6700k isn't on the supported CPU list: Windows Processor Requirements Windows 11 Supported Intel Processors. For Intel,, 8000 series or newer CPUs are on the list. That said, I suspect as it gets closer to launch Windows 11 will install on some older CPUs not on that list, it just wont be "recommended", as I can't see any reason for, say, 6000/7000 series intel CPUs wouldn't work based on the technical documentation here: https://download.microsoft.com/down...imum Hardware Requirements for Windows 11.pdf
xrobwx71 said: but it still says my processor is not compatible. Click to expand... 6700k isn't on the supported CPU list: Windows Processor Requirements Windows 11 Supported Intel Processors. For Intel,, 8000 series or newer CPUs are on the list. That said, I suspect as it gets closer to launch Windows 11 will install on some older CPUs not on that list, it just wont be "recommended", as I can't see any reason for, say, 6000/7000 series intel CPUs wouldn't work based on the technical documentation here: https://download.microsoft.com/down...imum Hardware Requirements for Windows 11.pdf