Thanks for the reply Umberto. I did in fact find a solution to this security problem. Not sure if it affects all later Windows 10 Pro builds but it did modify mine!
My build for reference is 19042.685. It required a Group Policy edit but all fine now.
Many thanks.