It turns out that the reported issue is based on: On certain Windows platforms, several versions of the IBM DB2 client do not correctly registry the IBM DB2 .Net Data Providers.
Windows 8, 10 and 2012 require certain DB2 Fix Pack levels for the client to ensure that the DB2 dlls are properly registered in the Global Assembly Cache (GAC):
DB2 10.5 FixPack 4
DB2 10.1 FixPack 4
DB2 9.7 FixPack 10
This will be contained in our release notes going forward.