I wonder if part of the 2.0 consumer/final file was corrupted during download causing the strange behavior you saw? Others here can probably comment on the probability of this guess being right.

Glad it's going now.

-Zeke