Nov 02, 2016 Event 2: Log Name: System Source: Microsoft-Windows-WAS Event ID: 5117 Description includes: WsusPool Solution. If you are encountering Event ID 1309 in the Application log at around the same time as event ID 5117 in the System log, you most likely need to increase the memory allocated to the WSUS Application Pool in IIS. Event 2: Log Name: System Source: Microsoft-Windows-WAS Event ID: 5117 Description includes: WsusPool Solution. If you are encountering Event ID 1309 in the Application log at around the same time as event ID 5117 in the System log, you most likely need to increase the memory allocated to the WSUS Application Pool in IIS. In the event log we see automatic updates installing and rebooting the server. We thought we turned off automatic udpates prior to the last update/reboot events. When you turn off automatic updates, does it write an event to the log? If so, what is the 'source' of the log entry? 1074 Logged when an app (ex: Windows Update) causes the system to restart, or when a user initiates a restart or shutdown. 6006 Logged as a clean shutdown. It gives the message 'The Event log service was stopped'. 6008 Logged as a dirty shutdown. It gives the message 'The previous system shutdown at. Does the event log get an entry when automatic updates are turned off on Windows Server 2003. Ask Question. Browse other questions tagged windows-server-2003 windows-update or ask your own question. Does a Required Restart for Windows Update log an event? If so what is the source/id? Sep 09, 2019 I understand that you want to know if there is an specific event ID to detect the Windows Update restart or postpone pop-up. There is no way, from event viewer or script to detect the Windows Update pop-up in Windows 7. Please refer to the information provided in.
Event Id 300
One of the changes in Windows 10 is to the format of the log file of Windows Update. Instead of maintaining a plain text log file like all earlier releases of Windows, the Windows Update service now writes a number of Event Tracing for Windows logs (ETL files) under the location C:WindowslogsWindowsUpdate. Here is how to get the good old log file for Windows Update in Windows 10.
RECOMMENDED: Click here to fix Windows errors and optimize system performance
The *.etl files are created by the the Event Tracing subsystem for Windows (ETW). In Windows 10, Windows Update is almost active all the time since it is a service so the log file has to be maintained and written to on a nearly continuous basis. While switching to ETL files has allowed Microsoft to reduce the disk load and not impact disk I/O or operating system performance, this method makes it harder for users to easily read the log. To make matters worse, these *.etl files are cached, so their contents doesn't become available instantly.
Microsoft is aware of this issue. To overcome it and make the Windows Update log readable, Windows 10 provides two methods to read the log. One of them is a special PowerShell cmdlet and the other one is the built-in Event Viewer tool. Let's see how to use them.
To find the Windows Update Log in Windows 10, do the following.
- Open PowerShell.
- Type the following command at the PowerShell console:
- When it finishes running, the cmdlet will create the classic WindowsUpdate.log file in your Desktop folder.
You can open it with Notepad and read it to troubleshoot any issues you may be having with Windows Update such as some updates not installing, getting stuck or throwing cryptic errors.
You are done!
Alternatively, you can use Event Viewer to read the Windows Update log. Here is how.
Read Windows Update log with Event Viewer
- Press the Win + X keys or right-click the Start button and select Event Viewer in the context menu.
- In Event Viewer, go to Applications and Service LogsMicrosoftWindowsWindowsUpdateClientOperational.
- Select the events in the middle column of the app's window to read the log in the details pane below.
Tip: You might be interested in reading the following article:
The Settings app includes a special page, where the installation log is displayed in a friendly view. From Update History, you can also remove certain updates.
That's it!
RECOMMENDED: Click here to fix Windows errors and optimize system performance
Active3 years, 6 months ago
In the event log we see automatic updates installing and rebooting the server. We thought we turned off automatic udpates prior to the last update/reboot events. When you turn off automatic updates, does it write an event to the log? If so, what is the 'source' of the log entry?
Evan Anderson137k1515 gold badges178178 silver badges316316 bronze badges
Roger GuessRoger Guess18011 gold badge22 silver badges1010 bronze badges
1 Answer
The Automated Updates client doesn't generate any specific Event Log messages when its configuration is changed. You'll have better luck locating information about how it is behaving in
Evan AndersonEvan Anderson%SystemRoot%WindowsUpdate.Log
, where the Automated Updates client puts most of its logging information.137k1515 gold badges178178 silver badges316316 bronze badges