Hi @bjcresswell, thanks for the heads-up on this, I’ve passed it on to the other members of our support team 
Not sure how the SERVO output could have been set to disabled without direct user input, since parameters generally aren’t set automatically - that’s definitely odd. Perhaps worth noting that the reset parameters to defaults functionality in QGroundControl can be used if the Pixhawk starts acting weirdly.
Given you flashed the SD card directly there was no update script that could have potentially changed something, so I’m not sure that’s a possible cause. If 0.0.31 was setting a parameter on startup it should happen every time to everyone, which isn’t the case. That said, I don’t know what did cause it, so it’s at least something we know has happened now, and can try to keep an eye out for in case it comes up again some time.
Fair point, although that’s something of a bandaid fix for the underlying issue that “it should be obvious how to update the software correctly”. As I understand it most of the links are to a documentation or website page, which should have the latest information or automatically redirect to somewhere that does. Direct download links tend to be of custom temporary versions that fixed a specific issue, and generally we expect that the context there will discourage people from using them, especially if they’re old links. If and when that kind of thing gets attempted by mistake it generally doesn’t work anymore, which either leads to the relevant documentation being found, or a question on the forum/to our support email asking how to fix the issue.
Conveniently, the existing companion software is in the process of being replaced with a version that is very different, and requires flashing to upgrade to, so we effectively get a fresh start. We’re also in the process of replacing our docs system and structure, along with various other changes that should improve information accessibility (e.g. I’ve just added a Software and Firmware section to our work-in-progress Technical Reference)