The Mixed Reality Forums here are no longer being used or maintained.
There are a few other places we would like to direct you to for support, both from Microsoft and from the community.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality.
If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers, or in our Microsoft Tech Communities forums at https://techcommunity.microsoft.com/t5/mixed-reality/ct-p/MicrosoftMixedReality.
And always feel free to hit us up on Twitter @MxdRealityDev.
App Installation Error - wrong Target Device Family
Hello - I'm having an issue trying to deploy and install an application which I do not have the source for. I've used the DesktopAppConverter to create a package appx file using the following command which ran without error.
DesktopAppConverter.exe -Installer "C:\Users\myUsername\Documents\TestMyApplicationConverted\PackageFiles\" -AppExecutable "MyApplication.exe" -Destination "C:\Users\myUsername\Documents" -PackageName "MyApplicationConverted" -Publisher "CN=TestPublisher" -Version 18.104.22.168 -MakeAppx -Sign
When I try to deploy the app (using the MyApplication.appx file created with the previous command) on the HoloLens via the Windows Device Portal (connected via wifi) I get the following error:
Failure reason: Windows cannot install package MyApplication_22.214.171.124_x86__q7djbd8vek6zr because this package is not compatible with the device. The package can only be installed on the following device families: Windows.Mobile Failure text: A Prerequisite for an install could not be satisfied. (0x80073cfd)
However, in the appxManifest.xml the Target Device Family is:
<Dependencies> <TargetDeviceFamily Name="Windows.Desktop" MaxVersionTested="10.0.16299.15" MinVersion="10.0.14393.0"/> </Dependencies>
Does anyone know where the Windows.Mobile target device family is coming from? Or a workaround to this error? Thank you in advance.