The error doesn't happen anymore in the current update, but even when the error appeared, it only affected an optimization which increased the speed of the update, but the update would work nonetheless, although a bit slower than it might have been.
However, it's not an issue anymore with current version.