• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Visual Studio Code updates still failing with auto-close

Started by Jared, July 20, 2021, 06:14:46 AM

Previous topic - Next topic

Jared

Hi Andrew,

Yes, it's definitely an issue with the VS Code installer.  The question was really how or if we could work around it in an automated way.  The pre-script idea is great, I just haven't had a chance to implement it yet.  I'll report back when I do!

Jared

Hi, sorry to resurrect this post, but this continues to be an on-going issue for our organization.  I myself just got a new laptop and I'm already facing this issue with every update to VS Code.

Something I did notice, even though we have "Auto-close conflicting application process before installation", I see a /NOCLOSEAPPLICATION switch in the installer command, which seems strange.  Please find the VS Code install log and the PatchMyPC script runner log entries from Jan 13.

Dan Gough (Patch My PC)

I've just done some testing and have not been able to reproduce this so far.

With Manage Conflicting Processes enabled, the app is closed and the update succeeds.
If MCP is set to ignore the running app and proceed, then the installer fails quickly before attempting to install.

It doesn't make sense to have /NOCLOSEAPPLICATIONS though, so we'll remove this from the default command line as it seems it could conflict with the other option on offer /FORCECLOSEAPPLICATIONS.

I also tested with /FORCECLOSEAPPLICATIONS /LOGCLOSEAPPLICATIONS though, and that did force close anything either.

Jared

Thanks, any estimate on when the parameter changes will go in?

Myself and other users again got this error with the latest update.  Is there anything you want me to do for diagnostics the next time we see the error?

Jared

Can you also let me know the behavior of the "Skip installation when conflicting processes are in use" option?  I couldn't find any documentation on this.

VS Code is one of those apps that is often running any time the PC is in use, so if this option only checks to see if the process is running during a software update cycle, it will likely be skipped forever.  But if it somehow will wait until the moment the process is no longer running, such as after a reboot, this might be a good solution.

Dan Gough (Patch My PC)

Sorry this change did not go in, I'll push to get it in today's release.

Skip means it will exit and not try to update. It will retry whenever WSUS / ConfigMgr / Intune (whatever is deploying it) decides to do so - we cannot indefinitely snooze updates since that would block other updates from running and also be subject to a timeout. Here is the a post on this:

https://patchmypc.com/manage-conflicting-processes-when-updating-third-party-applications

And the docs for Patch My PC Cloud:

https://docs.patchmypc.com/installation-guides/patch-my-pc-cloud/deployments/deploy-an-app/configurations#conflicting-process