Same here too. Exactly the same error although in my case it happens on a desktop PC. Returning to 16.1.2 solves the issue.
