New
#11
We are potentially on to something here I think!
I will start testing first thing tomorrow. I've had the issue since first using W10 on 16xx. I always believed it was intentional by Microsoft. Even on PCs that are prebuilt I've had the issue.
So I'm beginning to believe it may be a localisation bug with Pro. I would have to double check the iso for Enterprise as I'm not 100% sure if it is a localised or US version.