We'd like to remind Forumites to please avoid political debate on the Forum... Read More »
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are - or become - political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
"It then looks at the TPM to make sure that the boot entry is from an accepted vendor, like MS or Ubuntu .... and of course that part must be signed and verified as well ... only run systems that are cryptographically verified..."
Or, for a while, you can bypass that. Until, your bank account is hacked....
There are quite a lot of people who have loaded W11 onto systems that can't implement the security system properly. As long as they don't have email on those computers, or do shopping or online banking, it may not expose them to much loss.
In the meantime, they'll tell you how clever they have been.
TMP 1.2 is so unsafe everyone is currently inundated with all these nasties already, or maybe it's a MS plot as all these nasties will be suddenly released when support for Win 10 ends to get those who used unsupported hardware to get Win 11
You have to wonder about their motivation here.... Even if you enabled it, it wouldn't stop people from clicking on dodgy links. Cryptography isn't going to save you from that.
I do wonder as well, it seems strange on a money saving site. I'm guessing some don't even know that MS has released a version of Win11 that doesn't even require any TMP and can use legacy BIOS
In anticipation for the October deadline for W10 support. I am looking for my options without changing my PC and laptop. One of the options is to use OPatch to handle security updates which MS will cease to do. Does anyone know how efficient this is and what it costs in comparison to MS's option to pay $30 for an extra years security updates.
Just to reiterate. Just move to Windows 11. Bypass the compatibility check and install anyway. Likelihood is that you'll be okay until 2028....but don't quote me on that
What you mean is that there’s a few risks involved!
There are NO risks involved. Don't tell me what I mean. I wrote what I meant. Stop the Trolling. Thank you.
I apologise then. What did you mean by 'don't quote me'?
If 25H2 is released as an Enablement Package, there will likely not be an impediment to unsupported devices upgrading to it from 24H2.....hence supported two years after October the 13th 2026. But don't quote me on that