Yet another person struggling to get Windows 10 unviersal to work. I had similar issues on my Windows 8 PC when building for 8 Universal a long time ago… I thought I would share the issues I’ve been having building using Unity 5.3.1f1 to build for Windows 10 Universal.
The error messages I’m currently getting are:
Severity Code Description Project File Line Suppression State
Warning The referenced component 'Windows Mobile Extensions for the UWP' could not be found. Vector Wars
Error CS0103 The name 'StatusBar' does not exist in the current context Vector Wars E:\Dropbox\Releases\VectorWars\U10\Vector Wars\App.xaml.cs 105 Active
Error Could not find SDK "WindowsMobile, Version=10.0.10586.0". Vector Wars
Warning Failed to resolve all project references for 'Vector Wars'. The package restore result for 'Vector Wars' may be incomplete. 0
This is running Windows 10 Pro with the latest updates, fresh install of Unity 5.3.1f1 and the 20 odd GB of data it brings with it. A fresh install of Visual Studio. And the 10.0.10586.0 Windows 10 SDK.
I’ve tried installing earlier SDK’s and trying to push that, but with no success. I upgraded from Unity 5.3.0 to 5.3.1 (wasted a lot of time on the 20GB of installers) but with no success. I’ve removed and re-installed the SDK’s several times, losing a couple more hours, also with no success. I’ve read every forum post I could find in depth, checking everything from the nuget settings to physical files. I’ve rebooted many times, changed the SDK references, blown away and recreated the built project, added all Windows updates, and done just about everything I can think of.
I’ve made sure that Microsoft Visual studio does recognize the SDK’s as installed (and allows me to change to them in the Project Settings). However, on build, these errors always occur. I tried to upgrade to the latest patch release, but the Unity Downloader seems to be bugged and wont let me progress through the menus. Because the runtimes and editor are now seperated, and the runtimes are inaccessible, I cannot go any further with the patched release for installation.
I’m in the process of removing everything again, and reinstalling again with 5.3.1f1 and the appropriate SDKs, wasting another half day on Windows Universal already. But if I find a solution I’ll post it.
I’ve found out why the SDK’s aren’t being recognized.
The Windows 10 SDK let you specify any folder you want for installation (so YAY, you can push it to some barely used drive, if you are like me). However, once installed, no matter if you remove the SDK (etc) you cannot change it to install to a different path than the one you selected. It always forces you back to the folder you specified.
The problem? You guessed it. Some brilliant mind (I’m assuming developers working at Microsoft) have hard coded references to only access SDK’s listed in this folder:
C:\Program Files (x86)\Windows Kits\10\Include
Just to think, this is an indication of what to expect in their SDK. Fun… symlink time.
Also, although this lets me get “farther”, it hasn’t resolved the issue yet. Still plugging away…
Reinstalling both SDK’s. Using the “new” folder that it keeps forcing me to and raising it up as a symlink to the folder on C:\ got the game to compile and run for me.
Skip Windows Universal unless you really need to use it - save yourself 20GB of space… and maybe some gray hair in the process.
Alternatively:
When you install the Windows 10 Universal SDK’s DO NOT change the installation path when requested to do so. If you do, even though you did everything correctly, Visual Studio will forever look at the wrong path for the DLL’s and generate an error. And I could not find a way to reinstall the SDK to a different path later without some deep registry changes.
… To verify this is your problem, run the SDK installer. It will show the old path and it will not let you change it.
My lazy way to fix this issue:
Press Start > and type CMD in the search bar.
Right click on Command Prompt and run as administrator.
Type in
*CD C:\Program Files (x86)\Windows Kits*
You should see a missing folder called 10 (because you installed it somewhere else). We are going to create symlink, its like a reference, that will tell the OS to use the paths interchangeably. Learn to love symlinks, you can use this to trick all kinds of programs (like dropbox) into storing files on non-standard locations.
Type in mklink /d “10” “(path_you_installed_the_win10_kits)”
For example, my kits are stored in D:\W10Kits. mklink /d “10” “D:\W10Kits”
To verify this, type explorer .
When explorer opens, right lick on the 10 folder you created (it should have a blue shortcut icon on it) and press Properties → Shortcut. It should show Target: as having your non-default install folder (D:\W10Kits in my case).
Completely restart Visual Studio.
If it is the same problem I had, It should find the SDK’s now. If not, then it isn’t the same pathing issue and you’ll be embarking on your own journey
Using Unity 2017.1.2f1 I got same error:
error MSB3774: Could not find SDK “WindowsMobile, Version=10.0.16299.0”.
Visual Studio 2017 all updated. What am I missing to install in VS installation?
There is no WindowsMobile here…I also installed the mobile (Android, iOS stuff):
It turns out the Mobile SDK was not copied when installing all these components.
(C:\Program Files (x86)\Windows Kits\10\Extension SDKs\WindowsMobile\10.0.16299.0) folder was missing.
I uninstalled VS and all SDK’s and reinstalled everything and it worked
