And then you're left searching for bullshit error messages and potentially unable to fix the problem regardless of your level of expertise.
I'm sorry, something went wrong. Here is all the information we can give you about it: ":("
... No you just use Windows built-in rollback feature. Which I think even auto-recovers these days of it detects a failure to boot after an update.
Hah! Can someone here chime in and tell me when the slow AF (as in, it can take hours) rollback feature actually workedβ½
Who TF is that patientβ½ You can reinstall Windows and all your apps in half the time required.
As someone who has hundreds of installed programs with tweaks on top of tweaks and hundreds of thousands of files, I always find the suggestion to "just reinstall" beyond laughable.
I think it recovered my PC for me twice, and it took about ~10 minutes each time at most. Good luck reinstalling everything in that time lol.
Windows recovery fails in plenty of circumstances, it's not a magic bullet. Snapshots are like you can do with btrfs, but that's not exactly how Windows recovery works.
Of course not, but it works 9/10 times for most people. Enough so that most people never have to deal with a faulty Windows update.
Sure if it fails completely it will, but it doesnβt catch everything. Hereβs a related story I have:
At work we had a bunch of Lenovo X1 Carbons running windows that would have the usb-c ports die seemingly randomly on users which was a big problem since thatβs also the charging port. There never seemed to be any similar root cause connecting the incidents and Lenovoβs support wasnβt any help. Our entire company is remote but luckily we had onsite support so for a while they would just come by and replace the whole motherboard each time.
Finally one day while scheduling a repair the support guy I was talking to just said, βOh Iβve seen this before. Itβs just a bad update and resetting the CMOS battery by putting a paper clip in this hidden hole fixes it.β We had the user try it out and the ports worked fine again. Apparently they had run some windows updates that failed silently and were causing the hardware issues.
From then on any time a user has had a hardware issue we canβt figure out we just have them try the reset and it has worked every time. This only happens probably 3-4 times a year but we only have less than 40 of these machines so not an insignificant amount.
And Microsoft support that's in fact clueless fanboys.
sfc /scannow didn't work? Well too bad, cuz now you gotta reinstall your OS
And then you're left searching for bullshit error messages and potentially unable to fix the problem regardless of your level of expertise.
I'm sorry, something went wrong. Here is all the information we can give you about it: ":("
... No you just use Windows built-in rollback feature. Which I think even auto-recovers these days of it detects a failure to boot after an update.
Hah! Can someone here chime in and tell me when the slow AF (as in, it can take hours) rollback feature actually workedβ½
Who TF is that patientβ½ You can reinstall Windows and all your apps in half the time required.
As someone who has hundreds of installed programs with tweaks on top of tweaks and hundreds of thousands of files, I always find the suggestion to "just reinstall" beyond laughable.
I think it recovered my PC for me twice, and it took about ~10 minutes each time at most. Good luck reinstalling everything in that time lol.
Windows recovery fails in plenty of circumstances, it's not a magic bullet. Snapshots are like you can do with btrfs, but that's not exactly how Windows recovery works.
Of course not, but it works 9/10 times for most people. Enough so that most people never have to deal with a faulty Windows update.
Sure if it fails completely it will, but it doesnβt catch everything. Hereβs a related story I have:
At work we had a bunch of Lenovo X1 Carbons running windows that would have the usb-c ports die seemingly randomly on users which was a big problem since thatβs also the charging port. There never seemed to be any similar root cause connecting the incidents and Lenovoβs support wasnβt any help. Our entire company is remote but luckily we had onsite support so for a while they would just come by and replace the whole motherboard each time.
Finally one day while scheduling a repair the support guy I was talking to just said, βOh Iβve seen this before. Itβs just a bad update and resetting the CMOS battery by putting a paper clip in this hidden hole fixes it.β We had the user try it out and the ports worked fine again. Apparently they had run some windows updates that failed silently and were causing the hardware issues.
From then on any time a user has had a hardware issue we canβt figure out we just have them try the reset and it has worked every time. This only happens probably 3-4 times a year but we only have less than 40 of these machines so not an insignificant amount.
And Microsoft support that's in fact clueless fanboys.
sfc /scannow didn't work? Well too bad, cuz now you gotta reinstall your OS