After many time of workarounds and time spend in making windows installs, i have found the problem for some installations based on runonceex, not working 100%.

I dont want to copy-paste the explanation, so i put a link to my post:

http://www.msfn.org/board/index.php?s=&...st&p=558393

And from what i can see, many "runonceex-able" unattended installers aren't aware of this problem. So i ask to their makers, if they can apply the simple fixes i suggest in the post.

In resume the solutions:
1 - Use WinRAR Sfx in TempMode, and then just call the command
example:


2 - Use StartX or RunHiddenConsole utilities (both freeware). Join them in your sfx pack and invoke the command like this:
examples:



Note: anything related with this subject, reply here.

I hope that i could help! Thanks for your time.

And what if its not a .MSI ?

I'm not 100% sure, but from the preliminar tests i have done ... only .msi has this problem, maybe because the way msiexec works. But like i told you ... not really sure of this.

All the problems i had, was principally with .msi installations, and this fix was effective.

OK and now check my post #94:
http://www.msfn.org/board/index.php?showto...mp;#entry562764

WinRar sfx or StarX or even msistub and Hide.exe aren't necessary, if everyone would just update to the latest modified 7z SFX module... instead of using the old official one