We came by the same error as well. Only cost us a couple of days, ffs!!!  Overwrote the new SOURCE Dotnetnuke dlls in the Bin folder with the Dotnetnuke dlls from the UPGRADE  folder and lo and behold it worked OK. Now what really ******* me off is that this is a brand new version and it failed at the very FIRST hurdle. So who has tested this so-called "STABLE' release?

Maybe it's time Dotnetnuke reverted to its former format (and glory!!) before the days of Share certificates! What do you reckon Mr Shaun Walker?

[PS Because this was a new release we mistakenly believed this had been tested thoroughly and put all of our efforts into our own modules and third Party modules assuming that was where the error was.

After the issues we suffered with IMC on DNN 5.0.0 not so very long ago and the reticence of Mr Charles Nurse to readily admit there was an issue, somebody, somewhere in the upper reaches of the Dotnetnuke hierarchy needs to get a grip on testing.

Try copying the standards that the FDA imposes I would respectfully suggest.]

Okej, this did happened again yesterday. I was trying to upgrade to 05.01.04 and I did get the same error message again. But the last trick didn't work this time. So I tried a lot of things until I founded the new solution. What I noticed was that it didn't even unzip the js files, I DotNetNuke_Community_05.01.04_Upgrade/js and there was no js files in there. And when trying to extract only the js folder, it actually says "An error occurred while copying the file". It doesn't say that when extracting all instead it just skips the files. So the problem yesterday was that I didn't use the newest files.