Windows fails updating from 10240 to 10586

Hi guys, Overkill here...I'm pretty tech savvy; work at an MSP providing tech support all day. Can't solve this issue on a laptop at home though.

When updating my laptop from build 10240 to 10586, I get the following behavior depending on the method:

Windows Update - reboots but does not attempt to install update
TechBench ISO/MCT Upgrade Install - Generates the following setuperr.log

Code:

2016-06-20 23:23:09, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:23:09, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:23:10, Error    MOUPG    CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Suspend(1066): Result = 0xC1800104
2016-06-20 23:23:10, Error    MOUPG    CSetupManager::ExecuteInstallMode(724): Result = 0x800705BB
2016-06-20 23:23:10, Error    MOUPG    CSetupManager::ExecuteDownlevelMode(389): Result = 0x800705BB
2016-06-20 23:23:10, Error    MOUPG    CSetupManager::Execute(232): Result = 0x800705BB
2016-06-20 23:23:10, Error    MOUPG    CSetupHost::Execute(371): Result = 0x800705BB
2016-06-20 23:30:28, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:30:28, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:30:30, Error    CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2016-06-20 23:30:30, Error    CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2016-06-20 23:30:31, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:30:31, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:30:48, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:32:41, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:32:47, Error    CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2016-06-20 23:32:47, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session[gle=0x000000b7]
2016-06-20 23:33:02, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:33:07, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:34:27, Error    CDiagnosticsHelper::SetDeferredSQMDatapoint: Attempting to set a deferred SQM datapoint in an invalid SQM session[gle=0x000000b7]
2016-06-20 23:34:39, Error    CDiagnosticsHelper::SetSQMDatapoint: Attempting to set a datapoint in an invalid SQM session
2016-06-20 23:35:20, Error    CONX    Failed to open inf key SYSTEM\CurrentControlSet\Control\Network\{4d36e975-e325-11ce-bfc1-08002be10318}\{58474950-424f-0058-cfe8-aba2187557f2}
2016-06-20 23:35:20, Error    CONX    Failed to add net component 80070002
2016-06-20 23:35:20, Error    CONX    Failed to open inf key SYSTEM\CurrentControlSet\Control\Network\{6bdd1fc5-810f-11d0-bec7-08002be2092f}\{25039ecb-5038-4aa8-a0fc-d4a6bf429d19}
2016-06-20 23:35:20, Error    CONX    Failed to add net component 80070002
2016-06-20 23:39:40, Error    SP    pSPRemoveUpgradeRegTree: failed to delete reg tree HKLM\SYSTEM\Setup\Upgrade[gle=0x00000005]
2016-06-20 23:39:54, Error    [0x080831] MIG    CSIAgent: Invalid xml format: FormatException: "id" attribute is mandatory. void __cdecl Mig::CMXEMigrationXml::LoadSupportedComponent(class UnBCL::XmlNode *,int,class Mig::CMXEMigrationXml *,class Mig::CMXEXmlComponent *)
2016-06-20 23:40:01, Error    [0x080831] MIG    CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{39CC25F3-AF21-4C42-854D-0524249F02CE} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2016-06-20 23:40:48, Error    [0x0808fe] MIG    Plugin {65cbf70b-1d78-4cac-8400-9acd65ced94a}: CreateProcess(s) failed. GLE = d
2016-06-20 23:42:18, Error    [0x0808fe] MIG    Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] Failed to get preferred homegroup with hr=0x80070490
2016-06-20 23:42:26, Error    [0x0808fe] MIG    Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: CBrgUnattend::CollectBridgeSettings failed: 0x1, 0
2016-06-20 23:42:36, Error    CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2016-06-20 23:42:36, Error    SP    CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2016-06-20 23:42:42, Error    IBSLIB OSRollbackService::CBootFilesRestoreCheckpoint::Finalize: Failed to backup BCD database from "F:\EFI\Microsoft\Boot\BCD" to "C:\$WINDOWS.~BT\Sources\Rollback\EFI\Microsoft\Boot\BCD".[gle=0x00000006]
2016-06-20 23:42:42, Error    [0x064199] IBSLIB SetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(6), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000006]
2016-06-20 23:42:42, Error    [0x06418a] IBSLIB RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint): threw exception.: class RollbackException: RollbackException: Error(6), CSystemVolumeSelectionCheckpoint: Failed to backup BCD database. void __cdecl OSRollbackService::CCheckpointImpressario::SetCheckpoint(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)
void __cdecl OSRollbackService::CBootFilesRestoreCheckpoint::Finalize(const unsigned short *,struct OSRollbackService::ICheckpointParameters *)[gle=0x00000006]
2016-06-20 23:42:42, Error    [0x06414e] IBSLIB RollbackSetCheckpoint(WinPEBootFilesRestoreCheckpoint) failed. Disabling Rollback.[gle=0x00000006]
2016-06-20 23:42:42, Error    SP    Error setting OS Switch Rollback checkpoint[gle=0x00000006]
2016-06-20 23:42:42, Error    SP    Operation failed: Update Boot Code. Error: 0x80004005[gle=0x000000b7]
2016-06-20 23:42:42, Error    MOUPG    MoSetupPlatform: Finalize reported failure![gle=0x000000b7]
2016-06-20 23:42:42, Error    MOUPG    MoSetupPlatform: Using action error code: [0x80004005][gle=0x000000b7]
2016-06-20 23:42:42, Error    MOUPG    CDlpActionFinalize::ExecuteSetupPlatformFinalize(1310): Result = 0x80004005[gle=0x000000b7]
2016-06-20 23:42:42, Error    MOUPG    CDlpActionFinalize::ExecuteRoutine(479): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CDlpActionImpl<class CDlpErrorImpl<class CDlpObjectInternalImpl<class CUnknownImpl<class IMoSetupDlpAction> > > >::Execute(441): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CDlpTask::ExecuteAction(3243): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CDlpTask::ExecuteActions(3397): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CDlpTask::Execute(1631): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CSetupManager::ExecuteTask(2024): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CSetupManager::ExecuteTask(1987): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CSetupManager::ExecuteInstallMode(804): Result = 0x80004005
2016-06-20 23:43:03, Error    MOUPG    CSetupManager::ExecuteDownlevelMode(389): Result = 0x80004005
2016-06-20 23:43:03, Error    SP    CSetupPlatform::ResurrectNewSystem: Cannot resurrect new system.: 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)[gle=0x00000002]
2016-06-20 23:43:05, Error    MOUPG    CSetupManager::Execute(232): Result = 0x80004005
2016-06-20 23:43:05, Error    MOUPG    CSetupHost::Execute(371): Result = 0x80004005

I have deleted the offending registry keys but they still come up in the failures; not sure why.

I ran a DISM online restorehealth and it was successful, and afterward, SFC found no violations.

Please advise!
Thanks,
Overkill

I'm hoping not to have to do that :/

I just had to do that on a Laptop I am fixing too , was stuck on .240 and would not let 318 or 420 on , even an in-place upgrade would not work ,got that annoying error message "Something went Wrong" etc etc each time.

Luckily on the backup drive they had, I had made a Windows system image taken before the Windows 8.1 to Win10 upgrade , so I applied the image and had 8.1 back , then used a fresh USB made with the Media Creator , to run setup from with in 8.1 which a least got the Owner some of his programs and pics etc back , hopefully the rest is on the WD Passport Drive. The Win10 Upgrade applied .164 , it then accepted the .420 update package applied directly (catalog file). Now just got to copy the Docs. Pics etc off the backup drive back.

Unfortunately, this machine shipped with 10 and I cannot revert.

I have an idea. Run the Windows Update Diagnostics!

Here:

Step 1: Click this link to download the Windows Update Troubleshooter (No virus. I promise. It's coming straight from the microsoft website)
http://go.microsoft.com/?linkid=9830262

Step 2: Now click on the downloaded file

Step 3: In the program that just opened, click next.

Step 4: Wait for it to detect things.

Step 5: Click the "Run Windows 10 Update Troubleshooter" Button

Step 6: Once the new window pops up, click next.

Step 7: Wait for it to detect any problems.

Step 8: Let it fix any errors found.

I hope I helped :)

P.S. For future reference about your P.C, please fill out the System Specs in your profile :)

Overkill said:

Unfortunately, this machine shipped with 10 and I cannot revert.

Then Swarfega maybe right , I was on the verge of a Clean install ,when I check the drive for images/backups but the Owner had never made any since he upgraded it to Win10 , I tried anything I could think of and some some off the Net and none of it helped.

You could revert to the Manufacturer's Image of 10 and immediately try .420 , but that would mean all their Bloatware too so a Clean install maybe better ?

I'd rather not wipe it because

• There's a lot of software/DLC to re-download and reinstall
• As an engineer, I would prefer to fix the problem rather than throw "durrr reinstall windows durrr" at it
• There are no other issues with the machine
• I spend most of my day troubleshooting issues like these for clients, and there are several clients that are too busy to be without their machines. It would be good to have an actual fix for this issue instead of dealing with the fallout of a clean install in the event I run into this in the future.
• The system shipped with Windows 10, and we don't use any 3rd party bullshit. I have been working in IT for 15 years, and would consider myself a competent technician (not just "that computer kid") for probably 10 of those years; Windows should not have any problems updating from a vanilla build with no "stupid" registry changes made to it.
• I'm sure I have more reasons, I just can't think of any right now

I have ran any/all Microsoft tools to fix this for me to no avail. I'll upload logs for anybody who wants to try and fix the issue when I have more time to work on this.

Windows 10 upgrades often fail because Windows update on the current system is stalled because of a failed upgrade, and the updates during setup of the new system timeout - because WUAUServ is called by setup in the early phases, and is busy. I think that changes to setup in RS-2 will avoid this problem, but not for 10240->10586.

There are 2 approaches - either reset windows update on the current system ( a bit pointless, because you are about to upgrade the system),
or simply turn off the network and run setup offline, turning on the network after installation to download the updates later. - you can either unplug the ethernet cable for wired systems, or disable the wireless adapter in the old system, or of course, turn off the router. You may find that your system takes a short while to update drivers and run any other Windows Updates post-setup.

If you want to do the first approach see:

Windows Update - Reset in Windows 10 - Windows 10 Forums