Watch what is next for Windows event on June 24, 2021

Cliff S said:

Some members thinking their CPU doesn't have an intergrated TPM, but do or might.
One other factor many are over looking is the DirectX 12 compatible graphics / WDDM 2.x.
So if you have a TPM but a butt old graphics card.....

Even my 970 supported Dx12 / WDDM2.x - it'd have to be a pretty

RingTailCoon said:

Intel Core i5 6400

Caledon Ken said:

@RingTailCoon

List of processors supported


https://docs.microsoft.com/en-us/win...tel-processors


6700 not on list. Pretty sure that gets a "Fail". Think it is 8 series and above.


Will be interesting to see what happens with public release.

Indeed

steve108 said:

Microsoft is working on a fix for the PC Health Check app, first update scheduled for today

Just downloaded and installed it now:
PC Health Check
Version 2.3.210625001-s2

Maybe there's hope for PCs not meeting the processor requirement on MS Windows 11 current processor list:
CPU Compatibility: A Brief Explanation (99.99% of all CPUs should run Windows 11 ) : Windows11

Maybe. Wouldn't hold your breath though ;P

Ground Sloth said:

If PC Health Check app said that your computer wasn't Windows 11 compatible, run it again. The new version of the app (which should install automatically) might tell you why it's not compatible.

Not really.

jh30uk said:

Tool update itself, tell me the CPU is issue.

Yup - the update is pushing out live to everyone who already has it.

CountMike said:

Attachment 338676

I'm really confuse with this Secure Boot requirement. When enabled it usually stops writing to boot sector and prevents OS installation.

Here is some reading on Secure Boot.

https://docs.microsoft.com/en-us/win...em-secure-boot

Secure boot is a security standard developed by members of the PC industry to help make sure that a device boots using only software that is trusted by the Original Equipment Manufacturer (OEM). When the PC starts, the firmware checks the signature of each piece of boot software, including UEFI firmware drivers (also known as Option ROMs), EFI applications, and the operating system. If the signatures are valid, the PC boots, and the firmware gives control to the operating system.

https://docs.microsoft.com/en-us/win...ss#secure-boot

When a PC equipped with UEFI starts, the PC first verifies that the firmware is digitally signed, reducing the risk of firmware rootkits. If Secure Boot is enabled, the firmware examines the bootloader’s digital signature to verify that it hasn’t been modified. If the bootloader is intact, the firmware starts the bootloader only if one of the following conditions is true:

• The bootloader was signed using a trusted certificate. In the case of PCs certified for Windows 10, the Microsoft® certificate is trusted.
• The user has manually approved the bootloader’s digital signature. This allows the user to load non-Microsoft operating systems.

All x86-based Certified For Windows 10 PCs must meet several requirements related to Secure Boot:

• They must have Secure Boot enabled by default.
• They must trust Microsoft’s certificate (and thus any bootloader Microsoft has signed).
• They must allow the user to configure Secure Boot to trust other bootloaders.
• They must allow the user to completely disable Secure Boot.

A Microsoft OS will have the required certificate, so it gets past that block.