SOLVED

MSIX App Attach - Staging Fails

%3CLINGO-SUB%20id%3D%22lingo-sub-1516807%22%20slang%3D%22en-US%22%3EMSIX%20App%20Attach%20-%20Staging%20Fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516807%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAm%20trying%20trying%20out%20the%20MSIX%20App%20Attach%20feature%20on%20my%20lab.%20I%20have%20a%20Physical%20machine%20with%20W10%201909%20Enterprise%20Build.%20Sideloading%20is%20enabled%20on%20the%20same.%20Am%20following%20the%20documentation%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-desktop%2Fapp-attach%23prepare-powershell-scripts-for-msix-app-attach%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Ehere%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEverything%20works%20until%20the%20below%20line%20under%20Staging%3A%3C%2FP%3E%3CP%3E%3CEM%3E%24asyncOperation%20%3D%20%24packageManager.StagePackageAsync(%22%24path%22%2C%20%24null%2C%20%22StageInPlace%22)%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpon%20execution%20of%20above%20line%2C%20get%20the%20below%20error%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3E%3CEM%3ECannot%20convert%20argument%20%22deploymentOptions%22%2C%20with%20value%3A%20%22StageInPlace%22%2C%20for%20%22StagePackageAsync%22%20to%20type%20%22Windows.Management.Deployment.DeploymentOptions%22%3A%20%22Cannot%20convert%20value%20%22StageInPlace%22%20to%20type%20%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3E%22Windows.Management.Deployment.DeploymentOptions%22.%20Error%3A%20%22Unable%20to%20match%20the%20identifier%20name%20StageInPlace%20to%20a%20valid%20enumerator%20name.%20Specify%20one%20of%20the%20following%20enumerator%20names%20and%20try%20again%3A%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3ENone%2C%20ForceApplicationShutdown%2C%20DevelopmentMode%2C%20InstallAllResources%2C%20ForceTargetApplicationShutdown%2C%20RequiredContentGroupOnly%2C%20ForceUpdateFromAnyVersion%2C%20RetainFilesOnFailure%22%22%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuestions%3A%3CBR%20%2F%3EI%20see%202004%20release%20of%20W10%20as%20Pre-req.%20Is%20this%20only%20because%20of%20the%20fact%20that%20sideloading%20is%20enabled%20on%20this%20build.%20If%20yes%2C%20I%20have%20that%20enabled%20on%20my%20W10%201909%20build%20as%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1518492%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20App%20Attach%20-%20Staging%20Fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1518492%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F680605%22%20target%3D%22_blank%22%3E%40DS2803%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWindows%2010%202004%20build%20is%20required%20due%20to%20some%20specific%20APIs%20it%20offers.%20You%20will%20not%20be%20able%20to%20execute%20the%20discussed%20overload%20of%20%3CEM%3EStagePackageAsync%3C%2FEM%3E%26nbsp%3Bon%20Windows%201909%2C%20regardless%20of%20the%20sideloading%20settings.%20Upgrade%20your%20lab%20to%20Windows%2010%202004%20or%20an%20Insider%20build%26nbsp%3B%3CSPAN%3E19041%2B.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1520410%22%20slang%3D%22en-US%22%3ERe%3A%20MSIX%20App%20Attach%20-%20Staging%20Fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1520410%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F354316%22%20target%3D%22_blank%22%3E%40marcinotorowski%3C%2FA%3EThank%20You%20for%20confirming!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,

 

Am trying trying out the MSIX App Attach feature on my lab. I have a Physical machine with W10 1909 Enterprise Build. Sideloading is enabled on the same. Am following the documentation here

 

Everything works until the below line under Staging:

$asyncOperation = $packageManager.StagePackageAsync("$path", $null, "StageInPlace")

 

Upon execution of above line, get the below error:


Cannot convert argument "deploymentOptions", with value: "StageInPlace", for "StagePackageAsync" to type "Windows.Management.Deployment.DeploymentOptions": "Cannot convert value "StageInPlace" to type
"Windows.Management.Deployment.DeploymentOptions". Error: "Unable to match the identifier name StageInPlace to a valid enumerator name. Specify one of the following enumerator names and try again:
None, ForceApplicationShutdown, DevelopmentMode, InstallAllResources, ForceTargetApplicationShutdown, RequiredContentGroupOnly, ForceUpdateFromAnyVersion, RetainFilesOnFailure""

 

Questions:
I see 2004 release of W10 as Pre-req. Is this only because of the fact that sideloading is enabled on this build. If yes, I have that enabled on my W10 1909 build as well.

 

2 Replies
best response confirmed by DS2803 (Occasional Contributor)
Solution

@DS2803 

Windows 10 2004 build is required due to some specific APIs it offers. You will not be able to execute the discussed overload of StagePackageAsync on Windows 1909, regardless of the sideloading settings. Upgrade your lab to Windows 10 2004 or an Insider build 19041+.

@marcinotorowskiThank You for confirming!