Hi everyone,
I just installed the new Silo 2.5 update.
When I click on its icon, nothing happens (it doesn’t show up).
However it’s running in the Task Manager.
Anyone getting an issue like this? 
win10 Pro 64-bit
i7 6700k
32gb ram
1080 gtx
Thanks…
I have had a similar issue with the pre-2.5 releases. Oddly what has worked for me is to open windows explorer before starting Silo. Then after starting Silo I immediately switch to the explorer window to be sure it is the active program. Once Silo started I could kill the explorer window.
Most of the time Silo would just crash and doing the above would solve the issue. The ‘not showing up’ problem was solved by this about 30% of the time.
Huh. This is certainly not behavior that we want with the program–thanks for the report! We’ll look into it and likely post back here with some follow-up questions.
@makit3d, you said you had this is pre-2.5 releases? Do you mean the full releases or the beta releases leading up to 2.5? (Also: nice creative workaround, there…)
@Djeust, have you run earlier versions of Silo that have worked without this issue?
@Nevercenter (Presque)
The focus issue has been there since the early 2.3 release. The latest 2.4/2.5 releases have not had this issue for me. It’s been so nice. 
Thanks for the help,
I figured out the problem.
2.5 didn’t install correctly alongside 2.3, I probably should’ve uninstalled 2.3 to begin with, but I figured that they could coexist since 2.5 is 64-bit.
But apparently they were both installed in Program Files (not Program Files x86 for Silo 2.3) And for some reason 2.5’s shortcut was pointing to 2.3 and 2.5 didn’t exist in the Program Files folder…I hope I didn’t lose you guys there.
So all I did was uninstall Silo 2 and tried to unistall the other Silo 2 but it can"t find the folder……I guess that’s normal because I just uninstalled it (a/o it doesn’t exist).
So I went and installed 2.5 and it works!
Now I have a ghost of Silo 2 floating in my app list, but that’s not too important. Because 2.5 seems to be working properly.
Lesson learned :“First, I must unistall then I may install”.
Thanks again for your help.
@Cinnsealach: You’re probably right.
If I can remember correctly , I believe that, under the anxiety induced upon me at the moment I discovered/down-loaded the latest Silo release, I spammed the enter key so eagerly during its install that I most certainly pointed it to the wrong folder.
I’m “djeust” an idiot!.
@nevercenter Thanks & keep up the good work! I’m Sooooooo happy to see Silo getting the love it deserves