Log files and resolving upgrade errors - Windows Deployment (2023)

  • Article
  • 7 minutes to read

Applies to

  • Windows 10

Note

This is a 400-level topic (advanced).

See Resolve Windows 10 upgrade errors for a full list of topics in this article.

Several log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is setupact.log. The log files are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code.

The following table describes some log files and how to use them for troubleshooting purposes:

Log filePhase: LocationDescriptionWhen to use
setupact.logDown-Level:
$Windows.~BT\Sources\Panther
Contains information about setup actions during the downlevel phase.All down-level failures and starting point for rollback investigations.
Setup.act is the most important log for diagnosing setup issues.
setupact.logOOBE:
$Windows.~BT\Sources\Panther\UnattendGC
Contains information about actions during the OOBE phase.Investigating rollbacks that failed during OOBE phase and operations - 0x4001C, 0x4001D, 0x4001E, 0x4001F.
setupact.logRollback:
$Windows.~BT\Sources\Rollback
Contains information about actions during rollback.Investigating generic rollbacks - 0xC1900101.
setupact.logPre-initialization (prior to downlevel):
Windows
Contains information about initializing setup.If setup fails to launch.
setupact.logPost-upgrade (after OOBE):
Windows\Panther
Contains information about setup actions during the installation.Investigate post-upgrade related issues.
setuperr.logSame as setupact.logContains information about setup errors during the installation.Review all errors encountered during the installation phase.
miglog.xmlPost-upgrade (after OOBE):
Windows\Panther
Contains information about what was migrated during the installation.Identify post upgrade data migration issues.
BlueBox.logDown-Level:
Windows\Logs\Mosetup
Contains information communication between setup.exe and Windows Update.Use during WSUS and Windows Update down-level failures or for 0xC1900107.
Supplemental rollback logs:
Setupmem.dmp
setupapi.dev.log
Event logs (*.evtx)
$Windows.~BT\Sources\RollbackAdditional logs collected during rollback.Setupmem.dmp: If OS bug checks during upgrade, setup will attempt to extract a mini-dump.
Setupapi: Device install issues - 0x30018
Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.

Log entry structure

A setupact.log or setuperr.log entry (files are located at C:\Windows) includes the following elements:

  1. The date and time - 2016-09-08 09:20:05

  2. The log level - Info, Warning, Error, Fatal Error

  3. The logging component - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS

    The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are useful for troubleshooting Windows Setup errors.

  4. The message - Operation completed successfully.

    (Video) Defrag Tools #193 - Windows Upgrade Logs

See the following example:

Date/TimeLog levelComponentMessage
2016-09-08 09:23:50,WarningMIGCouldn't replace object C:\Users\name\Cookies. Target Object can't be removed.

Analyze log files

The following instructions are meant for IT professionals. Also see the Upgrade error codes section in this guide to familiarize yourself with result codes and extend codes.

To analyze Windows Setup log files:

  1. Determine the Windows Setup error code. This code should be returned by Windows Setup if it isn't successful with the upgrade process.

  2. Based on the extend code portion of the error code, determine the type and location of a log file to investigate.

  3. Open the log file in a text editor, such as notepad.

  4. Using the result code portion of the Windows Setup error code, search for the result code in the file and find the last occurrence of the code. Alternatively search for the "abort" and abandoning" text strings described in step 7 below.

  5. To find the last occurrence of the result code:

    1. Scroll to the bottom of the file and select after the last character.
    2. Select Edit.
    3. Select Find.
    4. Type the result code.
    5. Under Direction select Up.
    6. Select Find Next.
  6. When you've located the last occurrence of the result code, scroll up a few lines from this location in the file and review the processes that failed prior to generating the result code.

    (Video) DISM /Cleanup-Image /RestoreHealth & SFC /ScanNow not Working Windows 10, 8 & 7 | Fix All Errors

  7. Search for the following important text strings:

    • Shell application requested abort
    • Abandoning apply due to error for object
  8. Decode Win32 errors that appear in this section.

  9. Write down the timestamp for the observed errors in this section.

  10. Search other log files for additional information matching these timestamps or errors.

For example, assume that the error code for an error is 0x8007042B - 0x2000D. Searching for "8007042B" reveals the following content from the setuperr.log file:

Note

Some lines in the text below are shortened to enhance readability. For example

  • The date and time at the start of each line (ex: 2016-10-05 15:27:08) is shortened to minutes and seconds
  • The certificate file name, which is a long text string, is shortened to just "CN."

setuperr.log content:

(Video) Windows 8/10: How To Repair Component Store Corruption Using DISM.exe

27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570]27:08, Error Gather failed. Last error: 0x0000000027:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C27:09, Error SP CMigrateFramework: Gather framework failed. Status: 4427:09, Error SP Operation failed: Migrate framework (Full). Error: 0x8007042B[gle=0x000000b7]27:09, Error SP Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]27:09, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x8007042B[gle=0x000000b7]

The first line indicates there was an error 0x00000570 with the file C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN] (shown below):

27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]

The error 0x00000570 is a Win32 error code corresponding to: ERROR_FILE_CORRUPT: The file or directory is corrupted and unreadable.

Therefore, Windows Setup failed because it wasn't able to migrate the corrupt file C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18[CN]. This file is a local system certificate and can be safely deleted. Searching the setupact.log file for more details, the phrase "Shell application requested abort" is found in a location with the same timestamp as the lines in setuperr.log. This confirms our suspicion that this file is the cause of the upgrade failure:

setupact.log content:

27:00, Info Gather started at 10/5/2016 23:27:0027:00, Info [0x080489] MIG Setting system object filter context (System)27:00, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped27:00, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped27:00, Info SP ExecuteProgress: Elapsed events:1 of 4, Percent: 1227:00, Info [0x0802c6] MIG Processing GATHER for migration unit: <System>\UpgradeFramework (CMXEAgent)27:08, Error SP Error READ, 0x00000570 while gathering/applying object: File, C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Will return 0[gle=0x00000570]27:08, Error MIG Error 1392 while gathering object C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 [CN]. Shell application requested abort![gle=0x00000570]27:08, Info SP ExecuteProgress: Elapsed events:2 of 4, Percent: 2527:08, Info SP ExecuteProgress: Elapsed events:3 of 4, Percent: 3727:08, Info [0x080489] MIG Setting system object filter context (System)27:08, Info [0x0803e5] MIG Not unmapping HKCU\Software\Classes; it is not mapped27:08, Info [0x0803e5] MIG Not unmapping HKCU; it is not mapped27:08, Info MIG COutOfProcPluginFactory::FreeSurrogateHost: Shutdown in progress.27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost::CommandLine: -shortened-27:08, Info MIG COutOfProcPluginFactory::LaunchSurrogateHost: Successfully launched host and got control object.27:08, Error Gather failed. Last error: 0x0000000027:08, Info Gather ended at 10/5/2016 23:27:08 with result 4427:08, Info Leaving MigGather method27:08, Error SP SPDoFrameworkGather: Gather operation failed. Error: 0x0000002C

setupapi.dev.log content:

>>> [Device Install (UpdateDriverForPlugAndPlayDevices) - PCI\VEN_8086&DEV_8C4F]>>> Section start 2019/09/26 20:13:01.623 cmd: rundll32.exe "C:\WINDOWS\Installer\MSI6E4C.tmp",zzzzInvokeManagedCustomActionOutOfProc SfxCA_95972906 484 ChipsetWiX.CustomAction!Intel.Deployment.ChipsetWiX.CustomActions.InstallDrivers ndv: INF path: C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf ndv: Install flags: 0x00000000 ndv: {Update Device Driver - PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8} ndv: Search options: 0x00000081 ndv: Searching single INF 'C:\WINDOWS\TEMP\{15B1CD41-69F5-48EA-9F45-0560A40FE2D8}\Drivers\lynxpoint\LynxPointSystem.inf' dvi: {Build Driver List} 20:13:01.643 dvi: Searching for hardware ID(s): dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 dvi: pci\ven_8086&dev_8c4f&cc_060100 dvi: pci\ven_8086&dev_8c4f&cc_0601 dvi: Searching for compatible ID(s): dvi: pci\ven_8086&dev_8c4f&rev_04 dvi: pci\ven_8086&dev_8c4f dvi: pci\ven_8086&cc_060100 dvi: pci\ven_8086&cc_0601 dvi: pci\ven_8086 dvi: pci\cc_060100 dvi: pci\cc_0601 sig: {_VERIFY_FILE_SIGNATURE} 20:13:01.667 sig: Key = lynxpointsystem.inf sig: FilePath = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf sig: Catalog = c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\LynxPoint.cat sig: Success: File is signed in catalog. sig: {_VERIFY_FILE_SIGNATURE exit(0x00000000)} 20:13:01.683 dvi: Created Driver Node: dvi: HardwareID - PCI\VEN_8086&DEV_8C4F dvi: InfName - c:\windows\temp\{15b1cd41-69f5-48ea-9f45-0560a40fe2d8}\drivers\lynxpoint\lynxpointsystem.inf dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F dvi: Section - Needs_ISAPNP_DRV dvi: Rank - 0x00ff2001 dvi: Signer Score - WHQL dvi: DrvDate - 04/04/2016 dvi: Version - 10.1.1.18 dvi: {Build Driver List - exit(0x00000000)} 20:13:01.699 ndv: Searching currently installed INF dvi: {Build Driver List} 20:13:01.699 dvi: Searching for hardware ID(s): dvi: pci\ven_8086&dev_8c4f&subsys_05be1028&rev_04 dvi: pci\ven_8086&dev_8c4f&subsys_05be1028 dvi: pci\ven_8086&dev_8c4f&cc_060100 dvi: pci\ven_8086&dev_8c4f&cc_0601 dvi: Searching for compatible ID(s): dvi: pci\ven_8086&dev_8c4f&rev_04 dvi: pci\ven_8086&dev_8c4f dvi: pci\ven_8086&cc_060100 dvi: pci\ven_8086&cc_0601 dvi: pci\ven_8086 dvi: pci\cc_060100 dvi: pci\cc_0601 dvi: Created Driver Node: dvi: HardwareID - PCI\VEN_8086&DEV_8C4F dvi: InfName - C:\WINDOWS\System32\DriverStore\FileRepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf dvi: DevDesc - Intel(R) QM87 LPC Controller - 8C4F dvi: Section - Needs_ISAPNP_DRV dvi: Rank - 0x00ff2001 dvi: Signer Score - WHQL dvi: DrvDate - 10/03/2016 dvi: Version - 10.1.1.38 dvi: {Build Driver List - exit(0x00000000)} 20:13:01.731 dvi: {DIF_SELECTBESTCOMPATDRV} 20:13:01.731 dvi: Default installer: Enter 20:13:01.735 dvi: {Select Best Driver} dvi: Class GUID of device changed to: {4d36e97d-e325-11ce-bfc1-08002be10318}. dvi: Selected Driver: dvi: Description - Intel(R) QM87 LPC Controller - 8C4F dvi: InfFile - c:\windows\system32\driverstore\filerepository\lynxpointsystem.inf_amd64_cd1e518d883ecdfe\lynxpointsystem.inf dvi: Section - Needs_ISAPNP_DRV dvi: {Select Best Driver - exit(0x00000000)} dvi: Default installer: Exit dvi: {DIF_SELECTBESTCOMPATDRV - exit(0x00000000)} 20:13:01.743 ndv: Currently Installed Driver: ndv: Inf Name - oem1.inf ndv: Driver Date - 10/03/2016 ndv: Driver Version - 10.1.1.38 ndv: {Update Device Driver - exit(00000103)}! ndv: No better matching drivers found for device 'PCI\VEN_8086&DEV_8C4F&SUBSYS_05BE1028&REV_04\3&11583659&0&F8'.! ndv: No devices were updated.<<< Section end 2019/09/26 20:13:01.759<<< [Exit status: FAILURE(0xC1900101)]

This analysis indicates that the Windows upgrade error can be resolved by deleting the C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18[CN] file.

Note

In this example, the full, unshortened file name is C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18\be8228fb2d3cb6c6b0ccd9ad51b320b4_a43d512c-69f2-42de-aef9-7a88fabdaa3f.

(Video) [How To] Fix : Windows Resource Protection found corrupt files

Related articles

Windows 10 FAQ for IT professionals
Windows 10 Enterprise system requirements
Windows 10 Specifications
Windows 10 IT pro forums
Fix Windows Update errors by using the DISM or System Update Readiness tool

FAQs

How do I get Windows Update and deployment logs? ›

To find the Windows Update Log in Windows 10, do the following.
  1. Open PowerShell.
  2. Type the following command at the PowerShell console: Get-WindowsUpdateLog.
  3. When it finishes running, the cmdlet will create the classic WindowsUpdate. log file in your Desktop folder.
Dec 19, 2017

What are Windows upgrade log files? ›

These log files are essential for troubleshooting upgrade problems. By default, the folders that contain these log files are hidden on the upgrade target computer. To view the log files, configure Windows Explorer to view hidden items, or use a tool to automatically gather these logs. The most useful log is setupact.

Is it okay to delete Windows upgrade log files? ›

To give you a background, these files are only needed if you had issues with windows after an upgrade and or an update. If your computer is stable after an update or an upgrade, then Yes, it is safe to delete those files.

How do I get a list of hotfixes and updates? ›

Steps
  1. Open Command Prompt.
  2. Type wmic qfe list full /format:list > hotfixes.txt.
  3. Type start notepad hotfixes.txt.
Jun 29, 2022

What are the different methods of deploying Windows updates? ›

New versions of Windows have typically been deployed by organizations using an image-based process built on top of tools provided in the Windows Assessment and Deployment Kit, Windows Deployment Services, the Microsoft Deployment Toolkit, and Microsoft Configuration Manager.

How do I view Windows error logs? ›

Click Start > Control Panel > System and Security > Administrative Tools. Double-click Event Viewer. Select the type of logs that you wish to review (ex: Windows Logs)

Where are Windows Installer logs located? ›

The log file, Msi. log, appears in the Temp folder of the system volume. For more information about MSI logging, see Windows Help. To do this, search by using the phrase msi logging, and then select Managing options for computers through Group Policy.

How do I find the error log file? ›

To check for error logs, follow these steps:
  1. Check the log files for error messages. Examine errlog. log first.
  2. If indicated, check optional log files for error messages.
  3. Identify the errors associated with your problem.
Jun 29, 2022

How do I analyze Windows Update logs? ›

Method 2: Read the Windows Update logs via Event Viewer
  1. Press Windows key + R to open up a Run dialog box. ...
  2. Once you're inside the Event Viewer utility, use the menu on the left to navigate to the following location: Applications and Service Logs\Microsoft\Windows\WindowsUpdateClient.
Sep 27, 2022

How do I find out why Windows Update failed? ›

If you get an error code while downloading and installing Windows updates, the Update Troubleshooter can help resolve the problem. Select Start > Settings > Update & Security > Troubleshoot > Additional troubleshooters.

What are the four standard Windows logs? ›

They are Information, Warning, Error, Success Audit (Security Log) and Failure Audit (Security Log).

Are Windows log files important? ›

They help you track what happened and troubleshoot problems. The Windows event log contains logs from the operating system and applications such as SQL Server or Internet Information Services (IIS). The logs use a structured data format, making them easy to search and analyze.

What happens if you delete Windows log files? ›

You should not manually delete the log files. Some of them will be logged as system files so that you can not delete them. Manually trying to delete them is likely to leave you with a mess. Run the Disk Cleanup that is part of Windows and it will correctly clean them up for you.

What happens if I delete log files? ›

Deleting log files will remove them temporarily. If your Mac needs to log any further information, however, the log files will be recreated.

How do I force a server to check for updates? ›

Now lets get started!
  1. Open an Administrative (elevated) command prompt.
  2. Run “sconfig” to launch the “Server Configuration” application.
  3. Select option “6” to “Download and Install Windows Updates”
  4. Choose “A” for all updates, or “R” for recommended updates, and a scan will start.
Jan 21, 2022

How do you check hotfixes? ›

Resolution
  1. Click Start, Run, and type cmd to launch a command window.
  2. Type systeminfo to display the information on screen, or systeminfo >C:\systeminfo. txt to write the output to a file called systeminfo. txt at the root of the C drive.
  3. Search the list of hotfixes for the patch that is sought.
Nov 17, 2010

How do I fix failed updates? ›

Methods to fix Windows Update failing errors
  1. Run the Windows Update Troubleshooter tool.
  2. Restart Windows Update related services.
  3. Run the System File Checker (SFC) scan.
  4. Execute the DISM command.
  5. Temporarily disable your antivirus.
  6. Restore Windows 10 from a backup.

What are the 3 main steps in the deployment process? ›

Software deployment process mainly consists of 3 stages: development, testing and monitoring.

What are the three phases of deployment? ›

Generally speaking, this flow consists of three phases: pre-deploy, deploy and post-deploy.

What are the four deployment models? ›

There are four cloud deployment models: public, private, community, and hybrid. Each deployment model is defined according to where the infrastructure for the environment is located.

Where are Windows error reporting files stored? ›

WER settings are located in one of the following registry subkeys: HKEY_CURRENT_USER\Software\Microsoft\Windows\Windows Error Reporting. HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Windows Error Reporting.

How do I analyze Windows error reporting files? ›

To open the Problem Reports log, type problem reports in the search box and then click View All Problem Reports. Figure 17-3 shows a portion of the error history for a computer that was upgraded to Windows 10 in the first month after it was available.

What is a Windows log file? ›

A log file is a computer-generated data file that contains information about usage patterns, activities, and operations within an operating system, application, server or another device.

What is the setup log files? ›

The Setupact. log file in this directory contains information about the progress of the initial options that are selected on the Windows installation screen. The Windows installation screen appears when you start the computer by using the Windows installation media.

How do I find my software installation history? ›

  1. Type and search [Apps & features] in the Windows search bar①, then click [Open]②.
  2. In Apps & features, click [Sort by]③ and select [Install date]④.
  3. Click [Filter by]⑤ and select [All drives]⑥. ...
  4. Applications will be sorted by the latest installation date.
Sep 1, 2022

How do I create a log file for setup exe? ›

Run the following command: "C:\setup.exe" /v"/l*v LogFile. log", where "C:\setup.exe" is the path to the EXE installation file, and "LogFile. log" is the path to the file to be used to output the log file. As you continue with the installation, make sure that LogFile.

What are the two types of log files? ›

Types of Logs

Server Log: a text document containing a record of activities related to a specific server in a specific period of time. System Log (syslog): a record of operating system events.

Where are error logs stored? ›

The location of the error log file itself can be set manually in the php. ini file. On a Windows server, in IIS, it may be something like "'error_log = C:\log_files\php_errors. log'" in Linux it may be a value of "'/var/log/php_errors.

How to read Windows Update ETL logs? ›

etl files of Windows 10 updates, open the 'Choose Data Source' window of FullEventLogView tool (F7), choose the 'Load events from external folder with log files' option, fill the desired Windows Update logs folder (Usually the folder is C:\Windows\Logs\WindowsUpdate ), and then press the 'OK' button.

Why does my Windows 10 upgrade keep failing? ›

The most common upgrade errors can be traced to a handful of basic causes: software incompatibilities, storage-related issues, and errors in the Setup wizard. Even if you don't know the exact reason for an upgrade problem, you might be able to resolve it with some simple troubleshooting measures.

How do I fix a corrupted Windows 10 update? ›

Fix Windows Update repairing corrupted system files
  1. Open Start.
  2. Search for Command Prompt, right-click the top result, and select the Run as administrator option.
  3. Type the following DISM command to repair corrupted system files and press Enter: dism.exe /Online /Cleanup-image /Restorehealth.
Dec 8, 2022

How do I fix incomplete Windows Update? ›

How to fix a stuck Windows 10 update
  1. Make sure the updates really are stuck.
  2. Turn it off and on again.
  3. Check the Windows Update utility.
  4. Run Microsoft's troubleshooter program.
  5. Launch Windows in Safe Mode.
  6. Go back in time with System Restore.
  7. Delete the Windows Update file cache yourself.
  8. Launch a thorough virus scan.
Mar 25, 2022

What are the three primary event logs in Windows? ›

Viewing Events Logs in Event Viewer

The major log files that will likely be used for most Windows troubleshooting are application, security, and system.

How many types of log files are there? ›

There are three types of log files: 1. Request log files that document the execution of a concurrent program running as the result of a concurrent request. Every concurrent request generates a log file.

What is the difference between log and event? ›

An event is a conceptual abstraction and a structured log is one possible representation of that abstraction. The interesting part of the conversation is where to draw the lines around that abstraction; the technical implementation part is how to represent that event.

What are the different types of logs? ›

Types of log data
  • Perimeter device logs.
  • Windows event logs.
  • Endpoint logs.
  • Application logs.
  • Proxy logs.
  • IoT logs.

Which logs should be monitored? ›

Top 10 Log Sources You Should Monitor
  • 1 – Infrastructure Devices. These are those devices that are the “information superhighway” of your infrastructure. ...
  • 2 – Security Devices. ...
  • 3 – Server Logs. ...
  • 4 – Web Servers. ...
  • 5 – Authentication Servers. ...
  • 6 – Hypervisors. ...
  • 7 – Containers. ...
  • 8 – SAN Infrastructure.
Dec 17, 2018

Are log files necessary? ›

Why is logging important? Log files (also known as machine data) are important data points for security and surveillance, providing a full history of events over time. Beyond operating systems, log files are found in applications, web browsers, hardware, and even email.

How do I clean Windows log files? ›

Open Administrative Tools, and then Computer Management. In the left frame, double-click Event Viewer, and then Windows Logs. Right-click Security and choose Clear Log.... You will have the option to save the details of the log.

Can I safely delete log files? ›

You can remove a log file if all of the following are true: the log file is not involved in an active transaction. a checkpoint has been performed after the log file was created. the log file is not the only log file in the environment.

Can I delete all log files in Windows 10? ›

In Windows, you can clear the event logs by selecting Clear all Events on the Action menu after selecting the appropriate log file.

Should I delete driver installation log files? ›

Setup Log Files: These log files are created while software is installing. If a problem occurs, the log files can help identify the problem. If you're not trying to troubleshoot a software installation, you can remove them.

Why would you need to keep copies of log files? ›

Logs provide important insight regarding the activity on a system or a network. With the help of logs, your security professionals can keep track of the activity on the systems and networks of your organization, notice unusual activity, scan vulnerabilities and enhance the security posture of your organization.

How do I find Windows software installation logs? ›

View the Windows Setup event logs
  1. Start the Event Viewer, expand the Windows Logs node, and then click System.
  2. In the Actions pane, click Open Saved Log and then locate the Setup. etl file. By default, this file is available in the %WINDIR%\Panther directory.
  3. The log file contents appear in the Event Viewer.
Jan 20, 2022

How do I get a list of installed updates? ›

To view the history list of Windows 10 updates using Command Prompt:
  1. Open Start.
  2. Search for Command Prompt and click the top result to open the app.
  3. Type the following command to view the update history and press Enter: wmic qfe list. ...
  4. Check the Windows Update history of your device.
Jan 11, 2023

Which log we can check for deployment status? ›

You can view EC2/On-Premises deployment logs on your instances in the following locations: Amazon Linux, RHEL, and Ubuntu Server: /opt/codedeploy-agent/deployment-root/deployment-logs/codedeploy-agent-deployments. log. Windows Server: C:\ProgramData\Amazon\CodeDeploy<DEPLOYMENT-GROUP-ID><DEPLOYMENT-ID>\logs\scripts.

How do I download windows system logs? ›

Answer
  1. Start Event Viewer by going to Start > search box (or press Windows key + R to open the Run dialog box) and type eventvwr .
  2. Within Event Viewer, expand Windows Logs.
  3. Click the type of logs you need to export.
  4. Click Action > Save All Events As...
  5. Ensure that the Save as type is set to .
Jan 21, 2021

Where are Windows error logs stored? ›

By default, Event Viewer log files use the . evt extension and are located in the %SystemRoot%\System32\winevt\Logs folder. Log file name and location information is stored in the registry.

How do I check Windows error logs? ›

Click Start > Control Panel > System and Security > Administrative Tools. Double-click Event Viewer. Select the type of logs that you wish to review (ex: Windows Logs)

Where are installation logs stored? ›

Windows installer logs are usually kept in the temp folder, you can get to this by going to run or an explorer bar and type the location as %temp% . x - Extra debugging information.

How do I check Windows patch update history? ›

Solution
  1. Right-click the Windows icon (Start menu). Select Settings.
  2. In Windows Settings, click Update & Security (scroll down to see this option). Select Windows Update.
  3. Select View update history.

How do you force Windows Update to check for updates? ›

To check for updates, select Start > Settings > Windows Update , then select Check for updates. If updates are available, you can choose to install them.

How do I check Windows Update progress? ›

How to check for updates on a Windows 10 PC
  1. At the bottom of the Settings menu, click "Update & Security." ...
  2. Click on "Check for updates" to see if your computer is up-to-date, or if there are any updates available. ...
  3. If there were updates available, they'll begin to download automatically.
Nov 6, 2020

How do I view code deploy logs? ›

You can view the log data created by a CodeDeploy deployment by setting up the Amazon CloudWatch Logs agent to view aggregated data in the CloudWatch console or by logging into an individual instance to review the log file. Logs are not supported for AWS Lambda or Amazon ECS deployments.

Where are code deploy logs? ›

Go to the CloudWatch console, and choose Logs. To view the CodeDeploy agent log, choose codedeploy-agent-logs. To view the deployment scripts log, choose codedeploy-deployment-logs. To view the CodeDeploy agent updater log, choose codedeploy-updater-logs.

How do you check the logs of a pod or deployment? ›

Here's how you can look at these logs.
  1. Default Logs. kubectl logs podname -n namespace. The above kubectl command shows you the logs of the pod in the specified namespace. ...
  2. Specific Container Logs. kubectl logs podname -n namespace -c container_name. ...
  3. All Containers. Kubectl logs podname -n namespace –all-containers=true.
Oct 14, 2022

What are Windows log files? ›

A log file is a computer-generated data file that contains information about usage patterns, activities, and operations within an operating system, application, server or another device.

What is stored in a system log file? ›

System Log (syslog): a record of operating system events. It includes startup messages, system changes, unexpected shutdowns, errors and warnings, and other important processes. Windows, Linux, and macOS all generate syslogs.

Videos

1. Fix Failure (5616): 15299: Verify BCDBootEx | Windows 10 ADK 2004!
(BTNHD)
2. Cbs.Log Causes High Disk Usage in Windows 10 (Solution)
(MDTechVideos)
3. Ultimate Guide to Fix Almost ANY Windows Corruption (Without Reinstalling)
(ThioJoe)
4. How to fix MDT Deployment Workbench Windows PE crash
(Danny Moran)
5. Deep Dive #2 Windows Update Logs
(LiveWindowsTraining-DougBetts)
6. (Resolved) We Couldn’t Create A New Partition Or Locate An Existing One
(Cap Trong Nam - How To)
Top Articles
Latest Posts
Article information

Author: Ms. Lucile Johns

Last Updated: 02/23/2023

Views: 6200

Rating: 4 / 5 (41 voted)

Reviews: 88% of readers found this page helpful

Author information

Name: Ms. Lucile Johns

Birthday: 1999-11-16

Address: Suite 237 56046 Walsh Coves, West Enid, VT 46557

Phone: +59115435987187

Job: Education Supervisor

Hobby: Genealogy, Stone skipping, Skydiving, Nordic skating, Couponing, Coloring, Gardening

Introduction: My name is Ms. Lucile Johns, I am a successful, friendly, friendly, homely, adventurous, handsome, delightful person who loves writing and wants to share my knowledge and understanding with you.