Error #132 after patch 10.0.5

Exactly same here.