I have not been able to download most of the P3Dv5.3 install files without getting "hash does not match" errors using the Checksum utility. Some components pass the checksum test but most don't.  I get the same outcome after many repeated downloads. Have no problems with other large downloads eg the recent MSFS 2020 update.  Seems to be some hassle with the P3D site.  Any suggestions?  Looks like I will have to revert to 5.2. Thanks

Bruce

Heya Bruce. I personally cannot see myself downloading *anything* without using Internet Download Manager. I forget what it cost me (not much IIRC) but it is indispensable for downloading large files.  

Hi Bruce,

I had your same problem with MD5 Checksum not matching with those of P3D but I have checked with an MD5 program that if I repeated the large downloads they didn't show
the Checksum I often found their diversity and this with both Download Manager (FDM) and without and all tested on different browsers.

This issue can be caused by hardware RAM / CPU problems especially if overclocked and the first thing to do is reduce BIOS overclocking or damage to the Windows component store or library
 of the protocols used on the network which was the case in my case.
  
To check for any damage, these commands must be run with CMD Administrators:

SFC  / Scannow

If any damage is found, execute these 3 commands:

DISM  / Online  / Cleanup-Image  / CheckHealth

DISM  / Online  / Cleanup-Image  / ScanHealth

DISM  / Online  / Cleanup-Image  / RestoreHealth

repeat SFC  / Scannow and at the end it should note that no integrity violations were found.

For the network protocol library, execute the command

NETSH  winsock reset

at the end restart the PC.

Try to download and check the checksum and if they are correct I recommend to do before making especially large downloads, check with SFC  / Scannow and then perform NETSH  winsock reset and restart your PC.

 

Thank you.

I was finally able to get a clean download with matching checksum by using a local M.2 disk as the target drive instead of the usual network drive located on my NAS.  I suspect there could be issues with my NAS drives or the RAID setup however the ReadyNAS interface app indicates a "healthy" system.  The spinning rust drives on the NAS are probably over 8 years old so would not surprise if there were issues.  But I also have a firmware upgrade that I can apply to the NAS so that might help.  There was a further complication after installing the upgrade -  Prepar3D.exe kept getting suspended in task manager.  It took quite a bit of online searching to make sense of this.  There were numerous posts that said all you need to do was right click on the exe in task manager and select resume, however I could not get the resume option in my Task Manager only end task.  Then I came across a post that said you did this in Resource Monitor and sure enough you could.  P3d then completed the loading process and fired up normally.  Haven't had the suspend thing again so perhaps was something to do with getting the new version going for the first time.  Just one other niggle I keep getting an EZDOK sound buffer cannot be created error - no idea what that means.  Oh one other thing P3D now takes over 7 minutes to fully load on a M.2 drive much longer than previously.

Bruce