this post was submitted on 03 Nov 2025
33 points (97.1% liked)

Windows

597 readers
1 users here now

For all things Windows.

founded 4 years ago
MODERATORS
top 8 comments
sorted by: hot top controversial new old
[–] Onomatopoeia@lemmy.cafe 8 points 6 days ago

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

[–] bali10050@lemmy.world 5 points 6 days ago
[–] SoftestSapphic@lemmy.world 2 points 5 days ago

Microsoft hasn't tested their updates in years.

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

[–] aramis87@fedia.io 2 points 6 days ago (1 children)

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

[–] elvith@feddit.org 1 points 6 days 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.

[–] orbitz@lemmy.ca 1 points 6 days ago (1 children)

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.

[–] helix@feddit.org 1 points 6 days ago

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

[–] Fuckswearwords@lemmy.world 1 points 6 days 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.