+++ This PCR was initially created as a clone of PCR #15353 +++

When a process has a relocatable executable and one or more automounted owned filesystems the executable will be mapped over the automounted filesystems. This will likely cause a user mode access violation when attempting to access the automounted filesystems.

If the registry defines a process instance with an none empty (i.e. not "") automountPath, objdump should be used as follows, to check if the process executable is impacted by this limitation: 

* objdump can be used to check if the executable is linked relocatable. To do this issue '<arch-prefix>-objdump -p <executableName> | grep LOAD' and look at the vaddr of the first LOAD line found, if it is 0 then the file is relocatable. e.g.:
$ arm-eabi-objdump -p foo.exe | grep LOAD
    LOAD off    0x00000000 vaddr 0x00000000 paddr 0x00000000 align 2**16
    LOAD off    0x0000145c vaddr 0x0001145c paddr 0x0001145c align 2**16
foo.exe is relocatable because vaddr is 0.

Workaround:
For process configured to have automounted filesystems, link the executables at a  fixed address.