Could a 64-bit-executable version of the OEM installer be available

Describe the bug
The current oem npac installer is a 32-bit executable. Some of our customers object to any 32-bit-running things on their Windows machines.

To Reproduce
With a policy in-place not to run 32-bit executables, try to launch the oem installer. It will not launch, or at least not launch seamlessly, because it is not a 64-bit executable.

Expected behavior
A user with a policy against running non-64-bit executables, but who needs a 64-bit component hidden in a 32-bit executable install set wants the package to install its 64-bit-executable contents.

Diagnostic information

• we had to update our NSIS-based installer to be a 64-bit executable to satisfy a customer with such a policy
• it required nothing more than adding the line
  Target amd64-unicode
  to our NSI script.

Additional context
I understand that the installer may also contain 32-bit binaries but I haven't access to any 32-bit machines anymore so as to prove it. So I understand that the OEM installer MUST (for the sake of backward compatibility) be available as a 32-bit executable. What I am asking is that an OEM installer as 64-bit NSI executable be provided -- or that you would point out where the sources are for such an installer so we can patch it ourselves. I have been looking for such sources and have been so far unable to locate them.

Start by locating the OEM installer’s NSIS source or build definition and review how its 32-bit executable is produced and which binaries it packages. Done means a reproducible 64-bit OEM installer is available while the existing 32-bit installer remains usable for backward compatibility.