I too am getting this error. Is there any work around or ETA on a patch? This is currently a show stopper for my upgrading to to the latest build (up from the beta version).