15
waszqba
3y

Dam wandows... My system is up to date almost all the time as I install those forced updates before they are actually forced, just so I can be in control of saving things and not losing anything valuable during a forced restart. I've updated literally last evening and made sure the day is done only after all the updates have been made. Today I was working on a personal project and made an hour break for lunch and some rest. My computer went to sleep as it usually does when I leave it for 10 minutes or so... Or so I thought. After my break I sat behind the damn computer to get back to work only to realize that I woke it up to wrong system (windows is secondary as I only use it for this single project that needs to be done in .net and UWP) and there's no work to get back to. It just made an update without even letting me know there is one to be made.
I swear, if the person who made this design choice have paid only 1% of all the lost works' worth, they would smash the thing on day one and went bankrupt in first 2hrs of that 'feature' living it's life. And people wonder I daily drive *NIX based system...

Comments
  • 1
    That sounds like bad settings.

    I have only encountered that when I either postpone updates for weeks or due to enforced domain setting which are not Microsofts fault but the IT department.
  • 1
    Bugs in WSUS are far from unexpected.

    But yeah, usually admins configure group policies and you don't have a chance to change the settings.
  • 4
    It's not enough to do Windows updates. You also have to re-check all of your settings afterwards because Microsoft likes to reset them behind your back, and some machines even ignore group policies randomly. Windows is a high maintenance OS.

    In this case, it sounds like fast boot had been re-enabled without you realising that.
  • 1
    Trust the computer!
    The computer is always right!
    Don't oppose its decisions!
  • 2
    @IntrusionCM It is my personal computer and i am the only admin here, but yeah, what you mentioned was encountered by my colleague on his work laptop
Add Comment