Windows Update KB2698365 RRS feed

  • Question

  • Why would Windows update kb2698365 crash my website on windows 7 running IE9? The website is older and uses Active X controls. After removing that specific update, the website runs fine.

    IE Error when crashing:

    Problem signature:

      Problem Event Name:                        APPCRASH

      Application Name:                             iexplore.exe

      Application Version:                           9.0.8112.16447

      Application Timestamp:                     4fc9cd53

      Fault Module Name:                          msdarem.dll

      Fault Module Version:                        6.1.7601.17514

      Fault Module Timestamp:                  4ce7b8de

      Exception Code:                                  c0000005

      Exception Offset:                                0000a01b

      OS Version:                                          6.1.7601.

      Locale ID:                                             1033

      Additional Information 1:                  bfbc

      Additional Information 2:                  bfbcd8d8467fc306cefb09e831139a0a

      Additional Information 3:                  8da1

      Additional Information 4:                  8da1345f7f7538eaa9cf82d97c7c7a99

    Thursday, July 12, 2012 3:53 PM


  • Yes, since it can be downloaded again, the previous package signing problem should be resolved.

    Please download the fix again at: http://support.microsoft.com/kb/2734642 

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    • Marked as answer by Jeremy_Wu Thursday, October 25, 2012 5:23 PM
    Friday, September 14, 2012 3:15 AM

All replies

  • We are having the same issues with the active x components on our website.

    I tried opening the source code in VB6 to debug the issue further on a machine with that update and had a similar application crash to the above

    Faulting application name: vb6.exe, version:, time stamp: 0x3592011f

    Faulting module name: msdarem.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b8de

    Exception code: 0xc0000005

    Fault offset: 0x0000a01b

    Faulting process id: 0x11a4

    Faulting application start time: 0x01cd603eb2ec4879

    Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio\VB98\vb6.exe

    Faulting module path: C:\Program Files (x86)\Common Files\System\msadc\msdarem.dll

    Report Id: 6653fccb-cc34-11e1-a108-005056a86c6a

    It seems to create the connection ok using the following connection string, but as soon as you try to open a recordset with it, it crashes Visual Basic all together.

    Provider=MS Remote;Remote Server=HTTP://the_webserver;Remote Provider=MSDASQL;DSN=the_database;UID=the_user;PWD=the_password

    XP Machines still work ok, Its only Windows 7 machines that seem to be affected. I think IE8 and 9 are both affected.

    • Edited by For8sicks Friday, July 13, 2012 8:54 AM
    Friday, July 13, 2012 8:50 AM
  • We are seeing the same problem on Windows 7. Not a problem on XP with the update applied. Is that because they have different versions of the Data Access Components?
    Friday, July 13, 2012 9:02 AM
  • Example code to reproduce to the problem

        Dim rst As New ADODB.Recordset

        Dim sqlConn As String
        sqlConn = "Provider=MS Remote;Remote Server=HTTP://web_server;Remote Provider=MSDASQL;DSN=dsn_name;UID=user_name;PWD=user_pass"
        Dim objConn As New ADODB.Connection
        With objConn
            .ConnectionTimeout = 60
            .CommandTimeout = 60
            .Open sqlConn

        End With
        rst.Open "Select * from table", objConn  'Crash! Bang!
        rst.Close 'Will never hit this

    Friday, July 13, 2012 9:44 AM
  • Having the same problem with this update currently working with MS no solution as of yet, I have a felling due to the MDAC being part of the OS system in Win 7 its going to be an issue.
    Friday, July 13, 2012 4:04 PM
  • Yes having same issue ourselves.  Works fine on XP machines, not working on Windows 7 machines.  We are running the code in a VB6 Windows application.

    I have confirmed that this issue is not happening on Windows XP and not happening on Windows Server 2008, SP1

    • Edited by bslaski Friday, July 13, 2012 5:34 PM
    Friday, July 13, 2012 4:28 PM
  • We are also seeing this issue on Windows 7 workstations after this update is applied.  The back end for the product runs on SQL 2005 on a Windows 2003 server.  I applied the update to the server but the Windows 7 machines still have problems with the program, but I can successfully run the program on the Windows 2003 server. 

    Anyone have any suggestions about how to fix this without removing the update from the Windows 7 boxes?


    Friday, July 13, 2012 6:52 PM
  • We have a open case with MS, still have no word from them on a fix.

    • Proposed as answer by Tekwene Friday, July 13, 2012 8:30 PM
    • Unproposed as answer by Tekwene Friday, July 13, 2012 8:30 PM
    Friday, July 13, 2012 7:06 PM
  • If you are using Microsoft WSUS Server, logon to your WSUS console and deauthorize the Patch (KB2698365) and schedule it for removal.  You will only need to do this on your Windows 7 machines (the patch on Servers at least via WSUS can not be rolled back).  Once you schedule the removal, you can speed up your testing by going to a workstation that is having the problem and typing at a command line: wuauclt /detectnow which will force a WSUS update.  Depending on how big your network is and how fast your WSUS server is you will see the Update icon in the workstations system tray in just a few seconds.  Click on it and you will see that the KB2698365 patch is listed as ready to uninstall.  Perform the uninstall.  There is no need to reboot.  Test your application. 

    • Edited by Tekwene Friday, July 13, 2012 8:39 PM
    Friday, July 13, 2012 8:37 PM
  • rroyjrm3,

    Yes you are correct that the applications will work once the patch is removed, however the issue is that the "update" will continue to want to apply itself, the issue is resolving the mdac compatibility within the patch and the confilct running vb6 programs and applications.

    Friday, July 13, 2012 8:48 PM
  • Same problem with our web application.  Windows 7 with IE9.  We removed the update and all was well.  While that works, it's not the fix we are expecting.

    Friday, July 13, 2012 10:16 PM
  • Spoke with level 2 support at MS issue has been escalated to update and security team for compatabilty issues with vista/7 for programs running in VB6, not sure where it will go, have to wait.

    Saturday, July 14, 2012 3:02 PM
  • Thanks Tg8d 

    Can you let us know if you hear any more news

    Monday, July 16, 2012 8:21 AM
  • Having analysed this a bit, they've released versions of msado<nn>.tlb which are not compatible with msado15.dll.

    For reference,  the details are in my post here:


    (Thanks For8sicks for pointing me to this thread)

    Phil Penney

    • Edited by Wedgeley Monday, July 16, 2012 11:25 AM
    Monday, July 16, 2012 11:23 AM
  • I'm also having a problem with KB2698365 on Windows 7 systems (both 32-bit and 64-bit) that are hosting VB6 DLLs.  We have an ASP application that calls a function in a VB6 DLL to return an ADO recordset.  When the VB6 function is called from server-side ASP code on the Windows 7 box, it works fine.  But when the DLL is called from vbscript using RDS, the call will fail with this error: Unexpected error (0x8003001e).  If I uninstall KB2698365, it goes back to working just fine.

    Below are a few code samples which demonstrate the problem I'm seeing.

    'This is my VB6 function which is compiled into a DLL and registered on my Windows 7 machine
    Public Function GetRecordset() As ADODB.Recordset Dim Cn As ADODB.Connection Dim rs As ADODB.Recordset Set Cn = New ADODB.Connection Cn.Open "Provider=SQLOLEDB;Data Source=mysqlserver;Initial Catalog=pubs;Network Library=DBNETLIB;User ID=testuser;Password=password" Set rs = New ADODB.Recordset rs.CursorLocation = adUseClient rs.Open "SELECT db_name()", Cn, adOpenStatic, adLockReadOnly Set rs.ActiveConnection = Nothing 'must be done to send disconnected recordset back to client Set GetRecordset = rs Set rs = Nothing Cn.Close Set Cn = Nothing End Function <%
    'ASP server-side code works fine... Set objTest = Server.CreateObject("MyDLL.Code") Set rs = objTest.GetRecordset() 'works fine, even with KB2698365 installed %> <script language=vbscript>
    'but client-side vbscript calls to the function fail when KB2698365 is installed... Set objDS = CreateObject("RDS.DataSpace") Set objTest = objDS.CreateObject("MyDLL.Code", "http://MyWin7Server") Set rs = objTest.GetRecordset() 'This fails when on Win7 when KB2698365 is installed </script>

    This code works fine when the DLL is registered on a Windows 2003 server or XP machine (even with KB2698365 installed), but started failing on Windows 7 systems after that KB was installed.

    Monday, July 16, 2012 2:23 PM
  • MS now stating that there is no known issues with this update according to thier research team, however still have the case open and have been elevated again, We'll see what happens.
    Monday, July 16, 2012 5:05 PM
  • Just heard from Microsoft support - they state they are aware of the issue with Windows 7 and are working to correct this issue by the end of the week.
    Monday, July 16, 2012 5:49 PM
  • Wedgeley,

    These are two different issues.

    Installing the KB 2698365 would break the RDS application on Windows 7 SP1 is a known issue, and our support team is working on this right now. Basically, we have understood the root cause of the issue and we are investigating how to fix the issue right now. (Actually, the same issue would happen in Windows Server 2008 R2 SP1 as well). 

    For the interface change issue mentioned by Wedgeley, this is actually a design change (DCR) we did in the KB #2640696. The KB #2698365 is simply including the KB #2640696. Basically, the combination (Win7 SP1 + KB #2698365) represents the final design of the ADO typelib issue (but we will still handle the compatibility issue in RDS component, which does not requires to further change the design anymore).

    As mentioned in the KB #2640696 (or see the forum discussion at here for more detail), there was a huge compatibility issue in Win7 SP1 (compared to Win7 RTM) when we changed the IID of the symbolic name _Recordset from {00000556-0000-0010-8000-00AA006D2EA4} to {00001556-0000-0010-8000-00AA006D2EA4}. If you recompile your applications on Win7 SP1 (without KB #2640696), your application won't work on any downlevel platforms (e.g. WinXP) since the new interface{00001556-0000-0010-8000-00AA006D2EA4does not exist on downlevel. Eventually, we found that this is unacceptable by most customers and we fixed this issue in a DCR (KB #2640696).

    There are many fixes in the DCR. One of them is to revert all "old" typelib (msado2x.tlb) back into their original state in Win7 RTM. This will allow all existing applications (referencing to these old typelibs) to be recompiled on Win7 SP1, and work on downlevel platforms. So, you see that the msado26.tlb becomes the same as in Win7 RTM. 

    However, in order to support the platform independent behavior (Office 64-bit required this feature), we have to include the v.6.1 typelib in msado15.dll. Therefore, you will see both _Recordset and _Recordset_Deprecated exists in the typelib embedded in msado15.dll in the DCR.

    Also, in one of the previous studies, we found that we shouldn't support platform independent behavior for the interface "ADO_RecordsetConstruction", since its Chapter property is actually a handle (varied length in different platform) although it was defined as integral type. Since "ADO_RecordsetConstruction" cannot be used in script environment (e.g. VBA in Office), we decided to revert back the "ADO_RecordsetConstruction" interface. This explains all changes you have observed.


    More importantly, if your system requires to import both msado26.tlb and msado15.dll at the same time, you can consider to workaround the issue by changing the reference of msado15.dll into msado60.tlb (or msado28.tlb). Basically, msado60.tlb and msado28.tlb are the same, but normally our team will recommend you to use msado60.tlb if possible.

    Actually, we are now recommending customers to use the v.6.1 typelib (embedded inside msado15.dll), only when you want the platform independent behavior or when there are no other downlevel dependencies. Otherwise, you may want to use the old typelib for your development work.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Tuesday, July 17, 2012 10:39 AM
  • Ming,

    Thank you for the detailed response.  I'm glad to hear that Microsoft is aware of the RDS problem with KB2698365 and is working on a fix.  I know that it's early, but do you have any indication on when a fix might be available?  Also, do you know if Microsoft has created a new KB article (or some other page) which officially acknowledges this problem?  Or, perhaps they should list this problem under the "Known Issues" section on the MS12-045 security bulletin here.



    Tuesday, July 17, 2012 3:53 PM
  • Ming,

    I noticed that if I install the KB2640696 hotfix on Windows 7 SP1, the RDS problem comes back.  So, installing either KB2640696 or KB2698365 will break applications that use RDS to call a VB6 component that returns an ADO recordset.  I assume the same would happen on Windows Server 2008 R2 SP1.  Can you confirm that Microsoft is working on a fix for this issue?


    Wednesday, July 18, 2012 2:08 PM
  • This sounds like to be a similar instance of the issue.

    It is using RDS and get a recordset.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, July 18, 2012 4:02 PM
  • Jay,

    Yes, we are actively working on this compatibility issue.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, July 18, 2012 4:03 PM
  • I am having a different problem with this update, it keeps failing with:

    Security Update for Windows 7 for x64-based Systems (KB2698365)

    Installation date: ‎7/‎18/‎2012 11:06 AM

    Installation status: Failed

    Error details: Code 800736B3

    Update type: Important

    A security issue has been identified that could allow an unauthenticated remote attacker to compromise your system and gain control over it. You can help protect your system by installing this update from Microsoft. After you install this update, you may have to restart your system.

    More information: 

    Help and Support: 

    CIO Outsourcing

    Wednesday, July 18, 2012 4:23 PM
  • Jorqe,

    This forum thread is not about the error from "Windows update". It is about the RDS compatibility issue of the security update, after you installed the security update successfully.

    For you issue, you may want to reinstall the update after rebooting your machine again. Or, you may need to consult our support team, since I have no much idea on the error from "Windows Update".

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, July 18, 2012 4:33 PM
  • Pak-Ming Cheung,

    Is there any ETA on when this issue will be corrected for windows 7 and Vista for programs that are running in VB6? I have had no luck with MS support on the phone.

    Thursday, July 19, 2012 1:19 AM
  • Ming,

    Do you have any updates on the fix for KB2698365? - RDS call?


    Monday, July 23, 2012 5:48 PM
  • Still waiting to hear from Microsoft on the issue, if anyone hears something please let us know, only happening on Vista and Win 7 OS systems running VB6 programs.
    Tuesday, July 24, 2012 1:12 AM
  • Another vote for getting this fixed ASAP!  We have a commercial application that consumes Recordsets generated by a 3rd party COM object (apparently using RDS "under the hood") that is failing because of KB2698365 in both 32-bit and 64-bit Windows 7 and Server 2008 environments.  A lot of angry customers out there, with their internal IT departments balking about removing a "Security Update" (KB2698365).

    Thanks to all for their insights and sharing their troubleshooting experiences!

    Tuesday, July 24, 2012 5:53 PM
  • Neal,

    Since this impacts your business, it would be better to contact our support team directly.

    A public forum may not be a good media to communicate the release timeline. Also, our priority can be raised if the issue impacts customer's business. Therefore, it would be better for you to communicate to our support team, and they can better evaluate how much impact to your business.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Tuesday, July 24, 2012 10:23 PM
  • Pak-Ming Cheung,

    I to am a business owner I have contacted your support team directly and it was escalated to tier 2 support, then I was told there was nothing that could be done other than Microsoft was looking into it. This forum and the information from you is more than I recieved directly from Microsoft, I have been in touch with Geraldine a supervisor with Microsoft I have emailed her yesterday with the same issues and tech. info and still have not heard back, I have a case number that I have been following and still no information from Microsoft on this issue. Any assistance you could provide would help.


    Tuesday, July 24, 2012 11:22 PM
  • Pak-Ming Cheung,

    Thanks for your prompt response and I have already done what you suggested (contacted support) for the very reason you mentioned (to enhance Microsoft visibility to the problem and escalate).  I appreciate everything you are doing to keep us informed!

    Thanks, and Best Regards,


    Wednesday, July 25, 2012 12:21 AM
  • Ming,

    Like Neal, we also have clients who have run into this problem and are reluctant to remove a Microsoft security update to work around the issue.  Until the problem is resolved, it would be helpful if we could point our clients to a page on Microsoft's website which acknowledges that Microsoft is aware of the problem and is working on a fix, and mentions that a work-around is to uninstall KB2698365.  Do you know if such a page has been posted yet?  If not, can you request that something like that get put out there?


    Wednesday, July 25, 2012 2:44 PM
  • Ming,

    I have an ADP application "People @ Work" now broken due to this update. I think it would be accurate that the majority of people on this forum have real business needs to get this fixed ASAP. ADP is claiming Microsoft and not them. Bottom line, I get stuck with the problem. I have to provide reports on compliance and this one is going to be hot topic of debate. Any updates would be greatly appreciated.

    Thank you.


    Wednesday, July 25, 2012 5:27 PM
  • All - Earlier today, I received an update from the Support Engineer assigned to our support case indicating that the problem has been identified and a fix for the RDS issue is to be released in the 7/31 timeframe.  The Support Engineer also provided me with access to a test build, which I have confirmed (at least from initial testing) addresses the problem on 32-bit and 64-bit versions of Windows 7.

    Ming - What mechanisms are available to make the test build available to the community of concerned individuals on this thread?  Obviously, broadening the testing scope for this apparent fix is in everyone's best interest, Microsoft and RDS/ADO consumers alike!

    Best Regards,


    Wednesday, July 25, 2012 11:44 PM
  • Neal,

    Thanks for the update, I have tried several times to get an answer from Ming and others at MS (even with a case number and speaking with a supervisor) all have not responded and have blown this issue off, if you hear anything please post.



    Wednesday, July 25, 2012 11:50 PM
  • As mentioned by Neal earlier, our support team has committed to fix the RDS-related issue by 7/31 (or early Aug in case if there is any sudden issue comes up).

    Currently, I think that you have to contact our support team, in order to obtain the private patch for testing purpose.

    btw, if some of you are hitting the problem with "Windows Server 2008" (Note: this is not Windows Server 2008 *R2*), then you may actually hit another issue not addressed by the private patch, unless you have installed a hotfix (or QFE) on your Windows Server 2008 before.

    If the issue impacts your business a lot, you can contact our support team. Otherwise, you may want to post a simple program to reproduce the issue in this forum, and we can take a closer look.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Thursday, July 26, 2012 12:17 AM
  • Pak-Ming Cheung,

    Thank you for the information you have provided so far.  I am among the many that experienced code breakage and/or functionality impact from the KB2698365 update.  Do you have an updated timeline for the “fix”?  If not can you post or forward information on how to contact your support team for information or a patch?

    The update impacted 15-20% of our users.  Rather than asking my customers to hide the update or uninstall it each day, I tried moving to a different connection.

    I released versions that used an encrypted connection to the SQL server rather than RDS but a number users, who were actually still working fine with the RDS versions, are getting dbNetLib.dll SSL errors with the MSDASQL Proivder.  Until I am able to diagnose those issues I moved those users back to RDS.  I now have some users connecting via RDS (MS Remote) and others connecting via MSDASQL.  I would like to return everyone to the RDS method until I can create a Web service and re-write program code. 

    Any information you could share is appreciated.



    Tuesday, July 31, 2012 6:51 PM
  • Pak-Ming Cheung,

    Any  news on when a solution to this bug will be availible?

    Tuesday, July 31, 2012 10:17 PM
  • Tq8d,

    I just got confirmation that there is a private patch available. It is "private", since we are still working on some dependency issues and the final fix may be changed. You can get a copy of the private patch from our customer support, if this issue impacts your business.

    Please note that the private patch is only for testing purpose. Please double-check with the customer support about the license of the patch (e.g. redistribution policy, etc.).

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, August 1, 2012 4:45 AM
  • i spoke to customer service at 800-936-5700, they couldn't figure out where to connect my call. is there a direct number available for support, or a link to the download.

    Wednesday, August 1, 2012 3:44 PM
  • Shafi,

    Have you tried the link at: http://support.microsoft.com/select/default.aspx?target=assistance&c1=509&

    WDAC team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, August 1, 2012 3:52 PM
  • Finally i spoke to someone in technical support. He couldn't send the fix as it was private. he created a case and forwarded to another technical team. I should be getting call back in 2 hours.
    Wednesday, August 1, 2012 4:00 PM
  • Ming,

    Can you please provide a KB # for Customer Support to identify this "private" patch? On the phone with them now and they state they are unable to identify this without a KB #.

    Thursday, August 2, 2012 7:33 PM
  • I have a support case working as well.   The first level technical support team was not sure how to connect my case to your team.  After reviewing your post here and confirming the issue on one of my workstations, they are forwarding my issue to the IIS team. They believe the IIS team will have access to the patch.  I am expecting a call today from that team.  Is there any information we can provide to the support team that will streamline the process of contacting your team?


    Friday, August 3, 2012 2:33 PM
  • I was able to get the test patch from MS support (KB2724642). The patch seems to work fine as long as you reinstall the original patch (kb2698365) first and then install the Hotfix. At first I received the Hotfix for testing purposes only but then recieved and updated patch that does not say it's for testing. I have e-mailed support to make sure the Hotfix is good for production--I have yet to receive a response. I also asked if they plan on making this part of the Windows updates in the future.

    M. Quick

    Friday, August 3, 2012 3:30 PM
  • M Quickman,

    any idea where we can download kb2724642, any help in this manner would be appreciated.


    Friday, August 3, 2012 3:49 PM
  • PCWerks,

    We are working on updating the KB with more information, so that other support teams can have a clearer understanding about the issue.

    In the meantime, I think that you would ask the CSS technican to contact the support team for WDAC. The IIS team may not have much information about this.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Saturday, August 4, 2012 9:12 AM
  • After a short stop  at the IIS team yesterday, then the Windows Forms team I was forwarded the ADO team.  They made a hot patch availble as KB2734642.  I  ran the update on both x86 and x64 boxes. It appears to work, you do need to make sure the original KB2698365 is applied first.  I was asked to test over the weekend to to discuss deployment Monday. Thanks so much for your help! Having this forum available saved time.


    Saturday, August 4, 2012 12:29 PM
  • Pc Werks,

    I too have recieved the hot fix patch and after installing kb2698365 then intsalling kb2734642 everything is running fine, I belive this update will be part of the next rounds of updates that go out this forum helped alot and cut down on wait times, thanks all!

    Tuesday, August 7, 2012 12:40 PM
  • I can't find kb2734642. When searching the only thing that comes up is this thread.
    Thursday, August 9, 2012 6:33 PM
  • Ming,

    Do you know when the KB2734642 hot fix will be released?  We have a number of customers who are anxious to get this patch.  I was hoping that it would be included in the monthly security updates that come out today, but I didn't see it in there at first glance.  If it's not ready to be released through Windows Update, is there a link that you can provide where we can download it?



    Tuesday, August 14, 2012 8:02 PM
  • Jay,

    As mentioned before, public forum is not a good place to talk about the release schedule. If this is urgent to your business, you can try to talk to Microsoft Support. They may be able to share some more information than what i can share here.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Wednesday, August 15, 2012 5:59 AM
  • Is the hot fix KB2724642 or KB2734642? Both are mentioned in this thread. Is one a typo?
    Thursday, August 16, 2012 12:36 PM
  • The name of the hotfix is KB2734642.  It took a little while, but I was able to obtain a copy of the hotfix from Microsoft support and I have successfully tested it out on both Windows 7 SP1 and Windows 2008 R2 SP1 (both 64-bit).  According to the support rep I was working with, they are hoping to include the hotfix with the regular September monthly updates. 
    Thursday, August 16, 2012 1:41 PM
  • We have a problem with an Access 97 application. It has stopped working after latest Windows update.

    Vladimir Cvajniga

    Friday, August 17, 2012 5:19 AM
  • Microsoft: Please, stop "updating" Windows that way. Now we're under heavy criticism of our customers.

    Vladimir Cvajniga

    Sunday, August 19, 2012 9:04 AM
  • The hotfix is now publicly available to download -


    Tuesday, August 21, 2012 12:19 PM
  • And now it isn't -


    The KB article has no public hotfixes. Please contact support if you need immediate assistance.

    Does anyone know what's happened to it? I haven't received any notification from Microsoft that there is a problem with it.

    Friday, August 24, 2012 9:04 AM
  • I'd like to add to for everyone that IE8 with the latest updates also appears to be effected by this issue. We need the patch guys!
    Friday, August 24, 2012 10:38 AM
  • W0lfqanq,

    Thanks for reporting this issue. I am contacting the support team to understand the issue. Once I have more information, I can update this thread.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Friday, August 24, 2012 2:55 PM
  • W0lfqanq,

    According to the support team, there was an issue in the package signing in the previous hotfix package. Therefore, we have pulled out the package. However, there is no plan to change the fix.

    We are working on the issue in high priority. Therefore, please expect that you can download the fix again soon.

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    Friday, August 24, 2012 4:05 PM
  • Ming,

    Do you know if the hotfix will be included in tomorrow's "Patch Tuesday" automatic updates?

    Monday, September 10, 2012 2:23 PM
  • Can this be your fix?


    I have not yet found the time to test it :-(

    Wednesday, September 12, 2012 2:06 PM
  • Yes, since it can be downloaded again, the previous package signing problem should be resolved.

    Please download the fix again at: http://support.microsoft.com/kb/2734642 

    WDAC Team, Microsoft.

    Pak-Ming Cheung - MSFT

    • Marked as answer by Jeremy_Wu Thursday, October 25, 2012 5:23 PM
    Friday, September 14, 2012 3:15 AM
  • Is there any way to deploy this .msu file from kb 2734642 using SUS or group policy?  We have a large number of computers affected by this apparently and are looking for a solution where we don't have to visit each individual computer.
    Friday, December 13, 2013 3:48 PM
  • Hello Gentlemen,

    Our application uses ADO\RDS components to fetch the data.


    Surfed the web to find RDS removed components for IIS 8 / windows server 2012 O/S. Also found another link where an alternative solution to solve RDS with IIS 8

    Currently I am seeing the below error while opening UI of our web application.

    Unexpected error. (0x8003001e). I remember there was a hotfix with KB KB2734642 for MS12-045 (kb2698365)patch . When i applied this hotfix and restart the server, the above error used to get resolved.  But the same hotfix is not applicable for Windows server 2012 R2 O/S. Can you please let us know if there is any similar hotfix available for windows Server 2012 ? Thanks in Advance. Chandra

    Monday, August 3, 2015 1:55 PM
  • Hi Chandra,

    I am facing the same situation. did you fix the issue for RDS component on the windows server 2012 R2. Please let me know as soon as possible. 

    Friday, February 3, 2017 3:30 PM