search

qzind / qz-print

Archive for legacy qz-print versions (1.8, 1.9). See https://github.com/qzind/tray for modern versions.
Other
141 stars 101 forks source link

Alpha 2.0 Windows 10 installers issue #166

Closed robert-gazsi closed 8 years ago

robert-gazsi commented 8 years ago

Hi,

For some reason, only the first release installer works: https://github.com/tresf/qz-print/releases/download/2.0.0-alpha1/qz-tray-2.0.0-alpha1-1.exe

All other newer ones (up to 6 at this moment) are downloading ok but are not starting. I have Windows 10, and tried with AV off as well.

Thanks.

tresf commented 8 years ago

Sorry, I had replied to the wrong bug report.

We can't reproduce this.... Can you please post the output of your installer log for alpha6?

tresf commented 8 years ago

@robert-gazsi can you try the latest RC1 installer here? https://github.com/qzind/qz-print/releases/tag/2.0.0-RC1

Note, nothing significant has changed in this version, but unless we can reproduce a problem with the installer, we'll have to close this as invalid.

robert-gazsi commented 8 years ago

Where can I get that log file?

tresf commented 8 years ago

Assuming you're installing on Windows, it will be in the installer window when "Show details" is pressed.

image

tresf commented 8 years ago

Note, if you've recently upgraded Java, a botched Java install can render the installer useless, which is usually fixed by 1. Rebooting and then 2. Reinstalling the 32-bit and 64-bit versions from the offline installers.

robert-gazsi commented 8 years ago

I don't get to this window, only the allow to run warning box :(

tresf commented 8 years ago

I don't get to this window, only the allow to run warning box :(

Are you on a solid state hard drive? I would recommend forcing a scandisk and a reboot. The installer should at least greet you with the "Next" screen. Your issue is symptomatic of something interrupting the executable, often caused by a corrupt in-memory system process (or a virus, a blocking antivirus, bad HD sectors, or not rebooting after a Windows Update, etc). In all of the scenarios, I don't think our installer has an issue, but we'd be happy to continue troubleshooting to get things going again.

robert-gazsi commented 8 years ago

A reboot actually got it solved! It was Symantec AV, even though I disabled it...

Thanks a lot!

tresf commented 8 years ago

:+1: