Mismatched Taskbar error prevents everything in the task bar from working, including the windows key. Reset your shell. Instructions in the “How to Solve” section of this post.
So, I love windows 10 multiple desktops (FINALLY!). But I noticed recently that when I switch back and forth several times in rapid succession, the task bar has a tendency to lag; resulting in a mis-match from the correct desktop.
Example Desktop 1 will have the corresponding task bar for Desktop 2 and Desktop 2 will have the task bar for Desktop 1.
How to Solve
Reset your Shell. If you don’t know how to do that here’s how.
Because this error prevented everything in the task bar from working, including the windows key, use Ctrl+Alt+Del to pull up the task manager.
Then find the first instance of explorer.exe. This is the shell containing the task bar. End that process.
To run it again. Click File > Run and type explorer, this will boot the shell again and get your task bar running.
Solution: Check Versions of Unity and VS tools as well as Emulator Version
This error occurred because the download link to the latest Unity Editor build was not compatible with the Emulator Unity Tools for Visual Studio. The Unity version of the editor I had was 5.4.0b14. The Origami demo and the Emulator tools currently work with b10, if your looking at this post several months down the line just make sure your versions are compatible. Also make sure you have the VS Update 2 installed.
Error cs0234: the type or namespace name wsa' does not exist in the namespace unityengine.vr’. are you missing an assembly reference?
Solution: Make sure the correct version of Unity and VS Emulator Tools are installed. Then make sure the correct version of UWP tools are installed.
You should have the 10.0.10586 UWP tools not Win 10 SDK 10.0.10240. The Win 10 SDK at the moment conflicts with the tools for some reason when I was trying to deploy my project. This may change in the future.
Error – Connectivity.Remote.Device.Ping()
Solution: Check to see if Remote tools version 10.0.10586 is installed and then try downloading the Remote tools.
Error – Project not Deploying
There are a number of reasons for faulty deployment
Solution: Wait. The first time I ran the Emulator it took 15 minutes to run and load my app.
Solution: Make sure your versions are correct.
Solution: Look at the Project in Visual Studio; make sure there are no popup windows that are halting the debugging and stopping the deployment. The first time you run the emulator Visual Studio will ask you if you want to continue debugging in Emulator mode, if you select “Continue (always use this option)” they Deployment process won’t hang waiting for your permission.
Solution: Make sure you don’t have too many other programs running
Error – Project is Deploying to Emulator but not starting
Solution: Hit the plus on the right side of the menu Window.
This will take you to All Apps Running in the Emulator, you should see your app there.
Error – No ‘Home’ or ‘Menu’ Window in emulator
Solution: Hit the Windows Key. If that doesn’t work restart.
Error – Stuck in Windowed Mode of the Emulator
If you see the Unity Logo with a white screen you will be stuck in Windowed mode of the Emulator and be unable to run your app.
Solution: Turn off emulator. Clean your Solution. Build it. Then hit Run again for the Emulator. The emulator is still new and sometimes will get stuck.
Error – HoloLens Emulator is not appearing in Visual Studio Devices drop-down
Solution: Make sure the tools are downloaded and you are in x86 mode with Release Mode selected
So those are the main ones. Again I’ll keep adding them. Let me know what cool projects you’re working on and if you ran into more errors that I can add =)