SQL Query to preserve any executables configured under 'Install Behavior' This second case we opened is still going, I'm not letting Microsoft close it until they give me an ETA on when the bug is going to be fixed. Thankfully, I modified a SQL query I found to pull up to 6 executables configured under 'Install Behavior' for all applications in our database (below). So to battle this, we had to change all of our 'Required' deployments with executables listed under 'Install Behavior' to only install when no user is logged in.įast forward to November of 2022, we decided to see if upgrading to release 2207 would resolve the problem but that only made things worse - with this release, now any superseded application that was configured in the current application you were deploying, if installed on targeted PC any executables listed under 'Install Behavior' would force close, even if you had only install when no user is logged on.the PC wasn't even attempting to install the new application, it was attempting to uninstall anything superseded by the new app - so now we have to take another drastic approach, and unconfigure any 'Install Behavior' executables in all currently deployed applications if Supersedence is configured for said app as well.

Ostroushko, according to Microsoft, this is a known bug within MECM and it was introduced when upgrading to release 2111 (but it could have been introduced in release 2107, which we never went to) - my organization upgraded in March of 2022 to release 2111, and we began receiving reports of running applications just closing (not just Office apps).we finally tracked down the Event Details you describe, and ultimately reproduced the problem on-demand.unfortunately, once we opened a case with Microsoft, they didn't have good news for us they acknowledged the issue to be a bug with no ETA on when they'd be able to fix.only that it would be fixed in a future release.

Microsoft office quit unexpectedly mac