Forum Discussion
The Registry File
I have used the MSIX Packaging Tool to generate a MSIX file. When I am exploring it, I found there are two more .dat files compare to the APPX package. Are there any docs avaible now to explain the d...
While someone from MS should give a "correct" answer, here's what we think we know.
The DAT files are standard registry format. Meaning that you can go into the regedit, create a blank key, and import the dat file onto that key. Or possibly use other tools that understand the format.
Values in REG_SZ types that look like file paths are subject to variablization. In other words, if the app wanted "c:\Program Files (x86)" this might appear as ProgramFilesX86.
In the case of App-V use of these same dat files, value types (when in binary form) might have high order bits set to indicate things not normally considered in the registry (for hiding when layering and deletion markers). I don't think MSIX uses or sets these high order bits, at least at this time.
User.dat contains the user hive changes, excluding the Software\Classes key which is in the UserClasses.dat.
The DAT files are standard registry format. Meaning that you can go into the regedit, create a blank key, and import the dat file onto that key. Or possibly use other tools that understand the format.
Values in REG_SZ types that look like file paths are subject to variablization. In other words, if the app wanted "c:\Program Files (x86)" this might appear as ProgramFilesX86.
In the case of App-V use of these same dat files, value types (when in binary form) might have high order bits set to indicate things not normally considered in the registry (for hiding when layering and deletion markers). I don't think MSIX uses or sets these high order bits, at least at this time.
User.dat contains the user hive changes, excluding the Software\Classes key which is in the UserClasses.dat.