[SOLVED] Windows update multiple bug latest W10 feature update (1809)

pasranno

Well-known member
Joined
Mar 24, 2016
Posts
51
Location
NYC
Hello,

Today windows update begun the download and installation of the latest W10 feature release however it didn't worked out. Upon restarting the update failed code 0x8007001f.

Then I decided to troubleshoot windows update and then it got worse. Suddenly windows update is prompting installation of KB4023057 whereas I already installed it successful 2 months ago. By the way even when I try to install it again it ends up failing code 0x80070643

Since then I scanned everything sfc & dism and nothing unusual.
 

Attachments

I haven't tried anything else since my previous message however the KB4023057 has been successfully installed a second time somehow. Now windows update is not encountering any problem however it stops prompting for the feature update.

Should I wait for it or should I find a way to bruteforce the feature update installation?
 
Hello and welcome!

1. Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
2. Accept the License Agreement
3. Download the ISO file to your desktop.
4. Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.
 
Hello and welcome!

1. Download the Media Creation Tool and save this to your desktop. Go ahead and run this as well. Note: Click the Download tool now button when you get to this link.
2. Accept the License Agreement
3. Download the ISO file to your desktop.
4. Double-click on the ISO and then run the setup to try and upgrade your machine.

We want to get the ISO so that you don't have to keep downloading which can take hours.

Uptade failed

Code:
We couldn't install W10
Code : 0x8007001F - 0x3000D
The installation failed in FIRST_BOOT phase with an error during MIGRATE_DATA operation
Same error code as during my first try using windows update
 
Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
Please remove Bitdefender from your system with its removal tool as well as the following:

f.lux
DriverBooster 5
Daemon Tools Lite
IOBit Uninstaller 8
Popcorn Time


Afterwards, unplug your Ethernet cable/disconnect your wifi and retry the upgrade from the iso. If it fails, attach setuperr.log and CBS.log.
 
Uninstalled all mentioned software and rebooted the device before trying the installation again.
Ended up failing with exactly the same error at the same stage.

Logs attached
 

Attachments

Hi!

I'd try rebuilding your BCD next:

You will need a bootable Windows disc or recovery flash drive to boot from to do this.
How to create a recovery flash drive: https://support.microsoft.com/en-us/help/4026852/windows-create-a-recovery-drive

After you create the recovery drive, boot from it by using the advanced startup options and choosing boot from device (or using the UEFI interface, whichever is simpler :) ).
Here's the instructions that other users have had success with:



Alright, apparently the issue is with the BCD (Boot Configuration Data). A few users reported that rebuilding it solved that issue.

https://answers.microsoft.com/en-us/...4-9ae12cfd89a2 - "Most Helpful Reply" from Cifad

If you cannot read the commands properly, here goes (to be entered in the command prompt from the Recovery Environment):

diskpart - Opens the Disk Partitionning tool
select disk 0 - Will select your first hard drive (the one with the Windows partition on it)
list volume - Note the number of the partition that have no drive letter assigned to it, is of 260MB of size and have "FAT32" listed under the "FS" column
select volume X - X will be the number of your partition with a size of 260MB, the EFI System Partition one that you identified in the last command
assign letter=Z: - It'll assign the Z: letter to the EFI System Partition
exit - To exit the diskpart utility

Now you'll be back in the command prompt, enter the following commands:

cd /d Z:\EFI\Microsoft\Boot - Goes to the "Boot" directory in the Z: partition
attrib Z:\EFI\Microsoft\Boot\BCD -h -r -s - Removes the hidden, read-only and system attributes from the BCD folder
ren Z:\EFI\Microsoft\Boot\BCD BCD.old - Renamed the BCD folder to BCD.old
bootrec /rebuildbcd - This command will rebuild the BCD.

When it asks you Add the installation to boot list?, press on y followed by Enter and if it succeed, you'll have a The operation completed successfully message. Once you're done, close the command prompt, restart your computer and try to upgrade again.



Make sure you have a complete backup of anything important on your computer BEFORE attempting any of these steps.
 
BCD rebuild : OK
Update attempt NOK

Still encoutering the same issue (same error code). The installation process goes well until it reaches 42% and then it blocks for few minutes and after the reboot it start undo the modification.
 
It seems that the error which ends up blocking the process is the following

Code:
2019-02-13 23:22:29, Info                         MIG_FAKE_APPLY is not set; apply will be real
2019-02-13 23:22:29, Error                        Mig::CUpgradeTransportPlatform::SetUserContext: Store platform failed to find the user with ID: USER00000002, SID: S-1-0-0[gle=0x000000cb]
2019-02-13 23:22:29, Error                 MIG    Mig::CKnowledgeManager::BeginProcessingContext: Source platform failed to set the user context USER00000002[gle=0x000000cb]
2019-02-13 23:22:29, Error                        MigApply caught exception: Win32Exception: Can't switch to requested user context: USER00000002.: Un p�riph�rique attach� au syst�me ne fonctionne pas correctement. [0x0000001F] int __cdecl Mig::CKnowledgeManager::Apply(class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CUserMappingList *,class UnBCL::Hashtable<class UnBCL::String *,class UnBCL::String *> *,class Mig::CAgentManager *,class Mig::CMigrationLogger *,struct IMigExecuteProgress *)[gle=0x000000cb]
2019-02-13 23:22:29, Info                  MIG    Received request to restart the explorer process from context: SYSTEM
2019-02-13 23:22:29, Info                         Leaving MigApply method
2019-02-13 23:22:29, Error                 SP     pSPExecuteApply: Apply operation failed. Error: 0x00000004[gle=0x000000cb]
2019-02-13 23:22:29, Info                         Entering MigCloseCurrentStore method

Does USER00000002 has anything to do with USERS directory ? I am asking because I moved Users directory in D: drive a while ago so that I can have a System & Data splited in 2 different drives.
 

Attachments

Hello,

I don't know how to export it so I took a screenshot of it. I think having Default & Public mapped to systemdrive whereas all the USERS directory in in D: drive might be the problem right ?

Thanks for your help !
 

Attachments

  • 1550217537649.png
    1550217537649.png
    24.5 KB · Views: 34

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top