Installer turns an obscure resource file into PowerShell input

The executable’s PowerShell child did not launch a conventional .ps1 file. Its command read Amnesias.Und from a directory under the user’s roaming profile, extracted three characters from the file’s contents and used the resulting string as a command name. That raises a more useful question than whether the installer used PowerShell: was this obscurely named file a passive resource, or part of the execution mechanism? The records establish the latter.