It was related to that update as our clients running the ADNM were having a similar issue that was fixed with today’s update