This was requested by a partner back in Jan 2015. Just adding to the echo just in case.
Unfortunately, we are aware of this issue but have yet to find any way around like problem. For SSL piggybacking, we simply pass on your URL to Microsoft's API, which now appears to require a trailing slash when specifying a virtual directory (meaning, if your piggybacked site ishttps://mysecuresite.com/SC/ then your users would need to include that trailing slash in order for the page to load correctly). Apparently, the trailing slash is meant to differentiate the virtual directory from an actual directory.
I will get a defect registered regarding the Guest Session Starter Exe, so that we can get that fixed.
Customer support service by UserEcho