none
KB4019264 causes DNS service to not start.

    Question

  • After yesterdays KB install DNS service would not start.

    Windows Server 2008 R2. All current service packs are applied.

    Removing the KB and restarting the server fixed the issue.

    Log Name:      Application
    Source:        Application Error
    Date:          5/10/2017 9:22:51 PM
    Event ID:      1000
    Task Category: (100)
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      SVR3.xxxxxxxxxxx.com
    Description:
    Faulting application name: dns.exe, version: 6.1.7601.23764, time stamp: 0x58e7aa3d
    Faulting module name: dns.exe, version: 6.1.7601.23764, time stamp: 0x58e7aa3d
    Exception code: 0xc0000005
    Fault offset: 0x0000000000061393
    Faulting process id: 0x20d0
    Faulting application start time: 0x01d2c990852d4e32
    Faulting application path: C:\Windows\system32\dns.exe
    Faulting module path: C:\Windows\system32\dns.exe
    Report Id: c41b5b30-3583-11e7-8969-842b2b764eb7
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2017-05-10T13:22:51.000000000Z" />
        <EventRecordID>1288542</EventRecordID>
        <Channel>Application</Channel>
        <Computer>SVR3.xxxxxxxxxxx.com</Computer>
        <Security />
      </System>
      <EventData>
        <Data>dns.exe</Data>
        <Data>6.1.7601.23764</Data>
        <Data>58e7aa3d</Data>
        <Data>dns.exe</Data>
        <Data>6.1.7601.23764</Data>
        <Data>58e7aa3d</Data>
        <Data>c0000005</Data>
        <Data>0000000000061393</Data>
        <Data>20d0</Data>
        <Data>01d2c990852d4e32</Data>
        <Data>C:\Windows\system32\dns.exe</Data>
        <Data>C:\Windows\system32\dns.exe</Data>
        <Data>c41b5b30-3583-11e7-8969-842b2b764eb7</Data>
      </EventData>
    </Event>


    Gary Herbstman Byte Solutions, Inc. http://bytesolutions.com


    • Edited by GaryH-bytes Wednesday, May 10, 2017 3:49 PM
    Wednesday, May 10, 2017 3:40 PM

Answers

All replies

  • What operating system is used?

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, May 10, 2017 3:44 PM
  • 2008 R2 Standard

    Gary Herbstman Byte Solutions, Inc. http://bytesolutions.com

    Wednesday, May 10, 2017 3:51 PM
  • You might try;

    sfc /scannow

    also system update readiness tool

    https://support.microsoft.com/en-us/kb/947821

    Then check for errors in;
    %SYSTEMROOT%\Logs\CBS\CheckSUR.log

    If no joy I'd call it in to product support or also mention it over here.

    https://windowsserver.uservoice.com/forums/304618-installation-and-patching

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, May 10, 2017 3:54 PM
  • I just had the same issue this morning.  I am running Windows Server 2008 R2 Service Pack 1.  It is a DC.  DNS starts and fails immediately with KB4019264 installed. 

    Event 1000 is logged in the Application log:

    Faulting application name: dns.exe, version: 6.1.7601.23764, time stamp: 0x58e7aa3d
    Faulting module name: dns.exe, version: 6.1.7601.23764, time stamp: 0x58e7aa3d
    Exception code: 0xc0000005
    Fault offset: 0x0000000000061393
    Faulting process id: 0xf14
    Faulting application start time: 0x01d2c9a513521f1e
    Faulting application path: C:\Windows\system32\dns.exe
    Faulting module path: C:\Windows\system32\dns.exe
    Report Id: 52b96bef-3598-11e7-8255-000c2975f597


    • Edited by Kixtart Wednesday, May 10, 2017 3:56 PM
    Wednesday, May 10, 2017 3:56 PM
  • SFC was run as well as a CHKDSK... and many other checks. It boils down to the service pack install.

    Gary Herbstman Byte Solutions, Inc. http://bytesolutions.com

    Wednesday, May 10, 2017 8:05 PM
  • I am also seeing this exact issue on my 2008R2 Domain controller...

    Not good...

    Wednesday, May 10, 2017 8:13 PM
  •  

    If you need assistance with the issue I'd call it in to product support or if just reporting then I'd mention it over here.

    https://windowsserver.uservoice.com/forums/304618-installation-and-patching

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, May 10, 2017 8:15 PM
  • This is the same problem that occurred last year with KB3145126.  Solution can be found here.

    https://www.reddit.com/r/sysadmin/comments/6aec2a/kb4019264_killed_dns_server_on_2008_r2/dhfd840/

    • Marked as answer by GaryH-bytes Thursday, May 11, 2017 5:27 PM
    Thursday, May 11, 2017 4:38 PM
  • I had the same issue on multiple Server 2008r2 machines this morning after applying the updates last night.  Removing KB4019264 was the answer!
    • Proposed as answer by maine-guy Thursday, May 11, 2017 4:44 PM
    • Edited by maine-guy Thursday, May 11, 2017 4:55 PM
    • Marked as answer by GaryH-bytes Thursday, May 11, 2017 5:27 PM
    Thursday, May 11, 2017 4:44 PM
  • Did you mean KB4019264 not KB4019364?

    Gary Herbstman Byte Solutions, Inc. http://bytesolutions.com

    Thursday, May 11, 2017 4:49 PM
  • KB4019264 Thanks fixed that!
    Thursday, May 11, 2017 4:55 PM
  • The instructions in dsmtoday's answer worked for me. This is a much better solution than blocking the update. Thanks!
    Thursday, May 11, 2017 8:42 PM
  • Dsmtoday's reply was also exactly what I needed. The Reddit article he linked to was perfect, and the reddit poster links to Microsoft Article ID: 3145126, which is useful because it contains a powershell script you can run to identify the DNS zone causing the trouble. 

    I have 4 DNS servers, two of which run Server 2008 R2 (one of them being an SBS 2011 box), 1 Server 2012, and 1 Server 2012 R2. I only experienced the issue with the DNS Server service not starting on the Server 2008 R2 boxes. 

    After fixing the issue, I gave the affected servers one more reboot for good measure, since the inability to resolve DNS queries may well have affected the ability of other services to operate properly, if not prevent them from starting at all.

    Saturday, May 13, 2017 10:50 PM
  • I had this issue as well, removing KB4019264 resolved the issue.
    Monday, May 15, 2017 1:44 PM
  • THANK YOU!  This worked.
    Monday, May 15, 2017 1:51 PM
  • Thank you, Worked for me too, Why MS does not recalled the KB ??


    El Khiyati

    Wednesday, May 17, 2017 11:21 AM
  • thank you so much,

    It worked. I have expended 6 hours to find the fix.

    best regards.

    Wednesday, May 17, 2017 2:53 PM
  • Had the same issue with KB4019263.   Removed it, rebooted server, and now DNS service is back online. 
    Tuesday, May 30, 2017 4:46 PM
  • Thanks!  This problem was driving me crazy.  It reappeared with KB4019265 and KB4022719.  I am glad to finally have the issue resolved without having to remove critical updates.


    • Edited by Kixtart Tuesday, June 20, 2017 10:57 PM
    Tuesday, June 20, 2017 10:56 PM
  • Thanks!  I also had the same issue, however, i did not have (KB4019264) installed individually.  Or, more like, it was installed as part of a rollup I assume since (KB4019264) was part of (KB4014504).  I uninstalled (KB4014504) and was still not able to start DNS.  I saw Kixtart post and noticed i had(KB4022719) installed.  After I removed that update and rebooted, DNS started on my 2008R2 DC's.  Much thanks everyone.. this was also driving me crazy.
    Monday, July 10, 2017 11:58 AM