Bug 393098

Summary: Silent Install /S not obeyed if installing to an existing install
Product: [Applications] krita Reporter: TonyS <tony>
Component: GeneralAssignee: Alvin Wong <alvin>
Status: RESOLVED FIXED    
Severity: normal CC: alvin
Priority: NOR    
Version: 4.0.1   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
URL: https://github.com/alvinhochun/KritaShellExtension/issues/17
Latest Commit: Version Fixed In:

Description TonyS 2018-04-13 10:03:37 UTC
Installing using the Silent option /S 

It works on a CLEAN machine.

But if there is an existing install of krita, a pop up will appear saying that an existing install is found and that it would be reinstalled. But should this still pop up even if I used the /S switch for silent install? 

This needs to be totally silent install, otherwise it will pop up for everyone, pausing the install when I do a network deployment to a classroom.
Comment 1 Alvin Wong 2018-04-13 14:05:19 UTC
If you need it to work immediately, the uninstaller should run properly in silent mode (the installer actually does it). Assuming you haven't changed the install path, run the command `C:\Program Files\Krita (x64)\uninstall.exe /S _?=C:\Program Files\Krita (x64)` before running the installer.
Comment 2 Alvin Wong 2018-04-13 14:06:37 UTC
Also make sure that Krita isn't running before you call the uninstaller... because that will also cause a message box to show,
Comment 3 Alvin Wong 2018-05-20 20:20:12 UTC
I've made the change in the code, now I just need to add something else that needs to be added and make a new release of the shell extension so that it can be used in the future builds of Krita...
Comment 4 Alvin Wong 2018-06-04 18:56:04 UTC
Hi TonyS, the installer of the latest nightly build should have this resolved. Can you verify it? (Don't deploy it to an in-use classroom though.)

Nightly build: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/

I think this might not be in the next 4.0.x release, but will be in 4.1.
Comment 5 Alvin Wong 2018-07-25 14:45:22 UTC
Assume fixed in latest versions