Known Issue: Fatal error when installing the Windows emulators: 2147023293 (Windows 10 Insider Preview SDK and tools, April 2015 release)

When installing the Windows 10 emulators, you may receive the following error:
Error: Emulators for Windows Mobile 10.0.10069 : The installer failed. Fatal error during installation. Error code: -2147023293

To resolve this issue, run Visual Studio setup again to add the emulators. To do this
Reboot your computer
Open Control Panel, and select Programs and Features.
Select Microsoft Visual Studio 2015 RC, click Change, and then click
Modify.
Select the feature “Emulators for Windows 10 Mobile”, and click Update.

Similar Messages

Known Issue: How to Install Visual Studio Tools for Universal Windows App Development (Windows 10 Insider Preview SDK and tools, April 2015 release)

The Visual Studio Tools for Universal Windows App Development are not installed by default. If they are not installed, in the New Project dialog in Visual Studio 2015, you will see only a template “Download Windows Universal Tools”.
For additional known issues with using Visual Studio 2015 RC, see
https://support.microsoft.com/kb/3025133/

Additional Installation Known issues:
Visual Studio Tools for Universal Windows Apps Requires Windows 10 Build 10074 or later
https://social.msdn.microsoft.com/Forums/en-US/de06c7c0-4248-4d68-bfcb-4b9a23fae1c0
You cannot install the Visual Studio Tools for Universal Windows Apps on a pre-RC build of Visual Studio 2015
https://social.msdn.microsoft.com/Forums/en-US/25d0b000-3ebb-4032-a786-99caf0390e9b
Emulators for Windows Mobile 10.0.10069 : The installer failed. User cancelled installation. Error code: -2147023294
https://social.msdn.microsoft.com/Forums/en-US/17bc9d5e-2ea7-4149-bb75-23997db8bd25/
Setup warnings for Windows 10 SDK, Emulators for Windows Mobile, and Tools for Windows 10 Universal Apps
https://social.msdn.microsoft.com/Forums/en-US/bfc4fcc0-cb48-4bb0-aab3-5797e31b08e0
Fatal error when installing the Windows emulators: 2147023293
https://social.msdn.microsoft.com/Forums/en-US/5485554c-e7e8-414e-a542-d1f7c0b6291c
Do not install Visual Studio Express 2015 for Windows 10 on a Machine with Visual Studio Community, Professional, or Enterprise
https://social.msdn.microsoft.com/Forums/en-US/94a29b17-baaf-4318-98ff-1cfc90a54bad/
How to enable your Windows 10 device for development
https://social.msdn.microsoft.com/Forums/en-US/6e34c9f0-5e3a-4b44-9aae-586ba94f8a28/

Known issue: BackgroundTransfer sample fails with 0x80070002 error when using Windows Phone Emulator (Windows 10 Insider Preview SDK and tools, April 2015 release)

When running the Universal Windows Platform (UWP) BackgroundTansfer sample (C# or C++) in a phone emulator (i.e., Debug Target is Emulator 10.0.1.0) the sample builds and deploys successfully, but clicking any button in "Scenario 1 File Download",
"Scenario 3 Completion Notifications" or "Scenario 4 Completion Groups" will result in the following exception:
An exception of type 'System.IO.FileNotFoundException' occurred in mscorlib.ni.dll but was not handled in user code. Additional information: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
This posting is provided "AS IS" with no warranties, and confers no rights.

I am getting the same error even with the references recommended here. This is my code
using (var stream = await Windows.Storage.ApplicationData.Current.LocalFolder.OpenStreamForWriteAsync(
JSONFILENAME,
CreationCollisionOption.OpenIfExists ))
serializer.WriteObject(stream, myCars);
I can read it back as long as I don't stop the app/emulator. When I run the emulator again the file is gone. I tried loading the app to my Windows Phone and the same thing still happens.

Known Issue: Windows Emulators Are Not Supported When Visual Studio Installed in a Virtual Machine (Windows 10 Insider Preview SDK and tools, April 2015 release)

If you install Visual Studio 2015 with the Windows 10 Mobile emulators in a virtual machine, setup will succeed but the emulators will not be available as valid debug targets.

The Windows Emulators require a physical machine that runs Windows 8.1 (x64) Professional edition or higher, and a processor that supports Client Hyper-V and Second Level Address Translation (SLAT). The emulators will not run when Visual Studio is installed
in a Virtual Machine (VM).
The emulators for Universal Windows app development work best with Windows 10.

Known Issue: You cannot install the Visual Studio Tools for Universal Windows Apps on a pre-RC build of Visual Studio 2015 (Windows 10 Insider Preview SDK and tools, April 2015 release)

The Tools for Universal Windows Apps requires Visual Studio 2015 RC. If you have an earlier build installed, for example, Visual Studio 2015 CTP6, you must first uninstall Visual Studio 2015 and the Tools for Windows.

To uninstall earlier versions of Visual Studio 2015 and the tools for Universal Windows app development,
Go to Control Panel, and select Programs & Features.
Select Microsoft Visual Studio 2015 and click Change.
Click Remove, and then Yes.
Next, select Microsoft Visual Studio 2015 Tools for Windows 10, and click
Change.
Click Remove, and then Yes.

Known issue: Remote deployment fails when windows 10 C++ apps (Windows Universal) with a reference to a Windows Runtime Component is deployed in a remote machine (Windows 10 Insider Preview SDK and tools, April 2015 release)

When you attempt to deploy a windows 10 C++ Universal app that has a reference to a Windows Runtime component, to a Remote Machine (windows 10 machine), you will get an error message instead of successful deployment.

Right click solution, Go to Properties -> Configuration Properties -> Configuration - Uncheck "Deploy" checkbox for the Windows Runtime Component project. Then retry deployment to remote machine.

Known issue: Cortana will not pronounce your name during setup or when changing your name (Windows 10 Insider Preview SDK and tools, April 2015 release)

Cortana may not speak your name when tapping the "Hear how I'll say it" button when setting up your name for the first time or when changing your name in the settings panel.

There is no workaround for this issue. However, you can still complete the process of setting or changing your name.

Known issue: Cortana background voice command cannot be debugged due to 5 second timeout (Windows 10 Insider Preview SDK and tools, April 2015 release)

Cortana currently dismisses itself as soon as it loses focus. If you switch to Visual Studio when debugging a background voice command, Cortana will dismiss itself, end the connection with your app and kill the app's background task.

You can work around this issue by remotely debugging your app on a different machine. This eliminates the focus problem by allowing Cortana to remain in focus (on the remote machine) while you debug with Visual Studio (on your local machine).
Prerequisites
You have installed Windows 10 and Visual Studio 2015 RC on your main development computer.
You have installed Windows 10 on a separate computer or virtual machine (Visual Studio not required).
Note: Download Windows 10 from
http://windows.microsoft.com/en-us/windows/preview-iso-update-1504
Terminology
Your local computer is your main development box with Visual Studio 2015 RC and your project files.
Your remote computer is a separate machine that will run your app remotely while maintaining a connection with Visual Studio on your local computer.
Step 1: Enable Remote Desktop
Ensure your remote computer can receive Remote Desktop requests:
Sign into your remote machine
Right-click the Start menu and select System
Make a note of the machine name (you will reference it often)
Click the Remote settings link
Select the Allow remote connections to this computer radio button
Save and close
Step 2: Configure your Remote Desktop connection and remote microphone
On your local machine, start Remote Desktop Connection from the Start menu
Click Show Options
On the General tab, type of the name of the remote machine
Navigate to the Local Resources tab
Click the Settings button in the Remote Audio section
Change Remote audio recording to Record from this computer. This enables the remote microphone
Hit OK and navigate back to the General tab
Click Save As and save the Remote Desktop connection to a location on your computer
Connect to the remote machine
Step 3: Install Remote Tools for Visual Studio 2015 RC on the remote machine
Sign into the remote machine
Navigate to
https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
Expand Additional Tools and look for Remote Tools for Visual Studio 2015 RC
Download and install
Configure the remote debugger as described at
https://msdn.microsoft.com/en-us/library/bt727f1t.aspx. Tip: Scroll down to “Start and configure the remote tools for the first time”
Run Remote Debugger from the start menu and keep the app running
Step 4: Enable developer mode on the remote machine
This step allows you to deploy and test apps to the remote machine. For details and alternate instructions see
https://msdn.microsoft.com/en-us/library/windows/apps/dn706236.aspx.
Remain signed into the remote machine
Run gpedit.msc from the start menu (this is the Local Group Policy editor)
Ignore the two popup error messages that will appear immediately
Use the tree view on the left side to navigate to Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> App Package Deployment
Double-click and enable Allow all trusted apps to install
Double-click and enable Allows development of Windows Store applications and installing them directly from an IDE
Step 5: Enable Cortana debugging on the remote machine
This step disables the 5-second timeout when running a background task.
Remain signed into the remote machine
Run Debuggable Package Manager from the start menu
Copy/paste the following line exactly and hit enter: $a=Get-AppxPackage | Where-Object {$_.Name -eq "Microsoft.Cortana"}
Copy/paste the following line exactly and hit enter: Enable-AppxDebug $a
Type exit and hit enter to close the window
Step 6: Confirm you can connect to the remote machine with Visual Studio
Sign into the local machine and start Visual Studio
Click the Debug -> Attach to process menu (a project does not have to be open)
Type the name of the remote machine and hit enter
Provide your credentials (if using a Microsoft account, type your email display name and password, ignoring the domain text)
The connection is successful if you see a list of processes
Tip: If you experience a problem, make sure the Remote Debugger app is running on the remote machine
Step 7: Configure remote debugging in your Visual Studio project
Open your project in Visual Studio on the local machine
Open the project properties (e.g., right-click the project in the solution explorer and select
Properties)
Navigate to the Debug section
Select Remote Machine for the target device
Type the name of the remote machine
Close settings
If necessary, on the Visual Studio toolbar select Remote Machine
If necessary, switch to x86 or x64 depending on the remote architecture
Run
If prompted, enter your credentials
Switch to the remote machine over Remote Desktop and confirm the app shows up
Sometimes it will not show up during the first run; stop and restart
Set a breakpoint and confirm the debugger on the local machine is triggered
You should now be able to debug Cortana voice commands, including background commands.

Known Issue: Setup warnings for Windows 10 SDK, Emulators for Windows Mobile, and Tools for Windows 10 Universal Apps (Windows 10 Insider Preview SDK and tools, April 2015 release)

When you install Visual Studio 2015 when not connected to the internet, for example from an ISO, you may receive warnings after setup completes for Tools for Windows 10 Universal Apps, Windows 10 SDK, and Emulators for Windows Mobile. These warnings include:
This product did not download successfully: The server did not return the file size.
This product did not download successfully: Signature verification failed on downloaded file.
This product did not download successfully: HTTP Status 502: The server….

To fix this issue, your computer must be connected to the internet to download these components.
Make sure your computer is connected to the internet.
Open Control Panel, and select Programs and Features.
Select Microsoft Visual Studio 2015 RC, click Change, and then click
Modify.
Select the feature “Universal Windows App Development Tools”, and click
Update.

Known Issue: Visual Studio Tools for Universal Windows Apps Requires Windows 10 Build 10074 or later (Windows 10 Insider Preview SDK and tools, April 2015 release)

The Visual Studio Tools for Universal Windows Apps requires Windows 10 build 10074 or later. If you use an earlier build of Windows 10, you will see a notification in Visual Studio, the XAML designer will not be available, and you will get the following
error when deploying apps to your local machine:
Error : DEP0700 : Registration of the app failed. Deployment Register operation with target volume C: on Package
<package ID> from: (<path_to_AppxManifest.xml>) failed with error 0x80073CFD. See
http://go.microsoft.com/fwlink/?LinkId=235160 for help diagnosing app deployment issues. (0x80073cfd)

To work around this issue, either
Use Windows 8.1 and deploy to the Windows Mobile Emulator
Or, update your computer from an earlier Windows 10 flight to build 10074 or later. To do this,
in Settings, open the Update & security section, and select the
Windows Update tab. Then click Check for updates.

Known issue: Speech APIs fail in Silverlight for Phone (Windows 10 Insider Preview SDK and tools, April 2015 release)

Silverlight speech APIs fail when running the Silverlight app on a Windows 10 phone.

There is no workaround for this issue. You should continue to develop your Silverlight application on older versions of Windows Phone.

Known issue: How to enable your Windows 10 device for development (Windows 10 Insider Preview SDK and tools, April 2015 release)

With the current release of Windows 10 Insider Preview, you cannot enable developer mode using the System Setting Developer Mode control. This feature will be enabled in a future release of Windows 10.
Editing for clarification:
If you try to Developer unlock your Windows 10 system by going to (Search) Settings --> Update & Recovery --> For Developers, you will notice that the "Settings" window closes. You cannot set these Settings through the UI in the current
Build due to the known issue.
VT Mobile Application Development

To enable your device for development, please follow the links below:
Windows 10 Mobile: Register your phone to
enable developer mode using the existing Windows Phone 8.1 tools
Windows 10 Desktop: Enable your device
for development using the Group Policy Editor
VT Mobile Application Development

Known Issue: People Picker fails to launch in Desktop when PickContactAysnc() is called (Windows 10 Insider Preview SDK and tools, April 2015 release)

When you launch the People Picker in desktop using PickContactAsync() API, the app will fail to start.

There is no workaround for this issue. However, you can still complete the process of setting or changing your name.

Known issue: Speech APIs fail when an x86 package is run on an x64 desktop (Windows 10 Insider Preview SDK and tools, April 2015 release)

When building an app for the x86 platform, speech APIs fail when the x86 package is run on the desktop of an x64 system. You may see an error with the message "mod not found".

Use the Visual Studio Configuration Manager to retarget the app to x64 when running on an x64 system.

Known issue: Cortana voice command definitions are not cleaned up after uninstalling the app (Windows 10 Insider Preview SDK and tools, April 2015 release)

Voice command definitions are not removed from Cortana's cache when an app is uninstalled. This may cause conflicts between two apps that share the same voice commands.

This issue should not impact your ability to reinstall and test the same application. However, you must reinstall the OS in order to reset the cache in cases where you are seeing conflicts between different apps.

Known Issue: Fatal error when installing the Windows emulators: 2147023293 (Windows 10 Insider Preview SDK and tools, April 2015 release)

Similar Messages

Maybe you are looking for