Hi Steve,
i would put a hint in two places on this page:
"3. Use a Free, Automated Issuing Service, such as Let's Encrypt with a tool like win-acme to get short-term certificates"
All such Let's Encrypt certificates are issued by intermediate CAs. PFX files generated by ACME clients and directly loaded into ProGet would therefore cause the issue initially described. This is probably also the easiest approach to reproduce the issue.
"2. To use a ".pfx" file that was exported from your certificate store"
Based on my observations this would still require potentially involved intermediate CA certificates to be present in Windows' certificate store, that ProGet sends those to clients allowing them to validate the full chain.
Thank you for addressing the problem this way.