I was able to resolve this issue, it was a minor defect on the update mechanism.
You might continue to see this error for up to a few hours, because the update info is cached. Eventually the data will be refreshed and you will not be seeing this error any more.
Thanks again for your help in identifying it.