If that is all it takes, that seems like a reasonable solution for now - at least until the bug is fixed. Cleanliness and simplicity are great, but stability is definitely more important.
In .NET, you could automatically invoke it via a static class constructor. The problem would just be determining which class to put that constructor in to make sure it is invoked in time. If there are multiple classes that must invoke it before they are used, a simple internal "helper" class could be added to ensure its only called once.