This issue was already reported by some other members, see: White screen in thinapp of Firefox, thinapp not working - Firefox version 50 and higher
Perhaps Lakshman can update you (us) on the status of the issue(s).
The latest version of Firefox supported by ThinApp is 50.1. Any version after 50.1 still have issues when virtualizing them and are not supported at the moment.
Please check this KB:
Thanks Everyone for the information!!
I wasn't aware of this article (published march 17th, 2017), to be honest, and I've been Thinapping Firefox up until 52.0.2 without much issues. I just learned there are problems with Firefox and Thinapp, apparently since 50.1 (release date: december 16th, 2016 a full three months before the article was published). I'll be having a go at 53.x real soon and I assume it won't give me much headaches either. Sure I have some weird stuff and I did have to do some workarounds (https://communities.vmware.com/thread/538883, check it out OP, it will solve your problem), but Thinapp 5.2.2 is perfectly able to build a functional Firefox package. At least for me, in my environment, with my settings.
Can you explain what exactly the problem is with FF 50.1+ and Thinapp? A blanket "not supported" isn't of much help. Maybe I can relate some of the (albeit minor) issues to it so I can close some internal support tickets complaining about that minor stuff with that info.
Firefox 53.0 doesn't work as Thinapp sofar. "Couldn't initialize broker services". Our friends at the Mozilla project have been doing some funky changes again, and it looks like it's now definitly broken in combination with Thinapp. Yay.
I lied...it works as a raw capture with only the ExternalDLLs thing. Now to figure which setting/change I use for my builds breaks it...things are looking ip again.
[edit2]I lied again...firefox starts but is non functional.
[edit3]Weird, can't get 53.0 to work. Funky enough, a Nightly works fine, so here's hoping 55 will start working again. I'll go try a beta (54.x) now...
[edit4]Beta doesn't want to work either. Sucks.
Funky. Recently FF 54.0 released, making 55.0 the beta and 56.0 nightly. Here I was hoping that by the time 55.x rolls around I was able to build a working Firefox again. But alas, it seems between Nightly and Beta something consistently changes in Firefox, yielding it inoperable when Thinapped. The behaviour changed though. It went from doing nothing to generating a crash report for a "crashed" tab.
I made a support request for the "hotpatch" referenced in the article linked above. Hopefully that helps. If not, well, I guess I'll bug VMware support some more. With some luck they'll be able to work with the Mozilla guys to get these problems ironed out.
Ye gods, it works again!
Caveat: It turns out the Thinapp of Firefox doesn't pick up the system proxy settings. When entered manually, it works. At least I can deploy FF55.0 now!