ADDITIONAL SYSTEM INFORMATION :
OpenJDK 14, Windows 10

A DESCRIPTION OF THE PROBLEM :
Currently, JPackage generates msi packages for Windows that always follow the same folder structure:
<app root> folder
  |-- <app>.exe
  |-- applauncher.dll
  |-- dozen of useless dll files
  |-- app folder
  | |-- <app>.cfg
  |-- runtime folder
             |-- <custom JDK>

The complexity of the JDK is nicely hidden behind the runtime folder but the root folder is littered with dozen mostly useless dll files... confusing users and developers alike.

There should be at most 4 items visible in the root folder with the applauncher.dll being statically linked to the required Visual C++ runtime library files:
<app root> folder
  |-- <app>.exe
  |-- applauncher.dll
  |-- app folder
  |-- runtime folder

It makes sense to have the JDK made dynamically linked to the Visual C++ runtime dll files as there are a lot of binaries to handle. However, this technicity becomes void as soon as we talk about application packaging for everyday users.