none
Clients' wuaueng.dll crashes with 0xc00000fd RRS feed

  • Question

  • We are using Windows Server 2016 Essentials and provide updates via WSUS for 6 laptops with Windows 10 Pro. The server was installed in April 2018 and the 6th laptop was purchased and joined to the domain in February 2019. With this 6th laptop we're not able to get updates from WSUS. While trying to fix this we also noticed that our Windows server has the same problem itself, however everything works as expected for the other 5 laptops:

    The "checking for updates..." screen loads forever and the event viewer shows this exception after a few minutes:


    Name der fehlerhaften Anwendung: svchost.exe_wuauserv, Version: 10.0.14393.0, Zeitstempel: 0x57899b1c
    Name des fehlerhaften Moduls: wuaueng.dll, Version: 10.0.14393.2608, Zeitstempel: 0x5bd1346f
    Ausnahmecode: 0xc00000fd
    Fehleroffset: 0x000000000005a70c
    ID des fehlerhaften Prozesses: 0xb70
    Startzeit der fehlerhaften Anwendung: 0x01d4d7e36980242a
    Pfad der fehlerhaften Anwendung: C:\Windows\system32\svchost.exe
    Pfad des fehlerhaften Moduls: c:\windows\system32\wuaueng.dll
    Berichtskennung: 9485e301-f9aa-4133-8e34-d2e286c37421
    Vollständiger Name des fehlerhaften Pakets:
    Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
    

    0xc00000fd is a stack overflow exception, as far as I know.

    We've been trying to fix this now for weeks. Here is what we did:

    • this troubleshooter-tool (https://support.microsoft.com/de-de/help/4027322/windows-update-troubleshooter) - it requires a restart. In the end the tool has the same problem like the Windows Update GUI, it loads forever
    • Reset Windows Update components (https://support.microsoft.com/de-de/help/971058/how-do-i-reset-windows-update-components) - we did that multiple times
    • wsusutil.exe usecustomwebsite true
    • wsusutil.exe checkhealth - the event view contains a warning that one of the clients didn't connect within 30 days, which is true
    • DISM + sfc /scannow (https://support.microsoft.com/de-de/help/947821/fix-windows-update-errors-by-using-the-dism-or-system-update-readiness) - all files seem to be good
    • cleaned WSUS
    • re-installed WSUS via Server Manager
    • disabled the WSUS-GPO so that all clients connect to Microsoft Update directly. This allowed us to update the new laptop and the server itself.

    We noticed that someone had the same problem here:

    https://social.technet.microsoft.com/Forums/en-US/ba8bb1ad-ea2f-4b2b-9c68-c7cf8c8f1acb/windows-10-windows-update-crash-with-wuauengdll-exception-code-0xc00000fd?forum=win10itprogeneral

    ...But the solution didn't work for us. Also we don't have access to the mentioned wsus-clean-script.

    wuaueng.dll versions:

    • 10.0.17763.292 - working laptops and non working laptop
    • 10.0.14393.2608 - windows server 2016 essentials = wsus server

    Monday, March 11, 2019 3:17 PM

Answers

  • @Yic Lv Thanks for your reply. However, the links you posted are all related to older versions of Windows Server. In the "update guide" there is no "Windows 10" option.


    After weeks we finally solved this the same way like the author with the exact same problem I mentioned in my question (https://social.technet.microsoft.com/Forums/en-US/ba8bb1ad-ea2f-4b2b-9c68-c7cf8c8f1acb/windows-10-windows-update-crash-with-wuauengdll-exception-code-0xc00000fd?forum=win10itprogeneral): We purchased the "WSUS Automated Maintenance" software by AJTek. As we followed the guide for cleaning up WSUS manually I didn't expect that this is necessary.

    For MS I think it's embarassing that users (who payed for your server os) rely on third party tools to fix the WSUS mess. The "WSUS Automated Maintenance" is exactly what I'd expect from WSUS itself.
    • Marked as answer by fishbone.1 Friday, March 29, 2019 8:21 AM
    Friday, March 29, 2019 8:21 AM

All replies

  • Hi,
     

    Thank you for posting here.
     

    Excluding the Troubleshooting you have already done, the following questions may be possible in the next research direction:
     

    1. Is the antivirus software installed on the client or server? This may hinder the normal operation of the WUA.
    2. Updating the WUA to the latest version has attempted to resolve the issue: How to update the Windows Update Agent to the latest version
       

    There are no more ideas yet, but this thread seems to be a problem similar to yours: Windows Update stopped working on Two Windows 2008 Servers
     

    Hope the above can help you.
     

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, March 12, 2019 6:40 AM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, March 27, 2019 7:39 AM
  • @Yic Lv Thanks for your reply. However, the links you posted are all related to older versions of Windows Server. In the "update guide" there is no "Windows 10" option.


    After weeks we finally solved this the same way like the author with the exact same problem I mentioned in my question (https://social.technet.microsoft.com/Forums/en-US/ba8bb1ad-ea2f-4b2b-9c68-c7cf8c8f1acb/windows-10-windows-update-crash-with-wuauengdll-exception-code-0xc00000fd?forum=win10itprogeneral): We purchased the "WSUS Automated Maintenance" software by AJTek. As we followed the guide for cleaning up WSUS manually I didn't expect that this is necessary.

    For MS I think it's embarassing that users (who payed for your server os) rely on third party tools to fix the WSUS mess. The "WSUS Automated Maintenance" is exactly what I'd expect from WSUS itself.
    • Marked as answer by fishbone.1 Friday, March 29, 2019 8:21 AM
    Friday, March 29, 2019 8:21 AM