Windows 7 SP1 Breaks ADO Compatibility

Question

After installing SP1 on Windows 7 the compatibility of programs referencing "Microsoft ActiveX Data Objects Recordset 2.x Library" or in other words the infamous MSADOR15.DLL (located in "\Program Files (x86)\Common Files\System\ado\msador15.dll" for x64 users) and of course on "\Program Files\Common Files\System\ado\msador15.dll" is broken.

Having to build 100 VB6 projects all over again doesn't sound like a good perspective and it seems to me this is just a bad build none was supposed to include in SP1.

Of course anyone having the problem can just ... take ownership from TrustedInstaller then change the security permissions to a user that belongs at his group and then rename the file and finally restore the old versions from a pre SP1 version, but still... doesn't sound right !

Also discovered that I don't see the library in the type libraries at OLE/COM Object Viewer although at the build-in typelib viewer when I browse the file it seems relatively ok (always compared to the old version) but with difference in many UUID's (most start from 00001505 instead of 00000505) and some parameters have changed type from long* to ADO_LONGPTR* and the PositionEnum to PositionEnum_Param (could be the x64 version not sure about it)....

Anyway the workaround is here, hope a quick reply from a official representative of Microsoft...

Answer 1

With all due respect, this has nothing to do with Windows Update functionality if SP1 has successfully installed. Try posting in the Programs forum instead: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs

Free unlimited installation and compatibility support is available for issues related to Windows 7 Service Packs. Availability of chat, phone or e-mail support differs depending on your geographic location. Some issues may require more advanced support for which there may be a charge:  https://support.microsoft.com/oas/default.aspx?&gprid=14496&&st=1&wfxredirect=1&sd=gn 

Good luck!

---

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

Answer 2

With all due respect, this has nothing to do with Windows Update if SP1 has successfully installed. Try posting in the Programs forum instead: http://social.answers.microsoft.com/Forums/en-US/w7programs/threads  

Good luck!

---

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

This is I believe the third time I'm trying to get an answer about this problem on 3 different forums. This is something SP1 * actually * breaks. Hope to have more luck on a developer thread if anyone there can comprehend what I'm talking about.

Answer 3

I fully empathize but your post-SP1 issues have nothing to do with Windows Update functionality.

Yes, I think you'd be much better off posting in a TechNet, MSDN or ITPro forum, Chris. Again, good luck.

====================================

Free unlimited installation and compatibility support is available for issues related to Windows 7 Service Packs. Availability of chat, phone or e-mail support differs depending on your geographic location. Some issues may require more advanced support for which there may be a charge:  https://support.microsoft.com/oas/default.aspx?&gprid=14496&&st=1&wfxredirect=1&sd=gn

---

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

Answer 4

Dear PA Bear:

I'm not sure what you mean in your answer; or perhaps you didn't understand Chris' post.

After updating a Windows 7 machine to SP1, all the 32-bit ADO files are no longer version compatible with previous versions. So if you compile a program against the SP1 msado15.dll, that program will not work on unpatched Win7, Win2k3, Win2k8, etc.

I've tested this by compiling a small program that references msado15.dll, and I can confirm that program doesn't work on any other operating system. This seems incredible to me -- but true.

Answer 5

Hi,

I can also confirm this - we have a major VB6 application that uses ADO data controls all over the place, and have found that Win7 SP1 redefines out of existence a whole bunch of the functionality on this control - the WillMove and the MoveComplete functionality disappears - effecively breaking our App completely.

Using the restore point to remove Win7 SP1 fixed the issue, but it is not a sustainable situation to be unable to take a Service Pack because of the fact that it breaks fundamental functionality of a major part of Microsoft's Database access routines.