VMware Horizon Community
mardah
Enthusiast
Enthusiast

Thinapp process never ends when starting IE10 native

Hi

I have a couple of applications that use Internet Explorer through Thinapp due to special add-ons etc. And it works great except that it never closes the Thinapp EXE file when Internet Explorer ends on 4.7.3.

However I know this was working as it should on the servers before we upgraded to IE 10. Now, it does not work as it should and the processes just piles up. How to solve this?

I tried AutoShutdownServices (even thouhg its for services) and all other debuging options that was commented out, nothing seems to help.

I tried to package this in Thinapp 5 instead and the process does end, but it throws an error on Internet Explorer with werfault.exe that you have to acknoweldge before process ends and I'm not able to get around this error or supress it.

Tried to disabled WER and add registry exceptions etc. nothing helps. Also tried enabling the IgnoreDDEMessages without any help.

I read some mentioned that we should have an exception on child process svchost.exe, I tried this in external/virtual or whatever without any success. Anyone have any idea?

The Thinapp package is supposed to run on 2008 R2 servers with no admin rights.

Maybe I'm starting it wrong? I use commandline to iexplore followed by web address like this. CommandLine="%ProgramFilesDIR%\Internet Explorer\iexplore.exe" http://Your.URL

Or I have to do a full packaging of IE 10?

Thanks for any input

Reply
0 Kudos
2 Replies
mardah
Enthusiast
Enthusiast

As noone replies i guess noone have this particular issue. However I found out that on Thinapp 5, enabling wow64=0 removes the crash notification and no processes are left behind.. in other words it works perfectly except printing that fails when enabling wow64=0.

Have anyone got a solution to get Thinapp to work with the print service when wow64=0 is enabled? Like including files or certain externaldlls etc.?

Again, thanks for any input you may have

Reply
0 Kudos
bebris
Contributor
Contributor

Hello Mardah,

I had problems with printing in 64bit environment which I solved by copying spool folder form %SystemSystem% also to %SystemSystem(x64)%. Problem was that in 64bit environment spool folder was in WriteCopy mode!

regards

bebris

Reply
0 Kudos