 
            The affected application is 16-bit, so it's unlikely that the registry mapping would help.
Our 16-bit profile functions forward to the 32-bit ones.
On the other hand I've checked win.ini contents in Windows 11 and it has an explicit comment there "; for 16-bit app support" with empty [fonts],[extensions],[msi extensions],[files] and [mail]/MAPI=1 sections. Note, that this is on 64-bit Windows 11 where 16-bit support was completely removed.
Okay, if native has it that's probably a good enough reason.