Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "not your typical windows update rant"
Battle of titans:
Me vs Windows Update.
No, this time not about automatic restarts interrupting my work because I've postponed "important" updates for far too long.
Well, technically I lied.
Last evening windows force rebooted to install updates. OK then, I'll go home. This morning I saw windows update frozen at some percentage.
This evening I've got 3 forced restarts in 5 minutes. Only notepad++ with an opened and unsaved document saved my life.
Apparently, windows update follows a simple logic:
if(user.IsUsingComputer && lastUpgradeAttempt.HasFailedWithTotalFreeze && versionUpgrade.CanInstallOnlyWithFreshWindowsInstallation)
Seriosly. Why am I forced to install an update only to see it lock up the entire computer and rollback after I intervene? Last time I had this issue only reinstalling windows helped, which costs about 2 days. Excluding one day to try suggested solutions, remove drivers, av scanner, etc.
Is it really that hard to implement logic like: