When Microsoft launches an update for Windows 10, the upgrade process creates tons of log files at each step. These log files are useful for analysis in case of an upgrade problem. Although the analysis is not easy, it is a gold mine for IT administrators. In this article, we will discuss the log files created when upgrading to a new version of Windows. We also indicated when or at what stage these log files are created.
Log files created during the Windows 10 upgrade
Here are some terminologies that you would see in the list below:
- Lower level: This is the first phase of the upgrade process and, as this phase is performed on the source operating system, upgrade errors are usually not detected, at least once a year. exception of log files. This also ensures that the Windows installation source and the destination drive are accessible.
- OOBE: Experience off the beaten track.
- Back back: This is when the configuration decides to go back to the initial phase.
- landfills: This is an extremely useful file in which all debug information is written when the computer unexpectedly stops due to a shutdown error (also called "screen"). blue, "system crash or bug check) or during a Windows upgrade process.
The following is a list of log files, where they are, why they are created, and when to use these log files. If they are intended for IT administrators, anyone interested can do their analysis.
| Log file | Phase: Location | The description | When to use |
| setupact.log | Lower level: $ Windows. ~ BT Sources Panther |
List of configuration actions to take during the low level phase. | It contains all failures and starting points for restoration surveys. Without that, failures would be stuck forever. |
| OOBE: $ Windows. ~ BT Sources Panther UnattendGC |
It contains the unattended installation experience and contains details about the actions during the OOBE phase. | Find failed restores during OOBE phase and operations. Error code 0x4001C, 0x4001D, 0x4001E, 0x4001F. | |
| Back back: $ Windows. ~ BT Sources Rollback |
It includes instructions for restoration. | Survey of Generic Restorations – 0xC1900101. | |
| Pre-initialization (before lower level): the Windows |
Contains information about initializing the configuration. | If the installation fails to start. | |
| After the upgrade (after OOBE): Windows Panther |
Instructions to follow during installation. | The log is used to investigate issues related to the upgrade. | |
| setuperr.log | Same as setupact.log | Data on installation errors during installation. | Check for any errors encountered during the installation phase. |
| miglog.xml | After the upgrade (after OOBE): Windows Panther |
List of items migrated during installation. | Identify post-upgrade data migration issues. |
| BlueBox.log | Lower level: Windows Logs Mosetup |
Information about what will be communicated between the setup.exe file and Windows Update. | Use when WSUS and WU low level failures or for 0xC1900107. |
| Additional catering diaries: Setupmem.dmp setupapi.dev.log Event Logs (* .evtx) |
$ Windows. ~ BT Sources Rollback | Additional logs collected during the restoration. | Setupmem.dmp: created in the presence of an operating system bug. Setupapi: When Windows Fails to Install on Device – 0x30018 Event Logs: Generic Cancels (0xC1900101) or Unexpected Restarts. |
The list of log files is created in case of failure or successful completion of the upgrade
A log file is generated for each event. In fact, log files are created even for an upgrade and the computer restarts for the second time or in case of rollback. Here is the list:
Log files created when an upgrade is successful
- C: Windows Panther Setupact.log
- C: Windows panther setuperr.log
- C: Windows inf setupapi.app.log
- C: Windows inf setupapi.dev.log
- C: Windows panther PreGatherPnPList.log
- C: Windows Panther PostApplyPnPList.log
- C: Windows panther miglog.xml
Log files created when an upgrade fails during installation before restarting the computer for the second time
- C: $ Windows. ~ BT Sources panther setupact.log
- C: $ Windows. ~ BT Sources panther miglog.xml
- C: Windows setupapi.log
- (Windows 10 🙂 C: Windows Logs MoSetup BlueBox.log
Log files created when an upgrade fails during installation after restarting the computer for the second time
- C: Windows panther setupact.log
- C: Windows panther miglog.xml
- C: Windows inf setupapi.app.log
- C: Windows inf setupapi.dev.log
- C: Windows panther PreGatherPnPList.log
- C: Windows Panther PostApplyPnPList.log
- C: Windows memory.dmp
Log files created in case of failure of an upgrade, then you restore the desktop
- C: $ Windows. ~ BT Sources panther setupact.log
- C: $ Windows. ~ BT Sources panther miglog.xml
- C: $ Windows. ~ BT sources panther setupapi setupapi.dev.log
- C: $ Windows. ~ BT sources panther setupapi setupapi.app.log
- C: Windows memory.dmp
The following log files are created when an upgrade fails and the installation restore is launched:
- C: $ Windows. ~ BT Sources Rollback setupact.log
- C: $ Windows. ~ BT Sources Rollback setupact.err
Learn more about them right here and right here.
We hope that this message has been informative enough to inform you about the type of log files, the memory dumps, the location of these files that are not easy to find.
