Log files created when you upgrade Windows 11/10 to a newer version
When Microsoft rolls an update for Windows 11/10, the upgrade process creates tons of log files in every step. These log files are useful for analysis if at that place is any Upgrade problem. While information technology may not find information technology easy to analyze, information technology'southward a gold mine for IT admins. In this post, we will discuss the Log files that are created when you upgrade to a new version of Windows. We have besides included when or in which phase these log files are created.
Log files created when you lot upgrade Windows eleven/10
Here are some terminologies you would see in the listing below:
- Downward-Level: It is the get-go phase of the Upgrade process, and since this phase runs on the source Os, upgrade errors are not typically seen except in the log files. Information technology besides ensures that the Windows setup source and the destination drive are accessible.
- OOBE: Out of the box experience.
- Rollback: Its when the setup decides to go back to the initial phase.
- Dumps: Its an extremely useful file where all the debugging information is written when the computer stops unexpectedly because of a End mistake (besides known as a "blue screen," system crash, or issues cheque) or during a Windows Upgrade process.
Below is the listing of log files, their location, why are they created, and when you lot should use these log files. While they are meant for It admins, anyone who is interested tin do their bit of analysis.
| Log file | Phase: Location | Description | When to use |
| setupact.log | Down-Level: $Windows.~BT\Sources\Panther | Listing of gear up upwards actions to exist taken during the downlevel phase. | It contains all the down-level failures and starting point for rollback investigations. Without it, failures would be stuck forever. |
| OOBE: $Windows.~BT\Sources\Panther\ UnattendGC | It contains the unattended setup experience and contains details about deportment during the OOBE phase. | Investigating rollbacks that failed during OOBE phase and operations . Fault Code 0x4001C, 0x4001D, 0x4001E, 0x4001F. | |
| Rollback: $Windows.~BT\Sources\Rollback | It includes instructions for rollback. | Investigating generic rollbacks – 0xC1900101. | |
| Pre-initialization (prior to downlevel): Windows | Contains information nearly initializing the setup. | If the setup fails to launch. | |
| Post-upgrade (after OOBE): Windows\Panther | Instructions to follow during the installation. | The log helps to investigate post-upgrade related issues. | |
| setuperr.log | Same as setupact.log | Data about setup errors during the installation. | Review all errors encountered during the installation phase. |
| miglog.xml | Mail-upgrade (afterwards OOBE): Windows\Panther | Listing of items migrated during the installation. | Identify postal service upgrade information migration issues. |
| BlueBox.log | Down-Level: Windows\Logs\Mosetup | Information on what will be communicated between the setup.exe and Windows Update. | Use during WSUS and WU down-level failures or for 0xC1900107. |
| Supplemental rollback logs: Setupmem.dmp setupapi.dev.log Effect logs (*.evtx) | $Windows.~BT\Sources\Rollback | Additional logs collected during rollback. | Setupmem.dmp: Created when in that location is an OS problems. Setupapi: When Windows fails to install on the device – 0x30018 Consequence logs: Generic rollbacks (0xC1900101) or unexpected reboots. |
List of Log files are created when the upgrade is successful or failure
For every event, at that place is a log file generated. In fact, Log files are created even for an upgrade fails, and reckoner restarts for the 2nd time or when in that location is a 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 the estimator restarts 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 the estimator restarts for the 2nd 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\retentiveness.dmp
Log files created when an upgrade fails, and 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 post-obit log files are created when an upgrade fails, and the installation rollback is initiated:
- C:\$Windows.~BT\Sources\Rollback\setupact.log
- C:\$Windows.~BT\Sources\Rollback\setupact.err
Read more about them on Microsoft hither and hither.
We hope this post was informative enough to make you enlightened of the type of log files, memory dumps, location of those files which are not like shooting fish in a barrel to find.
Source: https://www.thewindowsclub.com/log-files-upgrade-new-version-of-windows
Posted by: rochaunpleted1961.blogspot.com
0 Response to "Log files created when you upgrade Windows 11/10 to a newer version"
Post a Comment