Windows 10: Update to version 1703 failing

The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation
Error code 0x8007002C - 0x4000D

Had this before on another computer, which got fixed by uninstalling antivirus, firewall and messing with a few reg keys.
That didn't work on this device. The installation still fails at 75% with a very short BSOD CRITICAL_PROCESS_DIED

Drivers are up-to-date automatically by HP's applications. (HP ENVY h8-1410eb)
setupact and setuperr log files are attached.

Thank you in advance!


Edit: Please don't give me the clean install "solution"..

:)

 

Windows 10, version 1703 update failing to install on my Asus ROG GL502VS laptop

Hi, I am a creative professional and currently facing this horrible Windows creator's update 1703 on my Asus ROG GL502VS laptop. It downloads and try to install the update daily but unable to do so. I am looking for a solution to this problem from Windows
if any. Please help. It's updated till 1607.

 

Windows 10, version 1703 update failing to install on my Asus ROG GL502VS laptop

I too own a ASUS ROG GL502VS laptop and have been having the exact same problem. To resolve this problem you will need to boot into the BIOS then under the ADVANCED tab you need to disable SMART. Once you have do so, be sure to save your changes and then
exit the bios. Now you will be able to update to the newest version of Windows 10 which as of today (2.19.2018) is 1709 (Windows Fall Creator Update).

Official Link from ASUS:

Windows 10 OS cannot update to version RS2(1703), how to fix it ? | Official Support | ASUS Global

 

1) Rename the cbs and dism logs by adding old.
C:\Windows\Logs\CBS\CBS.log
C:\Windows\Logs\Dism\Dism.log
Rename the panther logs by adding old. (setupact and setuperr logs)
2) Perform windows updates
Post into the thread any failed KB# with error code.
Open administrative command prompt and type or copy and paste these commands:
1) winver (post an image into the thread after the windows updates)
2) sfc /scannow
3) dism /online /cleanup-image /checkhealth
4) dism /online /cleanup-image /scanhealth
5) dism /online /cleanup-image /restorehealth
6) chkdsk /scan
When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on copy > paste into the thread


7) msconfig (in the pop up system configuration > move the dot from normal startup to selective startup > uncheck load startup items > click service tab > in left lower corner check hide all Microsoft services > in the lower right side click disable all > click apply or ok > do not reboot)


8) taskmgr (in the pop up task manager > click on the start up tab > click on status so that the column sorts with enable rising to the top > right click on each row with enable and change to disable)


9) shutdown /r (you will reboot the computer so that it is in clean boot)

10) disconnect all non essential hardware from the computer (printer, camera, smart phone, etc)

11) attempt to upgrade windows in clean boot.

12) run the panther command again if windows upgrade fails

13) post the new setupact and setuperr logs

14)obtain a flash drive that you can format

15) create a bootable windows 10 iso: Download Windows 10

 

I don't understand your second point "perform windows updates". There are none left. Only the upgrade to 1703 remains.

I did an sfc /scannow and dism check/scan/restore already before, but no damage was detected.


I'll try the rest when I can, but haven't you found anything inside the logs i have given you?

 

Each time a command is run there will be information in the logs. The error codes can potentially be deciphered to come up with a possible solution. So the aim was to make the logs a managable size and have sufficient commands with error codes to see if the problem preventing the upgrade could be found and fixed. The cbs is likely the largest file so it needs to be reduced in size. Windows updates and windows upgrades are similar but different. So running the windows updates, the scannow, restorehealth and the panther commands all create logs that may have some information that can be deciphered. Many times though the failure codes are to general to arrive at any concrete conclusion. For my windows upgrade failure from 1607 to 1703 a review of the logs indicated that it wanted more free space in the EFI partition. This allowed further troubleshooting. An in place upgrade or a clean install often eliminate the need to troubleshoot but the troubleshooting can be done.

 

The list of startup processes contains Windows-hostprocess (rundll32)
Do I have to disable that aswell? Isn't that... bad?

 

This link may be useful:
What Is , and Why Are So Many Running on My PC?

 

I did everything as you told. Tried to install 1703 with Media Creation Tool (it doesn't appear in Windows Update anymore)

Failed again, at the exact same moment as before.
(reboots at 75% and shortly after a BSOD CRITICAL_PROCESS_DIED)

I attached everything you need. (the copy-paste of the cmd is in cmd.txt)

 

Were there any new error codes?

 

No. Exactly the same as before.

The installation failed in the SECOND_BOOT phase with an error during MIGRATE_DATA operation
Error code 0x8007002C - 0x4000D

 

Type winver in the left lower corner search and post your windows version and build into the thread.
Were you able to place the computer in clean boot using msconfig and task manager and disconnect all devices?
Which antivirus are you using?
When you view windows update when was the last successful update?

 

Oh I'm sorry I indeed forgot to upload the winver.
It's version 1607, build 14393.1358 (Win10 Home 64-bit)

It was completely in clean boot state, nothing else except windows elements were running.
I uninstalled Avira (antivirus) and my firewall, because they refused to disable themselves in msconfig. (But normally they shouldn't interfere with the update because other devices at home upgraded to 1703 without any issue, while these were installed)

Last update was KB4013214, on June 29th (the same day at which I performed the first attempt to update to 1703)
Edit: that's the update that contains the preparation for your privacy-settings. (to start the 1703 upgrade)

Since the installation failed once more in clean boot state, I suspect it's hardware/driver related rather than software (hence the CRITICAL_PROCESS_DIED code in the BSOD)

Isn't there anything inside the Panther log that indicates faulty drivers or registry entries?

 

In the logs I cannot find the error code that you posted. That is usually where you start and work backwards. All of the logs including CBS old and DISM old were checked for the error that you posted.
Have you yet been to technet? That is where I learned. They have some experts there on reading the logs. There tough to interpret as they use codes and general terms that may have little meaning to even tech pros. See if you can post it there for this challenging case.
If your error code is correct its a puzzle that it is not in any of the logs. The error code is for the second boot phase. That is the 4000d but again that was not found in the logs.

 

2017-07-05 10:19:41, Info CBS Client specifies manual store corruption detect or repair.
2017-07-05 10:19:42, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30602599_1942279522
2017-07-05 10:22:11, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:45]'10.0.14393.1439 (rs1_release_sec.170519-2028)'.
2017-07-05 10:22:11, Info CSI 00000006@2017/7/5:08:22:11.930 Starting corruption detection (InnerFlags=5)
2017-07-05 10:36:02, Info CSI 00000007@2017/7/5:08:36:02.020 Corruption detection complete. numCorruptions = 0, Disp = 1.
2017-07-05 10:36:02, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2017-07-05 10:36:02, Info CBS Ensure CBS corruption flag is clear
2017-07-05 10:36:02, Info CBS Ensure WCP corruption flag is clear
2017-07-05 10:36:02, Info CBS Exec: Processing complete, session(Corruption Detecting): 30602599_1942279522 [HRESULT = 0x00000000 - S_OK]