Hmmm… I have seen this sort of error caused when an OTA update does not download correctly, but that was with earlier SDK versions. I haven’t tried to reproduce it with SDK 38 before. I was hoping that with the recent changes to the Updates code that this would have been fixed.
Here’s a comment from me about this along with a link to something that seemed to fix it for me: