Problems using HTML-Export on Internet Explorer on Windows 10

[Tobias-FWWS]

Screens contains of
- Synchronized video wich ends with a still-image for some seconds.
- Button for "go to next screen" wich appears a few sevonds before the end of the video with stop-function 1 Second before end of the video

So the still-image at the end of the video is shown at the end of the screen, waiting for the user to press the button to proceed to the next screen.

Export as HTML worked quite fine in any tested browser:
Good internet connection: video plays, when reaching stop-point defined in the button the video stops. Click to the button leads to next screen.
Poor internet connection: load-symbol appears, video plays some seconds then stops, load symbol appears, video plays some seconds, ..., when reaching stop-point defined in the button the video stops.
This way it does with Chrome on any tested systems, Firefox on any tested systems, Internet Explorer on Windows 7 and Edge on Windows 10. Everything is OK and fine.

Now someone told me about problems with Internet Explorer on Windows 10. Until this i thought Win10 has only Edge as system-browser. Well, it has hidden also Internet Explorer and some companies really still use it.

It does not exactly the same on each try. Most times the video plays without stopping AND above it a load-symbol appears from time to time or even while playing the whole Video long.
Build and exported with Captivate 2017 the main-problem is the overlay of the "load"-symbol; it ends with a black field where the video should be and the button.
Build and exported with older Captivate-Version 8 (where the project ones was done first) it sometimes goes on without the load-symbol and even seems to work, but in most cases it also shows the load-overlay and at least the whole think freezes even without showing the button and the user can not do anything further.

For me it seems to be more a problem of the Microsoft-system and browser than one of Captivate. But in any case it has to work on the systems used by the customer and perhaps somebody also here knows how to fix it.

[Tobias-FWWS]

Tried several things wich does not solve the problem and got at least a hint that seams to work:

Just leave free about 0,5 of a second in any timeline with a video before the video starts.

Worked on several computers with windows 10 and internet explorer and i have some hope that it will work on every one.

(Just posted to help someone with the same problem)