There's been a report on this thread that this has been addressed. Please reply back and confirm that you're no longer getting this error. Thanks @PaulE1
