.net patches breaking blue prism scheduled processes

[comicto]

Hello,

Has anyone out there running into issues with .net patching breaking scheduled processes on there VM's? We are currently running into issues with

KB4344146

KB4457035

We are a big enterprise, so unfortunately they can't just block the patches from coming through as that proves as a security risk. We usually have to manually uninstall the patches from the VM's. Our processes will run for a couple days without issue, but then of course SCCM will see that our VM's are not compliant and push them out again.

 

[Emil.Tophoej]

We had a problem with .net patch (august 2018 release i think) - we ended rolling back and now we have the servers out of the loop of automatic updates - the agreement is that the patches will roll out at one of the servers for us to approve.

The issue we got was “Could not identify process owning the current foreground” - and variants of this.

The newer version was supposed to be a fix - but we're still waiting.

 

[comicto]

I'm surprised not more people run into issues with these patches or that Blue Prism is aware of any .NET conflicts. All of our VM's/Desktops/Laptops run into process issues if these KB's are installed. We uninstall them, and everything works fine.