6

!dev

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)
{
update();
}

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:

If(lastUpdateAttempt.HasFuckedUp)
{
windowsUpdate.FuckOff();
}

Comments
  • 2
    Freezes are worse than BSODs. They at least come with an error code to debug with
  • 2
    @asgs this is why we need the kernel debugger back. depending on what level hung up, you could manually generate a crashdump, view the fault, etc. at any time if something happened.
  • 1
    @Parzi I think that reinstalling everything is faster. If anyone wants to do hardcore debugging and problem solving he can install gentoo. I expect a paid product to work. And if not, usually the vendor/developer is responsible for update/bug induced faults. Not the user.
  • 0
    @darthkebab but if the problem is a driver or some such, reinstalling might not help. You could at least see the cause of the freezes if we still had the debuggers.
Add Comment