Same here.. that should never been enabled.. I guess now we know why..
although my NEXT suggestion would have been to do a factory-reset, which would have set that setting back to off, thereby fixing the issue, so technically, given a long-enough timeline, I was right.