Thanks for sharing the details and the error message — that was really helpful to follow. I had a similar sort of hiccup after an update, and you could try Dominik's portable 2.61 workaround in the meantime if you haven't already, just to keep things running while the plugin is updated. It might also be worth checking whether the plugin author has mentioned a newer build, as a small fix on their side could sort it more cleanly.