Howard Kapustein
Howard Kapustein
This sounds like a bug in the protocol deregistration work in the deployment pipeline. I've passed along word to the protocol handling team => https://task.ms/54265091 Thanks for reporting this!
Thank you for reporting this issue. This has been identified and fixed; the fix will be in the next patch update (1.6.2) Internal bug tracking: https://task.ms/53958200
>https://learn.microsoft.com/en-us/windows/win32/secauthz/app-isolation-supported-capabilities Well that's terribly confusing. The phrase "app isolation" is a new one by me. The page also says 'app isolation' is in preview. I'm not sure if that's current....
P.S. There's a nifty ~trick~ feature :-) here. AppSilo requires Windows 24H2 but the uap18:RB+TL attributes act as _overrides_ if present, so you can make 1 package that runs uplevel...
>if you specify EntryPoint="Windows.FullTrustApplication" but nothing else on an Application tag, and specify rescap:runFullTrust as the capability, and then install via MSIX, what level of sandboxing is applied? `EntryPoint="Windows.FullTrustApplication"` is...
I got word, "App Isolation" is the right term (today), the feature's in Preview (so take into consideration), and yes the manifest currently says "appSilo" (though if the name sticks...
> The manifest does _not_ declare `RuntimeBehavior=appSilo` or any other equivalent that would trigger sandboxing. > > Therefore this perhaps isn't a question at all but a bug report. Something...
VS F5 registers the package using the project's $(OutDir), equivalent to Powershell -c Add-AppxPackage -Register $(OutDir)\appxmanifest.xml Or var uri = new Uri("$(OutDir)\appxmanifest.xml"); PackageManager.RegisterPackageByUriAsync(uri, new RegisterPackageOptions(){ DevelopmentMode=true }); But...VS F5 tries...
Why a list of PackageFamilyName? Are PackageSIDs the only thing folks need to grant access? The background section says `... in order to be shared outside the package.`, it doesn't...