Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

11
  • What OS do you in mind? Commented Nov 5, 2019 at 22:58
  • We are using Windows. Do you think that is an important consideration? Commented Nov 5, 2019 at 23:08
  • 2
    Enforcing that updates are disabled sounds dodgy. Not just because updates often bring security patches (and it initially comes across as wanting to avoid those security updates), but also that you've developed an application tied to not only an incredibly precise OS version. I would consider prohibiting OS updates to be a quality and regulatory concern in and of itself. That being said, it's perfectly possible that there is a good reason for this that I am not aware of. Commented Nov 6, 2019 at 7:42
  • 3
    @Flater In the medical device industry, every change to a system must be evaluated, documented, and tested. Automatic updates are a huge risk because they have the potential to break something. In the world of medical devices, this can literally cause injury or death. Commented Nov 6, 2019 at 19:44
  • 2
    @00Zero It probably makes sense as a system specification rather than an application specification. Blocking updates is a property of the operating system configuration, and isn't something that your application actually needs to do (or worry about). Commented Nov 6, 2019 at 22:07