Yes, that would fix the installer issue and we do recommend moving to SQL Server 2016. The bundled SQL 2005 instance in the old installer was intended more for quick setup for evaluation purposes rather than production use, but we did a very poor job of making that clear. We are fixing that now; we're working on updating all of our installers to detect the SQL Server version and suggest/require an upgrade. Here is the current article about SQL Server requirements - basically it's any version currently supported by Microsoft. Sorry for the confusion, and hope this helps!

Hello, Just following up: The root cause of Windows images from connectors not working is that ProGet was not telling the connector that it supported v2 manifests, and the v1 manifests generated for Windows images by Docker Hub are broken. This is PG-1351.