Aug 07 2018 09:03 AM
Running a MSIX package on a domain joined machine, logged in as a domain admin. The MSIX application works with a file from a network share. The user and machine accounts have full permissions on the share (and folders). The MSIX app calls:
System.IO.Directory.CreateDirectory(foldername)
to create a folder on the network share. This call succeeds in a native install of the application, but fails with a ACCESS_DENIED
Aug 07 2018 11:08 AM
Hi Timothy,
Can you elaborate - when do you see the ACCESS_DENIED error?
Aug 07 2018 11:57 AM
The Access_Denied error is seen in the procmon trace of the application when it makes this call.
Aug 07 2018 12:48 PM
This sounds like something we should take a look at in more depth. Are you able to file a bug through the feedback hub using the "Recreate My Problem" option to capture logs and screenshots?
Aug 07 2018 01:05 PM
This is easier. Here is the MSIX file with the app. One would launch the app (TMEdit), and open a Microsoft App-V package from a file share, such as \\server\share\somefolder\packagename\packagename.appv
Then save the file off using default settings. This would attempt to create the folder \\server\share\somefolder\packagename_2 and this causes the access denied.
The app version in this package doesn't actually trap for this and crashes when it subsequently tries to use that folder, but the problem is the access denied. Your test team can re-sign the package to test, or contact me and I'll send the self-signed cert and password.