The update installation should retry based on the “Software Update deployment re-evaluation” schedule. If the time limit is reached and notepad++.exe isn’t closed, the script will exit with exit code 1618 / 0x87D00664 (Updates handler job was cancelled) in Configuration Manager and the Notepad++ update will not be installed. For example, you could use / checkforconflicts 120 to specify a conflicting process check for up to 120 minutes. In order for the process check to work, both the / checkforconflicts and an integer number must be defined in the command line argument. The script will recheck every minute for up to the max runtime you specify or until conflicting processes are closed. You need specify the max runtime in minutes by adding an integer number in the command line argument after the / checkforconflicts.

/ checkforconflicts – this command line argument will tell the wrapper script to check if notepad++.exe is running.

Command Line Argument Supported In Version 1: EXE installer (SFX installer) that will use a wrapper script (VBScript) that can optionally perform various checks prior to calling the Notepad++ installer. In order to work workaround to this problem, we created a self-extracting. This is to address and issue where if the Notepad++ installer runs while the notepad++.exe process is also running, the update will fail and in some cases may uninstall Notepad++ and fail to install the update. This starts with the update “Notepad++ 7.3.3” and any future Notepad++ update. We are releasing a wrapper script to perform the installation of Notepad++. You can now perform custom actions directly using our publishing service, and we no longer need to directly modify the Notepad++ installer with a wrapper script to perform these actions.

The wrapper script for Notepad++ is no longer supported.

Notepad++ plugin manager is blank