@loginerror I believe that this is happening because Chrome first creates a .tmp file and only rename it to a .crdownload file when the actual downloading starts. In between, Chrome is checking if the download link is pointing to a malicious file. This check is usually very fast so it’s not a problem for most people. But if there’s a delay between the renaming from .tmp to .crdownload, the Wait For Download might think that the .tmp file is the downloaded file.