[xjd]

1. Is there way to prevent JD trying to autoupdate itself? Just notifying is enough since I have to use downloader to install new version (sometimes 4 in a day).

2. And above brings 2nd question: Why JD always wants to install itself to administrator's Documents not where it actually is installed?

[Jiaz]

1.) why not just let JDownloader update itself? If you have issues with updates, then we should find the cause and help you solving them. What problem do you have with updates?

2.) by default JDownloader installs into AppData folder of the user on windows, else into home folder on linux or max.

JDownloader does not need admin, so no sudo/run as admin.

[MsChif]

On a somewhat related topic, why are there so many updates on some days? I'm going through my fourth update today, as I type this. I believe my record for updates in a day is eight... that is unacceptable, IMO.

It seems as though each item requires its own separate update... can't multiple issues be addressed in a single update?

[Jiaz]

@MsChif: Please read JDownloaders' update frequency is too high/annoying for me, why are there so many updates and what can I do about it? on https://support.jdownloader.org/de/k...pdate-behavior

[Jiaz]

Originally Posted by MsChif

It seems as though each item requires its own separate update... can't multiple issues be addressed in a single update?

In short: of course we do batch up updates but why let some user unnecessary wait for a plugin he/she is waiting for? all explained in the linked article

[xjd]

Originally Posted by Jiaz

1.) why not just let JDownloader update itself? If you have issues with updates, then we should find the cause and help you solving them. What problem do you have with updates?

2.) by default JDownloader installs into AppData folder of the user on windows, else into home folder on linux or max.

JDownloader does not need admin, so no sudo/run as admin.

1. Cause Comodo Internet Security blocks (contains) that .jar-file while JD tries to update itself resulting on fail (and me dling JD once again and clearing containment, sometimes as said like 4 times per day) and nothing I nor Comodo can do to it (per Comodo team unsigned file etc).

2. Running? No. Installing? Yes (besides when JD autoupdates itself (occasionally slips past Comodo)).

[Jiaz]

@xjd: Stupid comodo as the .jar file is not even a jar file you should be able to add JDownloader to whitelist or whitelist domain. Comodo can for sure do something to ease your pain but simply spoken, they don't want to. The .jar file only has .jar as extension. I will change the file extension later but unsure if that wil solve your problems.

[xjd]

Originally Posted by Jiaz

@xjd: Stupid comodo as the .jar file is not even a jar file you should be able to add JDownloader to whitelist or whitelist domain. Comodo can for sure do something to ease your pain but simply spoken, they don't want to. The .jar file only has .jar as extension. I will change the file extension later but unsure if that wil solve your problems.

Well send your regards to them. I have whined about it enough at Comodo forum.

Won't help unless update file is signed since Comodo blocks unsigned as it's supposed to. JD.exe is Trusted but update isn't.

Sometimes autoupdate goes ok and most of time needs to abort autoupdate and do manual update.

[Jiaz]

Originally Posted by xjd

Won't help unless update file is signed since Comodo blocks unsigned as it's supposed to. JD.exe is Trusted but update isn't.

They simply don't want to look deeper into this issue
1.) the updates are signed
2.) the updates are not in any format that Comodo does support, not exe, not jar file, so they can't even know about signature status
3.) most likely Comodo is behaving *crazy* as the file has .jar extension and they simply fail to recognize that extension doesn't mean anything when it is about scanning of files.

Originally Posted by Jiaz

@xjd: I will change the file extension later but unsure if that wil solve your problems.

I will do this by tomorrow. I will ping here once the change is live, so you can check if the issue keeps happening

[Jiaz]

Originally Posted by Jiaz

I will do this by tomorrow. I will ping here once the change is live, so you can check if the issue keeps happening

I just have renamed from .jar to .bin

[xjd]

Originally Posted by Jiaz

I just have renamed from .jar to .bin

Well it worked for a few updates but stopped working last week and now update file is .jar again.

Not a issue since I can use installer.

[Jiaz]

Originally Posted by xjd

Well it worked for a few updates but stopped working last week and now update file is .jar again

?? What do you mean? I did not revert my change and the file is still .bin?! Can you explain?

[MsChif]

Originally Posted by Jiaz

In short: of course we do batch up updates but why let some user unnecessary wait for a plugin he/she is waiting for? all explained in the linked article

Granted, but it seems like updates are done one site at a time... isn't it possible to combine multiple sites into a single update? The frequency is maddening, IMO.

[pspzockerscene]

Originally Posted by MsChif

Granted, but it seems like updates are done one site at a time

No they are not - only if developers push changes in such a way that multiple "restart needed" auto builds can happen in one row which can happen sometimes.

If this is annoying for you, feel free to only update JD once per day.