- Mar 29, 2020
As far as I know, this error only happens on the MS store version? It seems to be a bug introduced by the February patch.
I thought I'd guessed a workaround, and that my update would fix it, but since I don't have the error myself I couldn't be sure. If it still doesn't work, I don't really know what to do except wait until this is the bug is patched :/
Exactly, i'm on Windows Store Version. I'll stay on the PDF version so !