The issue can be resolved by allocating an additional 250 MB of storage space to the recovery partition. Details on how to do that can be found here.
However, at least on Windows 10, Microsoft has acknowledged that an automatic resolution for this issue will not be released and as such, the only way to fix this is manually.
So there is a solution and the headline should be "Microsoft admits it can't automatically fix..."
If it can be done manually, I don't see any reason it can't be done automatically. Other than just not wanting to allocate the person-power to it.
Letting the installer autonomously adjust the recovery partition may open up vulnerabilities where malicious software can be placed in recovery. I don't know how accurate that is, but it makes sense to me, and would be why they want it done on a case by case basis as needed and not just a mass fix to all installs whether they need it or not.
That security concern is there whether it is for this or something else.
Would you like automatic update to mess with your disk partition allocations without requesting explicit permission to do so? As long as searching the error code would give me the explanation and solution I'm Ok with manual fix this time
Me no, but for most users with only windows installed and not dual booting, having it automatically doing it would probably be fine and bailing out when it detects a more advance configuration such as extra partitions would make sense. Then display a message about manual intervention is required or something.
Why would they do that when they can use this as yet another push to move people to windows 11.
That was my thought. I'm not sure if it's based in science, but I remember being a huge fan of Windows 2000 back in the day, and Microsoft pushed a final service pack that made it highly unstable in 2005, and refused to update/fix it. My theory was that they were trying to push everyone to Windows XP, but I'm prone to thinking the worst of large corporations.
TWO of my laptops were bit by that bug/error. Not one. Two.
But what they offered was not a real solution. I'm an experienced computer user, and still didn't wanna mess with that "solution".
This was done just to force people to upgrade to a Win11 (and maybe get a new PC too, if their old one couldn't run Win11). If not that, then simply, incompetence in general.
It's all laughable, really.
One issue is that some people are still on windows 7 installs that were upgraded. Windows 7 had a large enough partition for then, but the upgrade now needs more. Unfortunately 2009 Microsoft didn't anticipate that this should be bigger for 2023 installs. Making it larger is a hassle I wouldn't want to code either.
Both my laptops were Win10-native, not upgrades from previous versions.
I used to have a very nice laptop that had a blue screen error I could never figure out, I wonder if this was it. Actually I still have it 🤔
So there is a solution and the headline should be "Microsoft admits it can't automatically fix..."
If it can be done manually, I don't see any reason it can't be done automatically. Other than just not wanting to allocate the person-power to it.
Letting the installer autonomously adjust the recovery partition may open up vulnerabilities where malicious software can be placed in recovery. I don't know how accurate that is, but it makes sense to me, and would be why they want it done on a case by case basis as needed and not just a mass fix to all installs whether they need it or not.
That security concern is there whether it is for this or something else.
Would you like automatic update to mess with your disk partition allocations without requesting explicit permission to do so? As long as searching the error code would give me the explanation and solution I'm Ok with manual fix this time
Me no, but for most users with only windows installed and not dual booting, having it automatically doing it would probably be fine and bailing out when it detects a more advance configuration such as extra partitions would make sense. Then display a message about manual intervention is required or something.
Why would they do that when they can use this as yet another push to move people to windows 11.
That was my thought. I'm not sure if it's based in science, but I remember being a huge fan of Windows 2000 back in the day, and Microsoft pushed a final service pack that made it highly unstable in 2005, and refused to update/fix it. My theory was that they were trying to push everyone to Windows XP, but I'm prone to thinking the worst of large corporations.
TWO of my laptops were bit by that bug/error. Not one. Two.
But what they offered was not a real solution. I'm an experienced computer user, and still didn't wanna mess with that "solution".
This was done just to force people to upgrade to a Win11 (and maybe get a new PC too, if their old one couldn't run Win11). If not that, then simply, incompetence in general.
It's all laughable, really.
One issue is that some people are still on windows 7 installs that were upgraded. Windows 7 had a large enough partition for then, but the upgrade now needs more. Unfortunately 2009 Microsoft didn't anticipate that this should be bigger for 2023 installs. Making it larger is a hassle I wouldn't want to code either.
Both my laptops were Win10-native, not upgrades from previous versions.
I used to have a very nice laptop that had a blue screen error I could never figure out, I wonder if this was it. Actually I still have it 🤔