The script debugging thing did the trick, though. Haven't gotten the error since. It was definitely something that the Office installation did, though that seems like an odd step to include in the installation.