From 64c1dff4cee74afdae9cb58d7ea107d511155c10 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 11:12:05 -0700 Subject: [PATCH 01/30] update --- .../resolve-windows-10-upgrade-errors.md | 133 ++++++++++-------- 1 file changed, 73 insertions(+), 60 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 9c18df817e..fd561281af 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -57,7 +57,7 @@ Note: If only a result code is returned, this can be because a tool is being use Result codes can be matched to the type of error encountered. To match a result code to an error: -1. Identify the error code type, using the first hexidecimal digit: +1. Identify the error code type, either Win32 or NTSTATUS, using the first hexidecimal digit:
8 = Win32 error code (ex: 0x**8**0070070)
C = NTSTATUS value (ex: 0x**C**1900107) 2. Write down the last 4 digits of the error code (ex: 0x8007**0070** = 0070). These digits correspond to the last 16 bits of the [HRESULT](https://msdn.microsoft.com/en-us/library/cc231198.aspx) or the [NTSTATUS](https://msdn.microsoft.com/en-us/library/cc231200.aspx) structure. @@ -180,7 +180,13 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots. ### 0xC1900101 -A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the SafeOS phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as the minidump file (($Windows.~bt\Sources\Rollback\setupmem.dmp), event logs (($Windows.~bt\Sources\Rollback\*.evtx), and the device install log ($Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log). The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). To resolve a rollback due to driver conflicts, run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process. +A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the Downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:
+ +- The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp, +- Event logs: $Windows.~bt\Sources\Rollback\*.evtx +- The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log + +The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018). To resolve a rollback due to driver conflicts, run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process.

See the following general troubleshooting procedures associated with a result code of 0xC1900101: @@ -392,9 +398,74 @@ For more information, see [How to perform a clean boot in Windows](https://suppo ### 0x800xxxxx +Result codes starting with the digits 0x800 are also relatively common. These error codes indicate general operating system errors, and are not unique to the Windows upgrade process. Examples include timeouts, devices not functioning, and a process stopping unexpectedly. +

See the following general troubleshooting procedures associated with a result code of 0x800xxxxx: + + + + + + + + + + +
+ + +
Code +
+ +8000405 - 0x20007 + +
+ +

+
Cause +
+ +Here is a cause. + +
+

 + + +
Mitigation +
+ +Here is a mitigation procedure. + +
+
+ + +
Code +
+ +800704B8 - 0x3001A + +
+ +

+
Cause +
+ +Here is a cause. + +
+

 + + +
Mitigation +
+ +Here is a mitigation procedure. + +
+
@@ -494,67 +565,9 @@ Here is a mitigation procedure. - - - - - - - - -
- -
Code -
-800704B8 - 0x3001A -
- -

-
Cause -
- -Here is a cause. - -
-

 - - -
Mitigation -
- -Here is a mitigation procedure. - -
-
- - -
Code -
- -8000405 - 0x20007 - -
- -

-
Cause -
- -Here is a cause. - -
-

 - - -
Mitigation -
- -Here is a mitigation procedure. - -
-
From 8c3d96e8ba8a092e613d43737a155e85e29db505 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 11:22:55 -0700 Subject: [PATCH 02/30] update --- .../deploy/resolve-windows-10-upgrade-errors.md | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index fd561281af..ea892339b7 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -480,7 +480,8 @@ Here is a mitigation procedure.
Cause
-Here is a cause +The installation failed during the second boot phase while attempting the MIGRATE_DATA operation. +
This issue can occur due to an application or driver incompatibility.
@@ -491,7 +492,9 @@ Here is a cause Mitigation -Here is a mitigation procedure. +Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). + +

Ensure you select the option to "Download and install updates (recommended)." @@ -511,8 +514,7 @@ Here is a mitigation procedure. Cause -The installation failed during the second boot phase while attempting the MIGRATE_DATA operation. -
This issue can occur due to an application or driver incompatibility. +Need cause here. @@ -523,11 +525,7 @@ The installation failed during the second boot phase while attempting the MIGRAT Mitigation -Clean boot into Windows, and then attempt the upgrade to Windows 10.
- -For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135). - -

Ensure you select the option to "Download and install updates (recommended)." +Need mitigation here. From d199fe6e0ad00c142d152984b3e735e818270113 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 12:15:53 -0700 Subject: [PATCH 03/30] update --- .../resolve-windows-10-upgrade-errors.md | 31 ++++++++++++++++++- 1 file changed, 30 insertions(+), 1 deletion(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index ea892339b7..4aea6c8de5 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -18,6 +18,21 @@ localizationpriority: high This topic provides a brief introduction to Windows 10 installation processes and provides resolution procedures you can use to resolve common problems. +## In this topic + +The following topics and procedures are provided in this guide: + +- [The Windows 10 upgrade process](#the-windows-10-upgrade-process): An explanation of phases used during the upgrade process.
+- [Quick fixes](#quick-fixes): Steps you can take to eliminate common Windows upgrade errors.
+- [Upgrade error codes](#upgrade-error-codes): The composition of an error code is explained. + - [Result codes](#result-codes): Information about result codes. + - [Extend codes](#extend-codes): Information about extend codes. +- [Log files](#log-files): A list and description of log files useful for troubleshooting. +- [Common error codes](#common-error-codes): Causes and mitigation procedures associated with some common error codes. + - [0xC1900101](#0xC1900101): Information about the 0xC1900101 result code. + - [0x800xxxxx](#0x800xxxxx): Information about result codes that start with 0x800. +- [Other error codes](#less-common-error-codes): Some additional causes and mitigation procedures associated with various error codes. + ## The Windows 10 upgrade process The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings. When performing an operating system upgrade, Windows Setup uses the following phases: @@ -40,6 +55,20 @@ DU = Driver/device updates.
OOBE = Out of box experience.
WIM = Windows image (Microsoft) +## Quick fixes + +The following steps can resolve many common Windows upgrade problems. + +1. Update Windows so that all available recommended updates are installed. +2. Uninstall non-Microsoft antivirus software. +
- Use Windows Defender for protection during the upgrade. +
- Verify compatibility information and re-install antivirus applications after the upgrade. +3. Uninstall all nonessential software. +4. Remove nonessential external hardware. +5. Update firmware and drivers. +6. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. + + ## Upgrade error codes If the upgrade process is not successful, Windows Setup will return two codes: @@ -570,7 +599,7 @@ Here is a mitigation procedure. -## Common errors I've edited but don't know how to classify +## Other error codes From 329b6ae15e576deae84e497733436044fe694aaa Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 13:47:15 -0700 Subject: [PATCH 04/30] update --- windows/deploy/resolve-windows-10-upgrade-errors.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 4aea6c8de5..4f92ffb9f7 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -204,6 +204,9 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
+### Analyzing log files + + ## Common error codes @@ -447,7 +450,7 @@ Result codes starting with the digits 0x800 are also relatively common. These er Cause -Here is a cause. +An unspecified error occurred with a driver during the SafeOS phase. @@ -458,7 +461,7 @@ Here is a cause. Mitigation -Here is a mitigation procedure. +Analyze logs. @@ -489,7 +492,7 @@ Here is a cause. Mitigation -Here is a mitigation procedure. +Disable AV, disconnect devices, clean boot. @@ -885,9 +888,6 @@ Use the Media Creation tool and create an ISO and then start the upgrade of the -## Appendix A: Example setupact.log - - ## Related topics From 162695905d86fe93963f9d3dffbdbade074fa0dc Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 17:02:11 -0700 Subject: [PATCH 05/30] update --- .../resolve-windows-10-upgrade-errors.md | 233 ++++++++---------- 1 file changed, 99 insertions(+), 134 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 4f92ffb9f7..1ff874c41a 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -59,15 +59,36 @@ WIM = Windows image (Microsoft) The following steps can resolve many common Windows upgrade problems. -1. Update Windows so that all available recommended updates are installed. -2. Uninstall non-Microsoft antivirus software. +1. [Repair system files](#repair-system-files). +2. Update Windows so that all available recommended updates are installed. +3. Uninstall non-Microsoft antivirus software.
- Use Windows Defender for protection during the upgrade.
- Verify compatibility information and re-install antivirus applications after the upgrade. -3. Uninstall all nonessential software. -4. Remove nonessential external hardware. -5. Update firmware and drivers. -6. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. +4. Uninstall all nonessential software. +5. Remove nonessential external hardware. +6. Update firmware and drivers. +7. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. +### Repair system files + +Use the following commands to repair system files. +
It may take several minutes for the command operations to be completed. + +To repair damaged system files: + +1. Open an elevated command prompt. +2. Type the following command, and then press ENTER. + +``` +DISM.exe /Online /Cleanup-image /Restorehealth +``` + +3. Type the following command, and then press ENTER. + +``` +sfc /scannow +``` +For more information, see [Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/en-us/kb/947821). ## Upgrade error codes @@ -96,6 +117,7 @@ For example: - 0x80070070 = Win32 = 0070 = 0x00000070 = ERROR_DISK_FULL - 0xC1900107 = NTSTATUS = 0107 = 0x00000107 = STATUS_SOME_NOT_MAPPED +Some result codes are self-explanatory, whereas others are more generic and require further analysis. In the examples shown above, ERROR_DISK_FULL indicates that the hard drive is full and additional room is needed to complete Windows upgrade. The message STATUS_SOME_NOT_MAPPED is more abiguous, and means that an action is pending. In this case, the action pending is often the cleanup operation from a previous installation attempt, which can be resolved with a system reboot. ### Extend codes @@ -170,7 +192,7 @@ For example: An extend code of **0x4000D**, represents a problem during phase 4 ## Log files -Various log files are created during each phase of the upgrade process. These log files are essential for troubleshooting upgrade problems. The most useful log is **setupact.log**. These logs are located in a different folder depending on the Windows Setup phase. Recall that you can determine the phase from the extend code. +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: @@ -204,9 +226,75 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots. -### Analyzing log files +### Analyze log files +To analyze Windows Setup log files: +

    +
  1. Determine the Windows Setup error code. +
  2. Based on the extend code portion of the error code, determine the type and location of a log files to investigate. +
    • Review the [Extend codes](#extend-codes) and [Log files](#log-files) sections in this topic for more information.
    +
  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 fine the last occurrence of the code. +
  5. To find the last occurrence of the result code: +
      +
    1. Scroll to the bottom of the file and click after the last character +
    2. Click Edit +
    3. Click Find +
    4. Type the result code +
    5. Select Up under Direction +
    6. Click Find Next +
    +
  6. When you have 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 just prior to generating the result code. +
  7. Search for the following important text strings: +
      +
    • Shell application requested abort +
    • Abandoning apply due to error for object +
    +
  8. Decode other Win32 errors that appear in this section. +
  9. Search other log files for additional information related to your findings. +
+ +For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file: + +``` +2016-09-08 09:20:05, Error SP Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb] +2016-09-08 09:23:33, Error MIG COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0] +2016-09-08 09:23:50, Error SP Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0 +2016-09-08 09:23:50, Error MIG Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort +2016-09-08 09:23:50, Error [0x08097b] MIG Abandoning apply due to error for object: C:\Users\user1\Cookies +2016-09-08 09:23:51, Error Apply failed. Last error: 0x00000000 +2016-09-08 09:23:51, Error SP pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C +2016-09-08 09:23:52, Error SP Apply: Migration phase failed. Result: 44 +2016-09-08 09:23:52, Error SP Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7] +2016-09-08 09:23:52, Error SP Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7] +2016-09-08 09:23:52, Error SP Operation execution failed.[gle=0x000000b7] +2016-09-08 09:23:52, Error SP CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7] +``` + +In this example, the third line indicates there was an error 0x00000497 with the folder **C:\Users\user1\Cookies**: + +

Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0 + +The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: ERROR_UNABLE_TO_REMOVE_REPLACED, Unable to remove the file to be replaced. Therefore, it appears that Windows Setup failed because it was not able to migrate the "C:\Users\user1\Cookies" folder. Searching the setupact.log file for additional details, the following text is found: + +``` +2016-09-08 09:23:50, Warning RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7 +2016-09-08 09:23:50, Info MIG Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists. [0x000000B7] void __cdecl Mig::CUpgradeTransportStreamProxy::CreateFolder(class UnBCL::String *,int,int *,struct ILocalProgress *) +2016-09-08 09:23:50, Warning MIG Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed. Exception class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *) +2016-09-08 09:23:50, Info MIG Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution. +2016-09-08 09:23:50, Error SP Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0 +2016-09-08 09:23:50, Error MIG Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort +2016-09-08 09:23:50, Error [0x08097b] MIG Abandoning apply due to error for object: C:\Users\user1\Cookies +``` + +The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location: + +``` +2016-09-08 08:49:12, Info MIG Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No +``` + +This error can be resolved by configuring the folder to use its default location. ## Common error codes @@ -602,7 +690,7 @@ Here is a mitigation procedure. -## Other error codes +## Other result codes @@ -683,12 +771,7 @@ Download and run the media creation tool. See [Download windows 10](https://www. - - - - - + @@ -699,18 +782,10 @@ Download and run the media creation tool. See [Download windows 10](https://www.

To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN.

- - - -
display is not compatibleThe display card installed is not compatible with Windows 10.Uninstall the display adapter and start the upgrade again. When setup completes successfully, install the latest display adapter driver using Windows Update or by downloading from the computer manufacturers website. Use compatibility mode if necessary. -
0x8007002 This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403)
Error 800705B4: This operation returned because the timeout period expired.A time out issue set by the task sequence limitation to 180 mins of run time. This can also occur if the System Center client is corrupted.Review the SMSTS.log file and verify the following error is displayed:
-Command line execution failed (800705B4) TSManager 3/30/2016 10:11:29 PM 8920 (0x22D8)
-Failed to run the action: Upgrade Windows.
-

To resolve this issue, increase the default task sequence run time and change the task sequence to have the content downloaded locally prior to installation. -
-## Appendix A: Less common errors I haven't edited yet +## Other error codes @@ -776,117 +851,7 @@ Some important points to remember if you choose to use an external storage drive
-## Appendix B: Less common errors I haven't edited and don't know how to classify - - - - - - - - - - - - - - - - - - - - - - - - -
Error CodesCauseMitigation
Contact your system administrator to upgrade Windows Server or Enterprise EditionsThis issue occurs if you run the updater tool. The tool works only with the Windows 10 Home, Pro, and Education editions.To resolve this issue, use a different method to upgrade to Windows 10 version 1607. For example, download the ISO, and then run Setup from it.
When doing an upgrade to Windows Version 1607 is it supported to use a custom install.wim (sysprepped) instead of the default install.wim that comes with Windows Version 1607 UnsupportedIt is not supported to replace the install.wim with custom wim (sysprepped or not). It is supported to do some minor changes to the default install.wim such as injecting latest cumulative update or remove inbox apps.
0xC1420127The typical conversion of the error means that the specified image in the specified wim is already mounted for read/write access. When we launch the setup.exe, it checks the registry key. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images to check for any previously mounted WIM files on the system and if the image is mounted we will get this error.This error would be very rare on Upgrades of WIN10 specially when upgrading to the Anniversary 1607 Build. This issue has been fixed with the Cumulative updates released in June 2016 for Windows 10. When we perform an Upgrade, it is recommended to Perform a Windows Update first and apply all important updates on the current OS and then start the Upgrade process for Windows 10.
0x8004100EThis error code indicates that there is a problem with an Application that has an Invalid WMI NamespaceIn order to fix this problem, we need to open Application Event log and Check for Errors for various applications that could be causing this error. You can use WMIDIAG tool and make sure that the WMI is working well. The step by step instructions are available at: https://technet.microsoft.com/en-us/library/ff404265.aspx
0x80070057This error means that One or more arguments are invalidThis is a very generic error, and it could be due to any of the issues that we would have on the machine. This error may not be related to Upgrade only. It could be due to any programs; device drivers etc. There is no specific resolution for this error
0x8007007eThe error indicates one of the modules required to upgrade to Windows 10 was not found, some of these modules could be manifest files, COM Classes, DLL or any app packages that may be missing."When we start the upgrade of the OS, the Setup engine is responsible to check and confirm that all OS components / modules are running in good health, so that the upgrade succeeds. When we have any issues being reported with manifest files, COM Classes, DLL or any app packages, the setup engine would give this error. In order to fix this error, we would suggest to follow the solutions as below and then start the upgrade again. - -Solution 1: System File Checker -Follow the detailed steps as in: https://support.microsoft.com/en-us/kb/929833 - -Solution 2: Integrated CHKSUR -Run DISM Command to verify the health of the system: -1. Go to Start -2. Search for """"Command Prompt"""" -3. Right Click and select """"Run as Administrator"""" -4. On the prompt type command: Dism /Online /Cleanup-Image /CheckHealth -5. Hit Enter. -6. When you use the /CheckHealth argument, the DISM tool will report whether the image is healthy, repairable, or non-repairable. If the image is non-repairable, you should discard the image and start again. -7. If the image is repairable, you can use the /RestoreHealth argument to repair the image. Dism /Online /Cleanup-Image /RestoreHealth. -"
0x8007045dThis error indicates that we ran into an I/O device error."Please ensure that all I/O devices are working correctly. Please review the Device Manager for any errors and troubleshoot accordingly. -Refer: https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations - -Additionally, you can review the following logs to verify which I/O device is causing the problem. - ""%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"" - -If unable to review the logs, post on Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) -"
0x80070542The user executing the Setup.exe does not have all permissions required to complete the upgrade. "Please ensure the user performing the upgrade is part of Local Administrators group or is a Local Admin. - -Additionally, to troubleshoot further you may need to identify which process is preventing access to certain resources required for upgrade process. That can be identify by using Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor). -Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to use Process Monitor and then post the results to Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) -"
0x80070652 This error occurs when another program is being installed at the same time as the upgrade.Ensure that the are no other installation currently in progress. If there is, wait for the installation to complete. Restart the computer and do the upgrade to Windows 10.
0x800F0923This error code indicates that the user entered Safe Mode during the upgrade process.In order to complete the upgrade successfully, we recommend that you reboot the system in normal mode. If a roll-back occurs, re-initiate the upgrade.
0x80200056This error indicates when the upgrade attempts to use a security token for some of the operations, but the token is not currently available. You can attempt to re-login to the machine with a local administrator privileges and attempt to re-run the upgrade. Ensure that you do not logoff until the upgrade is complete.
0xC0000005The error indicates that the setup process lead to an access violation"Please ensure the user performing the upgrade is part of Local Administrators group or is a Local Admin. - -Additionally, to troubleshoot further you may need to identify which process is preventing access to certain resources required for upgrade process. That can be identify by using Process Monitor (https://technet.microsoft.com/en-us/sysinternals/processmonitor). -Use this (https://support.microsoft.com/en-us/kb/939896) to understand how to use Process Monitor and then post the results to Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc) -"
0XC0000428"This error occurs when the digital signatures for one of the Boot Critical Drivers has not been verified. In most cases, we will see an error on Bootup which will be similar to as below: -File: \Windows\system32\boot\winload.exe -Status:0xc0000428 -Info: Windows cannot verify the digital signature for this file.""In order to fix this error, we need to look for the file that is causing the issue. The file listed in the cause section may vary as well. When this error occurs, the machine / device will show a bluescreen and will not be in a useable state. At this point, we would need to perform Automatic Repair using Windows 10 installation media. The Drivers, conflicts with other programs, malware, and memory can all cause startup problems. -Automatic repair can detect and fix problems that prevent your PC from starting. Refer to the steps: - -a. Insert the installation USB media and boot Windows Technical Preview from it. -b. In the ‘Windows setup’ page select the ‘language to install’, ‘Time and currency format’ and the ‘keyboard or input method’ and click on ‘next’. -c. Click on ‘Repair your computer’ and select ‘Troubleshoot’. -d. Select ‘Automatic Repair’ and select the operating system. -e. You will then see a blue screen and an option to choose. Choose the option Troubleshoot and select advanced options. - f. You may choose Automatic Repair from Advanced boot option. - g. Follow the instructions. - -The above steps should fix the issue and get the driver signatures back as well for the corrupted drivers. If that does not help, then we may not have any other option than performing a Clean Install of Windows 10 on the machine / device. You can create a Windows 10 installation Disc and perform a clean installation on the computer. To create a please find the below link: -https://www.microsoft.com/en-us/software-download/windows10 - -Once the media is created by the tool, it will walk you through how to set up Windows 10 on your PC. During setup, you might be asked to enter a product key. - If you bought Windows 10 and are installing it for the first time, you’ll need to enter the Windows 10 product key you received in the confirmation email after your purchase. If you don’t have a product key and you’ve not previously upgraded to Windows 10, select I need to buy a Windows 10 product key. -"
0xc1900106This indicate that upgrade process was forcefully terminated either by Rebooting or forcefully canceling the setup. "We recommended that when the Windows 10 Upgrade is initiated, one should not terminate the process at any time until the Setup completes. Before initiating the setup, we should make sure: -1. The device (Laptop or Surface) it should be connected to power source and adequately charged. -2. The user is not cancelling the setup on the Black Screen, when the setup.exe is installing devices and configuring user settings. -PS: It takes time on the device configuration and migration depending upon the Speed of the CPU and the amount of RAM on the system. -"
0xC1900208 -1047526904This error occurs when the computer does not pass the compatibility check for upgrading to Windows 10."This error comes when there is software/driver which is not yet certified to be compatible with windows 10. Hence you might want to re-run the compatibility check before initiating the Upgrade. -Refer AskCore Blog: Using the Windows 10 Compatibility Reports to understand upgrade issues (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/) - -Once you have found the in-compatible software/drivers: -1. Uninstall incompatible software or hardware or driver, -2. Now re-run the compatibility check just to verify that there no more in-compatible software/driver on the machine. -3. If it comes clean, initiate the upgrade. -4. Else, repeat the steps until the compatibility check is clean. -"
Couldn't Update System Reserved PartitionThis error occurs because the System Reserved Partition (SRP) is full.Free up 15MB of space on the SRP using the appropriate method described in Knowledge Base article 3086249, and then try the upgrade again.
MismatchedLanguage, found HardBlockThis error code indicates that the Current Language installed on the machine is not Supported for the Upgrade to start.We need to have English as the base Language in order to upgrade to Windows 10. There is a Hard block for the Upgrade to be performed and the compatibility scan data is saved to %Systemroot%\$WINDOWS.~BT\Sources\Panther\CompatData_YYYY.txt
Setup couldn’t start properly. Please reboot your PC and try running Windows 10 Setup againThis error occurs if the upgrade files are corrupt due to a failed Windows 10 download."The Setup.exe initializes the temporary folders to copy the data and prepare the machine for upgrade. The specific folders that are initialized are: - -1. C:\$Windows ~BT (Hidden Folder) -2. C:\$Windows~WS (Hidden Folder) - -In order to delete the above folders we would suggest that we use the Disk Clean Up tool and delete the folders and then try to run the upgrade again. -https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space -"
Unable to resurrect NewSystem object. hr=0x80070002"This error occurs when the setup.exe is unable to create the newsystem data file when the upgrade starts. If we look at the C:\$Windows.~BT\Sources\Panther\diagerr.xml, we should see something like: -CSetupPlatform::ResurrectNewSystem: -Failure: Win32Exception: \\?\C:\$Windows.~BT\Sources\NewSystem.dat: -The system cannot find the file specified. [0x00000002] __cdecl -UnBCL::FileStream::FileStream(const class UnBCL::String *,enum -UnBCL::FileMode,enum UnBCL::FileAccess,enum UnBCL::FileShare,unsigned long)""The NewSystem.dat is an operational file that is created at the beginning of the upgrade process and used at various points in the setup phase like driver migrations; disk space detections; Platforms detections and creating a base image of the new OS that is extracted from the INSTALL.WIM, which is the source file for the upgrade. -There are couple of solutions for this issue: -Solution 1: Disk Space -Check and Make sure that we have good amount of free disk space on the OS partition. Disk space requirements: -a. For 32-bit: Greater than 16gb -b. For 64-Bit: Greater than 20gb - -Solution 2: Upgrade Path -We need to make sure that we are upgrading the existing OS, to the New Version as per the guidelines described in https://technet.microsoft.com/en-us/itpro/windows/deploy/windows-10-upgrade-paths?f=255&MSPPError=-2147217396 - -Solution: Media Creation Tool -Use the Media Creation tool and create an ISO and then start the upgrade of the OS. The tool can be downloaded from: http://go.microsoft.com/fwlink/?LinkId=691209 -"
## Related topics From 29445b1d67607bc8eef41561de39a34ab69a810b Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 17:33:55 -0700 Subject: [PATCH 06/30] update --- .../resolve-windows-10-upgrade-errors.md | 71 ++++++++----------- 1 file changed, 30 insertions(+), 41 deletions(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 1ff874c41a..80aab4d2de 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -28,6 +28,7 @@ The following topics and procedures are provided in this guide: - [Result codes](#result-codes): Information about result codes. - [Extend codes](#extend-codes): Information about extend codes. - [Log files](#log-files): A list and description of log files useful for troubleshooting. + - [Analyzing log files](#analyzing-log-files): General procedures for log file analysis with an example. - [Common error codes](#common-error-codes): Causes and mitigation procedures associated with some common error codes. - [0xC1900101](#0xC1900101): Information about the 0xC1900101 result code. - [0x800xxxxx](#0x800xxxxx): Information about result codes that start with 0x800. @@ -59,7 +60,13 @@ WIM = Windows image (Microsoft) The following steps can resolve many common Windows upgrade problems. -1. [Repair system files](#repair-system-files). +1. Attept to repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed. + +``` +DISM.exe /Online /Cleanup-image /Restorehealth +sfc /scannow +``` + 2. Update Windows so that all available recommended updates are installed. 3. Uninstall non-Microsoft antivirus software.
- Use Windows Defender for protection during the upgrade. @@ -69,27 +76,6 @@ The following steps can resolve many common Windows upgrade problems. 6. Update firmware and drivers. 7. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. -### Repair system files - -Use the following commands to repair system files. -
It may take several minutes for the command operations to be completed. - -To repair damaged system files: - -1. Open an elevated command prompt. -2. Type the following command, and then press ENTER. - -``` -DISM.exe /Online /Cleanup-image /Restorehealth -``` - -3. Type the following command, and then press ENTER. - -``` -sfc /scannow -``` -For more information, see [Fix Windows Update errors by using the DISM or System Update Readiness tool](https://support.microsoft.com/en-us/kb/947821). - ## Upgrade error codes If the upgrade process is not successful, Windows Setup will return two codes: @@ -226,24 +212,23 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots. -### Analyze log files +### Analyzing log files To analyze Windows Setup log files:

  1. Determine the Windows Setup error code. -
  2. Based on the extend code portion of the error code, determine the type and location of a log files to investigate. -
    • Review the [Extend codes](#extend-codes) and [Log files](#log-files) sections in this topic for more information.
    +
  3. Based on the [extend code](#extend-codes) portion of the error code, determine the type and location of a [log files](#log-files) to investigate.
  4. Open the log file in a text editor, such as notepad. -
  5. Using the result code portion of the Windows Setup error code, search for the result code in the file and fine the last occurrence of the code. +
  6. 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.
  7. To find the last occurrence of the result code:
      -
    1. Scroll to the bottom of the file and click after the last character -
    2. Click Edit -
    3. Click Find -
    4. Type the result code -
    5. Select Up under Direction -
    6. Click Find Next +
    7. Scroll to the bottom of the file and click after the last character. +
    8. Click **Edit**. +
    9. Click **Find**. +
    10. Type the result code. +
    11. Under **Direction** select **Up**. +
    12. Click **Find Next**.
  8. When you have 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 just prior to generating the result code.
  9. Search for the following important text strings: @@ -257,7 +242,7 @@ To analyze Windows Setup log files: For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file: -``` +
     2016-09-08 09:20:05, Error                 SP     Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
 2016-09-08 09:23:33, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -270,15 +255,19 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 2016-09-08 09:23:52, Error                 SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
 2016-09-08 09:23:52, Error                 SP     Operation execution failed.[gle=0x000000b7]
 2016-09-08 09:23:52, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-```
+
    -In this example, the third line indicates there was an error 0x00000497 with the folder **C:\Users\user1\Cookies**: +In this example, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**: -

    Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0 +

    +2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+
    -The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: ERROR_UNABLE_TO_REMOVE_REPLACED, Unable to remove the file to be replaced. Therefore, it appears that Windows Setup failed because it was not able to migrate the "C:\Users\user1\Cookies" folder. Searching the setupact.log file for additional details, the following text is found: +The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: +
    • ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
    +Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder. Searching the setupact.log file for additional details, the following text is found: -``` +
     2016-09-08 09:23:50, Warning                      RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 2016-09-08 09:23:50, Info                  MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists. [0x000000B7] void __cdecl Mig::CUpgradeTransportStreamProxy::CreateFolder(class UnBCL::String *,int,int *,struct ILocalProgress *)
 2016-09-08 09:23:50, Warning               MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed. Exception class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *)
@@ -286,13 +275,13 @@ The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/li
 2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
 2016-09-08 09:23:50, Error                 MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
 2016-09-08 09:23:50, Error      [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-```
+
    The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location: -``` +
     2016-09-08 08:49:12, Info                  MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
-```
+
    This error can be resolved by configuring the folder to use its default location. From 17a5f3fd6188f8cc33c6c5ba8ba89432b5c10e9e Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 17:52:35 -0700 Subject: [PATCH 07/30] update --- windows/deploy/resolve-windows-10-upgrade-errors.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index 80aab4d2de..a8b840be82 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -242,6 +242,8 @@ To analyze Windows Setup log files: For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file: +
    + 
     2016-09-08 09:20:05, Error                 SP     Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
 2016-09-08 09:23:33, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
@@ -257,16 +259,21 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 2016-09-08 09:23:52, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
    +
    + In this example, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**: +
     2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
    +
    The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to:
    • ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
    Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder. Searching the setupact.log file for additional details, the following text is found: +
     2016-09-08 09:23:50, Warning                      RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 2016-09-08 09:23:50, Info                  MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists. [0x000000B7] void __cdecl Mig::CUpgradeTransportStreamProxy::CreateFolder(class UnBCL::String *,int,int *,struct ILocalProgress *)
@@ -276,12 +283,15 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 2016-09-08 09:23:50, Error                 MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
 2016-09-08 09:23:50, Error      [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
    +
    The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location: +
     2016-09-08 08:49:12, Info                  MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
    +
    This error can be resolved by configuring the folder to use its default location. From e18f350782eefbe791db381b7b9e125ca78808a2 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Tue, 4 Oct 2016 17:56:10 -0700 Subject: [PATCH 08/30] update --- windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md index a8b840be82..edbc1dac27 100644 --- a/windows/deploy/resolve-windows-10-upgrade-errors.md +++ b/windows/deploy/resolve-windows-10-upgrade-errors.md @@ -242,7 +242,7 @@ To analyze Windows Setup log files: For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file: -
    +
     2016-09-08 09:20:05, Error                 SP     Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]

From 4738df675856143a0b98b52b3661ddf2d88948d8 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Tue, 4 Oct 2016 18:07:21 -0700
Subject: [PATCH 09/30] update

---
 .../resolve-windows-10-upgrade-errors.md      | 28 +++++++------------
 1 file changed, 10 insertions(+), 18 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index edbc1dac27..cfdfbe1db9 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -242,9 +242,9 @@ To analyze Windows Setup log files:
 
 For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
 
-
    
 
-
    +
+```text
 2016-09-08 09:20:05, Error                 SP     Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
 2016-09-08 09:23:33, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -257,24 +257,19 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 2016-09-08 09:23:52, Error                 SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
 2016-09-08 09:23:52, Error                 SP     Operation execution failed.[gle=0x000000b7]
 2016-09-08 09:23:52, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
+```
 
-
    
+In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
-In this example, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
-
-
    
-
    +```text
 2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-
    
-
    
+```
 
 The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: 
 
    • ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
     
 Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder.  Searching the setupact.log file for additional details, the following text is found:
 
-
    
-
    +```text
 2016-09-08 09:23:50, Warning                      RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 2016-09-08 09:23:50, Info                  MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists. [0x000000B7] void __cdecl Mig::CUpgradeTransportStreamProxy::CreateFolder(class UnBCL::String *,int,int *,struct ILocalProgress *)
 2016-09-08 09:23:50, Warning               MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed. Exception class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *)
@@ -282,16 +277,13 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
 2016-09-08 09:23:50, Error                 MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
 2016-09-08 09:23:50, Error      [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-
    
-
    
+```
 
 The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
 
-
    
-
    +```text
 2016-09-08 08:49:12, Info                  MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
-
    
-
    
+```
 
 This error can be resolved by configuring the folder to use its default location.
 

From 8bf35d6d087ba1a218e70c3a9febd34ec5f30795 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 10:30:57 -0700
Subject: [PATCH 10/30] update

---
 .../resolve-windows-10-upgrade-errors.md      | 68 ++++++++++---------
 1 file changed, 36 insertions(+), 32 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index cfdfbe1db9..be7fd916d6 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -32,7 +32,7 @@ The following topics and procedures are provided in this guide:
 - [Common error codes](#common-error-codes): Causes and mitigation procedures associated with some common error codes.
     - [0xC1900101](#0xC1900101): Information about the 0xC1900101 result code.
     - [0x800xxxxx](#0x800xxxxx): Information about result codes that start with 0x800.
-- [Other error codes](#less-common-error-codes): Some additional causes and mitigation procedures associated with various error codes.
+- [Other error codes](#less-common-error-codes): Some causes and mitigation procedures are provided for other error codes.
 
 ## The Windows 10 upgrade process
 
@@ -60,21 +60,25 @@ WIM = Windows image (Microsoft)
 
 The following steps can resolve many common Windows upgrade problems.
 
-1. Attept to repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed. 
+
      
+
    1. Attept to repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed.
      2. 
 
 ```
 DISM.exe /Online /Cleanup-image /Restorehealth
 sfc /scannow
 ```
 
-2. Update Windows so that all available recommended updates are installed.
-3. Uninstall non-Microsoft antivirus software. 
-
          - Use Windows Defender for protection during the upgrade. 
-
          - Verify compatibility information and re-install antivirus applications after the upgrade. 
-4. Uninstall all nonessential software. 
-5. Remove nonessential external hardware. 
-6. Update firmware and drivers.
-7. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
+
    2. Update Windows so that all available recommended updates are installed.
      3. 
+
    3. Uninstall non-Microsoft antivirus software.
+  
         
+  
      • Use Windows Defender for protection during the upgrade. 
+  
      • Verify compatibility information and re-install antivirus applications after the upgrade.
        • 
+  
      
+
    4. Uninstall all nonessential software.
      5. 
+
    5. Remove nonessential external hardware.
      6.  
+
    6. Update firmware and drivers.
      7. 
+
    7. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
      8. 
+
    
 
 ## Upgrade error codes
 
@@ -242,27 +246,27 @@ To analyze Windows Setup log files:
 
 For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
 
-
+>Some lines in the text below are shortened for readability. The date and time at the start of each entry, which is formatted as: 2016-09-08 09:20:05, is replaced with [##].
 
 ```text
-2016-09-08 09:20:05, Error                 SP     Error READ, 0x00000002 while gathering/applying object: apply-success, Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll,{43CCF250-2A74-48c6-9620-FC312EC475D6},Apartment. Will return 2[gle=0x000000cb]
-2016-09-08 09:23:33, Error                 MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-2016-09-08 09:23:50, Error                 MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-2016-09-08 09:23:50, Error      [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-2016-09-08 09:23:51, Error                        Apply failed. Last error: 0x00000000
-2016-09-08 09:23:51, Error                 SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-2016-09-08 09:23:52, Error                 SP     Apply: Migration phase failed. Result: 44
-2016-09-08 09:23:52, Error                 SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-2016-09-08 09:23:52, Error                 SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-2016-09-08 09:23:52, Error                 SP     Operation execution failed.[gle=0x000000b7]
-2016-09-08 09:23:52, Error                 SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+[##], Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+[##], Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+[##], Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+[##], Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+[##], Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+[##], Error                   Apply failed. Last error: 0x00000000
+[##], Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+[##], Error            SP     Apply: Migration phase failed. Result: 44
+[##], Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+[##], Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+[##], Error            SP     Operation execution failed.[gle=0x000000b7]
+[##], Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 ```
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
 ```text
-2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+2016-09-08 09:23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
 ```
 
 The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: 
@@ -270,19 +274,19 @@ In the previous text, the third line indicates there was an error **0x00000497**
 Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder.  Searching the setupact.log file for additional details, the following text is found:
 
 ```text
-2016-09-08 09:23:50, Warning                      RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
-2016-09-08 09:23:50, Info                  MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists. [0x000000B7] void __cdecl Mig::CUpgradeTransportStreamProxy::CreateFolder(class UnBCL::String *,int,int *,struct ILocalProgress *)
-2016-09-08 09:23:50, Warning               MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed. Exception class Mig::TargetExistsException: (no exception message provided) void __cdecl Mig::CFileDataStore::Create(class Mig::CDataUnit *)
-2016-09-08 09:23:50, Info                  MIG    Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution.
-2016-09-08 09:23:50, Error                 SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
-2016-09-08 09:23:50, Error                 MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-2016-09-08 09:23:50, Error      [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+[##], Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
+[##], Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
+[##], Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
+[##], Info             MIG    Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution.
+[##], Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
+[##], Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+[##], Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
 ```
 
 The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
 
 ```text
-2016-09-08 08:49:12, Info                  MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
+[##], Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
 ```
 
 This error can be resolved by configuring the folder to use its default location.

From cec666e049bae63bc5a8ad3fdca4c2fe0e89b081 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 10:43:52 -0700
Subject: [PATCH 11/30] update

---
 .../resolve-windows-10-upgrade-errors.md      | 52 +++++++++++--------
 1 file changed, 29 insertions(+), 23 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index be7fd916d6..98546dbe98 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -246,47 +246,53 @@ To analyze Windows Setup log files:
 
 For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
 
->Some lines in the text below are shortened for readability. The date and time at the start of each entry, which is formatted as: 2016-09-08 09:20:05, is replaced with [##].
+>Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line, formatted as: 2016-09-08 09:20:05, is shortened to include only the minutes and seconds, i.e.: 20:05.
+
+
    setuperr.log content:
 
 ```text
-[##], Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-[##], Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-[##], Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-[##], Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-[##], Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-[##], Error                   Apply failed. Last error: 0x00000000
-[##], Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-[##], Error            SP     Apply: Migration phase failed. Result: 44
-[##], Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-[##], Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-[##], Error            SP     Operation execution failed.[gle=0x000000b7]
-[##], Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 ```
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
 ```text
-2016-09-08 09:23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
 ```
 
 The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: 
-
    • ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
     
+
+
    ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
+
 Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder.  Searching the setupact.log file for additional details, the following text is found:
 
+
    setupact.log content:
+
 ```text
-[##], Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
-[##], Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
-[##], Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
-[##], Info             MIG    Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution.
-[##], Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
-[##], Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-[##], Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
+23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
+23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
+23:50, Info             MIG    Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution.
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
 ```
 
 The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
 
 ```text
-[##], Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
+49:12, Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
 ```
 
 This error can be resolved by configuring the folder to use its default location.

From 44a3c0b22a37d4436822bd911515f23d91b94d6d Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 10:50:46 -0700
Subject: [PATCH 12/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 98546dbe98..5a5f73863e 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -250,7 +250,9 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-```text
+
+
+
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -263,7 +265,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
 23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-```
+
    
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 

From d8e8fbb1e22e3956c6359523ed1e3bc65701a4bd Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 11:10:12 -0700
Subject: [PATCH 13/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 5a5f73863e..cd3d4151ea 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -250,9 +250,9 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
+
    
 
-
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -267,6 +267,8 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 
    
 
+
    
+
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
 ```text

From 961e92f932224e12ec04e3f35c2ba2b4515a5e27 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 11:15:07 -0700
Subject: [PATCH 14/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index cd3d4151ea..4ecca4a737 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -250,7 +250,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    
+
    
 
 
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 

From 9939c0314f5a2c9f618a709a6d9dbc77400fbd2b Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 11:42:43 -0700
Subject: [PATCH 15/30] update

---
 .../resolve-windows-10-upgrade-errors.md       | 18 ++++++++++++++++--
 1 file changed, 16 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 4ecca4a737..2af9bffdcd 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -216,6 +216,20 @@ Event logs: Generic rollbacks (0xC1900101) or unexpected reboots.
 
 
 
+### Log entry structure
+
+A setupact.log or setuperr.log entry includes the following elements:
+
+
      
+
    1. The date and time. For example: 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) and MIG (migration engine) are particularly useful for troubleshooting Windows Setup errors.
+
      
+
    4. The message. For example: Operation completed successfully.
+
    
+
 ### Analyzing log files
 
 To analyze Windows Setup log files:
@@ -246,11 +260,11 @@ To analyze Windows Setup log files:
 
 For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
 
->Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line, formatted as: 2016-09-08 09:20:05, is shortened to include only the minutes and seconds, i.e.: 20:05.
+>Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line, formatted as: 2016-09-08 09:20:05, is shortened to minutes and seconds.
 
 
    setuperr.log content:
 
-
    
+
    
 
 
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 

From cd1cbd69cc647022a9539d63be6913f9479c391b Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 11:59:28 -0700
Subject: [PATCH 16/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 2af9bffdcd..5aa072a735 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -266,7 +266,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0

From f253da610e44f630c96af19c2557b5162e071b78 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:09:37 -0700
Subject: [PATCH 17/30] update

---
 .../deploy/resolve-windows-10-upgrade-errors.md   | 15 ++++++---------
 1 file changed, 6 insertions(+), 9 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 5aa072a735..1f3c8186de 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -264,8 +264,6 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    
-
 
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
@@ -281,13 +279,12 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 
    
 
-
    
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
-```text
+
     23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-```
+
    
 
 The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: 
 
@@ -297,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-```text
+
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
@@ -305,13 +302,13 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
 23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
 23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-```
+
    
 
 The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
 
-```text
+
     49:12, Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
-```
+
    
 
 This error can be resolved by configuring the folder to use its default location.
 

From 4b33daa3a5a6531b1a657bd984e65957894112d2 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:18:55 -0700
Subject: [PATCH 18/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 1f3c8186de..52802d75cc 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 0e438798b55130a59bd44591bdf4e358f87f665b Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:32:37 -0700
Subject: [PATCH 19/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 52802d75cc..ee4c047a4a 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 61e6065d15affad8f6dee1c977d5ffd635de293a Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:42:08 -0700
Subject: [PATCH 20/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index ee4c047a4a..5e57e8a23b 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -260,7 +260,7 @@ To analyze Windows Setup log files:
 
 For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
 
->Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line, formatted as: 2016-09-08 09:20:05, is shortened to minutes and seconds.
+>Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line (ex: 2016-09-08 09:20:05) is shortened to minutes and seconds.
 
 
    setuperr.log content:
 
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 59c6d9d96bd528944c4404491fb416240c8e4a4f Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:57:03 -0700
Subject: [PATCH 21/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 5e57e8a23b..caf07dd4d1 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -264,7 +264,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 95b7579c403ea0082aa7111a7d27b01ed8db8353 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 12:58:54 -0700
Subject: [PATCH 22/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index caf07dd4d1..3c2d044570 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -282,7 +282,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
-
    +
     23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
 
    
 

From 4c346245fe8ec8d03e385f402db5d3af14c12683 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 13:09:56 -0700
Subject: [PATCH 23/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 3c2d044570..7e201124cb 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -264,7 +264,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -282,7 +282,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
-
    +
     23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
 
    
 
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 83e85e4de006dd71a0c43d5de6afb452b526d221 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 13:18:58 -0700
Subject: [PATCH 24/30] update

---
 windows/deploy/test-pre.md | 104 +++++++++++++++++++++++++++++++++++++
 1 file changed, 104 insertions(+)
 create mode 100644 windows/deploy/test-pre.md

diff --git a/windows/deploy/test-pre.md b/windows/deploy/test-pre.md
new file mode 100644
index 0000000000..465412cb67
--- /dev/null
+++ b/windows/deploy/test-pre.md
@@ -0,0 +1,104 @@
+---
+title: Test table
+description: Test table
+ms.assetid: DFEFE22C-4FEF-4FD9-BFC4-9B419C339502
+keywords: deploy, error, troubleshoot, windows, 10
+ms.prod: w10
+ms.mktglfcycl: deploy
+ms.sitesec: library
+ms.pagetype: deploy
+author: greg-lindsay
+localizationpriority: high
+---
+
+# Test pre tag
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
\ No newline at end of file

From 2242238f93be939b916104bb5b808e6ce7c3f37f Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 13:29:46 -0700
Subject: [PATCH 25/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index 7e201124cb..f7f2e12083 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -264,7 +264,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.

From 21450d60f6bd3f14db9f5c9e0851e9e188bd7c87 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 13:51:01 -0700
Subject: [PATCH 26/30] update

---
 windows/deploy/test-pre.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/deploy/test-pre.md b/windows/deploy/test-pre.md
index 465412cb67..ee731ec4a9 100644
--- a/windows/deploy/test-pre.md
+++ b/windows/deploy/test-pre.md
@@ -1,5 +1,5 @@
 ---
-title: Test table
+title: Test pre tag
 description: Test table
 ms.assetid: DFEFE22C-4FEF-4FD9-BFC4-9B419C339502
 keywords: deploy, error, troubleshoot, windows, 10
@@ -88,7 +88,7 @@ localizationpriority: high
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 
    
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0

From 8730ad3149b723125c3431a8aa7aa06c88f7986d Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 13:53:20 -0700
Subject: [PATCH 27/30] update

---
 windows/deploy/test-pre.md | 15 +++++++++++++++
 1 file changed, 15 insertions(+)

diff --git a/windows/deploy/test-pre.md b/windows/deploy/test-pre.md
index ee731ec4a9..91bcd0c905 100644
--- a/windows/deploy/test-pre.md
+++ b/windows/deploy/test-pre.md
@@ -101,4 +101,19 @@ localizationpriority: high
 23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
 23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
 
    
\ No newline at end of file

From 5630ab749bcda5219f6f6f39a60f8510837bcba1 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 14:01:24 -0700
Subject: [PATCH 28/30] update

---
 windows/deploy/test-pre.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/windows/deploy/test-pre.md b/windows/deploy/test-pre.md
index 91bcd0c905..7cc861e9c7 100644
--- a/windows/deploy/test-pre.md
+++ b/windows/deploy/test-pre.md
@@ -116,4 +116,21 @@ localizationpriority: high
 23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
 23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
 23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
    
+
+
    +
+20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
+23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
+23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
+23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
+23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
+23:51, Error                   Apply failed. Last error: 0x00000000
+23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
+23:52, Error            SP     Apply: Migration phase failed. Result: 44
+23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
+23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
+23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
+
 
    
\ No newline at end of file

From e9503a89fbe4de52dc5a228872c6e43790b38cc9 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 14:43:25 -0700
Subject: [PATCH 29/30] update

---
 windows/deploy/resolve-windows-10-upgrade-errors.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
index f7f2e12083..2d522d6af7 100644
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ b/windows/deploy/resolve-windows-10-upgrade-errors.md
@@ -264,7 +264,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 
    setuperr.log content:
 
-
    +
     20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
 23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
 23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
@@ -282,7 +282,7 @@ For example, assume that searching for the result code "8007042B" reveals the fo
 
 In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
 
-
    +
     23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
 
    
 
@@ -294,7 +294,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 
    setupact.log content:
 
-
    +
     23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
 23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
 23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
@@ -306,7 +306,7 @@ Therefore, Windows Setup failed because it was not able to migrate the **C:\User
 
 The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
 
-
    +
     49:12, Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
 
    
 

From fc4ee9c656d2e5ab806b78358872b16f07d0e861 Mon Sep 17 00:00:00 2001
From: Greg Lindsay 
Date: Wed, 5 Oct 2016 14:49:08 -0700
Subject: [PATCH 30/30] update

---
 .../resolve-windows-10-upgrade-errors.md      | 877 ------------------
 windows/deploy/test-pre.md                    | 136 ---
 2 files changed, 1013 deletions(-)
 delete mode 100644 windows/deploy/resolve-windows-10-upgrade-errors.md
 delete mode 100644 windows/deploy/test-pre.md

diff --git a/windows/deploy/resolve-windows-10-upgrade-errors.md b/windows/deploy/resolve-windows-10-upgrade-errors.md
deleted file mode 100644
index 2d522d6af7..0000000000
--- a/windows/deploy/resolve-windows-10-upgrade-errors.md
+++ /dev/null
@@ -1,877 +0,0 @@
----
-title: Resolve common Windows 10 upgrade errors
-description: Resolve common Windows 10 upgrade errors
-ms.assetid: DFEFE22C-4FEF-4FD9-BFC4-9B419C339502
-keywords: deploy, error, troubleshoot, windows, 10
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: deploy
-author: greg-lindsay
-localizationpriority: high
----
-
-# Resolve common Windows 10 upgrade errors
-
-**Applies to**
--   Windows 10
-
-This topic provides a brief introduction to Windows 10 installation processes and provides resolution procedures you can use to resolve common problems.
-
-## In this topic
-
-The following topics and procedures are provided in this guide:
-
-- [The Windows 10 upgrade process](#the-windows-10-upgrade-process): An explanation of phases used during the upgrade process.
    
-- [Quick fixes](#quick-fixes): Steps you can take to eliminate common Windows upgrade errors.
    
-- [Upgrade error codes](#upgrade-error-codes): The composition of an error code is explained.
-    - [Result codes](#result-codes): Information about result codes.
-    - [Extend codes](#extend-codes): Information about extend codes.
-- [Log files](#log-files): A list and description of log files useful for troubleshooting.
-    - [Analyzing log files](#analyzing-log-files): General procedures for log file analysis with an example.
-- [Common error codes](#common-error-codes): Causes and mitigation procedures associated with some common error codes.
-    - [0xC1900101](#0xC1900101): Information about the 0xC1900101 result code.
-    - [0x800xxxxx](#0x800xxxxx): Information about result codes that start with 0x800.
-- [Other error codes](#less-common-error-codes): Some causes and mitigation procedures are provided for other error codes.
-
-## The Windows 10 upgrade process
-
-The Windows Setup application is used to upgrade a computer to Windows 10, or to perform a clean installation. Windows Setup starts and restarts the computer, gathers information, copies files, and creates or adjusts configuration settings. When performing an operating system upgrade, Windows Setup uses the following phases:
-
-1. **Downlevel phase**: The downlevel phase is run within the previous operating system. Installation components are gathered.
-2. **Safe OS phase**: A recovery partition is configured and updates are installed. An OS rollback is prepared if needed.
-        - Example error codes: 0x2000C, 0x20017
-3. **First boot phase**: Initial settings are applied.
-        - Example error codes: 0x30018, 0x3000D
-4. **Second boot phase**: Final settings are applied. This is also called the **OOBE boot phase**.
-        - Example error: 0x4000D, 0x40017
-5. **Uninstall phase**: This phase occurs if upgrade is unsuccessful.
-        - Example error: 0x50011, 0x50012
-
-**Figure 1**: Phases of a successful Windows 10 upgrade (uninstall is not shown):
-
-![Upgrade process](images/upgrade-process.png)
-
-DU = Driver/device updates.
    
-OOBE = Out of box experience.
    
-WIM = Windows image (Microsoft)
-
-## Quick fixes
-
-The following steps can resolve many common Windows upgrade problems.
-
-
      
-
    1. Attept to repair system files by typing the following commands at an elevated command prompt. It may take several minutes for the command operations to be completed.
      2. 
-
-```
-DISM.exe /Online /Cleanup-image /Restorehealth
-sfc /scannow
-```
-
-
    2. Update Windows so that all available recommended updates are installed.
      3. 
-
    3. Uninstall non-Microsoft antivirus software.
-  
         
-  
      • Use Windows Defender for protection during the upgrade. 
-  
      • Verify compatibility information and re-install antivirus applications after the upgrade.
        • 
-  
      
-
    4. Uninstall all nonessential software.
      5. 
-
    5. Remove nonessential external hardware.
      6.  
-
    6. Update firmware and drivers.
      7. 
-
    7. Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
      8. 
-
    
-
-## Upgrade error codes
-
-If the upgrade process is not successful, Windows Setup will return two codes:
-
-1. **A result code**: The result code corresponds to a specific Win32 error.
-2. **An extend code**: The extend code contains information about both the *phase* in which an error occurred, and the *operation* that was being performed when the error occurred.  
-
->For example, a result code of **0xC1900101** with an extend code of **0x4000D** will be returned as: **0xC1900101 - 0x4000D**.
-
-Note: If only a result code is returned, this can be because a tool is being used that was not able to capture the extend code. For example, if you are using the [Windows 10 Upgrade Assistant](https://support.microsoft.com/en-us/kb/3159635) then only a result code might be returned.
-
-### Result codes
-
->A result code of **0xC1900101** is generic and indicates that a rollback occurred. In most cases, the cause is a driver compatibility issue. 
    To troubleshoot a failed upgrade that has returned a result code of 0xC1900101, analyze the extend code to determine the Windows Setup phase, and see the [Common error codes](#common-error-codes) section later in this topic.
-
-Result codes can be matched to the type of error encountered. To match a result code to an error:
-
-1. Identify the error code type, either Win32 or NTSTATUS, using the first hexidecimal digit:
-        
    8 = Win32 error code (ex: 0x**8**0070070)
-        
    C = NTSTATUS value (ex: 0x**C**1900107)
-2. Write down the last 4 digits of the error code (ex: 0x8007**0070** = 0070). These digits correspond to the last 16 bits of the [HRESULT](https://msdn.microsoft.com/en-us/library/cc231198.aspx) or the [NTSTATUS](https://msdn.microsoft.com/en-us/library/cc231200.aspx) structure.
-3. Based on the type of error code determined in the first step, match the 4 digits derived from the second step to either a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx), or an [NTSTATUS value](https://msdn.microsoft.com/en-us/library/cc704588.aspx). 
-
-For example:
-- 0x80070070 = Win32 = 0070 = 0x00000070 = ERROR_DISK_FULL
-- 0xC1900107 = NTSTATUS = 0107 = 0x00000107 = STATUS_SOME_NOT_MAPPED
-
-Some result codes are self-explanatory, whereas others are more generic and require further analysis. In the examples shown above, ERROR_DISK_FULL indicates that the hard drive is full and additional room is needed to complete Windows upgrade. The message STATUS_SOME_NOT_MAPPED is more abiguous, and means that an action is pending. In this case, the action pending is often the cleanup operation from a previous installation attempt, which can be resolved with a system reboot. 
-
-### Extend codes
-
-Extend codes can be matched to the phase and operation when an error occurred. To match an extend code to the phase and operation:
-
-1. Use the first digit to identify the phase (ex: 0x4000D  = 4).
-2. Use the last two digits to identify the operation (ex: 0x4000D  = 0D).
-3. Match the phase and operation to values in the tables provided below.
-
-The following tables provide the corresponding phase and operation for values of an extend code:
-
-
-
-
    Extend code: phase
    HexPhase
-
    0SP_EXECUTION_UNKNOWN
-
    1SP_EXECUTION_DOWNLEVEL
-
    2SP_EXECUTION_SAFE_OS
-
    3SP_EXECUTION_FIRST_BOOT
-
    4SP_EXECUTION_OOBE_BOOT
-
    5SP_EXECUTION_UNINSTALL
-
    
-
-
-
-
-
-
-
    Extend code: operation
    
-
-
    HexOperation
-
    0SP_EXECUTION_OP_UNKNOWN
-
    1SP_EXECUTION_OP_COPY_PAYLOAD
-
    2SP_EXECUTION_OP_DOWNLOAD_UPDATES
-
    3SP_EXECUTION_OP_INSTALL_UPDATES
-
    4SP_EXECUTION_OP_INSTALL_RECOVERY_ENVIRONMENT
-
    5SP_EXECUTION_OP_INSTALL_RECOVERY_IMAGE
-
    6SP_EXECUTION_OP_REPLICATE_OC
-
    7SP_EXECUTION_OP_INSTALL_DRVIERS
-
    8SP_EXECUTION_OP_PREPARE_SAFE_OS
-
    9SP_EXECUTION_OP_PREPARE_ROLLBACK
-
    ASP_EXECUTION_OP_PREPARE_FIRST_BOOT
-
    BSP_EXECUTION_OP_PREPARE_OOBE_BOOT
-
    CSP_EXECUTION_OP_APPLY_IMAGE
-
    DSP_EXECUTION_OP_MIGRATE_DATA
-
    ESP_EXECUTION_OP_SET_PRODUCT_KEY
-
    FSP_EXECUTION_OP_ADD_UNATTEND
-
    
-    		
-
-
    HexOperation
-
    10SP_EXECUTION_OP_ADD_DRIVER
-
    11SP_EXECUTION_OP_ENABLE_FEATURE
-
    12SP_EXECUTION_OP_DISABLE_FEATURE
-
    13SP_EXECUTION_OP_REGISTER_ASYNC_PROCESS
-
    14SP_EXECUTION_OP_REGISTER_SYNC_PROCESS
-
    15SP_EXECUTION_OP_CREATE_FILE
-
    16SP_EXECUTION_OP_CREATE_REGISTRY
-
    17SP_EXECUTION_OP_BOOT
-
    18SP_EXECUTION_OP_SYSPREP
-
    19SP_EXECUTION_OP_OOBE
-
    1ASP_EXECUTION_OP_BEGIN_FIRST_BOOT
-
    1BSP_EXECUTION_OP_END_FIRST_BOOT
-
    1CSP_EXECUTION_OP_BEGIN_OOBE_BOOT
-
    1DSP_EXECUTION_OP_END_OOBE_BOOT
-
    1ESP_EXECUTION_OP_PRE_OOBE
-
    1FSP_EXECUTION_OP_POST_OOBE
-
    20SP_EXECUTION_OP_ADD_PROVISIONING_PACKAGE
-
    
-
    
-
-For example: An extend code of **0x4000D**, represents a problem during phase 4 (**0x4**) with data migration (**000D**).
-
-## Log files
-
-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.
     This is the most important log for diagnosing setup issues.
-
    OOBE:
    $Windows.~BT\Sources\Panther    		Contains information about actions during the OOBE phase.Investigating rollbacks that failed during OOBE phase and operations – 0x4001C, 0x4001D, 0x4001E, 0x4001F.
-
    Rollback:
    $Windows.~BT\Sources\Panther    		Contains information about actions during rollback.Investigating generic rollbacks - 0xC1900101.
-
    Pre-initialization (prior to downlevel):
    $Windows.~BT\Sources\Panther    		Contains information about initializing setup.If setup fails to launch.
-
    Post-upgrade (after OOBE):
    $Windows.~BT\Sources\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 WU 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 bugchecks 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 includes the following elements:
-
-
      
-
    1. The date and time. For example: 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) and MIG (migration engine) are particularly useful for troubleshooting Windows Setup errors.
-
      
-
    4. The message. For example: Operation completed successfully.
-
    
-
-### Analyzing log files
-
-To analyze Windows Setup log files:
-
-
      
-
    1. Determine the Windows Setup error code.
-
    2. Based on the [extend code](#extend-codes) portion of the error code, determine the type and location of a [log files](#log-files) 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.
-
    5. To find the last occurrence of the result code:
-  
        
-  
      1. Scroll to the bottom of the file and click after the last character.
-  
      2. Click **Edit**.
-  
      3. Click **Find**.
-  
      4. Type the result code.
-  
      5. Under **Direction** select **Up**.
-  
      6. Click **Find Next**.
-  
      
-
    6.  When you have 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 just prior to generating the result code.
-
    7.  Search for the following important text strings:
-  
        
-  
      • Shell application requested abort
-  
      • Abandoning apply due to error for object
-  
      
-
    8.  Decode other Win32 errors that appear in this section.
-
    9.  Search other log files for additional information related to your findings.
-
    
-
-For example, assume that searching for the result code "8007042B" reveals the following content from the setuperr.log file:
-
->Some lines in the text below are shortened for readability. In addition, the date and time at the start of each line (ex: 2016-09-08 09:20:05) is shortened to minutes and seconds.
-
-
    setuperr.log content:
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
-In the previous text, the third line indicates there was an error **0x00000497** with the folder **C:\Users\user1\Cookies**:
-
-
    -23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-
    
-
-The error 0x00000497 is a [Win32 error code](https://msdn.microsoft.com/en-us/library/cc231199.aspx) corresponding to: 
-
-
    ERROR_UNABLE_TO_REMOVE_REPLACED: Unable to remove the file to be replaced.
-
-Therefore, Windows Setup failed because it was not able to migrate the **C:\Users\user1\Cookies** folder.  Searching the setupact.log file for additional details, the following text is found:
-
-
    setupact.log content:
-
-
    -23:50, Warning                 RECAPPLY: Error while moving \\?\C:\Windows.old\Users\user1\Cookies to \\?\C:\Users\user1\Cookies. Error: 0x000000B7
-23:50, Info             MIG    Cannot apply recursively object: C:\Users\user1\Cookies: Win32Exception: Cannot create a file when that file already exists.
-23:50, Warning          MIG    Could not replace object C:\Users\user1\Cookies. Target Object cannot be removed.
-23:50, Info             MIG    Error 1175 during apply of object C:\Users\user1\Cookies. Will ask shell application for resolution.
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1b\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-
    
-
-The setupact.log file also contains information detailing the configuration of files and folders. By searching for "C:\Users\user1\Cookies" we are able to determine that this folder is not installed in the default location:
-
-
    -49:12, Info             MIG    Known folder CSIDL_COOKIES: C:\Users\user1\Cookies, default location: No
-
    
-
-This error can be resolved by configuring the folder to use its default location.
-
-## Common error codes
-
-### 0xC1900101
-
-A common result code is 0xC1900101. This result code can be thrown at any stage of the upgrade process, with the exception of the Downlevel phase. 0xC1900101 is a generic rollback code, and usually indicates that an incompatible driver is present. The incompatible driver can cause blue screens, system hangs, and unexpected reboots. Analysis of supplemental log files is often helpful, such as:
    
-
-- The minidump file: $Windows.~bt\Sources\Rollback\setupmem.dmp, 
-- Event logs: $Windows.~bt\Sources\Rollback\*.evtx 
-- The device install log: $Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
-
-The device install log is particularly helpful if rollback occurs during the sysprep operation (extend code 0x30018).  To resolve a rollback due to driver conflicts, run setup in the absence of drivers by performing a [clean boot](https://support.microsoft.com/en-us/kb/929135) before initiating the upgrade process. 
-
-
    See the following general troubleshooting procedures associated with a result code of 0xC1900101:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
    
-
-
-
    Code
-
    0xC1900101 - 0x20004
-
    
-
-
    
-
    Cause
-
    Windows Setup encountered an error during the SAFE_OS with the INSTALL_RECOVERY_ENVIRONMENT operation
-
    This is generally caused by out-of-date drivers. 
-
    
-
    		
-
-
-
    Mitigation
-
    Uninstall antivirus applications.
-
    Remove all unused SATA devices.
-
    Remove all unused devices and drivers.
-
    Update drivers and BIOS.
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x2000c
-
    
-
-
    
-
    Cause
-
    Windows Setup encountered an unspecified error during the WinPE phase.
-
    This is generally caused by out-of-date drivers. 
-
    
-
    		
-
-
-
    Mitigation
-
    Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
-
    Contact your hardware vendor to obtain updated device drivers.
-
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. 
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x20017
-
-
    
-
-
    
-
    Cause
-
    A driver has caused an illegal operation.
-
    Windows was not able to migrate the driver, resulting in a rollback of the operating system.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-Ensure that all that drivers are updated.
    
-Open the Setuperr.log and Setupact.log files in the %windir%\Panther directory, and then locate the problem drivers.
-
    For more information, see [Understanding Failures and Log Files](https://technet.microsoft.com/en-us/library/ee851579.aspx).
-
    Update or uninstall the problem drivers.
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x30018
-
    
-
-
    
-
    Cause
-
    A device driver has stopped responding to setup.exe during the upgrade process.
-
    
-
    		
-
-
-
    Mitigation
-
    
-Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
-
    Contact your hardware vendor to obtain updated device drivers.
-
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process. 
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x3000D
-
    
-
-
    
-
    Cause
-
    Installation failed during the FIRST_BOOT phase while attempting the MIGRATE_DATA operation.
-
    This can occur due to a problem with a display driver.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-Disconnect all peripheral devices that are connected to the system, except for the mouse, keyboard and display.
-
    Update or uninstall the display driver.
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x4000D
-
    
-
-
    
-
    Cause
-
    A rollback occurred due to a driver configuration issue.
-
    
-
    		
-
-
-
    Mitigation
-
    Review the rollback log and determine the stop code.
-
    The rollback log is located in the **C:\$Windows.~BT\Sources\Panther** folder.  Look for text similar to the following:
-
    Info SP     Crash 0x0000007E detected
-
    Info SP       Module name           : 
-
    Info SP       Bugcheck parameter 1  : 0xFFFFFFFFC0000005
-
    Info SP       Bugcheck parameter 2  : 0xFFFFF8015BC0036A
-
    Info SP       Bugcheck parameter 3  : 0xFFFFD000E5D23728
-
    Info SP       Bugcheck parameter 4  : 0xFFFFD000E5D22F40
-
    Info SP     Cannot recover the system.
-
    Info SP     Rollback: Showing splash window with restoring text: Restoring your previous version of Windows.
-
-
-
    Typically there is a a dump file for the crash to analyze. If you are not equipped to debug the dump, then attempt the following basic troubleshooting procedures:
    
-
-1. Make sure you have enough disk space.
    
-2. If a driver is identified in the bug check message, disable the driver or check with the manufacturer for driver updates.
    
-3. Try changing video adapters.
    
-4. Check with your hardware vendor for any BIOS updates.
    
-5. Disable BIOS memory options such as caching or shadowing.
-
    
-
    
-
    
-
-
-
    Code
-
    0xC1900101 - 0x40017
-
    
-
-
    
-
    Cause
-
    Windows 10 upgrade failed after the second reboot.
-
    This is usually caused by a faulty driver. For example: antivirus filter drivers or encryption drivers.
-
    
-
    		
-
-
-
    Mitigation
-
    Clean boot into Windows, and then attempt the upgrade to Windows 10.
    
-
-For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
-
-
    Ensure you select the option to "Download and install updates (recommended)."
-
    
-
    
-
-### 0x800xxxxx
-
-Result codes starting with the digits 0x800 are also relatively common. These error codes indicate general operating system errors, and are not unique to the Windows upgrade process. Examples include timeouts, devices not functioning, and a process stopping unexpectedly.
-
-
    See the following general troubleshooting procedures associated with a result code of 0x800xxxxx:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
    
-
-
-
    Code
-
    
-
-8000405 - 0x20007
-
-
    
-
-
    
-
    Cause
-
    
-
-An unspecified error occurred with a driver during the SafeOS phase.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-
-Analyze logs.
-
-
    
-
    
-
-
-
    Code
-
    
-
-800704B8 - 0x3001A
-
-
    
-
-
    
-
    Cause
-
    
-
-Here is a cause.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-
-Disable AV, disconnect devices, clean boot.
-
-
    
-
    
-
-
-
    Code
-
    
-
-8007042B - 0x4000D
-
-
    
-
-
    
-
    Cause
-
    
-
-The installation failed during the second boot phase while attempting the MIGRATE_DATA operation. 
-
    This issue can occur due to an application or driver incompatibility.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-
-Clean boot into Windows, and then attempt the upgrade to Windows 10. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
-
-
    Ensure you select the option to "Download and install updates (recommended)."
-
-
    
-
    
-
-
-
    Code
-
    
-
-8007001F - 0x4000D
-
-
    
-
-
    
-
    Cause
-
    
-
-Need cause here.  
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-
-Need mitigation here.
-
-
    
-
    
-
-
-
    Code
-
    
-
-8007042B - 0x4001E
-
-
    
-
-
    
-
    Cause
-
    
-
-Here is a cause.
-
-
    
-
    		
-
-
-
    Mitigation
-
    
-
-Here is a mitigation procedure.
-
-
    
-
    
-
-
-## Other result codes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
    Error code
-Cause
-Mitigation
-
    0xC1900200Setup.exe has detected that the machine does not meet the minimum system requirements.Ensure the system you are trying to upgrade meets the minimum system requirements. 
    See [Windows 10 specifications](https://www.microsoft.com/en-us/windows/windows-10-specifications)  for information.
    0x80090011A device driver error occurred during user data migration.Contact your hardware vendor and get all the device drivers updated. It is recommended to have an active internet connection during upgrade process. 
-
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
    0xC7700112Failure to complete writing data to the system drive, possibly due to write access failure on the hard disk.This issue is resolved in the latest version of Upgrade Assistant. 
-
    Ensure that "Download and install updates (recommended)" is accepted at the start of the upgrade process.
    0x80190001An unexpected error was encountered while attempting to download files required for upgrade.To resolve this issue, download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10).
-
    0x80246007The update was not downloaded successfully.Attempt other methods of upgrading the operatign system.
    
-Download and run the media creation tool. See [Download windows 10](https://www.microsoft.com/en-us/software-download/windows10). 
-
    Attempt to upgrade using .ISO or USB.
    
-**Note**: Windows 10 Enterprise isn’t available in the media creation tool. For more information, go to the [Volume Licensing Service Center](https://www.microsoft.com/licensing/servicecenter/default.aspx).
-
    0xC1900201The system did not pass the minimum requirements to install the update.Contact the hardware vendor to get the latest updates.
    0x80240017The upgrade is unavailable for this edition of Windows.Administrative policies enforced by your organization might be preventing the upgrade. Contact your IT administrator.
    0x80070020The existing process cannot access the file because it is being used by another process.Use the MSCONFIG tool to perform a clean boot on the machine and then try to perform the update again. For more information, see [How to perform a clean boot in Windows](https://support.microsoft.com/en-us/kb/929135).
    0x80070522The user doesn’t have required privilege or credentials to upgrade.Ensure that you have signed in as a local administrator or have local administrator privileges.
    0xC1900107A cleanup operation from a previous installation attempt is still pending and a system reboot is required in order to continue the upgrade.
-Reboot the device and run setup again. If restarting device does not resolve the issue, then use the Disk Cleanup utility and cleanup the temporary as well as the System files. For more information, see [Disk cleanup in Windows 10](https://support.microsoft.com/en-us/instantanswers/8fef4121-711b-4be1-996f-99e02c7301c2/disk-cleanup-in-windows-10).
    0xC1900209The user has chosen to cancel because the system does not pass the compatibility scan to install the update. Setup.exe will report this error when it can upgrade the machine with user data but cannot migrate installed applications.Incompatible software is blocking the upgrade process. Uninstall the application and try the upgrade again. See [Windows 10 Pre-Upgrade Validation using SETUP.EXE](https://blogs.technet.microsoft.com/mniehaus/2015/08/23/windows-10-pre-upgrade-validation-using-setup-exe/) for more information.
-
-
    You can also download the [Windows Assessment and Deployment Kit (ADK) for Windows 10](http://go.microsoft.com/fwlink/p/?LinkId=526740) and install Application Compatibility Tools.
-
    0x8007002 This error is specific to upgrades using System Center Configuration Manager 2012 R2 SP1 CU3 (5.00.8238.1403)Analyze the SMSTS.log and verify that the upgrade is failing on "Apply Operating system" Phase: Error 80072efe DownloadFileWithRanges() failed. 80072efe. ApplyOperatingSystem (0x0760)
-
-
    The error 80072efe means that the connection with the server was terminated abnormally.
-
-
    To resolve this issue, try the OS Deployment test on a client in same VLAN as the Configuration Manager server. Check the network configuration for random client-server connection issues happening on the remote VLAN.
-
    
-
-## Other error codes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
    Error CodesCauseMitigation
    0x80070003- 0x20007This error occurs when there is problem with the Internet connection during the Windows 10 upgrade."Since this error indicates that the internet connection ran into a problem, you may attempt to fix the connectivity issues and reattempt the download of the files.
-Alternatively, you may re-create installation media using ""Media Creation Tool"" from a different connected system. Refer: https://www.microsoft.com/en-us/software-download/windows10
-
-You can either create a USB drive or an ISO.
-"
    0x8007025D - 0x2000CThis error occurs if the ISO file's metadata is corrupt."Re-download the ISO/Media and re-attempt the upgrade.
-
-You may alternatively, re-create installation media using ""Media Creation Tool"" Refer: https://www.microsoft.com/en-us/software-download/windows10
-
-You can either create a USB drive or an ISO using the Media Creation Tool.
-"
    0x80070490 - 0x20007The error comes up during driver installation phase and it means that some of the device driver is incompatible."Please ensure that all the devices are working correctly. Please review the Device Manager for any errors and troubleshoot accordingly.
-Refer: https://msdn.microsoft.com/windows/hardware/drivers/install/troubleshooting-device-and-driver-installations
-
-Additionally, you can review the following logs to verify which I/O device is causing the problem.
- ""%systemroot%\$Windows.~BT\Sources\Panther\setupact.log"" 
-
-If unable to review the logs, post on Windows 10 TechNet Forum (https://social.technet.microsoft.com/Forums/en-us/home?forum=win10itprogeneral&filter=alltypes&sort=lastpostdesc)
-"
    0xC1900101 - 0x2000BThis error occurs when the device drivers of the hardware connected to the computer prevent the Windows 10 upgrade from building the migration file list.We recommended you disconnect the devices that aren't in use when you upgrade the computer.
    0xC1900101 - 0x2000cThe Setup Platform has encountered an unspecified error during the WINPE Phase. This is generally caused by drivers which are not updated at the time when the upgrade was started.It is recommended to select "Download and install updates (recommended)" during the upgrade process. Additionally, you can contact the Hardware Vendor and get the updates for the device drivers that are connected to the system. Ensure all the devices other than the Mouse; Keyboard and Display are disconnected during upgrade process. Then start setup again.
    0xC1900200 - 0x20008This error occurs when the computer doesn’t meet the minimum requirements to download or upgrade to Windows 10."Refer http://www.microsoft.com/en-us/windows/windows-10-specifications?OCID=win10_null_vanity_win10specs and make sure that the machine, on which the upgrade is being initiated, meets the minimum requirement.
-
-Secondly use the Windows 10 Compatibility Reports to understand upgrade issues (https://blogs.technet.microsoft.com/askcore/2016/01/21/using-the-windows-10-compatibility-reports-to-understand-upgrade-issues/)
-"
    0x80070004 - 0x3000DSYSTEM, LOCAL, SELF, System, and Network are reserved names that can’t be used for Computer Name."Ensure that you do not use the reserved names as the Computer names. Rename the system to a valid Computer name.
-See KB 3086101 for more details.
-"
    0xC1900101 - 0x40001"This error indicates that we saw an error in the OOBE Phase - Stop 9F. This behavior occurs when device drivers do not handle power state transition requests properly. The error message most often occurs during one of the following actions: 1. Shutting down
-2. Suspending or resuming from Standby mode
-3. Suspending or resuming from Hibernate mode""The most common causes for this error would be the connected devices on the machine / device as below and it would have suggested that we disable / disconnect them from the device /machine before performing the upgrade:
-1. Internal WIFI Modem
-2. Any External connected USB devices such as WEBCAMS; Printers; USB Hard Drives
-3. Check to be sure your computer and all devices are on the Hardware Compatibility List (HCL) and have WHQL signed and certified drivers.
-
-The setup.exe will perform a rollback of the OS and would return to the older OS. Once the rollback is complete if we find the problem causing driver than we need to check for %SystemDrive%\$Windows.~bt\sources\Rollback\setupmem.dmp file and have a Microsoft Support Professional look into the same.
-"
    0xC1900101 - 0x4001EThis error indicates that the installation failed in the SECOND_BOOT phase with an error during PRE_OOBE operation.This is a generic error that occurs during the OOBE phase of Setup. We recommend you to review the FAQ for Upgrade to Windows 10 (https://support.microsoft.com/en-us/help/12435/windows-10-upgrade-faq)
    0x80070005 - 0x4000DThis error code means The installation failed in the SECOND_BOOT phase with an error in during MIGRATE_DATA operation.This issue may occur if we have any application / driver that is causing an issue while the upgrade to Windows 10 is going on.  Preform a clean boot on the system. Refer https://support.microsoft.com/en-us/kb/929135 for steps to perform a Clean boot.
    0x80070004 - 0x50012The Computer account for the system has an invalid name. Please ensure that the machine name does not have any invalid characters (See https://technet.microsoft.com/en-us/library/cc749460(v=ws.10).aspx). Additionally, the names should not be any of the reserved names for systems. Rename the system to a valid computer name and try the Setup again. See KB 3086101 for more details.
    "0xC190020e 0x80070070 - 0x50011
-0x80070070 - 0x50012
-0x80070070 - 0x60000"These errors would occur if your computer doesn’t have enough free space available to install the upgrade."Typically to upgrade to Windows 10, you need free space of 16 GB for 32-bit OS and 20 GB for 64-bit OS. If there is not enough space refer the following article:
-https://support.microsoft.com/en-us/help/17421/windows-free-up-drive-space 
- 
-Note: Once the deletion is complete, initiate the upgrade and this time you should not receive the error if sufficient space has been made. If that is not enough 
-then, you can implement solution as mentioned below.
- 
-Using External Drive
-If your device allows it, you can use an external USB drive for the upgrade process. Windows setup will backup the previous version of Windows to a USB external drive. The external drive must be at least 8GB – but having 16GB is recommended. 
-Some important points to remember if you choose to use an external storage drive for installing Windows 10:
- - We recommend that the external drive is formatted in NTFS.  Drives that are formatted in FAT32 may run into errors due to FAT32 file size limitations.  To learn   how to format in NTFS, click here.
-- USB drives are preferred over SD cards because drivers for SD cards are not migrated if the device does not support Connected Standby.
-"
    
-
-
-
-
-## Related topics
-
-•	Windows 10 FAQ for IT professionals
-•	Windows 10 Enterprise system requirements
-•	Windows 10 IT pro forums
diff --git a/windows/deploy/test-pre.md b/windows/deploy/test-pre.md
deleted file mode 100644
index 7cc861e9c7..0000000000
--- a/windows/deploy/test-pre.md
+++ /dev/null
@@ -1,136 +0,0 @@
----
-title: Test pre tag
-description: Test table
-ms.assetid: DFEFE22C-4FEF-4FD9-BFC4-9B419C339502
-keywords: deploy, error, troubleshoot, windows, 10
-ms.prod: w10
-ms.mktglfcycl: deploy
-ms.sitesec: library
-ms.pagetype: deploy
-author: greg-lindsay
-localizationpriority: high
----
-
-# Test pre tag
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
    
-
-
    -
-20:05, Error            SP     Error READ, 0x00000002 while gathering/applying object: 
-23:33, Error            MIG    COnlineWinNTPlatform::AddPathToSearchIndexer - Failed to create CSearchManager instance, error: 0x80070422[gle=0x000003f0]
-23:50, Error            SP     Error WRITE, 0x00000497 while gathering/applying object: File, C:\Users\user1\Cookies. Will return 0
-23:50, Error            MIG    Error 1175 while applying object C:\Users\user1\Cookies. Shell application requested abort
-23:50, Error [0x08097b] MIG    Abandoning apply due to error for object: C:\Users\user1\Cookies
-23:51, Error                   Apply failed. Last error: 0x00000000
-23:51, Error            SP     pSPDoOnlineApply: Apply operation failed. Error: 0x0000002C
-23:52, Error            SP     Apply: Migration phase failed. Result: 44
-23:52, Error            SP     Operation failed: OOBE boot apply. Error: 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed: 13. hr = 0x8007042B[gle=0x000000b7]
-23:52, Error            SP     Operation execution failed.[gle=0x000000b7]
-23:52, Error            SP     CSetupPlatformPrivate::Execute: Failed to deserialize/execute pre-OOBEBoot operations. Error: 0x8007042B[gle=0x000000b7]
-
-
    
\ No newline at end of file