# Windows Patching Issues Database

**URL:** <https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716>\
**Category:** Ignition\
**Created:** [November 6, 2019, 10:55am UTC](https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716 "2019-11-06T10:55:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyP](https://avatars.discourse-cdn.com/v4/letter/a/8baadc/32.png) [@AndyP](https://forum.inductiveautomation.com/u/AndyP)\
**Post date:** [November 6, 2019, 10:55am UTC](https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716/1 "2019-11-06T10:55:31Z")

</div>

Question from one of our customers - Do Inductive maintain a database of any issues related to Operating System Patching? They are a large organisation with a large IT infrastructure who are always looking at best practices. We have a UAT (test) server that they test patches on before deployment to the production server but they asked if Inductive do or record testing of Ignition after Windows patches?

Given Ignition is OS independent and has multiple versions I imagine this is quite a complex issue but it crossed my mind that if it doesn’t already exist we could setup an Ignition community based database of OS / patching related issues. This would then allow developers / end users the opportunity do a quick query on the database to see if anyone has encountered issues with patches / upgrades. Of course it would rely on Integrator, customers , developers to contribute/add to it if they encounter issues or after successful patching.

Anyone have any thoughts on this?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 6, 2019, 2:46pm UTC](https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716/2 "2019-11-06T14:46:00Z")

</div>

Sounds like a great idea.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 6, 2019, 4:32pm UTC](https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716/3 "2019-11-06T16:32:35Z")

</div>

Generally speaking - no, we don’t crosscheck for compatibility unless someone reports a problem. We have a big advantage over truly native software in that regard - generally speaking, if you can run _any_ JVM, you can run Ignition; especially in 8 with embedded Java.

---

<div class="post-metadata">

**Author:** ![witman](https://avatars.discourse-cdn.com/v4/letter/w/d2c977/32.png) [@witman](https://forum.inductiveautomation.com/u/witman)\
**Post date:** [November 6, 2019, 7:47pm UTC](https://forum.inductiveautomation.com/t/windows-patching-issues-database/29716/4 "2019-11-06T19:47:22Z")

</div>

FWIW, for better or for worse we run Ignition on Windows everywhere and haven’t found Windows patches to be much of a concern with Ignition.
