I have a C# DLL (Registered for COM interlop) that we use to provide some extra functionality to a few of our customers. We have never had any problems with this dll in the past, and have been happy with things.

It was recently found that when we attempt to load the DLL with a Windows 10 machine the load fails. I've add strong type names to the DLL, registered, re-registered, added to Global Assembly Cache, built my primary executable with XE2 all the way through CX-Seattle, and tried every conceivable combination of listed items.

I can take my executable (from any XE2 through CX-Seattle) to a Windows 7 (or even 8.1) machine it works flawlessly (just have to register the DLL).

The main program is a VCL C++ 32bit application, it consists of a single executable, and other than the huge code base, isn't too fancy.

The return I get from my CreateInstance call is: -2147024882

I've been following this guide to help me setup both projects: http://edn.embarcadero.com/en/article/32754

Any help is greatly welcomed, I'm at a complete loss right now, and with Microsoft pushing hard to upgrade everybody to Windows 10 I need to figure this out before it becomes a serious issue.

Thanks,
Ryan