▲ 344 ▼ Microsoft Reveals How a Hidden Windows Bug Took Down Microsoft 365 Services Worldwide (cybersecuritynews.com) submitted 10 hours ago by Some_Emo_Chick@lemmy.world to c/technology@lemmy.world 49 comments fedilink hide all child comments
[–] eleijeep@piefed.social 29 points 17 hours ago (3 children) Where did they say it was a client side bug? permalink fedilink source parent hideshow 3 child comments replies: [–] threeonefour@piefed.ca 41 points 17 hours ago (1 child) It says multiple times that the issue was with Microsoft's internal cloud server software, not Windows. The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers. The failure was within Microsoft’s cloud infrastructure, not customer Windows systems permalink fedilink source parent hideshow 1 child comment replies: [–] eleijeep@piefed.social 7 points 11 hours ago* (last edited 8 hours ago) Yeah exactly, I don't understand how the original comment is still getting upvotes. Since your comment it gained (+36, -11). People don't read, I guess. permalink fedilink source parent [–] DougPiranha42@lemmy.world 2 points 5 hours ago I guess I misunderstood it. Inside an internal Windows process, competing tasks were waiting for access to shared resources, a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity. I read this as the behavior that precipitated the issue on the gateway was caused by how Windows sent traffic to exchange servers. So by Windows they mean whatever is running on the gateway? permalink fedilink source parent
[–] threeonefour@piefed.ca 41 points 17 hours ago (1 child) It says multiple times that the issue was with Microsoft's internal cloud server software, not Windows. The defect came from a fix prepared specifically for Microsoft 365 networking gateway servers. The failure was within Microsoft’s cloud infrastructure, not customer Windows systems permalink fedilink source parent hideshow 1 child comment replies: [–] eleijeep@piefed.social 7 points 11 hours ago* (last edited 8 hours ago) Yeah exactly, I don't understand how the original comment is still getting upvotes. Since your comment it gained (+36, -11). People don't read, I guess. permalink fedilink source parent
[–] eleijeep@piefed.social 7 points 11 hours ago* (last edited 8 hours ago) Yeah exactly, I don't understand how the original comment is still getting upvotes. Since your comment it gained (+36, -11). People don't read, I guess. permalink fedilink source parent
[–] DougPiranha42@lemmy.world 2 points 5 hours ago I guess I misunderstood it. Inside an internal Windows process, competing tasks were waiting for access to shared resources, a problem called lock contention. Under certain traffic conditions, this exhausted processor and memory capacity. I read this as the behavior that precipitated the issue on the gateway was caused by how Windows sent traffic to exchange servers. So by Windows they mean whatever is running on the gateway? permalink fedilink source parent