Microsoft should stop with this charade and make Windows 11 a paid upgrade


Recommended Posts

I get it, Microsoft wants to make money.

 

This new system requirements to get people to buy new PCs is ridiculous.

 

Microsoft should drop this charade and make Windows 11 a paid upgrade.

  • Mockingbird changed the title to Microsoft should stop with this charade and make Windows 11 a paid upgrade

That would add cost to an already expensive endevour for most.  Plus, most already have the TPM function it simply needs to be turned on in the BIOS/UEFI. 

 

Even if they did make it a paid upgrade, what makes one think they would drop the requirments?

8 minutes ago, xrobwx71 said:

That would add cost to an already expensive endevour for most.  Plus, most already have the TPM function it simply needs to be turned on in the BIOS/UEFI. 

1. It's not just TPM that is required, but TPM 2.0. (Microsoft has updated the requirements).

 

2. Even if it can be turned on in the BIOS, the layman would have trouble figuring out how to go into the BIOS and turn it on. 

 

3. There is also a processor support list that excludes anything older than 8th gen Intel Core and 2nd gen AMD Ryzen

 

8 minutes ago, xrobwx71 said:

Even if they did make it a paid upgrade, what makes one think they would drop the requirments?

...because MSFT already got the people's money

5 minutes ago, adrynalyne said:

This doesn’t even make sense. 

Which part do you not understand?

25 minutes ago, Mockingbird said:

1. It's not just TPM that is required, but TPM 2.0. (Microsoft has updated the requirements).

 

2. Even if it can be turned on in the BIOS, the layman would have trouble figuring out how to go into the BIOS and turn it on. 

 

...because MSFT already got the people's money

Which part do you not understand?

All of it. 
 

1. TPM 2.0 has existed since 2016.

2. Mainstream OEM users that have TPM 2.0 support had it enabled by default from the OEM. 

Even when Windows was a paid upgrade, it wasn’t a big moneymaker for them. Before Windows 10, the most common method of people upgrading their OS was via a new purchase. If Windows 10 hadn’t been forced on people, it would be the same scenario as the upgrade to Windows 11 is shaping up to be for some. However, because TPM 2.0 has been out for 5 years, it’s going to be less a purchase spree than pre Windows 10. 
 


 

So in short, you missed the Forrest for the trees. 

10 minutes ago, adrynalyne said:

All of it. 
 

1. TPM 2.0 has existed since 2016.

2. Mainstream OEM users that have TPM 2.0 support had it enabled by default from the OEM. 

Even when Windows was a paid upgrade, it wasn’t a big moneymaker for them. Before Windows 10, the most common method of people upgrading their OS was via a new purchase. If Windows 10 hadn’t been forced on people, it would be the same scenario as the upgrade to Windows 11 is shaping up to be for some. However, because TPM 2.0 has been out for 5 years, it’s going to be less a purchase spree than pre Windows 10. 
 


 

So in short, you missed Forrest for the trees. 

1. Certified Windows 10 PCs are required to have TPM, but not necessary turned on be default.

 

2. Even if the processor has built in TPM, it doesn't mean that the motherboard supports the feature or that it can be turned on.

 

3. Even if TPM is present and can be turned on, it might be disabled by default, and the layman would have trouble turning it on.

 

 

As far as the CPU list goes, I expect that will be expanded due to user complaints.  No reason a 7th or 6th gen, let alone even older quad core CPUs, can't run Windows 11.   I figure on the CPU side you'll be able to install/upgrade to 11 just fine, it'll just complain to you probably.   The TPM chip is another matter.  Personally my 6th gen skylake should support PTT/fTPM but my board maker doesn't give me the option to use it at all.   

 

Some of their higher end Z170 boards seem to give users the option though so I guess I got screwed without actually knowing it at the time.  

 

Regardless, even the TPM bit might be something you can skip and just upgrade and not get support for bitlocker and Windows Hello etc.    

 

They're not going to stop doing these free upgrades for users though, they only gain from it and don't lose anything.  Besides 11 is going to a single feature update a year again instead of 2 for Windows 10,  something a number of users would prefer.

1 hour ago, Mockingbird said:

1. Certified Windows 10 PCs are required to have TPM, but not necessary turned on be default.

 

2. Even if the processor has built in TPM, it doesn't mean that the motherboard supports the feature or that it can be turned on.

 

3. Even if TPM is present and can be turned on, it might be disabled by default, and the layman would have trouble turning it on.

 

 

You seem to have completely glossed over what I said. Hint: mainstream OEM machines are certified. I’ve yet to see one that supported TPM have it turned off. 

12 hours ago, Mockingbird said:

1. It's not just TPM that is required, but TPM 2.0. (Microsoft has updated the requirements).

 

2. Even if it can be turned on in the BIOS, the layman would have trouble figuring out how to go into the BIOS and turn it on. 

 

3. There is also a processor support list that excludes anything older than 8th gen Intel Core and 2nd gen AMD Ryzen

 

...because MSFT already got the people's money

Which part do you not understand?

1.

My understanding is 2.0 was a soft limit, 1.2 was a hard limit, meaning at least 1.2 is required if it's not 2.0 you get a warning but it'll still work, 2.0 is preferred though, maybe my understanding is wrong.

 

2.

True, but the layman would generally have an OEM machine, and those are enabled by default.

 

3.

You may be overreacting a bit, it's possible Microsoft are learning from the gong show release of Windows 10 2004, and 1909, and 1903..  It's possible they're limiting hardware at first, also, my CPU is 7th gen, it is not on the supported CPU list but if I run their little compatibility checker tool it says I am all good to run Windows 11, so maybe just wait and see what happens, sure I'll be slightly annoyed if Windows 11 wont work on my PC, but no one ever said it would did they and Windows 10 will be supported until 2025 or something.

 

 

I can understand why they don't understand your first post, it does seem pointless, and comes off purely as an entitled rant about Windows 11 possibly not working on your existing hardware.

Also, Windows 11 WILL be a paid product, if you're starting from nothing, otherwise the upgrade path is free.

 

Edited by JaredFrost
  • Like 2

There'd be more success in getting people on board if they made optional in the short-run whatever feature(s) it is that they are adding to Windows 11 that has caused this huge bump in the minimum requirements. Considering how reluctant most users were when Windows 10 landed (even though there weren't any major hardware barriers then), I don't think there'd be a welcome wagon of any kind waiting for Windows 11 if most people are going to need to buy a new PC just to get that OS fired up.

2 hours ago, BimBamSmash said:

There'd be more success in getting people on board if they made optional in the short-run whatever feature(s) it is that they are adding to Windows 11 that has caused this huge bump in the minimum requirements. Considering how reluctant most users were when Windows 10 landed (even though there weren't any major hardware barriers then), I don't think there'd be a welcome wagon of any kind waiting for Windows 11 if most people are going to need to buy a new PC just to get that OS fired up.

They'll tell you it's all security related.   8th gen Intel and newer CPUs might have something 7th and 6th etc don't on the security side, or microcode fixes to bugs/flaws like meltdown etc.   If MS was going to do this they should have released a detail blog post about why, but I think they will.

 

The problem is that they released the hardware requirements without any more info.  They should've waited until the first official insider build of 11 comes out and it's detailed docs along with releasing the hardware requirements.

 

As it stands they're going to have to deal with days of backlash because of this.   Even if they had some valid reasons you're not going to please everyone with them.    Lots of 6th and 7th gen systems on the intel side are more than capable of running the OS performance wise.    

  • Like 1

 

Quote

1. It's not just TPM that is required, but TPM 2.0. (Microsoft has updated the requirements).

Explain how MS charging for the upgrade would change this?

 

Quote

2. Even if it can be turned on in the BIOS, the layman would have trouble figuring out how to go into the BIOS and turn it on. 

Most layman can read and follow simple instruction.

 

Quote

. There is also a processor support list that excludes anything older than 8th gen Intel Core and 2nd gen AMD Ryzen

Again, explain how this changes whether MS charges or not.

I'm holding off any real opinion until 11 is released with respect to system requirements as they can change between now and then.

 

However, I'm not sure what one thing has to do with the other...are you implying that if it were a paid upgrade they would drop this TPM "requirement"?  

 

 

1 hour ago, Jim K said:

I'm holding off any real opinion until 11 is released with respect to system requirements as they can change between now and then.

 

However, I'm not sure what one thing has to do with the other...are you implying that if it were a paid upgrade they would drop this TPM "requirement"?  

 

 

He thinks that this is all a conspiracy for MS to get more people to buy new PCs so that they get more money from Windows (OEMs roll it into the cost of machine). 
 

Silly IMO. 

This "should" come off as obvious, but there are advantages for Microsoft if there is a high transition rate to the new OS platform.  Making the upgrade paid will result in an extremely slow transition.  The more people on the new platform, the more telemetry data they gather, more bug reports they'll receive, meaning the platform gets better faster.  There is less liability and security concerns if people abandon old platforms.  Making it paid would hardly move needle on their revenue model anyway.  The TPM requirement is already going to p*ss people off, so why push them even faster over to Apple?

9 minutes ago, Astra.Xtreme said:

This "should" come off as obvious, but there are advantages for Microsoft if there is a high transition rate to the new OS platform.  Making the upgrade paid will result in an extremely slow transition.  The more people on the new platform, the more telemetry data they gather, more bug reports they'll receive, meaning the platform gets better faster.  There is less liability and security concerns if people abandon old platforms.  Making it paid would hardly move needle on their revenue model anyway.  The TPM requirement is already going to p*ss people off, so why push them even faster over to Apple?

I think moving over to Apple is a counterintuitive thing to do with the situation at hand, They've had 2 major architecture changes in the last 20 years, this is the first time that comes to mind where it's like... You really might have to look at upgrading your hardware (that could otherwise be fine) for Windows 11.

 

Also, seeing as you're paying for a new Mac, why not just buy a PC as required anyway? The only reason you would is principle, but I'll refer you back to my first point if you think you'd be safe from something like this if you got a Mac.

 

I legit think they're doing this for a good reason, but I don't expect everyone to be happy about it.

On 26/06/2021 at 16:25, Mockingbird said:

I get it, Microsoft wants to make money.

 

This new system requirements to get people to buy new PCs is ridiculous.

 

Microsoft should drop this charade and make Windows 11 a paid upgrade.

That's not why the requirement is there.

On 26/06/2021 at 16:48, Mockingbird said:

1. It's not just TPM that is required, but TPM 2.0. (Microsoft has updated the requirements).

 

2. Even if it can be turned on in the BIOS, the layman would have trouble figuring out how to go into the BIOS and turn it on. 

 

3. There is also a processor support list that excludes anything older than 8th gen Intel Core and 2nd gen AMD Ryzen

To your first and third point, it has already been shown that 2.0 isn't a definite requirement. By extension that means that the processor support list could change as well.

 

For the point about the layman, remember that at this stage Windows 11 isn't being released to the layman. For the moment it is only available to those people that feel they absolutely have to try it, which makes them enthusiasts that should know what they are doing to make it work. Then it will become available to those on the insider ring, which again would mean they must be willing to do what is necessary to get it to work if they want to play around with it. When it finally becomes available to the average user, I'm willing to bet that there will be something in the upgrade process that will do things like enabling the TPM for those that have it but don't have it enabled. Anything to make the upgrade process as simple as possible for the layman.

 

EDIT: To answer the title of the thread, making Windows 11 a paid update will not change the requirements of the OS.

I feel the TPM requirement should only be for Enterprise as this does almost nothing for the home user besides cause issues down the road if they need data recovery. Looks like we will just have to hold out for Windows 12 or Windows 11.1.

19 minutes ago, Gotenks98 said:

I feel the TPM requirement should only be for Enterprise as this does almost nothing for the home user besides cause issues down the road if they need data recovery. Looks like we will just have to hold out for Windows 12 or Windows 11.1.

Why would it cause issues for data recovery for a home user?

33 minutes ago, adrynalyne said:

Why would it cause issues for data recovery for a home user?

If they force bitlocker on everyone and the user is careless with the keys and does not know how to retrieve them I can see this being an issue. The average user isn't going to know how bitlocker works and won't save the keyes.

  • Facepalm 1
8 minutes ago, Gotenks98 said:

If they force bitlocker on everyone and the user is careless with the keys and does not know how to retrieve them I can see this being an issue. The average user isn't going to know how bitlocker works and won't save the keyes.

They aren’t going to force bitlocker on anyone. 

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • I sort of agree with you on that. I had a telescope - a real hefty thing, although only around 500CHF - that got me so fascinated about the stars and planets. I would stare for hours, amazed that I could see the craters of the moon or the rings of Saturn in "realtime" (quotations because, y'know, speed of light and whatnot). A friend of mine has a telescope like the one mentioned in the review, and the pictures are amazing to look at. But there is something missing for me. I may as well just go to NASA's website and look through their gallery.
    • As opposed to catching bad press because it's the engine's fault? You didn't really think this through did you? lol. The engine has all the tools a dev needs to optimize their game, Epic isn't gonna hold their hand to make sure they use them. Also, Epic isn't forcing anyone to use Lumen, Nanite or super high resolution meshes and textures. Just because Nanite can render meshes with millions of polygons doesn't mean you should use it like that, in fact, Epic recommends you avoid doing that. Most of the stuttering can easily be fixed by cutting down on unique shaders by using master materials and generating a PSO cache and compiling every shader before loading the game and managing what must be loaded and unloaded at runtime, it's up to the developer to set all that up properly.
    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, another half hour unpacking and setting up the smart scope + tripod for equatorial tracking, then 15 more minutes mucking around with settings and shooting calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. Even with a smart scope like Dwarf 3, regular non-astro photography is still way more approachable to people getting into photography. I find this is a time consuming niche no matter how I go about it. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself in addition to everything else. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!