Hi,
I had actually the same issue when deploying Windows 10 1703 into my environment.
I have managed to rectify the situation which another blog refers to disabling the 'Consumer Experience' via GPO
The “Consumer Experience” is the default mode Windows 10 (including Enterprise) is shipped with. This mode, upon initial login of a new user, commences the automatic download of a plethora of (unrequested) UWP apps, thus filling the start menu with games like Candy Crush. I deplore this feature beyond anything Microsoft has done in the past. It cheapens the Windows experience and frankly, I think they should be embarrassed that this is included in their flagship product. Fortunately, this feature can be disabled – but only on Enterprise edition.
In my case this policy was not set and building the device into an OU in Active Directory where there were no GPO's proved successful but as this would not solve my issue I started to look at my build Task Sequence in SCCM.
I finally discovered the issue was related to us requiring a private store and me setting a registry key and all I had to do was move this to last part of the build process.