#1
|
|||
|
|||
2 questions about JD about updates
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? |
02.08.2024, 15:36 |
pspzockerscene |
Message deleted by pspzockerscene.
Reason: Nonsense
|
#2
|
||||
|
||||
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.
__________________
JD-Dev & Server-Admin |
02.08.2024, 15:37 |
Jiaz |
Message deleted by pspzockerscene.
Reason: Nonsense
|
#3
|
|||
|
|||
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? |
#4
|
||||
|
||||
@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
__________________
JD-Dev & Server-Admin |
#5
|
||||
|
||||
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
__________________
JD-Dev & Server-Admin |
#6
|
|||
|
|||
Quote:
2. Running? No. Installing? Yes (besides when JD autoupdates itself (occasionally slips past Comodo)). |
#7
|
||||
|
||||
@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.
__________________
JD-Dev & Server-Admin |
#8
|
|||
|
|||
Quote:
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. |
#9
|
||||
|
||||
Quote:
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. I will do this by tomorrow. I will ping here once the change is live, so you can check if the issue keeps happening
__________________
JD-Dev & Server-Admin Last edited by Jiaz; 15.08.2024 at 21:47. |
#10
|
||||
|
||||
I just have renamed from .jar to .bin
__________________
JD-Dev & Server-Admin |
#11
|
|||
|
|||
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. |
#12
|
||||
|
||||
?? What do you mean? I did not revert my change and the file is still .bin?! Can you explain?
__________________
JD-Dev & Server-Admin |
Thread Tools | |
Display Modes | |
|
|