SOLVED

How File redirection works in MSIX?

%3CLINGO-SUB%20id%3D%22lingo-sub-481893%22%20slang%3D%22en-US%22%3EHow%20File%20redirection%20works%20in%20MSIX%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-481893%22%20slang%3D%22en-US%22%3E%3CP%3ECan%20some%20one%20please%20explain%20me%20on%20how%20the%20file%20redirection%20works%20in%20MSIX%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-482881%22%20slang%3D%22en-US%22%3ERe%3A%20How%20File%20redirection%20works%20in%20MSIX%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-482881%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F325532%22%20target%3D%22_blank%22%3E%40GauravTamkoria%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20presume%20you%20mean%20the%20filesystem's%20behavioral%20rules%2C%20not%20the%20virtualization%20mechanism.%26nbsp%3B%20We%20have%20the%20filesystem's%20behavior%20rules%20enumerated%20here%2C%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fporting%2Fdesktop-to-uwp-behind-the-scenes%23file-system%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fwindows%2Fuwp%2Fporting%2Fdesktop-to-uwp-behind-the-scenes%23file-system%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20behavior%20of%20files%20for%20the%20%3CEM%3E%25AppData%25%3C%2FEM%3E%20location%20is%20changing%20a%20little%20in%201903%20to%20remove%20the%20copy-on-write%20behavior%20-%20the%20above%20link%20will%20soon%20be%20updated%20with%20the%20specific%20differences.%26nbsp%3B%20I'll%20paste%20a%20snippet%20here%20on%20the%201903%20changes%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%20class%3D%22%22%3EWindows%2010%2C%20version%201903%20and%20later%3A%3C%2FSTRONG%3E%3CSPAN%3E%26nbsp%3BNew%20files%20and%20folders%20created%20under%20the%20following%20directories%20are%20redirected%20to%20a%20per-user%2C%20per-package%20private%20location%3A%3C%2FSPAN%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3ELocal%3C%2FLI%3E%0A%3CLI%3ELocal%5CMicrosoft%3C%2FLI%3E%0A%3CLI%3ERoaming%3C%2FLI%3E%0A%3CLI%3ERoaming%5CMicrosoft%3C%2FLI%3E%0A%3CLI%3ERoaming%5CMicrosoft%5CWindows%5CStart%20Menu%5CPrograms%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSPAN%3EIn%20response%20to%20a%20file%20open%20command%2C%20the%20OS%20will%20open%20the%20file%20from%20the%20per-user%2C%20per-package%20location%20first.%20If%20this%20location%20doesn't%20exist%2C%20the%20OS%20will%20attempt%20to%20open%20the%20file%20from%20the%20real%20AppData%20location.%20If%20the%20file%20is%20opened%20from%20the%20real%20AppData%20location%2C%20no%20virtualization%20for%20that%20file%20occurs.%20File%20deletes%20under%20AppData%20are%20allowed%20if%20user%20has%20permissions.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EGood%20luck%2C%3C%2FP%3E%0A%3CP%3E-jw%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Can some one please explain me on how the file redirection works in MSIX

1 Reply
Highlighted
Best Response confirmed by Dian Hartono (Microsoft)
Solution

Hi @GauravTamkoria,

 

I presume you mean the filesystem's behavioral rules, not the virtualization mechanism.  We have the filesystem's behavior rules enumerated here,

https://docs.microsoft.com/en-us/windows/uwp/porting/desktop-to-uwp-behind-the-scenes#file-system

 

The behavior of files for the %AppData% location is changing a little in 1903 to remove the copy-on-write behavior - the above link will soon be updated with the specific differences.  I'll paste a snippet here on the 1903 changes,

 

Windows 10, version 1903 and later: New files and folders created under the following directories are redirected to a per-user, per-package private location:

  • Local
  • Local\Microsoft
  • Roaming
  • Roaming\Microsoft
  • Roaming\Microsoft\Windows\Start Menu\Programs

In response to a file open command, the OS will open the file from the per-user, per-package location first. If this location doesn't exist, the OS will attempt to open the file from the real AppData location. If the file is opened from the real AppData location, no virtualization for that file occurs. File deletes under AppData are allowed if user has permissions.

 

Good luck,

-jw