Is there a switch or series of switches that can be used to prevent background components from updating?

Nobody has claimed this yet.

Forgive me if that doesn't make sense. The problem that I'm having is this:

I have downloaded the last 'release' version of forge. It will run ok for a few days, but almost like clockwork at some point it will stop. Most times I have to delete the system directory, and drop it back in. After a few attempts of running the 'run.bat', and re-installing components, it will run.

Most of these failures to start seem to occur while checking for updates to components in the background, I've search many of them here and on the web at various times, been able to resolve some of them. I used to try to run the update regularly, but that made things more unstable.

I'd like to just be able to have the release version run stably and choose a more controlled method for updating, making sure the current directory is backed up, etc. Any insights would be appreciated, thank you.

No source file or test is named. Start with the run.bat workflow and trace where background component update checks occur; determine whether a user-controlled switch is feasible. Done should mean the release can run without unsolicited component updates and that controlled updating is documented or testable.

Written by the indexing model from the issue text.