Its a known bug on 6.3 so updating it to 7.0 will fix it. The other current anomaly is the updater also needs updating, just to get the current update to 7.0. And once updated, the updater needs to be put back how it was. Sounds worse than it is
I tried linking to the thread regarding the steps but it wouldn’t stick for some reason (my incompetence being the likely cause).
