Can’t or won’t? The same issue exists for both windows 10 and 11, but they haven’t closed the ticket for windows 11… Typical bullshit. It’s not exactly planned obsolescence, but when a bug comes up like that they’re just gonna grab the opportunity to go “sry impossible, plz buy new products”
Not to mention what a bitch that partition is when you need to shrink or increase the size of your windows partition. If you need to upgrade your storage, or resize to partition to make room for other operating systems, you have to follow like 20 steps of voodoo magic commands to do it.
Whoa learned that one at the weekend. Added a new nvme drive, cloned the old drive. I wanted to expand my linux partition, but it was at the start of the drive. So shifted all the windows stuff to the end and grew the Linux partition.
Thought I’d boot into windows to make sure it was okay, just in case (even though I’ve apparently not booted it in 3 years). BSOD. 2-3hrs later it was working again, I’m still not sure what fixed it of I’m honest, I seemed to just rerun the same bootrec commands and repair startup multiple times, but it works now, so yay!
Jeez, I’ve just looked at the list of utilities, I’m not surprised, it’s got FireWire drivers for dos included. You’ve got to be pretty deep into the weeds at the point you need FireWire support in DOS from a recovery disk!
Microsoft can’t even release a fix for Window’s recovery partition being too small to stage updates. I had to do it myself, fucking amateurs.
Can’t or won’t? The same issue exists for both windows 10 and 11, but they haven’t closed the ticket for windows 11… Typical bullshit. It’s not exactly planned obsolescence, but when a bug comes up like that they’re just gonna grab the opportunity to go “sry impossible, plz buy new products”
I didn’t know that. So the ticket is still open for 11 but there’s still no fix?
That is my understanding.
I can’t find the article that I read just yesterday, but this is somewhat the same story: https://www.theregister.com/2024/05/03/microsoft_windows_recovery_environment/
Not to mention what a bitch that partition is when you need to shrink or increase the size of your windows partition. If you need to upgrade your storage, or resize to partition to make room for other operating systems, you have to follow like 20 steps of voodoo magic commands to do it.
The possibility of a catastrophic fuck up is way too high to put this on the average Windows user.
Whoa learned that one at the weekend. Added a new nvme drive, cloned the old drive. I wanted to expand my linux partition, but it was at the start of the drive. So shifted all the windows stuff to the end and grew the Linux partition.
Thought I’d boot into windows to make sure it was okay, just in case (even though I’ve apparently not booted it in 3 years). BSOD. 2-3hrs later it was working again, I’m still not sure what fixed it of I’m honest, I seemed to just rerun the same bootrec commands and repair startup multiple times, but it works now, so yay!
Hiren’s Boot Cd has a handy tool that can fix that bsod. I’ve used it many times.
Jeez, I’ve just looked at the list of utilities, I’m not surprised, it’s got FireWire drivers for dos included. You’ve got to be pretty deep into the weeds at the point you need FireWire support in DOS from a recovery disk!