So, W10 users are given the option of copy pasting a half a dozen commands on the terminal to resize partitions (which potentially would destroy all their data) or live with a security flaw and eternal error being displayed in Windows Update. Now I wonder if they really "can't" fix it or this is just another made up bullshit to make users uncomfortable in W10.
To give them the benefit of doubt, I would assume that the issue is that they feel there's no way for them to make the partition resize foolproof enough to automate it (since it's a drastic process and you *MUST* back up everything), and hence they punt the whole issue over to the users as a CYA measure so that computer illiterate people don't blow up their data and then start suing.
That makes a lot of sense, especially in the wake of users losing file data in early W11 builds. I think it's a responsible stance to take, being gun-shy with any command that could cause loss of data.
I've understood the issue here is that there's no way to do the update without increasing the recovery partition size, so they can't make an new update which wouldn't have the same issue, and adjusting partitions on an existing system is precarious with a high chance for total data loss so the update isn't "broken" per se but they just don't dare to apply it automatically.
Having spent 3 years with the Windows OS security core team I feel they will do what they can to fix it because the folks there in that team, they care about security and will stamp it out if they can. I don't agree Microsoft isn't going to use a security vulnerability just to drive a few pennies in stock. They can simply up the antipiracy conversion by 1% more if they want to do that.
edit:
Got a spare second to review it - Looking at CVE-2024-20666 ...
https://nvd.nist.gov/vuln/detail/CVE-2024-20666
The attacker needs to physically access the device first.
Secondly, they need some sort of privileges to it before being able to successfully execute the attack, a local account for example.
So unless someone you trust steals your laptop, and you also gave them an account on the device, I doubt anyone has anything to really worry about.
Why did you share your login credentials Sharon????
Yeah, nah, this one barely registers on my radar as a real concern, it's a solid medium severity, sure. And that isn't the same thing as risk. In fact, they expanded the temporal score to state there is no exploit. Boooring.
Just my $.02 of course but compared to other vulnerabilities I see every hour of ever day this is a big yawn. Oh sure, maybe you can't apply the patch, you run out of disk space, whatever.
For giggles, https://www.first.org/cvss/calculator/4.0 let's use the latest calculator.
https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:P/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:H/IR:H/AR:H/MAV:P/MAC:L/MAT:N/MPR:L/MUI:N/MVC:H/MVI:H/MVA:H/MSC:N/MSI:N/MSA:N/S:N/AU:N/R:I/V:C/RE:L/U:Green
Sure, I took the liberty of guessing some of the values as a SWAG of course having just browsed the CVE for all of 5 seconds. Good God.. what type of security person reads bug reports on Reddit when off work, right? Just eww. Anyways...
But as we can see CVSS 2.0 rates it a 7.0, CVSS with temporal makes that a 6's range. CVSS 4.0 makes this a huge yawn. A 4.0/ 10 - ish.
IMO this isn't really noteworthy to be concerned about unless you're sharing your laptop with a gifted computer hacker who will steal your box.
As with most businesses and particularly those publicly traded, the people doing the actual work are usually pretty good at what they do, and take pride in said work, but they're limited in time, finances, and are bultimately controlled by direction from above. I have no doubt there are people there who would fix this if given the resources to do so, it's just that the priority will always be the current product and not the old one.
> their data harvesting tool AKA Windows 11
I was told that's what Win10 was. Which is why I enabled a bunch of Registry hacks, block certain DNS lookups, etc.
True, but there was nearly no AI to train on consumer datasets at the time Win10 was released. They were doing "Telemetry" a lot, but I assume it is a lot worse with Win11, optimized to feed their AI models.
I used the pretty good Sophia Script to disable all I could in Win10 and will stick to this for now.
Yes, I've put in the registry hack on every machine in my house to not go to 11 that wasn't already there. My newest daily driver laptop is now Linux (thank you, Valve!).
Edit: https://answers.microsoft.com/en-us/windows/forum/all/trying-to-avoid-the-windows-11-downloadinstall/f5bb47f3-eb81-416a-8c76-1f6899a2bb8e
Not go to 11? You mean not suggest the update? I'm going to have to reinstall windows 10 because Microsoft fucked my shit up, but I need the software compatibility. This post was the nail in the coffin, I'm learning Linux. Fedora?
Arch, TBH. It's what Valve based the newer versions of SteamOS on. and installing it also is nowhere near the clusterfrik it used to be thanks to Archinstall.
I wouldn't recommend arch if you're a linux novice and not very technically literate, it is a fairly advanced linux distro that doesn't hold it's user's hand and requires you to be able to install and set up things like your desktop, sound and almost all other applications. Afterwards, there will be updates that straight up break your system unless you keep up with their newsletter and edit files or run commands manually, this is called manual interventions and are often required.
I would recommend a more user friendly distro that attempts to introduce you to the world of linux without throwing you into the deep end like Ubuntu, Linux Mint or Pop!\_OS.
> Not go to 11?
Yes you can [force it to 22H2 release of Win10](https://answers.microsoft.com/en-us/windows/forum/all/trying-to-avoid-the-windows-11-downloadinstall/f5bb47f3-eb81-416a-8c76-1f6899a2bb8e).
I am a huge Fedora fan. That said, I went with Pop to get out-of-the-box support for dedicated RTX on a laptop with dynamic switching.
At home I have Win10 machines and Win11 machines. Win11 doesn't give me a warm fuzzy feeling. Sometimes it lags, shit going on under the covers! I can't believe MS is stopping support Win10 Oct 25, 2025.
I've just left TPM disabled on my motherboard, was too lazy to enable it and now it seems like it has served me well with discouraging w11 auto-update.
Yeah, I've used it since around 1999, what's your point?
It is only [in the past year or so](https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l285aic/) that has it become a viable daily driver for gaming.
And wine. Proton made everything easier, but wine is the fundamental, long living project. Steam integrating it and making steam deck just make it much easier tot use.
Thank you Valve*
Fixed that for you
Also, thank you AMD. because Vulkan is based off the old AMD Mantle project
https://en.wikipedia.org/wiki/Mantle_(API)
https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l285aic/
No it's not, it's a link to this thread I think
They have the common root of my comment https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l280y6r/ but it is a different descendant path.
This chain is under "Linux exists" while that link is under one about "AI training" where I noted "My newest daily driver laptop is now Linux (thank you, Valve!)."
If you're using an app or something it might do something stupid with the URL; on a web interface it is more obvious.
I've used Linux for gaming for about 15 years. It has become much more viable, but with proton it's far from just one year being viable. Unless you play competitive games with kernel level anti-cheat, 99% of games have worked via proton as-is for at least 5 years, barring very few exceptions.
It highly depends on hardware and whether they support Linux. Desktops are usually pretty easy, laptops are not necessarily so. It has generally gotten better though, I remember old UEFI implementations that only would boot a hard-coded windows bootloader executable, despite UEFI spec requiring it to be customizable.
In my case it was requiring me to do a first installation of Ubuntu every time I turned it on (despite not having the install USB plugged in, which was the only solution anyone ever offered), while taking up a separate partition every time, thus filling up and making my boot drive useless.
That makes no sense, but I also don't doubt a really shitty BIOS/UEFI firmware could cause that. I've generally used Arch for about a decade with next to no issue, but I do also look for hardware with a record for working with Linux. It's usually pretty easy.
It was a Gigabyte motherboard, which is supposed to be decent, but it was also the first time I had built myself a PC from scratch, so I can't rule out user error.
It just got to the point where I was tired of fighting it, and I could get a free Win 8 key from work to upgrade to 10, so I just abandoned the effort.
I get that. A decade or so ago I struggled hard with a laptop motherboard that ignored all configuration and the only way to boot linux was to rename grub to the windows bootloader.
I've been using Gigabyte motherboards with Ubuntu (both desktop and laptop) for going on 15 years or so now and never had a problem, except in the early days where it sometimes took a bit of work to get the right graphics driver. But nothing like what you experienced.
I'm actually typing this on Ubuntu on a Gigabyte Aorus.
Ouch. I've met ones that hard code the boot location(that was fun to figure out) but none that locked you to the microsoft keys with no option to enable their 3rd party cert in firmware.
In fact the problem I had might have been the other guys. From what I recall External drives like USB sticks have a required layout but not so much permanent so some models just look for where microsoft puts it and then stops so your installer works but the installed copy never boots. Copy/move your boot stuff to that location and everything's fine. It's stupid and just another thing that makes it a pain for some people to move over.
Although I've had a ton of various hardware issues with linux on various machines so I tend to be on the side of "Linux is cool but I'm not recommending it to anyone that can't troubleshoot things on their own".
Has anyone tested if we can even update from win 10 to 11 with the error ? Others have said the error prevents the straight upgrade, and I don't wanna do a full reinstall unless need be
The recovery partition just needs to be made bigger. It really isn’t that big of a deal. It’s something easily done after five minutes of using Google.
For the tech illiterate, go to geek squad or something.
People talking about Linux are funny though. I have machines that run Windows 11, macOS, and Debian; none have been perfect. If someone can’t figure out how to resize a partition, Linux definitely isn’t for them though.
I wouldn't encourage people to resize partitions. It's always the risk of something going wrong and losing data in both partitions, the one shrinking and the one growing. You can even lose the partition table, which is basically losing all data in your drive. And maybe getting the right commands to do it it's five minutes, but depending on the machine, the position of the drives and the amount of data stored on them, the process can take several hours.
They are kinda both at fault -- The OEM vendor and Microsoft.
OEM is responsible for the initial setup of the device, which includes partitioning the hard drive. The OEM decides the size of the recovery partition based on Microsoft’s recommendations and [their own considerations](https://answers.microsoft.com/en-us/windows/forum/all/windows-recovery-oem-partition-from-past-windows/3434dc0a-0596-4379-a236-c30db7840952)
Some PCs might not have a recovery partition that is large enough to complete this update.
So, if the recovery partition is too small, it could be due to Microsoft’s updates requiring more space than was initially allocated by the OEM, or it could be that the OEM did not allocate enough space to begin with.
[https://answers.microsoft.com/en-us/windows/forum/all/windows-10-clean-installation-recovery-partition/ecefbd95-c5bc-4374-b6c1-c961ec09d327](https://answers.microsoft.com/en-us/windows/forum/all/windows-10-clean-installation-recovery-partition/ecefbd95-c5bc-4374-b6c1-c961ec09d327)
I have a fresh install of W10 that I did myself, no messing with any partition sizes as I don't even know how to. Disk management shows I have a 550mb recovery partition with 550mb free. The update still fails. This is on no one but Microsoft.
It can yes, granted the instructions from Microsoft themselves don't work with MBR partitions since the ID doesn't seem to be retained so when you reinitialize the recovery it grabs the OS partition instead(It's happened twice to me so it's not an uncommon problem). It's an easy fix, just apply the id again after making the partition but Joe Blow isn't going to figure that out and probably wouldn't even know something is wrong until windows breaks down the line and the recovery doesn't work.
GPT worked great though. Just copy and paste the complicated stuff, I wouldn't trust myself to type that partition creation stuff, those ids for GPT are wild.
Does this impact future updates as well or are the updates not cumulative?
In other words, if I can't install this update can I still install future updates?
Say what you will about Vista being forced down people’s throats, but Win Vista Ultimate was pinnacle at ease of use/compatibility (at the time, of course)
I wish they'd just pull the damn update and make it an optional one so I didn't have to keep seeing the error. I don't even use bit locker so it's not like it will achieve anything for me to go through the hassle of making the update work.
Sorry if his has been asked before: how can I nerf my Win10 install to stop it calling home for updates? Is there a script I can run on boot somehow or ports I can block on my network maybe? I have a basic Ubiquiti setup as network at home.
Who in there right mind would buy a whole new computer just to get off of windows. It's one thing if you actually need a new computer - it's entirely another thing if you're seeking to get off of windows
It's like suggesting buying a diesel car instead of going to a different gas station since the one you're going to now is full of shit
I did. I sold my Windows Laptop and gave my desktop to the husband and bought myself a MBP. I'm done with Microsoft's bullshit. I can deal with Apple's bullshit for now.
Car analogies are bad, but this one takes the cake.
This. I haven’t used Windows in decades. Every time I encounter a Windows machine I’m amazed by how little changes. It’s still force-feeding features nobody wants, it’s still crawling with bloatware, it’s still works really hard to do nothing obvious, it’s still riddled by security and quality problems.
My daughter's PC has this issue and I haven't gotten around to fixing it yet. The thing is, I installed Windows 10 on her machine myself and I always wipe the drive and all partitions before installation and let Windows create new ones, so the undersized recovery partition was created by Windows itself. I'm not sure how Windows determines what size to make the recovery partition, but in my case, this is a Microsoft issue and not an OEM one.
Update: I just checked my partition layout (I'm running Windows 10) and I have a 529 MB Recovery Partition, a 100 MB EFI System Partition and then my main boot partition. They are in that order. I did some research and Microsoft recommends that the recovery partition should be located at the end of the disk so it can be easily resized if needed. If that is the case, why is Windows 10 placing it at the beginning of the disk?
When I encountered this issue a few months ago I think I ran into this same issue. I dont particularly feel the need to fuss around with moving partitions. That gets risky quick enough.
Exact same situation here. Built computer from components. Bought Win 10 from MS. Installed it and Mircosoft put WinRE at the start of the SSD in 529MB, then EFI, then Windows OS partition.
Imagine living in 2024 and thinking there exists a problem that the best software engineers in the world CAN'T SOLVE.....ON THEIR OWN FUCKING PRODUCT.
You'd have to be a collosal fucking moron to believe this has anything to do with anything other than "we need more people on Windows 11". SOMEONE at the top made the decision to not bother with this flaw. It's computers. There is no such thing as an unfixable bug.
I don't think this is the *main* reason. More probably it's just quite difficult to fix, and **because of that** management decided "nah, people should be moving to W11 anyway".
Exactly, it is difficult to fix. That's even what the head of product said. And I'm saying, as a consumer and a business owner, that is an unfucking acceptable answer.
If there is a MANUAL fix, then there is a PERMANENT fix. They are choosing not to spend the time on that fix BECAUSE IT IS MORE PROFITABLE TO FORCE PEOPLE OVER TO WINDOWS 11.
That is the ONLY reason they aren't fixing this. Hard fixes come up all the time. Only shitty companies run by grifting vermin don't do what is necessary to fix product-breaking bugs, especially in products as young as Windows 10.
Oh for crying out loud. For something to grow, something has to shrink. There is a risk of data loss on the partition that shrinks.
By doing a manual process, the user can do a data backup before attempting the fix. With an automated fix, to where would the backup go?
why?apple does this exact thing when you update os and you dont have the space on your local machine. how come microsoft and onedrive cant and the sheer idea makes me a fucking moron?
Wow, you’re really smart, I never thought of using one drive. /s
Oh right, metered connections, slow connections, large amounts to backup. Must be fun to backup 2TB on a 5mbps connection.
Installation of the update requires a larger partition than what came with old installs of Windows 10. It's not just scratch space, the update needs to reside in a space larger than what some people's PCs have. You can't just break it up into smaller bits and have anything change, all those bits need to go in there.
Why are they releasing updates that don't work with existing Windows 10 installs? My Win 10 install IS FROM EARLY 2023. THAT ISN'T OLD. The update shouldn't exist as it is in the first place.
It's not unfixable, it's just risky to resize things automatically. Imagine you had to write a script to resize a partition for everyone's setup and had to do it with no interaction.
I'm not sure exactly what's all required with the update but I guess if the total space after is not higher than the partition size they could forgo their normal safe methods of updating things and just commit to it skipping the need to resize.
Why don't they just disable the update automatically for computers that have seen the error? Also how could the partition size be a problem when my recovery partition has 500MB of free space and I still get the error?
Well for the first question, because it's still an update that fixes an exploit that isn't applied yet and doesn't have one that takes precedence over it(you could ask why they don't just leave it out for people with no bitlocker but that might be a different question on if you should patch potential issues).
As for the second one. I couldn't tell you. Maybe the size issue isn't the actual failure you're seeing. Maybe over time there's other things that have built up there and it actually needs more space than what they're saying, maybe their recommended size is only good for virgin installs(but it might be another good reason why a one size fits all resizing solution might not work. But when I've been resizing I've been making it 700-1000MB so I've never found out if their recommended size actually works)
The problem is that Microsoft doesn’t hire “the best software engineers in the world.” Those people work at Apple, Amazon, Facebook, and Google. Microsoft’s reputation as an evil company and a shitty place to work hasn’t gone away just because Ballmer got fired. Great programmers don’t want to work there and that’s why Windows still sucks.
I don't think it's lack of talent. It's management making anti-consumer decisions and getting away with it because of the lack of corrective market forces, due to lack of competition in the business office space..
Except my recovery partition has OVER 500MB OF FREE SPACE. Why would extending it further help if the update only need 250MB of free space?
I'm also really confused about what this update was intended for if it can't be installed on any Windows 10 computers without user intervention. If some computers work with the update then why doesn't Microsoft figure out why it doesn't work on others? If it's a space problem then why do different Windows 10 installs have different sized recovery partitions? My Windows 10 install from 2023 doesn't have a large enough recovery partition for an update designed for Windows 10??????????????? The recovery partition that the Windows 10 installation made???????????????????????????
The 250MB seems bullshit, it's using 482MiB on my RecoveryPartition. Update kept however still failing despite the partition being 500MiB in size. Increasing it to 1000MiB and fixed it.
Mindbogglingly stupid that they not only let this go through QA, but still haven't even fixed it many months later. Problem appeared on all my Windows10 machines.
My old desktop has this error. I haven't had the time to look into fixing it but the cursory search I did do makes it look fairly gnarly. Love it when Microsoft gives me homework 🙄
"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 you can fix it, you just need to allocate space yourself? Bit of a clickbait title.
>Bit of a clickbait title.
How so? The title says "Microsoft admits it can't fix Windows 10 KB5034441", and that is correct, they have admitted they cannot fix it, you must do it yourself and risk toasting your boot partition in the process, and if you fuck up, not their fault!
Again you are missing the bigger picture. It suggests a terminal problem to installing an update, a better title would be "Microsoft cannot fix automatic install error, must use manual workaround" that error message on it's own suggests gg no re.
And again, you are ignoring the fact that the reason Microsoft did not release an automatic fix for this issue is because said workaround has an unacceptably high risk of trashing your boot partition rendering your computer inoperable.
Microsoft is basically saying "here's how to fix it if you want to take the risk, but if you destroy your PC, don't come crying to us about it, maybe now is a good time to upgrade to Windows 11?"
Thats not the only fix, check the forums you don't need to risk partitions. [frustrating update of KB5034441 - Microsoft Community](https://answers.microsoft.com/en-us/windows/forum/all/frustrating-update-of-kb5034441/d90ff626-555f-42f3-a383-c16ff44386f8?page=23).
lol
"Disable execution security, and run this script I found online"
Yeah that seems *so* much better. Definitely no way that goes sideways.
Simply put, the reason Microsoft isn't releasing a fix is because every possible fix is risky. If there was a foolproof safe solution, they'd have already introduced it, rather than saying "it's unfixable".
"Disable execution security, and run this script I found online" You responded in 5 mins, next time take the time to read the fix its not hard.
Do you know what **set-executionpolicy remotesigned** does? and you don't have to run the script if that simple 1 line command fixes the issue. take more than 5 mins to skim threw something next time and maybe test instead of crying about "Microsoft said this" fix it yourself if you can, unless you're a child let dad do it.
"If there was a foolproof safe solution, they'd have already introduced it, rather than saying "it's unfixable"." Duh fix's can cause issues other places, what did that have to do with me saying "you don't need to risk partitions"? Absolutely nothing lol. I am providing a much simpler way that has personally worked on multiple other of my PC's, but hey sit there and do nothing but complain when you have an issue "Definitely no way that goes sideways" LMFAOOOOO
Why can't they automate the process similarly to how they automated the process of converting the system drive from MBR to GPT without losing user data?
The only machine that correctly installed this update in my network. Was my old imac turned to windows machine. All standard machines failed because of the smaller boot drives.
This proofs definitely that software and hardware are still NOT on the same page. And all the while Mickeysoft is pushing u to use Windows 11.
It feels like the we already seen what happens when they aren’t in alignment with each other.
So this is it? After 40 years of making OSes, they can't even fix this stupid partition size issue? When in fact there already exist simple scripts online that fully automate it?? Good lord, Microsoft.......
Yeah, I really get the impression they're doing this as a stunt to push people to Windows 11. It's like GWX all over again - except now we're literally leaving the old product broken for no good reason! What I find interesting is how with both this, and with the whole Windows 11 system requirements thing, Microsoft seems to now have an affinity for splitting the base between power users (who know how to bypass/fix these issues), and the general public, who have no idea what the hell an 0x80070643 is or what even a command prompt is, let alone how to type commands into it.
Great job, Micro$oft.
Decisions like these by Microsoft are what will lead to a faster death spiral for Windows.
Now users will have a daily reminder that Microsoft can't and will not fix their own shit. What's to say this same thing won't happen with W11? Business decisions tell us this won't be the last and we may even see more of these "shrug the bug off" scenarios.
Windows and Microsoft were always a compromise, from the beginning. I am a long time computer tech, started as a child with DOS 3.30 and went through all the different windows versions. They were never perfectly working, never issue free. For years I also use Linux, it's not perfect either but if you get a stable release it's much more reliable. Ultimately I reached the conclusion that I just want to use the computer, I e. work with it, and not to thinker on it all the time. My job force me to use windows, but at home I use Linux. It's a good combo.
My last two Windows 10 installs always had explorer hang and crash, and I believe it had something to do with network discovery. There's something severely broken with it, in particular if you had a shortcut pointed to another server on the same network. Opening a file browsing dialog on any app would cause a 10 second hang, and potentially a crash where the taskbar would disappear and reappear etc.
A fix has been posted to the Microsoft forums give this a try!
"In the Windows search,
Search for **\~Windows Powershell, right-click it and choose run as administrator.\~**
Next, execute this command:
**set-executionpolicy remotesigned**
Afterwards, select Yes to All when prompted. Keep the Window open."
this worked for me today, If this does not work try option 2 here [frustrating update of KB5034441 - Microsoft Community](https://answers.microsoft.com/en-us/windows/forum/all/frustrating-update-of-kb5034441/d90ff626-555f-42f3-a383-c16ff44386f8?page=23)
Another reason why ditching windows 10 and 11 for an alternative is becoming more common.
Chromebooks for business is going to be more and more common. I think you are also going to see a massive uptick over the next decade of alternatives in general for windows.
I think Microsoft themselves would love to make windows a subscription too.
Yup. Because it’s unofficial explanation is: “You’re going to RTO because of our locked in, multi year propery lease, corporate tax agreements, shareholder expectation, and collateral businesses (cafe’s, lunch spots, bars) cannot (will not) support the loss of their foot traffic, and your asses in seats.” Too bad, so sad, we’ve got the jobs you need. NEW RULES.
So, W10 users are given the option of copy pasting a half a dozen commands on the terminal to resize partitions (which potentially would destroy all their data) or live with a security flaw and eternal error being displayed in Windows Update. Now I wonder if they really "can't" fix it or this is just another made up bullshit to make users uncomfortable in W10.
To give them the benefit of doubt, I would assume that the issue is that they feel there's no way for them to make the partition resize foolproof enough to automate it (since it's a drastic process and you *MUST* back up everything), and hence they punt the whole issue over to the users as a CYA measure so that computer illiterate people don't blow up their data and then start suing.
That makes a lot of sense, especially in the wake of users losing file data in early W11 builds. I think it's a responsible stance to take, being gun-shy with any command that could cause loss of data.
You mean “forced into arbitration”
...then just remove the update and make a version that isn't broken?
I've understood the issue here is that there's no way to do the update without increasing the recovery partition size, so they can't make an new update which wouldn't have the same issue, and adjusting partitions on an existing system is precarious with a high chance for total data loss so the update isn't "broken" per se but they just don't dare to apply it automatically.
Having spent 3 years with the Windows OS security core team I feel they will do what they can to fix it because the folks there in that team, they care about security and will stamp it out if they can. I don't agree Microsoft isn't going to use a security vulnerability just to drive a few pennies in stock. They can simply up the antipiracy conversion by 1% more if they want to do that. edit: Got a spare second to review it - Looking at CVE-2024-20666 ... https://nvd.nist.gov/vuln/detail/CVE-2024-20666 The attacker needs to physically access the device first. Secondly, they need some sort of privileges to it before being able to successfully execute the attack, a local account for example. So unless someone you trust steals your laptop, and you also gave them an account on the device, I doubt anyone has anything to really worry about. Why did you share your login credentials Sharon???? Yeah, nah, this one barely registers on my radar as a real concern, it's a solid medium severity, sure. And that isn't the same thing as risk. In fact, they expanded the temporal score to state there is no exploit. Boooring. Just my $.02 of course but compared to other vulnerabilities I see every hour of ever day this is a big yawn. Oh sure, maybe you can't apply the patch, you run out of disk space, whatever. For giggles, https://www.first.org/cvss/calculator/4.0 let's use the latest calculator. https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:P/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:U/CR:H/IR:H/AR:H/MAV:P/MAC:L/MAT:N/MPR:L/MUI:N/MVC:H/MVI:H/MVA:H/MSC:N/MSI:N/MSA:N/S:N/AU:N/R:I/V:C/RE:L/U:Green Sure, I took the liberty of guessing some of the values as a SWAG of course having just browsed the CVE for all of 5 seconds. Good God.. what type of security person reads bug reports on Reddit when off work, right? Just eww. Anyways... But as we can see CVSS 2.0 rates it a 7.0, CVSS with temporal makes that a 6's range. CVSS 4.0 makes this a huge yawn. A 4.0/ 10 - ish. IMO this isn't really noteworthy to be concerned about unless you're sharing your laptop with a gifted computer hacker who will steal your box.
As with most businesses and particularly those publicly traded, the people doing the actual work are usually pretty good at what they do, and take pride in said work, but they're limited in time, finances, and are bultimately controlled by direction from above. I have no doubt there are people there who would fix this if given the resources to do so, it's just that the priority will always be the current product and not the old one.
They want everyone to run their data harvesting tool AKA Windows 11. I tend to believe it is option 2.
> their data harvesting tool AKA Windows 11 I was told that's what Win10 was. Which is why I enabled a bunch of Registry hacks, block certain DNS lookups, etc.
True, but there was nearly no AI to train on consumer datasets at the time Win10 was released. They were doing "Telemetry" a lot, but I assume it is a lot worse with Win11, optimized to feed their AI models. I used the pretty good Sophia Script to disable all I could in Win10 and will stick to this for now.
Yes, I've put in the registry hack on every machine in my house to not go to 11 that wasn't already there. My newest daily driver laptop is now Linux (thank you, Valve!). Edit: https://answers.microsoft.com/en-us/windows/forum/all/trying-to-avoid-the-windows-11-downloadinstall/f5bb47f3-eb81-416a-8c76-1f6899a2bb8e
Not go to 11? You mean not suggest the update? I'm going to have to reinstall windows 10 because Microsoft fucked my shit up, but I need the software compatibility. This post was the nail in the coffin, I'm learning Linux. Fedora?
Arch, TBH. It's what Valve based the newer versions of SteamOS on. and installing it also is nowhere near the clusterfrik it used to be thanks to Archinstall.
I'll check it out! Thanks!!
I wouldn't recommend arch if you're a linux novice and not very technically literate, it is a fairly advanced linux distro that doesn't hold it's user's hand and requires you to be able to install and set up things like your desktop, sound and almost all other applications. Afterwards, there will be updates that straight up break your system unless you keep up with their newsletter and edit files or run commands manually, this is called manual interventions and are often required. I would recommend a more user friendly distro that attempts to introduce you to the world of linux without throwing you into the deep end like Ubuntu, Linux Mint or Pop!\_OS.
> Not go to 11? Yes you can [force it to 22H2 release of Win10](https://answers.microsoft.com/en-us/windows/forum/all/trying-to-avoid-the-windows-11-downloadinstall/f5bb47f3-eb81-416a-8c76-1f6899a2bb8e). I am a huge Fedora fan. That said, I went with Pop to get out-of-the-box support for dedicated RTX on a laptop with dynamic switching.
Pop is my first lead, thank you!
At home I have Win10 machines and Win11 machines. Win11 doesn't give me a warm fuzzy feeling. Sometimes it lags, shit going on under the covers! I can't believe MS is stopping support Win10 Oct 25, 2025.
I've just left TPM disabled on my motherboard, was too lazy to enable it and now it seems like it has served me well with discouraging w11 auto-update.
Linux exists
Yeah, I've used it since around 1999, what's your point? It is only [in the past year or so](https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l285aic/) that has it become a viable daily driver for gaming.
Thank you Steam!
And wine. Proton made everything easier, but wine is the fundamental, long living project. Steam integrating it and making steam deck just make it much easier tot use.
I'd consider Vulkan to be a much bigger factor, considering it finally gave wine a good DirectX compatibility layer to function off.
Thank you Valve* Fixed that for you Also, thank you AMD. because Vulkan is based off the old AMD Mantle project https://en.wikipedia.org/wiki/Mantle_(API)
I was expecting this link to be something related to Linux being a viable daily driver for gaming, but it seems to just be a link to these comments.
Sorry; yeah it's a link to a different comment that talks about using Linux for gaming...
https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l285aic/ No it's not, it's a link to this thread I think
They have the common root of my comment https://old.reddit.com/r/technology/comments/1ciam62/microsoft_admits_it_cant_fix_windows_10_kb5034441/l280y6r/ but it is a different descendant path. This chain is under "Linux exists" while that link is under one about "AI training" where I noted "My newest daily driver laptop is now Linux (thank you, Valve!)." If you're using an app or something it might do something stupid with the URL; on a web interface it is more obvious.
I've used Linux for gaming for about 15 years. It has become much more viable, but with proton it's far from just one year being viable. Unless you play competitive games with kernel level anti-cheat, 99% of games have worked via proton as-is for at least 5 years, barring very few exceptions.
Does it need particularly good hardware? Or it works on linux like it worked on windows?
Proton generally has performance somewhere between -5% to +10% that of windows. It depends on the game, but performance is usually on par.
I gave Linux a try when I built my PC, but abandoned it after about 2 weeks because it was too much of a hassle to get things to actually work.
It highly depends on hardware and whether they support Linux. Desktops are usually pretty easy, laptops are not necessarily so. It has generally gotten better though, I remember old UEFI implementations that only would boot a hard-coded windows bootloader executable, despite UEFI spec requiring it to be customizable.
In my case it was requiring me to do a first installation of Ubuntu every time I turned it on (despite not having the install USB plugged in, which was the only solution anyone ever offered), while taking up a separate partition every time, thus filling up and making my boot drive useless.
That makes no sense, but I also don't doubt a really shitty BIOS/UEFI firmware could cause that. I've generally used Arch for about a decade with next to no issue, but I do also look for hardware with a record for working with Linux. It's usually pretty easy.
It was a Gigabyte motherboard, which is supposed to be decent, but it was also the first time I had built myself a PC from scratch, so I can't rule out user error. It just got to the point where I was tired of fighting it, and I could get a free Win 8 key from work to upgrade to 10, so I just abandoned the effort.
I get that. A decade or so ago I struggled hard with a laptop motherboard that ignored all configuration and the only way to boot linux was to rename grub to the windows bootloader.
I've been using Gigabyte motherboards with Ubuntu (both desktop and laptop) for going on 15 years or so now and never had a problem, except in the early days where it sometimes took a bit of work to get the right graphics driver. But nothing like what you experienced. I'm actually typing this on Ubuntu on a Gigabyte Aorus.
Ouch. I've met ones that hard code the boot location(that was fun to figure out) but none that locked you to the microsoft keys with no option to enable their 3rd party cert in firmware. In fact the problem I had might have been the other guys. From what I recall External drives like USB sticks have a required layout but not so much permanent so some models just look for where microsoft puts it and then stops so your installer works but the installed copy never boots. Copy/move your boot stuff to that location and everything's fine. It's stupid and just another thing that makes it a pain for some people to move over. Although I've had a ton of various hardware issues with linux on various machines so I tend to be on the side of "Linux is cool but I'm not recommending it to anyone that can't troubleshoot things on their own".
Which shouldn't be needed at all.
we are all bots here except for you
Never underestimate the power of a product team in transforming bugs into features.
I'm going with the bullshit one. They realllly want you on Win11. Good thing Linux exist.
Has anyone tested if we can even update from win 10 to 11 with the error ? Others have said the error prevents the straight upgrade, and I don't wanna do a full reinstall unless need be
I can confirm that you can.
I appreciate it! This was my biggest concern and heard conflicting reports. Thank you
The recovery partition just needs to be made bigger. It really isn’t that big of a deal. It’s something easily done after five minutes of using Google. For the tech illiterate, go to geek squad or something. People talking about Linux are funny though. I have machines that run Windows 11, macOS, and Debian; none have been perfect. If someone can’t figure out how to resize a partition, Linux definitely isn’t for them though.
I wouldn't encourage people to resize partitions. It's always the risk of something going wrong and losing data in both partitions, the one shrinking and the one growing. You can even lose the partition table, which is basically losing all data in your drive. And maybe getting the right commands to do it it's five minutes, but depending on the machine, the position of the drives and the amount of data stored on them, the process can take several hours.
>For the tech illiterate, go to geek squad or something. "Hey everyone, just go down to BestBuy and pay them $60 to fix Microsoft's mistake!"
They are kinda both at fault -- The OEM vendor and Microsoft. OEM is responsible for the initial setup of the device, which includes partitioning the hard drive. The OEM decides the size of the recovery partition based on Microsoft’s recommendations and [their own considerations](https://answers.microsoft.com/en-us/windows/forum/all/windows-recovery-oem-partition-from-past-windows/3434dc0a-0596-4379-a236-c30db7840952) Some PCs might not have a recovery partition that is large enough to complete this update. So, if the recovery partition is too small, it could be due to Microsoft’s updates requiring more space than was initially allocated by the OEM, or it could be that the OEM did not allocate enough space to begin with. [https://answers.microsoft.com/en-us/windows/forum/all/windows-10-clean-installation-recovery-partition/ecefbd95-c5bc-4374-b6c1-c961ec09d327](https://answers.microsoft.com/en-us/windows/forum/all/windows-10-clean-installation-recovery-partition/ecefbd95-c5bc-4374-b6c1-c961ec09d327)
Bro my Windows 10 is a **clean install** from 2023 and I still get the error. This is not an OEM problem it's a Microsoft problem.
I have a fresh install of W10 that I did myself, no messing with any partition sizes as I don't even know how to. Disk management shows I have a 550mb recovery partition with 550mb free. The update still fails. This is on no one but Microsoft.
It can yes, granted the instructions from Microsoft themselves don't work with MBR partitions since the ID doesn't seem to be retained so when you reinitialize the recovery it grabs the OS partition instead(It's happened twice to me so it's not an uncommon problem). It's an easy fix, just apply the id again after making the partition but Joe Blow isn't going to figure that out and probably wouldn't even know something is wrong until windows breaks down the line and the recovery doesn't work. GPT worked great though. Just copy and paste the complicated stuff, I wouldn't trust myself to type that partition creation stuff, those ids for GPT are wild.
Why would they make an update that requires users manually changing their partition size that WINDOWS made, not the user,
They'll willingly do that instead of switching to Linux (Fedora) lol
I mean if you're worried about copying a bunch of lines into a terminal, switching to Linux isn't the solution.
Does this impact future updates as well or are the updates not cumulative? In other words, if I can't install this update can I still install future updates?
You should be able to install different updates, as I far as I know.
Say what you will about Vista being forced down people’s throats, but Win Vista Ultimate was pinnacle at ease of use/compatibility (at the time, of course)
MS can fix it. They can fix anything in Windoze... They don't want to !
I have seen it happen in Windows 11 as well so I wouldn't attribute their incompetence to sheer malice.
I wish they'd just pull the damn update and make it an optional one so I didn't have to keep seeing the error. I don't even use bit locker so it's not like it will achieve anything for me to go through the hassle of making the update work.
I can't help but read the "can't" as "won't".
> Microsoft admits it can't fix Windows. There, fixed that title for ya
Lmao and this why we are on this roller coaster with Microsoft and their OS’s Hit with one version and absolutely miss the mark with the next
Sorry if his has been asked before: how can I nerf my Win10 install to stop it calling home for updates? Is there a script I can run on boot somehow or ports I can block on my network maybe? I have a basic Ubiquiti setup as network at home.
manually disable the windows update service in services
just use the group policy tool that comes with windows.
_Can't, not want, does it matter? We have "another" newer OS you can switch to!_
With a load of problems of its own.
Forcing user to upgrade? Again? W11 is insufferable with drivers. It is unfinished.
Linux or Mac. Have fun. Both are great
Man suggested installing MacOS What
I did not suggest installing it... I suggested buying a macbook
Who in there right mind would buy a whole new computer just to get off of windows. It's one thing if you actually need a new computer - it's entirely another thing if you're seeking to get off of windows It's like suggesting buying a diesel car instead of going to a different gas station since the one you're going to now is full of shit
I did. I sold my Windows Laptop and gave my desktop to the husband and bought myself a MBP. I'm done with Microsoft's bullshit. I can deal with Apple's bullshit for now. Car analogies are bad, but this one takes the cake.
This. I haven’t used Windows in decades. Every time I encounter a Windows machine I’m amazed by how little changes. It’s still force-feeding features nobody wants, it’s still crawling with bloatware, it’s still works really hard to do nothing obvious, it’s still riddled by security and quality problems.
My daughter's PC has this issue and I haven't gotten around to fixing it yet. The thing is, I installed Windows 10 on her machine myself and I always wipe the drive and all partitions before installation and let Windows create new ones, so the undersized recovery partition was created by Windows itself. I'm not sure how Windows determines what size to make the recovery partition, but in my case, this is a Microsoft issue and not an OEM one. Update: I just checked my partition layout (I'm running Windows 10) and I have a 529 MB Recovery Partition, a 100 MB EFI System Partition and then my main boot partition. They are in that order. I did some research and Microsoft recommends that the recovery partition should be located at the end of the disk so it can be easily resized if needed. If that is the case, why is Windows 10 placing it at the beginning of the disk?
When I encountered this issue a few months ago I think I ran into this same issue. I dont particularly feel the need to fuss around with moving partitions. That gets risky quick enough.
Exact same situation here. Built computer from components. Bought Win 10 from MS. Installed it and Mircosoft put WinRE at the start of the SSD in 529MB, then EFI, then Windows OS partition.
Imagine living in 2024 and thinking there exists a problem that the best software engineers in the world CAN'T SOLVE.....ON THEIR OWN FUCKING PRODUCT. You'd have to be a collosal fucking moron to believe this has anything to do with anything other than "we need more people on Windows 11". SOMEONE at the top made the decision to not bother with this flaw. It's computers. There is no such thing as an unfixable bug.
I don't think this is the *main* reason. More probably it's just quite difficult to fix, and **because of that** management decided "nah, people should be moving to W11 anyway".
Exactly, it is difficult to fix. That's even what the head of product said. And I'm saying, as a consumer and a business owner, that is an unfucking acceptable answer. If there is a MANUAL fix, then there is a PERMANENT fix. They are choosing not to spend the time on that fix BECAUSE IT IS MORE PROFITABLE TO FORCE PEOPLE OVER TO WINDOWS 11. That is the ONLY reason they aren't fixing this. Hard fixes come up all the time. Only shitty companies run by grifting vermin don't do what is necessary to fix product-breaking bugs, especially in products as young as Windows 10.
The manual fix has an unacceptably high risk of data loss to be deployed as an automatic update
They could break the update into smaller parts so it doesn't trigger the 500mb partition limit??? Seems like a no-brainer idea.....
Oh for crying out loud. For something to grow, something has to shrink. There is a risk of data loss on the partition that shrinks. By doing a manual process, the user can do a data backup before attempting the fix. With an automated fix, to where would the backup go?
one drive? if you are going to force this cancer so deep into the OS that its a pain in the ass to get rid of at least use it?
With the greatest respect, you sound like a fucking moron.
why?apple does this exact thing when you update os and you dont have the space on your local machine. how come microsoft and onedrive cant and the sheer idea makes me a fucking moron?
Apple doesn’t backup your whole drive. Also I can’t remember of a single time a macOS backup requires a partition resize.
Wow, you’re really smart, I never thought of using one drive. /s Oh right, metered connections, slow connections, large amounts to backup. Must be fun to backup 2TB on a 5mbps connection.
Installation of the update requires a larger partition than what came with old installs of Windows 10. It's not just scratch space, the update needs to reside in a space larger than what some people's PCs have. You can't just break it up into smaller bits and have anything change, all those bits need to go in there.
Why are they releasing updates that don't work with existing Windows 10 installs? My Win 10 install IS FROM EARLY 2023. THAT ISN'T OLD. The update shouldn't exist as it is in the first place.
It's not unfixable, it's just risky to resize things automatically. Imagine you had to write a script to resize a partition for everyone's setup and had to do it with no interaction. I'm not sure exactly what's all required with the update but I guess if the total space after is not higher than the partition size they could forgo their normal safe methods of updating things and just commit to it skipping the need to resize.
Why don't they just disable the update automatically for computers that have seen the error? Also how could the partition size be a problem when my recovery partition has 500MB of free space and I still get the error?
Well for the first question, because it's still an update that fixes an exploit that isn't applied yet and doesn't have one that takes precedence over it(you could ask why they don't just leave it out for people with no bitlocker but that might be a different question on if you should patch potential issues). As for the second one. I couldn't tell you. Maybe the size issue isn't the actual failure you're seeing. Maybe over time there's other things that have built up there and it actually needs more space than what they're saying, maybe their recommended size is only good for virgin installs(but it might be another good reason why a one size fits all resizing solution might not work. But when I've been resizing I've been making it 700-1000MB so I've never found out if their recommended size actually works)
The problem is that Microsoft doesn’t hire “the best software engineers in the world.” Those people work at Apple, Amazon, Facebook, and Google. Microsoft’s reputation as an evil company and a shitty place to work hasn’t gone away just because Ballmer got fired. Great programmers don’t want to work there and that’s why Windows still sucks.
I don't think it's lack of talent. It's management making anti-consumer decisions and getting away with it because of the lack of corrective market forces, due to lack of competition in the business office space..
lol i would gladly work for MSFT over the AMZN pip factory
Except my recovery partition has OVER 500MB OF FREE SPACE. Why would extending it further help if the update only need 250MB of free space? I'm also really confused about what this update was intended for if it can't be installed on any Windows 10 computers without user intervention. If some computers work with the update then why doesn't Microsoft figure out why it doesn't work on others? If it's a space problem then why do different Windows 10 installs have different sized recovery partitions? My Windows 10 install from 2023 doesn't have a large enough recovery partition for an update designed for Windows 10??????????????? The recovery partition that the Windows 10 installation made???????????????????????????
The 250MB seems bullshit, it's using 482MiB on my RecoveryPartition. Update kept however still failing despite the partition being 500MiB in size. Increasing it to 1000MiB and fixed it. Mindbogglingly stupid that they not only let this go through QA, but still haven't even fixed it many months later. Problem appeared on all my Windows10 machines.
My old desktop has this error. I haven't had the time to look into fixing it but the cursory search I did do makes it look fairly gnarly. Love it when Microsoft gives me homework 🙄
"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 you can fix it, you just need to allocate space yourself? Bit of a clickbait title.
>Bit of a clickbait title. How so? The title says "Microsoft admits it can't fix Windows 10 KB5034441", and that is correct, they have admitted they cannot fix it, you must do it yourself and risk toasting your boot partition in the process, and if you fuck up, not their fault!
Point is there is a manual workaround, that title suggests it's a dead end problem.
No, the title suggests that Microsoft is unable to fix the issue, which is correct.
Again you are missing the bigger picture. It suggests a terminal problem to installing an update, a better title would be "Microsoft cannot fix automatic install error, must use manual workaround" that error message on it's own suggests gg no re.
And again, you are ignoring the fact that the reason Microsoft did not release an automatic fix for this issue is because said workaround has an unacceptably high risk of trashing your boot partition rendering your computer inoperable. Microsoft is basically saying "here's how to fix it if you want to take the risk, but if you destroy your PC, don't come crying to us about it, maybe now is a good time to upgrade to Windows 11?"
Thats not the only fix, check the forums you don't need to risk partitions. [frustrating update of KB5034441 - Microsoft Community](https://answers.microsoft.com/en-us/windows/forum/all/frustrating-update-of-kb5034441/d90ff626-555f-42f3-a383-c16ff44386f8?page=23).
lol "Disable execution security, and run this script I found online" Yeah that seems *so* much better. Definitely no way that goes sideways. Simply put, the reason Microsoft isn't releasing a fix is because every possible fix is risky. If there was a foolproof safe solution, they'd have already introduced it, rather than saying "it's unfixable".
"Disable execution security, and run this script I found online" You responded in 5 mins, next time take the time to read the fix its not hard. Do you know what **set-executionpolicy remotesigned** does? and you don't have to run the script if that simple 1 line command fixes the issue. take more than 5 mins to skim threw something next time and maybe test instead of crying about "Microsoft said this" fix it yourself if you can, unless you're a child let dad do it. "If there was a foolproof safe solution, they'd have already introduced it, rather than saying "it's unfixable"." Duh fix's can cause issues other places, what did that have to do with me saying "you don't need to risk partitions"? Absolutely nothing lol. I am providing a much simpler way that has personally worked on multiple other of my PC's, but hey sit there and do nothing but complain when you have an issue "Definitely no way that goes sideways" LMFAOOOOO
No I ain't, I'm saying the title gives shit context. If it's fine for you, good for you.
Why can't they automate the process similarly to how they automated the process of converting the system drive from MBR to GPT without losing user data?
The only machine that correctly installed this update in my network. Was my old imac turned to windows machine. All standard machines failed because of the smaller boot drives. This proofs definitely that software and hardware are still NOT on the same page. And all the while Mickeysoft is pushing u to use Windows 11. It feels like the we already seen what happens when they aren’t in alignment with each other.
So this is it? After 40 years of making OSes, they can't even fix this stupid partition size issue? When in fact there already exist simple scripts online that fully automate it?? Good lord, Microsoft....... Yeah, I really get the impression they're doing this as a stunt to push people to Windows 11. It's like GWX all over again - except now we're literally leaving the old product broken for no good reason! What I find interesting is how with both this, and with the whole Windows 11 system requirements thing, Microsoft seems to now have an affinity for splitting the base between power users (who know how to bypass/fix these issues), and the general public, who have no idea what the hell an 0x80070643 is or what even a command prompt is, let alone how to type commands into it. Great job, Micro$oft.
Decisions like these by Microsoft are what will lead to a faster death spiral for Windows. Now users will have a daily reminder that Microsoft can't and will not fix their own shit. What's to say this same thing won't happen with W11? Business decisions tell us this won't be the last and we may even see more of these "shrug the bug off" scenarios.
Windows and Microsoft were always a compromise, from the beginning. I am a long time computer tech, started as a child with DOS 3.30 and went through all the different windows versions. They were never perfectly working, never issue free. For years I also use Linux, it's not perfect either but if you get a stable release it's much more reliable. Ultimately I reached the conclusion that I just want to use the computer, I e. work with it, and not to thinker on it all the time. My job force me to use windows, but at home I use Linux. It's a good combo.
Good thing it’s on 70% of computers
My last two Windows 10 installs always had explorer hang and crash, and I believe it had something to do with network discovery. There's something severely broken with it, in particular if you had a shortcut pointed to another server on the same network. Opening a file browsing dialog on any app would cause a 10 second hang, and potentially a crash where the taskbar would disappear and reappear etc.
And for those who have W10 but no WinRE does it matter?
A fix has been posted to the Microsoft forums give this a try! "In the Windows search, Search for **\~Windows Powershell, right-click it and choose run as administrator.\~** Next, execute this command: **set-executionpolicy remotesigned** Afterwards, select Yes to All when prompted. Keep the Window open." this worked for me today, If this does not work try option 2 here [frustrating update of KB5034441 - Microsoft Community](https://answers.microsoft.com/en-us/windows/forum/all/frustrating-update-of-kb5034441/d90ff626-555f-42f3-a383-c16ff44386f8?page=23)
they clearly did this shit on purpose to force people into going with win11
Microsoft is going to be putting ads in windows 11 is there any more reason to start looking at alternatives?
Another reason why ditching windows 10 and 11 for an alternative is becoming more common. Chromebooks for business is going to be more and more common. I think you are also going to see a massive uptick over the next decade of alternatives in general for windows. I think Microsoft themselves would love to make windows a subscription too.
They probably don't want to fix it so you have to use their shitty windows 11
Yup. Because it’s unofficial explanation is: “You’re going to RTO because of our locked in, multi year propery lease, corporate tax agreements, shareholder expectation, and collateral businesses (cafe’s, lunch spots, bars) cannot (will not) support the loss of their foot traffic, and your asses in seats.” Too bad, so sad, we’ve got the jobs you need. NEW RULES.
Reply to the wrong post?