Found a fix that worked for me on another post. Either an Office update broke things or a QB update broke things. Either way, reverting Office to an earlier version fixed things for me.

Follow the steps in this link (https://myinnerpc.zendesk.com/hc/en-us/articles/360042173231-How-to-Revert-Office-365-to-a-Previous-...). During step 3 of the process for making the .xml file, rather than using version 16.0.12527.20278 like in the article, use 16.0.15831.20208. I'll attach a photo of the .xml file I used as well just incase.

Hopefully this solves the issue for others as well.