> How does the converter deal with the VB6 runtime that had to be distributed? I've just checked on Windows 10, and yup, MSVBVM60.dll is still part of the OS

> How does the converter deal with the VB6 runtime that had to be distributed? I've just checked on Windows 10, and yup, MSVBVM60.dll is still part of the OS install - the mind boggles. This is classic MS - providing support for as long as they can, where they can. Of course I'm not sure how the UWP Bridge would work if your VB6 app referenced a bunch of old school .OCXs though, as typically even the self registering ones need to write to HKEY_LOCAL_MACHINE part of the Registry, which the Bridge docs say is a complete no-no.