Please consider helping out those that deploy this in managed environments.

  • Having the software autoupdate in a single user or non-managed environment is a great idea but you all have to realize that this software is popular enough that it is in managed environments and those of that manage those environments would like to offer advice on adjustments that would improve the ability to deploy and manage notepad++ effectively.

    I would like to suggest that Autoupdater not be placed in the user’s context (ie C:\Users\xxxxxxx\AppData\Roaming\Notepad++). First off the setting is software centric not user centric. If multiple people use the machine and person A wants the software updated but person B does not, my guess is the software is going to get updated no matter what person B wants or it wont get updated and person A will think the autoupdater is broken. So if you agree it should be in the context of the software I would ask that if this change is made it be configurable on install so that it can be turned off/on if so desired. I know you are wondering why you would want to turn off the autoupdater but in managed environments software tends to be updated uniformly to limit version support issues.

    Appreciate your time and efforts on this product it is an excellent piece of software.

  • First off Let me apologize I didn’t search before posting so this is a duplicate topic, but I do see that others share my concern about not being able to turn off the autoupdater in an efficient manner. I also see someone had agreed to look into this and add this functionality but has not done so (got this from a year old post). You might want to consider this, when we cannot install an application in a manner that makes it easy to maintain in an enterprise environment we will encourage our customers to choose apps that can be easily deployed and maintained and explain to them why applications that are less enterprise friendly might not be the best choice.

    Please consider addressing this in a near term release.

  • Well since I am not one to wait for others to solve my problem I thought I would post how I got around the issue I raised. I used Active Setup to to place the updated config xml file in the users profile. A coworker suggested this and it works like a charm. For those who dont know active setup is not supported by Microsoft but it does exist and is used to perform actions in the user’s context.

    So good luck to you others deploying this in a managed environment.

  • @Paul-Targett

    please ignore my ignorance but how exactly is this solving the issue you raised?
    And may I politely ask what exactly should be changed in order to make npp more useful
    for managed environments?

    Do you want to have additional/less install switches?
    If so, which?
    Or do you have something different in mind?


  • Which type of installation do you use?

    Notepad++ Installer 32-bit x86: Take this one if you have no idea which one you should take.
    Notepad++ zip package 32-bit x86: Don’t want to use installer? Check this one (zip format).
    Notepad++ 7z package 32-bit x86: Don’t want to use installer? 7z format.
    Notepad++ minimalist package 32-bit x86: No theme, no plugin, no updater, quick download and play directly. 7z format.

    The autoupdater is named gup.exe under Notepad++\updater and has a corresponding config file gup.xml. Gup.xml could be modified to avoid that the update page could be found or could be removed as in the minimalist package.

    The gpup.exe in the same folder is the updater for the plugin manager.

Log in to reply