Microsoft: Windows Task Manager won’t quit after KB5067036 update

Comments

• Onomatopoeia@lemmy.cafe ⁨3⁩ ⁨weeks⁩ ago

  Don’t forget to get updates immediately or you’re at risk of being hacked!

  source
• bali10050@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Image

  source
• SoftestSapphic@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  Microsoft hasn’t tested their updates in years.

  These days, they aren’t even writing the updates!

  source
• orbitz@lemmy.ca ⁨3⁩ ⁨weeks⁩ ago

  Recent update kiled IIS for my dev machine had to revert. After googling found other people same issue that morning. Wouldn’t be so bad if 1/3 our product wasn’t an iis hosted application and I’m the only developer. Emailed everyone to let them know in case customers had that issue later. Just wouldn’t go to the site, for a err_connect msg from the browser. Mean least I saw this early on my machine while testing but it took a bit to figure out what was happening cause of all things iis just not working anymore isn’t overly usual. Mean it has issues but to just stop working is different.

  source

  • helix@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    So you went to management and proposed rewriting the app to run on proper web servers, and proper server OS, right?

    source
• aramis87@fedia.io ⁨3⁩ ⁨weeks⁩ ago

  But Dave said Task Manager could kill anything, so shouldn't it be able to kill itself?

  source

  • elvith@feddit.org ⁨3⁩ ⁨weeks⁩ ago

    It is. To close the Taskmanager, you simply start a new instance and kill the old ones…

    So, just don’t forget to select Taskmanager in the list and kill it instead of clicking X and closing the window. Otherwise you need to start a new instance and use that.

    source
• Fuckswearwords@lemmy.world ⁨3⁩ ⁨weeks⁩ ago

  They haven’t fixed the bugs they pushed on their users with 24h2 yet and they’re already there with more bugs. How thoughtful of them.

  source