However, all of these changed when Windows 10 came along. Instead of a typical text file, the Windows Update service now writes a number of Event Tracing for Windows logs. So actually, there is no Windows update log location. Opening these logs isn’t as simple as it once used to be. However, there are workarounds for this.
How can I find the Windows Update Log in Windows 10?
We’ve compiled this step-by-step guide to show you how you can access the Windows Update logs using 2 different methods.
1. Use PowerShell
Once the command finishes running, it will create the classic WindowsUpdate.log file in your Desktop folder. This folder can be then easily opened with Notepad, and you can troubleshoot any issues you may have with Windows Update. If PowerShell has stopped working, check out our article and fix the issue in no time.
2. Use Event Viewer
The update logs on your device can be easily accessed using the built-in Event Viewer. You can select the events you are interested in and read the logs for each one of them.
Press Windows + X to open the WinX menu.
Select Event Viewer from the list.
Go to the following path: Applications and Service Logs\Microsoft\Windows\WindowsUpdateClient\Operational
Select the events whose logs you want to see from the middle column.
Read the log details listed for every event you are interested in.
Close Event Viewer when you finish.
If you want more options, check our comprehensive article to find the best event log viewers that you can use on Windows 10. By following these two methods you will be able to once again read the Windows Update Log as you used to in previous versions of Windows. Please remember that updating your Windows is important, and if you encounter any issues when trying to update, the Windows Update Log can come in handy. Do you think that the Windows Update Log was better off being the way it was before Windows 10? Let us know in the comment section below. Also, leave there any other questions or suggestions that you may have and we’ll be sure to check them out.
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ