@Nephilimi said:
I’m actually curious now, is the general population not using this on their servers?
There are only a handful of people who have come to the Community Forum from the “server” perspective – and most of those were coming to say, “why don’t you use installation-toolkit-xyz to make IT’s life easier”, and never really went into detail into how they were deploying to that point. And though it might not meet all the needs, the newer MSI installer (new to v8.8.8 in Nov 2025) seems to have quieted those types of inquiries down.
So in the Community, while we get great insight into how individual/personal users use Notepad++, we don’t have much insight into the server-deployed side of things. (In our minds – or, at least in my mind – the “general population” are individual users, not server-based users. I have no clue how the numbers actually pan out between the two user-bases; we just get a individual-user-bias in the Forum.)
But my guess is that the server-admins had auto-update turned off when they’d install it: either through pushing a custom config.xml to each user’s %AppData% folder, or through using a doLocalConf or -settingsDir to point to a more central config location (or, once the feature was enabled, bundling their own config.xml in the installation directory, which then gets used as the template for new %AppData%-based config.xml), or through deleting gup.exe in the old days or now using disableNppAutoUpdate.xml in the install directory
