# Windows update kb5012596

**URL:** <https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [May 2, 2022, 9:50pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137 "2022-05-02T21:50:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![drinaldi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drinaldi/32/32068_2.png) [@drinaldi](https://forum.inductiveautomation.com/u/drinaldi)\
**Post date:** [May 2, 2022, 9:50pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/1 "2022-05-02T21:50:21Z")

</div>

Hello, would anyone know if a current Windows patch (kb5012596) would cause any issues or latency issues with ignition?  
Thanks

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 3, 2022, 12:02am UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/2 "2022-05-03T00:02:02Z")

</div>

First I’ve heard anybody ask…

It seems unlikely based on the description, but I guess anything is possible.

[https://support.microsoft.com/en-us/topic/april-12-2022-kb5012596-os-build-14393-5066-f77f480c-5dea-4e85-88b8-1e70b1b5fcd2](https://support.microsoft.com/en-us/topic/april-12-2022-kb5012596-os-build-14393-5066-f77f480c-5dea-4e85-88b8-1e70b1b5fcd2)

---

<div class="post-metadata">

**Author:** ![drinaldi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drinaldi/32/32068_2.png) [@drinaldi](https://forum.inductiveautomation.com/u/drinaldi)\
**Post date:** [May 3, 2022, 11:35am UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/3 "2022-05-03T11:35:55Z")

</div>

Thanks Kevin. The customer installs updates all the time and for some reason our scripts are now taking longer to process.  
I’ll keep digging.

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [May 3, 2022, 12:24pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/4 "2022-05-03T12:24:33Z")

</div>

In my experience Windows updates are notorious for not releasing memory, and chewing up unneeded disk space.

If you haven’t already, and it’s possible, I would recommend a full cold boot.

One of the many evils of running Windows.

---

<div class="post-metadata">

**Author:** ![drinaldi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drinaldi/32/32068_2.png) [@drinaldi](https://forum.inductiveautomation.com/u/drinaldi)\
**Post date:** [May 3, 2022, 12:39pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/5 "2022-05-03T12:39:39Z")

</div>

Thanks, I will pass that along to our customer to try.

---

<div class="post-metadata">

**Author:** ![drinaldi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/drinaldi/32/32068_2.png) [@drinaldi](https://forum.inductiveautomation.com/u/drinaldi)\
**Post date:** [May 3, 2022, 2:40pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/6 "2022-05-03T14:40:51Z")

</div>

That did the trick!!! They did a cold reboot and the process times went back to normal.  
Thanks for the help!

---

<div class="post-metadata">

**Author:** ![bkarabinchak.psi](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bkarabinchak.psi/32/83567_2.png) [@bkarabinchak.psi](https://forum.inductiveautomation.com/u/bkarabinchak.psi)\
**Post date:** [May 3, 2022, 6:08pm UTC](https://forum.inductiveautomation.com/t/windows-update-kb5012596/59137/7 "2022-05-03T18:08:56Z")

</div>

On any windows system I maintain, if a problem crops up out of nowhere, and I see there was a recent update - cold reboot is 100% the first thing I try. Just for the future windows updates that are bound to cause issues lol.