http://imagej.273.s1.nabble.com/Fiji-not-starting-up-tp5011018p5011035.html
ImageJ Updater. So it should be feasible to update installations on Windows
now. Unfortunately, installations which have already been rendered
non-functional will still not start up. In that case, downloading a new
>
> Hi Jacob,
>
> > Here's my bad installation.
>
> Thank you very much. I can confirm that there is a bug in the ImageJ
> Updater on Windows, which causes it to hose installations. It downloads
> only a subset of the updated files. I fear that any Windows users who
> update will be stuck with a non-working installation.
>
> I am investigating the best way to fix things, but the best options for
> Windows users at the moment are: A) do not update; or B) download a fresh
> installation from
http://imagej.net/Downloads.
>
> Regards,
> Curtis
>
> On Mon, Dec 22, 2014 at 10:20 AM, Rebecca Keller <
[hidden email]>
> wrote:
>>
>> Here's my bad installation.
>>
>>
https://www.dropbox.com/s/j0xacahjedk2q5z/Fiji.app.zip?dl=0>>
>> Jacob
>>
>>
>>
>> On Mon, Dec 22, 2014 at 10:51 AM, Curtis Rueden <
[hidden email]>
>> wrote:
>>
>> > Hi everyone,
>> >
>> > > it might be a good idea to run Fiji from the command line and look at
>> > > the output. If you share it on this list, someone might be able to
>> > > provide more specific help.
>> >
>> > I second Jan's suggestion. In addition, it would be great if someone
>> could
>> > zip up an affected installation and post it online somewhere, for study.
>> > Having a broken installation would be helpful to understand what went
>> > wrong, and put safeguards in place to prevent it happening again.
>> >
>> > Regards,
>> > Curtis
>> >
>> > On Mon, Dec 22, 2014 at 9:45 AM, Jan Eglinger <
[hidden email]>
>> > wrote:
>> > >
>> > > Dear all,
>> > >
>> > > On 22.12.14 13:12, Rebecca Keller wrote:
>> > >
>> > >> Yes, I had already tried both task mgr and restarting, to no avail.
>> > But I
>> > >> guess no one else is having a problem? Also, the task mgr registers a
>> > >> short
>> > >> instance of FIJI, but then it goes away immediately.
>> > >>
>> > >
>> > > To see the cause for this, it might be a good idea to run Fiji from
>> the
>> > > command line and look at the output. If you share it on this list,
>> > someone
>> > > might be able to provide more specific help.
>> > >
>> > > In general, you can try to delete the "update" folder within
>> ./Fiji.app/
>> > > and it might also help to delete ij-updater-core-*.jar and
>> > > ij-ui-swing-updater-*.jar depending on what state your Fiji
>> installation
>> > > was *before* the last update [1]. This will trigger a new download of
>> the
>> > > updater upon starting Fiji.
>> > >
>> > > Hope that helps,
>> > > Jan
>> > >
>> > >
>> > > [1]:
http://fiji.sc/Fix_non-functional_ImageJ_after_Update>> > >
>> > >
>> > > --
>> > > ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>> > >
>> >
>> > --
>> > ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>> >
>>
>> --
>> ImageJ mailing list:
http://imagej.nih.gov/ij/list.html>>
>