They did say they will clarify more on the hardware requirements beyond the TPM 2.0. I don't know the ETA, since it's not officially announced, but I suspect it will be given on this upcoming Tuesday (since it's Patch Tuesday).
They can really f* themselves if it's some arbitrary CPU listing that makes this ~4 year old PC outdated (got the previous gen CPU in a deal back then, no real difference between the 6th, 7th and 8th gen Intel as many have said). But I'm confident that I'll be hacking myself through this if the whitelisted CPU list keeps as it is. Could there be some real explanation for the CPU list, or is it just arbitrary? (beyond the TPM requirement)
They did say they will clarify more on the hardware requirements beyond the TPM 2.0. I don't know the ETA, since it's not officially announced, but I suspect it will be given on this upcoming Tuesday (since it's Patch Tuesday).
All that program does is run a bunch of PowerShell commands and gives you a result based on the output. This is the PowerShell command it runs for the Disk Partitioning section:
I don't know why it's telling me that GPT isn't detected. I very clearly do not have MBR partitions:
Get-Partition -DriveLetter C | Get-Disk | Select-Object -Property PartitionStyle
All that program does is run a bunch of PowerShell commands and gives you a result based on the output. This is the PowerShell command it runs for the Disk Partitioning section:
Code:Get-Partition -DriveLetter C | Get-Disk | Select-Object -Property PartitionStyle
And then based on whether the command returns 'GPT' or not it shows as successful. What do you get if you run that command in PS?
did you set the locale to japan? if so maybe that's why it fails
Yea cause I'm a weeb who plays visual novels loldid you set the locale to japan? if so maybe that's why it fails
Pretty sure, that script test isn't accurate. Microsoft says I am good. I am also running a Gigabyte B550i and that script says I am not running secure boot, but its enable and running according to the the Bios.So looks like I dont have Secure Boot, or it's unsupported. Is that my Mobo?
It's new, a Gigabyte B550, released last summer. Not the best, not the worse.
I assume if it's unsupported then I need a new Mobo or something?
OK, so I'm not exactly sure why the PS command isn't working for you (maybe a Windows Service that should be running isn't or something), but that error explains why that open source program is returning 'GPT Not Detected' -- since it's designed to only give the OK if the response is 'GPT' and only 'GPT'. Obviously in your case it's not, so you get the red X. If you're sure you're using GPT though, I wouldn't really worry about it.
So I don't know if my previous post helped anyone with getting the PC Health Check to be successful, but I forgot to add that I also updated my BIOS to a more recent version from I think Dec. 2020. Not the absolute latest one, but the latest my motherboard updated to automatically with a network update from within BIOS menu.I have AMD Ryzen 7 3800X, and an ASUS TUF Gaming X570-Plus motherboard on a personally-built computer.
Had turned on fTPM in BIOS, but kept getting failed on the PC Health Check tool.
Eventually found some Windows help article saying CSM wasn't allowed with TPM, which is why my computer was failing. Had an older install of Windows that I had upgraded to 10 a long time ago, and I think the way I installed it, I had to use CSM to boot up, even though Windows UEFI was enabled on my Secure Boot menu.
I had to convert my hard drive from MBR to GPT, but the Windows tool MBR2GPT wasn't working for me.
Validated but wouldn't complete the actual conversion.
Eventually bit the bullet and just paid for a license on a partition manager because I couldn't figure out how to use the free Windows tool with all the errors I kept getting.
Used EaseUS Partition Master Pro to do the GPT conversion and it worked like a charm, no errors or hiccups.
I disabled CSM in BIOS, and since I was already on Windows UEFI in my Secure Boot menu in BIOS, Windows booted up afterwards, and now I am passing the PC Health Check tool.
Ready for Windows 11 after all that!
Could the supported list be tied to its vulnerability to Meltdown + Spectre?
All i know is my 6700k when i type tpm.msc shows i have version 2.0 active yet MS doesnt list that CPU as supported, so complete mess as usual.
isn't that laptop from 2015?
He said he will be getting a refurbished $2,300 ThinkPad P52, or if lucky, get a ThinkPad P53. Both of those laptops cost a fortune to get, even more expensive than my gaming laptop with GTX/RTX hyrbid setup.
It's absolute clownshoes. They get everybody excited for a new OS announcement only for it to have super-strict and inconsistent installation requirements.It's amazing how Microsoft fucked this up. They revealed W11 a few days ago and literally everybody hates it already. If at least there were some great features which make it clear why there are these specific requirements. Something like a new privacy initiative comparable to Apple for example. With a slogan like "Best privacy protection on the market." Instead we get stuff like rounded edges, who gives a fuck. Or Teams integrated into Windows - I will NEVER use Teams for private stuff.
And it seems like they were "surprised" by the reaction?? Not just by the backlash, but by, for example, people wanting to know what it takes to run Windows 11? Like, couldn't they have anticipated that people would be interested in this? Also, there are methods that could have eased the transition. They could have allowed W11 for old CPUs, but with certain features unavailable, like Apple did with macOS Monterey because old Intel chips are missing ML hardware accelerators. Or they could have talked to motherboard manufacturers, to convince them to produce TPM 2.0 modules in the next 12 months so you can use them on the TPM header of your old board to get your PC W11 ready.
This is a $2 trillion dollar company and that's the best they got. What a mess.
Yes, if you joined the dev ring you'll get to test Windows 11 goodness, as currently stated.So let me get this straight, the beta testing version of Windows 11 will work on basically any relatively modern hardware but the final release version will not? Saw this in a video earlier (don't remember which one). What the hell? Are they intentionally blocking older systems from running the OS? Is this some kind of plan to force people to have to buy entirely new computers? Some OEM/Microsoft partnership?
Yes, if you joined the dev ring you'll get to test Windows 11 goodness, as currently stated.
Supposedly there'll be a blog post about why they're intentionally blocking older systems from running the OS, but we'll wait and see. At the moment though, yeah it seems pretty arbitrary.
DIY/custom builders might just need a new processor (for those on Ryzen Gen 1 to a gen 2) and such, but yeah, it'll push a lot of OEM users to just upgrade or at least feel like their current (perfectly fine) pc is 'old'.
Is it an actual partnership? I doubt it, but the OEMs will definitely love it.
Don't worry too much about all the hardware requirements like CPU
I run a fully upgraded Win10 (supposed to be only compatible with 5th Gen Intel CPU and up), I'm running fine on a first Gen intel i7 950 with no issues what's so ever
Fair enoughWindows 10 has a soft cap, from the way people at Microsoft have been talking, Windows 11 has a hard cap of 8th gen Intel/2nd gen Ryzen with no exceptions.
If it is a hard cap, the Windows installer will detect incompatible CPUs and block the install.
That's why people want clarification from Microsoft. Is it a hard cap or a soft cap?
People need to know so they can plan accordingly on if they're going to upgrade their CPU, motherboard (due to socket differences) or even laptop.
In regards to TPM and security to quote someone from an Forum who said it pretty well:
TPM is a step to give up own control of the OS and hardware. The same applies to secure boot.
Such 'features' are pushed to strengthen markets. People get fooled by promises to have more security, but the company's in fact only care about their own interests.
The last time when I've heard about TPM it was W8 and secure boot (UEFI).
There already MS distorted the facts. They justified to introduce UEFI as an advantage for instance to use GPT. In realty EFI is not needed to boot GPT.
They wanted to have secure boot and TPM with no way to disable them. But due to resistance i.a. from the Linux community the OEMs realized secure boot as enable/disable system.
It seems now MS starts a new attempt to push it again.
Everybody who is looking for a reasonable security concept and cryptography would never go for a system that uses private keys which are issued/controlled by an unknown.
By using TPM the issuer could theoretically determine what is allowed to run on your PC and what is determined as 'malware'. The issuer could determine a condition of hardware/OS which they'd have signed to be 'original' and any own changes as unauthorized change....and might refuse to start.
General rule: Never use a security system of which you have no own control and no influence on creating the private keys...either for signing or for encoding...
By using TPM one always follows the idea of integrity of the issuer. This always comes with losing own freedom as soon as one has another idea of it.
The irony relies on fooling with terms: TPM stands for Trusted Platform Module.
In fact Trusted = it is cough trusted as released by the big companies.
It should be EPM = Enforced Platform Module.
In short yes TPM can be a good thing if the user controls it but that's not what MS has in mind with it. It's basically a lock for your PC and you are giving away the only keys to MS so they can do whatever they want with it what could possibly go wrong?