Downloads for Installation/Update Repeatedly Failing, Incomplete

Support
1

Operating system

Windows

Joplin version

3.2.11

Desktop version info

Joplin 3.2.11 (prod, win32)

Client ID: 6c256236d1294b2d80b2b8306232eebb
Sync Version: 3
Profile Version: 47
Keychain Supported: Yes

Revision: 2fba101

Backup: 1.4.2
Freehand Drawing: 2.14.0
Quick HTML tags: 0.2.0

Sync target

OneDrive

What issue do you have?

For many months now, each time I accept a prompt to download a Joplin update, when Firefox (latest) indicates completion, I end up with a large joplinxxxx.part file, some hundreds of kbytes and a, say, Joplin-Setup-3.2.11.exe file of ZERO bytes.
Inadvertently running the exe causes a 'This program can't run on this PC' pop-up, of course. Renaming the zero-byte .part file to .exe and running it fails, because, I have inferred, it is incomplete, too small.

I have just downloaded Joplin itself from the home page, renaming before saving as joplin-setup-etc-2.exe. When it completed I had Joplin-Setup-3.2.11.exe in full size plus Joplin-Setup-3.2.11-2.exe as a zero-byte file. The xxx.part file remained unchanged.
This is clearly not a successful download arrangement.

Only Windows 10's Defender is running as a file-checker. Firefox's uBlock Origin, BitWarden; nothing much else.

As I say, over many months this download faulting has been occurring.
Anyone else?

2

Let's try different environment for the download

  • different browser
  • different network
  • temporary disable file checking from Defender during the download

Does the same happen when you download portable version btw?

3

Ha! Mea culpa!
I had a 'light-bulb' moment today: it turns out that my 'nothing much else' was the cause of Joplin-Setup .part download failures.
I have Syncredible set up to synchronise two download folders between two computers, and, sure enough, Synchredible was detecting the arrival of the .part file and its zero-length .exe companion.
Copying a live downloading partial file really screwed things up.

By adding a *.part item in Syncredible's Exclusions list, things behaved well. The zero-length temporary .exe present during download was still copied to the sync computer, but that's a factor I can live with. It'll be detected in the next monitoring-activation event.

SO, this thread can be deleted or just marked as SOLVED, but it's a possible alert for anyone running a file and folder monitoring program - RealTime Sync, File & Folder Watch, etc.