You can consider this a false report. I believe it’s beyond the scope of the HTMExecutable setting and is quite possibly related to the way the Edge browser security operates. This behavior can be due to security policies, cached settings, or the nature of the resource being loaded, many...