deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-13 22:07:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

update

Browse Source
This commit is contained in:
Greg Lindsay 2016-10-05 17:13:36 -07:00
parent 812ece27f9
commit c58e7ad0f2
1 changed files with 9 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
windows/deploy/resolve-windows-10-upgrade-errors.md
View File

@ -223,15 +223,20 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
A setupact.log or setuperr.log entry includes the following elements: A setupact.log or setuperr.log entry includes the following elements:
<OL> <OL>
<LI>The date and time. For example: 2016-09-08 09:20:05. <LI><B>The date and time</B> - 2016-09-08 09:20:05.
<LI>The log level: Info, Warning, Error, Fatal Error. <LI><B>The log level</B> - Info, Warning, Error, Fatal Error.
<LI>The logging component: CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS. <LI><B>The logging component</B> - CONX, MOUPG, PANTHR, SP, IBSLIB, MIG, DISM, CSI, CBS.
<UL> <UL>
<LI>The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors. <LI>The logging components SP (setup platform), MIG (migration engine), and CONX (compatibility information) are particularly useful for troubleshooting Windows Setup errors.
</UL> </UL>
<LI>The message. For example: Operation completed successfully. <LI><B>The message</B> - Operation completed successfully.
</OL> </OL>
An example log entry is shown below:
<PRE>
2016-09-08 09:23:50, Warning MIG Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
</PRE>
### Analyze log files ### Analyze log files
To analyze Windows Setup log files: To analyze Windows Setup log files: