I got the same error here and I was able to determine what the problem was. In our case we got the error because the MSI was launched from a network drive, and not from a local drive. While I had full read access to the network drive (it was mapped to a drive letter) I was launching it from, the sha...