Not Found

The requested URL index.php was not found on this server.


Apache/2.2.22 (Linux) Server at Port 80
1 War Stories: My Build 18908 Upgrade – Win10.Guru
Go to ...

RSS Feed

War Stories: My Build 18908 Upgrade


Until now, I have always managed to upgrade to new Insider builds on my HP ProBook 470 G5 laptop. I have sometimes had difficulties and have been forced to use various workarounds, but it has ultimately worked, every time.

Last week and the release of build 18908 changed that. I did everything I could think of, but each upgrade attempt failed. The first try was a “standard” one, let Windows Update find the upgrade, download and install it, and restart. After two more restarts, Windows Setup told me it was reverting the changes.

Back on desktop, checking logs in C:\$WINDOWS.~BT\Sources\, this is what I found (click expand source to see the code):

2019-05-30 21:40:47, Error DU DU::CDUSession::Search: Failed to set WU internal configuration property for targeted scans. hr = 0x80070057
2019-05-30 21:47:22, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2019-05-30 21:48:20, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2019-05-30 21:48:23, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2019-05-30 21:51:20, Error CSetupAutomation::Resurrect: File not found: C:\$WINDOWS.~BT\Sources\Panther\automation.dat[gle=0x00000002]
2019-05-30 21:51:20, Error SP CSetupPlatform::ResurrectAutomation: Failed to resurrect automation: 0x80070002[gle=0x00000002]
2019-05-30 21:57:10, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2019-05-30 21:57:18, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(595)\shmig.dll!00007FFDDA5A7394: (caller: 00007FFDDA5A750E) ReturnHr(1) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(618)\shmig.dll!00007FFDDA5A752A: (caller: 00007FFDDA5A5438) LogHr(1) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(595)\shmig.dll!00007FFDDA5A7394: (caller: 00007FFDDA5A750E) ReturnHr(2) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(618)\shmig.dll!00007FFDDA5A752A: (caller: 00007FFDDA5A5438) LogHr(2) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(595)\shmig.dll!00007FFDDA5A7394: (caller: 00007FFDDA5A750E) ReturnHr(3) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(618)\shmig.dll!00007FFDDA5A752A: (caller: 00007FFDDA5A5438) LogHr(3) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(595)\shmig.dll!00007FFDDA5A7394: (caller: 00007FFDDA5A750E) ReturnHr(4) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {526D451C-721A-4b97-AD34-DCE5D8CD22C5}: [shmig] onecoreuap\internal\shell\inc\private\schemacachehelpers.cpp(618)\shmig.dll!00007FFDDA5A752A: (caller: 00007FFDDA5A5438) LogHr(4) tid(46e8) 8007139F The group or resource is not in the correct state to perform the requested operation.

2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: offline key (new) = '$OFFLINE_RW_BCE441CA$SYSTEM\Setup\Upgrade\Bridge'
2019-05-30 21:59:37, Error [0x0808fe] MIG Plugin {ee036dc0-f9b7-4d2d-bb94-3dd3102c5804}: BRIDGEMIG: ParseRegistryIfBridgeExists: query bridge presence key failed 0x139f, bridge present = 0
2019-05-30 21:59:37, Error [0x08038d] MIG Failure while calling IPostApply->ApplySuccess for Plugin={ServerPath="Microsoft-Windows-DirectoryServices-ADAM-Client\adammigrate.dll", CLSID={43CCF250-2A74-48c6-9620-FC312EC475D6}, ThreadingModel=Apartment}. Error: 0x80070002
2019-05-30 21:59:37, 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]
2019-05-30 22:01:18, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2019-05-30 22:02:47, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!RemoveObsoleteCHSHKLMRegkey - fail to open regkey (software\Microsoft\CTF\TIP\{E429B25A-E5D3-4D1F-9BE3-0C608477E3A1}\LanguageProfile\0x00000804) = 2
2019-05-30 22:02:47, Error [0x0808fe] MIG Plugin {0b23c863-4410-4153-8733-a60c9b1990fb}: TableTextServiceMig!ApplySuccess() remove HKLM Registries error
2019-05-30 22:08:00, Error MOUPG Finalize: Error obtaining Update and Shutdown Key: [0x80070002][gle=0x000000b7]
2019-05-30 22:08:08, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume6\EFI\Microsoft\Boot (kd_*_*.dll). Last Error = 0x6[gle=0x00000006]
2019-05-30 22:08:08, Error SP BFSVC: Error copying boot debugging files from C:\$WINDOWS.~BT\Sources\system32 to \\?\GLOBALROOT\Device\HarddiskVolume6\EFI\Microsoft\Boot (kdstub.dll). Last Error = 0x6[gle=0x00000006]
2019-05-30 22:09:46, Error MIG CoCreateInstance(CoClassIdentityStore) failed. hr = 0x800401F0[gle=0x00000534]
2019-05-30 22:09:46, Error [0x080a7b] MIG Failed to build the connected providers mappings[gle=0x00000534]
2019-05-30 22:09:47, Error MIG CoCreateInstance(CoClassIdentityStore) failed. hr = 0x800401F0[gle=0x00000534]
2019-05-30 22:09:47, Error [0x080a7b] MIG Failed to build the connected providers mappings[gle=0x00000534]
2019-05-30 22:13:43, Error [SetupPlatform.exe] winreHashWimFile: Failed to hash [C:\WINDOWS\System32\Recovery]: 0x5
2019-05-30 22:14:25, Error MIG Ignoring replacement manifest with no settingsVersionRange or versionRange attribute in migration element: Microsoft-Windows-Container-Manager
2019-05-30 22:14:38, Error [0x080831] MIG CSIAgent: Invalid xml format: FormatException: Component with display name: Plugin/{C939EC0F-2F56-4CE8-AF56-2336596A5FA7} already loaded __cdecl Mig::CMXEMigrationXml::CMXEMigrationXml(class Mig::CPlatform *,class UnBCL::String *,class UnBCL::XmlDocument *,class UnBCL::String *,class UnBCL::String *)
2019-05-30 22:15:28, Error SP Could not create the service, error: 0x00000431[gle=0x00000431]
2019-05-30 22:15:28, Error SP Could not create the service, error: 0x00000431[gle=0x00000431]

A hypothetical question to you geeks in Redmond designing these error messages: How much do you think the preceding error log helps me when it comes to troubleshooting the issues involved?

Anyway, my next try also ended the same: in failure. But this time I used a build 18908 ISO made with UUP Dump. I also disabled both Windows Defender and Firewall. That’s because Defender (like any other AV program) is known to cause upgrades to fail. But the same result ensued, although that install went a bit further this time. Whereas the first attempt failed at under 40%, this one went to over 50% of the way toward completion.

My third attempt to upgrade followed. In addition to disabling the AV and firewall, I disabled all third party services. But again, the upgrade failed. The fourth method I tried is something that has saved my behind several times, by allowing the laptop to upgrade. I booted to OOBE with the following command:

%windir%\system32\sysprep\syspre.exe /oobe /reboot

Restarting to OOBE is quite practical in certain troubleshooting scenarios. It preserves all user profiles, software, settings and such, but offers a clean boot, stopping before any user account data, start-up items, third party services and general Windows settings changed by users have been loaded. When OOBE stops on the region selection screen, pressing SHIFT + F10 opens Command Prompt and activates WIN-key shortcuts (WIN + E to open Explorer and so on). Command Prompt can be closed immediately. In this troubleshooting scenario, it was only needed to activate keyboard shortcuts.

OK. I ran WIN + E to open File Explorer, I mounted the 18908 ISO and ran setup.exe to start the upgrade process. The upgrade installed, and the laptop restarted. And, again, it failed at about 50%.

I decided to give it one more try. I created an upgrade task sequence in an existing deployment share inside the MDT Deployment Workbench, importing 18908 as the OS to be used. Running the task sequence, the task was run from a share on my  NAS. I was sure it would  finally work. No, no such luck: the upgrade failed immediately after the first restart.

I gave up, decided to wipe both the SSD and HDD and deploy a fresh, clean custom image I built in a Hyper-V VM. Everything went smoothly, and I am now running build 18908.

To check that there were no underlying issues which could prevent a next upgrade, I ran a repair install from the 18908 ISO. As you know, a repair install is nothing but an in-place upgrade exactly like build or feature upgrades. Its only distinguishing feature it that it’s done using install media for the same  Windows version and build as the current underlying Windows installation.

The repair / in-place install worked fine. That’s why I believe I will have no issues at least for the next few upgrades. But I still have absolutely no clue why this upgrade from 18898 to 18908 failed, no matter which upgrade approach I tried. I’m glad the VM deployment technique worked instead!

Kari

Author: Kari Finn

A former Windows Insider MVP, Kari started in computing in the mid 80’s writing code for VAX / VMS systems. Since then, he’s worked in a variety of IT positions. He specializes in Windows image capture, customization, repair and deployment as well as Hyper-V virtualization. Kari is a proud Team Member at number #1 Windows site TenForums.com.

Leave a Reply