It seem you are trying this directly from the file system. The launch scripts tries to load the AppMeasurement and uses a protocol agnostic //assets.adobedtm.com/...
When you open your file from the file system, it will have the file:// protocol and thus it won't find the AppMeasurement.
The easiest way is to have the file you are testing on an actual web server like Apache or IIS.
If you want to test it from the file system, I suggest to enable the download as archive option in the environment. You will then get a ZIP file with the launch script and AppMeasurement which you can extract locally. But still I am not sure if it will resolve relative paths correctly if used from file system as there are some restrictions.
We host all the files on our CMS, so if we download the zip from launch and extract it to the CMS it resolves the paths correctly. With the ZIP option enabled it generates the launch script differently with relative paths to AppMeasurement.