you are viewing a single comment's thread
view the rest of the comments
[–] 14 points 12 hours ago (3 children)

Yeah, rule of thumb: you need your Windows PC to be available 100% at a close future point? update it now, reboot, and then disable networking if possible.

  • source
  • hideshow 3 child comments
  • [–] 8 points 11 hours ago

    Also pause updates, it doesn't stop all updates but it does avoid most of the forced reboot Micro$lop dishes out for weeks at a time. Disabling networking is ideal, no doubt, including the telemetry spam.

  • source
  • parent
  • [–] 1 point 7 hours ago (1 child)

    You have to ignore the updates for a while before it will force reboot during your normal working hours.

    If it’s left alone overnight yeah it might reboot on you the day the patch came out. But if your active hours are set to something same it’s never rebooted on me.

  • source
  • parent
  • hideshow 1 child comment
  • Yeah enterprise images are set to default as 8am active time. If someone leaves their machine on they'll switch to an inactive state at like 8pm or whatever you configured, and do the updates at like 2am and you should never need to know anything about it if something doesn't break.

    Not every setup is done well though, ive have several coworkers and I have Mac OS and Windows images want to force a reboot during work hours, 99% of the time it is either the user never allows the machine to be on when it isn't in use, or IT dropped the ball on the image.

  • source
  • parent