The sandboxing means that OpenXR Tool's information does not reflect the user's real configuration, so can be a very misleading debugging tool.
Missing API layers
OpenKneeboard by default installs an OpenXR API layer via HKCU, to avoid unneeded elevation. OpenXR Tools will not include it in the list of API layers - for example, in this screenshot, OpenXR Toolkit is installed via HKLM and appears in both OpenXR tools and OpenXR Explorer, however OpenKneeboard is installed via HKCU and only shows up in OpenXR Explorer:
Unrepresentative ACLs
If an 'everyone'-readable/executable API layer is installed, but it is not readable by the restricted package users (which are not part of everyone), OpenXR Tools will hard-fail - for example, if OpenKneeboard is set to install OpenXR for 'all users', the layer files are in C:\ProgramData which does not have the restricted app ACLs, leading to this:
The sandboxing means that OpenXR Tool's information does not reflect the user's real configuration, so can be a very misleading debugging tool.
Missing API layers
OpenKneeboard by default installs an OpenXR API layer via HKCU, to avoid unneeded elevation. OpenXR Tools will not include it in the list of API layers - for example, in this screenshot, OpenXR Toolkit is installed via HKLM and appears in both OpenXR tools and OpenXR Explorer, however OpenKneeboard is installed via HKCU and only shows up in OpenXR Explorer:
Unrepresentative ACLs
If an 'everyone'-readable/executable API layer is installed, but it is not readable by the restricted package users (which are not part of everyone), OpenXR Tools will hard-fail - for example, if OpenKneeboard is set to install OpenXR for 'all users', the layer files are in
C:\ProgramData
which does not have the restricted app ACLs, leading to this: