Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

Run custom pre-update scripts prior to any PatchMyPC defined scripts

A bit of background on this... 

Our organisation requires various Java8 preferences/config remain in tact after an upgrade, these are even enforced via group policy. However when the application is uninstalled/installed these are lost until the next policy refresh which could be 90 mins. To ensure the configuration is in place immediately after an upgrade I started looking at utilising the pre/post update scripts. However upon review it appeared that the PatchMyPC defined script was running prior to the custom pre-update, not allowing me to copy out the config from "C:\Windows\Sun\Java\Deployment". 

What would be even better is to re-order the workflow such that:

  • Current: PatchMyPC defined >> Pre-Update >> Post-Update
  • Proposed: Pre-Update >> PatchMyPC defined >> Post-Update

Workaround: As per this post, Justin suggested disabling the PatchMyPC uninstall script for Java and copying the code from the uninstall script into the custom pre-update script.


  • Steven Walch
  • Jun 27 2019
  • Attach files
  • Steven Walch commented
    30 Jun, 2019 11:20pm

    Awesome! Thanks for swift product change.

  • Admin
    Justin Chalfant commented
    28 Jun, 2019 08:54pm

    Marking as shipped, this is available in the latest internal preview, and it will be available in build 1.4.0 along with the new application management feature in the coming weeks.

  • Admin
    Justin Chalfant commented
    27 Jun, 2019 02:00pm

    Marked as planned, we are going to look into changing the execution order on the client side to be Customer Defined Pre-Update >> PatchMyPC defined Pre-Update >> Customer Defined Post-Update >> PatchMyPC Defined Post-Update. I goal is to get this changed in version 1.4.0 with the application feature as this is a relatively inexpensive on the engineering side. My goal is to have this build out sometime in July 2019, but that can depend on what issues we come across in testing the application feature that we are already running with some customers.

  • +1