To improve Windows Server I suggest you ...

Resurrect WindowsUpdate.log, or create a proper dedicated Event Log

Enough said.

64 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Tom Stachowiak commented  ·   ·  Flag as inappropriate

    Removing the ability to look at a live log file is annoying. Also on some machines running 1709 (we are still on ) sometimes it gives some kind of error about the debug symbols and cant create the log. Yea that's helpful.

  • Rich B commented  ·   ·  Flag as inappropriate

    Additionally, the "Get-WindowsUpdateLog" PowerShell cmdlet that you have to run to generate the new WindowsUpdate.log doesn't work if you don't have Windows Defender installed, because the first step in the process tries to copy a Defender dll. You get the error message:
    "Copy-Item : Cannot find path 'C:\Program Files\Windows Defender\SymSrv.dll' because it does not exist."

  • Anonymous commented  ·   ·  Flag as inappropriate

    Log Name: System
    Source: Microsoft-Windows-DNS-Client
    Date: 09/26/2018 13:03:48
    Event ID: 1014
    Task Category: None
    Level: Warning
    Computer: farhad-PC
    Name resolution for the name timed out after none of the configured DNS servers responded.
    Event Xml:
    <Event xmlns="">
    <Provider Name="Microsoft-Windows-DNS-Client" Guid="{1C95126E-7EEA-49A9-A3FE-A378B03DDB4D}" />
    <TimeCreated SystemTime="2018-09-26T09:33:48.666725100Z" />
    <Correlation />
    <Execution ProcessID="1620" ThreadID="3144" />
    <Security UserID="S-1-5-20" />
    <Data Name="QueryName"></Data>
    <Data Name="AddressLength">16</Data>
    <Data Name="Address">02000035C0A801010000000000000000</Data>

Feedback and Knowledge Base