#168824
I also just got this error after updating to 1.37. I will try this manual fix.
Are there any change notes for 1.37 or was it just to update the TOC?