locked
Known Issue: Debugging on remote Windows 10 Device with Visual Studio 2015 Update 3, followed by Visual Studio 2015 Update 2 (or earlier), fails with DEP2100 or similar RRS feed

  • Question

  • If you debug a Windows application on a device using Visual Studio 2015 Update 3 or later, and then you or another developer tries to debug an application on the same device using Visual Studio 2015 Update 2 or earlier, the application will fail to deploy.

     

    The error message may vary depending on the version of Visual Studio that fails to deploy, but you may see:

    DEP2100: Cannot copy the file [FILENAME] to the target machine [IP ADDRESS]


    Wednesday, August 3, 2016 4:23 PM
    Moderator

Answers

  • To fix this issue, you can do one of the following depending on the remote device target:

    For all devices:

    • Make sure everyone working with the device is using Visual Studio 2015 Update 3 or later

     

    For remote PCs:

     

    For other devices (phones, IoT, Xbox, and HoloLens)

    • You can set the following registry key entry to work around the issue (if you cannot update to Visual Studio 2015 Update 3)
      • [HKEY_CURRENT_USER\SOFTWARE\Microsoft\VisualStudio\14.0\Deployment]: "SshForceRedeployment" value set to 0x00000001 (registry type is DWord)
      • Note: You will have to create this registry folder as it will not already exist
      • Once this is set, you can F5 the application to the target device
      • After you have deployed the application once from that version of Visual Studio, you can change the value of the key to 0x00000000 (to improve subsequent F5 speed)


    Wednesday, August 3, 2016 4:24 PM
    Moderator