Update: James C. Good news, we've identified the root cause. If the # is included in the event description, it is not correctly encoded in the URL and gets misinterpreted by the browser in the add-to-calendar link.
We will have a fix out shortly. As a workaround, if you edit the Event description to exclude the # character it will avoid this bug.