4 ms·

We all remember that Windows was a water-tight never-crash workhorse before the pesky EU stepped in and requested the APIs to be documented for once..

bongodongobob 2y ago
In an enterprise setting where you can prevent people from fucking with it, it pretty much is. M365/office is the vast majority of our help desk tickets.
- croes 2y ago
  Don't you forget all the withdrawn updates MS released? MS isn't testing either.
- antisthenes 2y ago
  My work laptop windows crashed more times in a year than my Windows 7 install in the 10 years that I was using it (2009-2019). Mostly due to Teams or Edge eating up all the memory, and the OS being unable to handle it gracefully.
  - bongodongobob 2y ago
    You're going to have issues on any OS if you're short on RAM, graceful or not.
    - CRConrad 2y ago
      Which makes RAM-eaters pretty much malware, doesn't it? And, as the GP says, the biggest RAM-eaters on most corporate Windows installs are... Microsoft corporate software, like Teams. So I find it pretty hard to take whatever Microsoft says as the last word on anti-malware, even on Windows, when it's at the same time the biggest purveyor of malware.
- al_borland 2y ago
  This comment might have gone over better if people didn't just spend their whole weekend recovering from what is likely the largest outage in history, which only impacted Windows.
  - fulafel 2y ago
    .. caused by 3rd party software trying to reactively counter other malware that regularly finds its way onto enterprise windows hosts.
  - lmm 2y ago
    An outage that was no fault of Windows itself, and entirely due to a faulty third-party component.
    - CRConrad 2y ago
      Entirely due to that faulty third-party component being able to run without limitations in the kernel, because Microsoft didn't want to build an API with those limitations.
    - gjsman-1000 2y ago
      A third party component which used a kernel extension in Windows, but did not need a kernel extension on either the Mac (System Extension, which runs in user space) or the Linux (eBPF, much more resistant to crashes) versions. Why would Cloudstrike need a kernel driver on Windows, and not their other platforms? Microsoft is responsible for that design and not moving past it at the pace alternative systems have. Additionally, there are other things Microsoft could have done. For example - if your computer fails to boot 3 times in a row, with a third party driver, how about automatically disabling the driver? If the driver manufacturer doesn’t like that, tell them to suck it up and write a driver that doesn’t crash.
      - pixel16 2y ago
        https://www.theregister.com/2024/07/21/crowdstrike_linux_crashes_restoration_tools/ https://www.theregister.com/2024/07/21/crowdstrike_linux_cra... You mean the same issues that Linux also faced?
- multimoon 2y ago
  Even in an enterprise setting heavily controlled by group policy and an AD domain, watertight and never-crash aren’t terms I’d ever associate with any windows release.

bongodongobob 2y ago

In an enterprise setting where you can prevent people from fucking with it, it pretty much is. M365/office is the vast majority of our help desk tickets.

croes 2y ago
Don't you forget all the withdrawn updates MS released? MS isn't testing either.
antisthenes 2y ago
My work laptop windows crashed more times in a year than my Windows 7 install in the 10 years that I was using it (2009-2019). Mostly due to Teams or Edge eating up all the memory, and the OS being unable to handle it gracefully.
- bongodongobob 2y ago
  You're going to have issues on any OS if you're short on RAM, graceful or not.
  - CRConrad 2y ago
    Which makes RAM-eaters pretty much malware, doesn't it? And, as the GP says, the biggest RAM-eaters on most corporate Windows installs are... Microsoft corporate software, like Teams. So I find it pretty hard to take whatever Microsoft says as the last word on anti-malware, even on Windows, when it's at the same time the biggest purveyor of malware.
al_borland 2y ago
This comment might have gone over better if people didn't just spend their whole weekend recovering from what is likely the largest outage in history, which only impacted Windows.
- fulafel 2y ago
  .. caused by 3rd party software trying to reactively counter other malware that regularly finds its way onto enterprise windows hosts.
- lmm 2y ago
  An outage that was no fault of Windows itself, and entirely due to a faulty third-party component.
  - CRConrad 2y ago
    Entirely due to that faulty third-party component being able to run without limitations in the kernel, because Microsoft didn't want to build an API with those limitations.
  - gjsman-1000 2y ago
    A third party component which used a kernel extension in Windows, but did not need a kernel extension on either the Mac (System Extension, which runs in user space) or the Linux (eBPF, much more resistant to crashes) versions. Why would Cloudstrike need a kernel driver on Windows, and not their other platforms? Microsoft is responsible for that design and not moving past it at the pace alternative systems have. Additionally, there are other things Microsoft could have done. For example - if your computer fails to boot 3 times in a row, with a third party driver, how about automatically disabling the driver? If the driver manufacturer doesn’t like that, tell them to suck it up and write a driver that doesn’t crash.
    - pixel16 2y ago
      https://www.theregister.com/2024/07/21/crowdstrike_linux_crashes_restoration_tools/ https://www.theregister.com/2024/07/21/crowdstrike_linux_cra... You mean the same issues that Linux also faced?
multimoon 2y ago
Even in an enterprise setting heavily controlled by group policy and an AD domain, watertight and never-crash aren’t terms I’d ever associate with any windows release.