Well, I re-tried it again this evening, and now comodo dragon will not run at all in the container or in the virtual desktop (dragon won’t launch). Nothing is recorded in the logs, so it does not appear to be blocked by CIS. It launches fine when not virtualized. I had this issue several times in the past few years, where starting dragon virtualized gets broken for some reason. In the past it was a dragon update that broke it. So, maybe the recent dragon update broke it again. rebooting no help, emptying container no help, diagnostics no help (as usual).
PS on my windows 10 machine, I did try adding comodo dragon to containment and firewall as shown in Cruelsister’s video, but it would not let me…comodo said it could not make the rule because it would lead to system instability 