Already asked and answered here, but to reiterate, this is a known issue specifically with the 202605210254 build and no other.
If you update to the latest build (or indeed revert to an earlier one), you won’t get this issue.
Already asked and answered here, but to reiterate, this is a known issue specifically with the 202605210254 build and no other.
If you update to the latest build (or indeed revert to an earlier one), you won’t get this issue.