Windows 10: Windows Update 1809 always fails around 90%-95% (current version: 1703)

Hello guys,


I would just like to ask help when upgrading my Windows 10 from 1703 to 1809. I've tried upgrading multiple times already. But whenever it restarts and at 90-95% already, it will restart and "undoing changes made to your computer" appears. One thing that constantly happening though is whenever it restarts, the same old version stays and the "start" is not working. I would run the troubleshooter and restart to fix it. I tried a lot of fixes from Google already (uninstalling Windows Developer Mode, deleting everything inside SoftwareDistribution folder to reset, etc.). Unfortunately, nothing worked.


I ran the SetupDiag.exe to check for some error logs. This is what I got:




Matching Profile found: FindMigGatherUnitFailure - D04C064B-CD77-4E64-96D6-D26F30B4EE29

System Information:

Machine Name = PH-L824

Manufacturer = Dell Inc.

Model = Latitude E7470

HostOSArchitecture = x64

FirmwareType = UEFI

BiosReleaseDate = 20170711000000.000000+000

BiosVendor = 1.17.5

BiosVersion = 1.17.5

HostOSVersion = 10.0.15063

HostOSBuildString = 15063.0.amd64fre.rs2_release.170317-1834

TargetOSBuildString = 10.0.17134.1 (rs4_release.180410-1804)

HostOSLanguageId = 1033

HostOSEdition = Professional

RegisteredAV = McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,McAfee Endpoint Security,

FilterDrivers = mfehidk,wcifs,CmgPassThrough,CmgShieldFFE,luafv,Wof,FileInfo,

UpgradeStartTime = 31-3-2019 13:45:15

FinalizeStartTime = 31-3-2019 14:30:04

UpgradeEndTime = 31-3-2019 15:23:57

UpgradeElapsedTime = 01:38:42

CV = p44x0J4IakuGBgM6

ReportId = 2043AFAC-8B6F-41B3-9848-319924E7920E





Error: SetupDiag reports Migration Unit Gather failure.

MigUnit: C:\Users\jennifer.ebora\AppData\Local\Packages\Microsoft.Windows.Cortana_cw5n1h2txyewy\LocalState\AppIconCache\100 [{01D0165C-B943-4FFE-AB09-E9EED4645B8F}]

Object Type: State

Operation: WRITE

Error: 0x0000065E



Refer to "https://docs.microsoft.com/en-us/windows/desktop/Debug/system-error-codes" for error information.



And from C:\$WINDOWS.~BT\Sources\Rollback\setuperr.log:



2019-03-31 15:24:43, Error SP Cannot map user hive C:\Users\Default\NTUSER.DAT in HKEY_USERS\S-1-0-0. Error: 0x00000020

2019-03-31 15:24:43, Error CSI 00000017 (F) STATUS_OBJECT_NAME_NOT_FOUND #3609# from Windows::Rtl::SystemImplementation:irectRegistryProvider::SysOpenKey(flg = 0, key = {provider=NULL, handle=0, name= ("null")}, da = (KEY_READ|KEY_WOW64_64KEY), oa = @0xf724f4b458->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[147]'\Registry\Machine\{bf1a281b-ad7b-4476-ac95-f47682990ce7}C:/WINDOWS/System32/config/SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-0-0'; aOBJ_CASE_INSENSITIVE)}, disp = Invalid)[gle=0xd0000034]

2019-03-31 15:24:43, Error CSI 00000018@2019/3/31:23:24:43.693 (F) onecore\base\wcp\sil\ntsystem.cpp(5229): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation:irectRegistryProvider::SysOpenKey expression: (null)

[gle=0x80004005]

2019-03-31 15:24:43, Error CSI 00000019 (F) STATUS_OBJECT_NAME_NOT_FOUND #3608# from Windows::Rtl::SystemImplementation::IRtlUserProvider::GetPathFromRegistry(...)[gle=0xd0000034]

2019-03-31 15:24:43, Error CSI 0000001a (F) STATUS_OBJECT_NAME_NOT_FOUND #3607# from Windows::Rtl::SystemImplementation::CUserProfile::GetSpecialDirectoryPath(f = 0, did = 1114112)[gle=0xd0000034]

2019-03-31 15:24:43, Error CSI 0000001b (F) STATUS_OBJECT_NAME_NOT_FOUND #3606# from Windows::Rtl::SystemImplementation::CUserProfile_IRtlUserProfileTearoff::GetSpecialDirectoryPath(...)[gle=0xd0000034]

2019-03-31 15:24:43, Error CSI 0000001c (F) HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) #3600# from Windows::WCP::COM::CCSIExternalTransformerExecutor::Commit(UserSID = S-1-0-0, LoadedUserHive=(null), LoadedUserClassesHive=HKEY_USERS\S-1-0-0_Classes, UserProfilePath=C:\Users\Default)[gle=0x80070002]

2019-03-31 15:24:43, Error SP Failure while calling Transformer Commit. Error: 0x80070002[gle=0x0000001f]

2019-03-31 15:24:44, Error SP UndoTransformers failed for C:\$WINDOWS.~BT\Sources\Rollback\MachineIndependent\Transformers. Error: 0x80070002




Anybody knows how I can fix this? Thank you!

:)

 

Current Status of Windows 10 October 2018 Update version 1809


Update for "Current Status" of Windows 10 October Update on first page.

[table][tr][td]Date[/td] [td]Current Status[/td] [td]Affected Platforms[/td] [td]Details[/td] [/tr] [tr][td]November 28, 2018 5:00 PM PT[/td] [td]Known Issue[/td] [td]

• Windows 10, version 1809
• Windows Server 2019
• Windows Server, version 1809

[/td] [td]Mapped drives may fail to reconnect after starting and logging onto a Windows device. Symptoms include:

• In File Explorer, a red "X" appears on the mapped network drives.
• Mapped network drives show as "Unavailable" when you run the net usecommand from a command prompt.
• In the notification area, a notification displays, "Could not reconnect all network drives."

Workaround: See KB4471218 for workaround scripts to automatically reconnect a mapped network drive when you log on to the device. Next Steps: Microsoft is working on a resolution and estimates a solution will be available by early December 2018.[/td] [/tr] [/table]

 

2017-06 Cumulative Update for Windows 10 Version 1703 FAILED

Dear Saurabh,

The update will fail in number of Scenarios:

• If the system is not compatible for the update.
• If the update is not required onto the system.
• If the update is already installed and the windows update has discovered a similar version i.e a copy of the same.

Hence if it is not getting installed there is no need to worry

 

Current Status of Windows 10 October 2018 Update version 1809


Update to current status of upgrade block in place on first page.

[table][tr][td]Date[/td] [td]Current Status[/td] [td]Affected Platforms[/td] [td]Details[/td] [/tr] [tr][td]December 1, 2018 5:20 PM PT[/td] [td]Upgrade block in place[/td] [td]

• Windows 10, version 1809

[/td] [td]Microsoft and Morphisec have identified an issue on devices that have installed Morphisec Protector or another application that uses the Morphisec Software Development Kit (SDK) including: Cisco AMP for Endpoints. These applications may impact customers’ ability to save Microsoft Office documents. Workaround: Uninstall affected applications and get updated versions from respective vendors when available. Next Steps: We are working with Morphisec and Cisco to address this issue in updated versions of their applications.[/td] [/tr] [/table]