On Windows 10 and Windows 11, run Get-WindowsUpdateLog in Windows PowerShell to convert Windows Update’s trace files into a readable WindowsUpdate.log snapshot. Open that file in Notepad, then search around the time of the failed update for download, installation, and error entries. The snapshot does not update automatically; run the command again to capture later activity.

PowerShell generates a Windows Update log showing an installation failure due to insufficient reserved partition space. Before you create the log​

This guide uses Windows PowerShell on the PC that experienced the update problem. The same basic command works on Windows 10 and Windows 11.

  • Allow several minutes. Conversion time depends on the amount of trace data available.
  • Note the failure time and update name. A KB number and error code, if shown, make the resulting log easier to search.
  • Use an account that can read the update traces and write the output file. If the command reports an access error, try Windows PowerShell as administrator or ask your organization’s IT administrator.
  • No restart is needed to create the snapshot. Generating it does not itself install or remove an update.
  • Windows 10 version matters for older logs. Microsoft says logs from version 1709 onward can be decoded without its symbol server. Logs from versions earlier than 1709 require access to the Microsoft symbol server and must be decoded on a pre-1709 Windows 10 system. The straightforward local procedure below is aimed at version 1709 or later and Windows 11.

Microsoft ended free Windows 10 security fixes and technical assistance on October 14, 2025. The logging procedure remains useful on a Windows 10 PC, but creating a log does not change that support status.

Create the readable Windows Update log​

  1. Record the update details, if available.

Open update history and note the update’s name, KB number, displayed error code, and approximate failure time:

  • Windows 11: Open Settings > Windows Update > Update history.
  • Windows 10: Open Settings > Update & Security > Windows Update > View update history.

You can still generate the log if the update is not listed or you do not know the exact time.

  1. Open Windows PowerShell.

Select Start, type Windows PowerShell, and open the result. Use Windows PowerShell rather than a Command Prompt window. If you already know your account needs elevation to read the traces, right-click Windows PowerShell, select Run as administrator, and approve the prompt.

If an administrator supplies different credentials, the command runs under that administrator’s account. Its default Desktop location can therefore be different from your usual Desktop.

  1. Generate the snapshot.

At the PowerShell prompt, enter:

Get-WindowsUpdateLog

Press Enter and wait for the command to finish and the prompt to return. Microsoft’s cmdlet merges and converts the available Windows Update .etl traces into a readable file. By default, the output is named WindowsUpdate.log on the current user’s Desktop.

Keep the PowerShell window open. Conversion can take time, and progress messages are not the same as a finished result. If the command reports an error, retain the message for troubleshooting rather than assuming the file was created successfully.

  1. Open the result.

Look for WindowsUpdate.log on the Desktop associated with the account running PowerShell. Double-click it, or open Notepad and use File > Open to select it. If Notepad’s file picker does not show the .log file, change its file-type filter to All Files.

You can also open the default location from the same PowerShell session:

notepad.exe (Join-Path ([Environment]::GetFolderPath('Desktop')) 'WindowsUpdate.log')

This command uses the Desktop location for the account running that session, including when the Desktop has been redirected.

  1. Check that it is a readable, relevant snapshot.

The file should contain text entries rather than unreadable raw trace data. Look for timestamps near the period you recorded. The amount and age of the available information depend on the traces still present on the PC; the command cannot recreate trace data that is no longer available.

If the update failure happened after you generated the file, generate another snapshot. The existing file is a static copy, not a live log. To preserve the first snapshot for comparison, rename or copy it before running the command again.

Find download and installation activity​

The log can be lengthy. Start with the failure time from Settings, then work outward instead of treating every occurrence of “error” as the cause.

  1. In Notepad, press Ctrl+F and search for the exact error code from update history, if you have one—for example, the full code beginning with 0x. Examine the surrounding lines as well as the matching line.
  2. Search for the update’s KB number. If it does not appear, search around the recorded time instead. Some entries identify updates with internal IDs rather than a familiar KB number, so the absence of a KB match does not prove that the update is missing from the log.
  3. Search for terms such as download, install, failed, or error. These are starting points, not guaranteed labels for every event. Read entries immediately before and after a match to determine which update or operation it concerns.
  4. Use the component name to narrow the investigation. Microsoft identifies DownloadManager with creating and monitoring payload downloads, while Handler and Setup relate to installer handlers. A relevant download entry may help establish whether work reached that stage; an installer-related entry can help you follow what happened later.
  5. Record the timestamp, component, exact error code, and several surrounding lines that describe the same operation. Compare them with the update name and status in Settings.

A log line can describe a failed attempt that was followed by a successful retry. Conversely, an entry saying a download started does not establish that installation finished. Check the surrounding sequence and update history before drawing a conclusion. Microsoft notes that entries are usually chronological, but exceptions can occur.

Search from PowerShell instead​

For a large file, PowerShell can show matching lines with a little surrounding context. In the same session used to create the default Desktop file, run:

Code:
$log = Join-Path ([Environment]::GetFolderPath('Desktop')) 'WindowsUpdate.log'
Select-String -Path $log -Pattern 'download','install','failed','error' -Context 2,2

This displays matches and two lines of context on either side. It does not change the log. It may produce many results, including unrelated or harmless entries.

To search for one specific code instead, replace the example below with the exact code you recorded:

Select-String -Path $log -Pattern '0x80070002' -SimpleMatch -Context 3,3

If you saved the log somewhere else, set $log to that file’s full path before searching. A lack of matches only means that the selected text was not found in that snapshot.

Check the log before sharing it​

Treat the log and any search output as potentially sensitive. Before posting it to a public forum or sending it outside your organization:

  1. Keep an unedited original locally. Make a separate copy for sharing so that redaction does not destroy the evidence you may need later.
  2. Review the copy in Notepad. Look for account or computer names, file paths containing usernames, internal server names or addresses, organization-specific URLs, and other identifying information. Also check any surrounding context you plan to paste into a post.
  3. Remove or replace sensitive text in the copy. Preserve useful technical details such as timestamps, component names, update identifiers, and error codes where it is safe to do so. Consistent placeholders—for example, [internal-server]—can make related entries easier to follow.
  4. Review the entire excerpt or attachment again. Search for your username, computer name, organization name, and internal domains if you know them. Search is a useful check, not a guarantee that all sensitive data has been found.
  5. Share only what is needed. Start with the update name, Windows version, error code, approximate failure time, and a short, reviewed excerpt. For a managed PC, follow your organization’s rules and use its approved support channel.

Do not post the full log merely because someone asks for “logs” without first checking what it contains and where it will be shared.

If the command or log does not help​

  • PowerShell says the command is not recognized. Confirm that you opened Windows PowerShell, not Command Prompt. Run Get-Command Get-WindowsUpdateLog to check whether the cmdlet is available. If it still is not found on a managed PC, give the exact message to IT rather than downloading an unrelated third-party update module.
  • Access is denied or the output cannot be written. Reopen Windows PowerShell with Run as administrator and try again. Remember that a session using different administrator credentials may put the result on that account’s Desktop. On a work device, ask IT if elevation is restricted.
  • The Desktop file is missing. First wait for the PowerShell prompt to return and check the command’s output for an error. Then check the Desktop for the account that ran the command. If the default location is unsuitable, specify a full output path to an existing folder you can write to, for example:

Get-WindowsUpdateLog -LogPath "$env:USERPROFILE\Documents\WindowsUpdate.log"

The path in this example belongs to the account running PowerShell. If that Documents folder does not exist or is not writable, choose another existing writable folder. The -LogPath parameter controls the output location.

  • The relevant event is missing. Confirm that you generated the snapshot after the failure and are looking at the correct date and time. Search for the error code and nearby time as well as the KB number. If the traces no longer contain the event, try capturing a new snapshot after a subsequent failure; do not repeatedly force a problem to occur on a managed or production PC without approval.
  • The log shows an installation failure but not enough detail. Microsoft identifies CBS.log, under %systemroot%\Logs\CBS, as a source of servicing-stack installation information. Treat it as sensitive too. For a feature-upgrade failure, Windows Setup logs may be more relevant than the Windows Update snapshot.
  • The update is downloaded but installation or restart does not begin. The update orchestration logs may provide additional context. On builds where the cmdlet offers it, Get-WindowsUpdateLog -IncludeAllLogs creates a Desktop folder containing readable Windows Update, USO, and UX logs. Microsoft documents that this switch cannot be combined with the cmdlet’s other parameters. Review every generated file for sensitive information before sharing.

If the snapshot was created successfully but the cause remains unclear, escalate with the Windows version, update name or KB number, exact error, failure time, and a reviewed excerpt. Keep the original log available in case the support technician needs more context.