Can I suggest a compromise between checking for updates every time NMM is launched and having the user do it manually? Let NMM check for updates on a schedule. It can be any sort of schedule really, after x number of starts it looks for an update, on the 15th of every month it looks for an update, or even after 2 weeks it looks for an update. All other behavior should remain the same. Ask the user if they want an update and so on. I believe this is a better solution, assuming I understand the OP. Its a nice middle ground that benefits users, we are a forgetful bunch and may not think to log in and check for updates, and it helps elevate support troubles/costs by helping users keep up to date with the latest version of NMM. Thanks for all the hard work, NMM rocks!