Upgrade fails, can't go back either. Such a mess. Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9System Information:Machine Name = Manufacturer = LENOVOModel = 20AMS4FC00HostOSArchitecture = x64FirmwareType = UEFIBiosReleaseDate = 20190219000000.000000+000BiosVendor = GIET95WW (2.45 )BiosVersion = GIET95WW (2.45 )HostOSVersion = 10.0.18356HostOSBuildString = 18356.1.amd64fre.19h1_release.190308-1607TargetOSBuildString = 10.0.18362.1 (19h1_release.190318-1202)HostOSLanguageId = 1033HostOSEdition = ProfessionalRegisteredAV = Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,FilterDrivers = bindflt,FsDepends,WdFilter,wcifs,wcifs,CldFlt,luafv,Wof,FileInfo,UpgradeStartTime = 23.03.2019 08:00:19FinalizeStartTime = 23.03.2019 08:31:52UpgradeEndTime = 23.03.2019 09:25:27UpgradeElapsedTime = 01:25:08CV = aJ3n+4/zaUCcm10JReportId = 8865774C-0CB0-4858-9400-947FFBA71ABFError: SetupDiag reports fatal migration plug-in failure.Setup Operation: Gather data, scope: EVERYTHINGPlug-in Error: 0x000005B4Plug-in Name and Action = Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll,{AE27C1A6-25F2-45FD-9A28-081B81F29E0A},Apartment.

With all the people reporting issues with the upgrade of this build, I'm wondering how it passed validation to become a 'slow ring' candidate...

Update to my previous replyI might've found a solution. I've upgraded successfully to 18362.1 just now. This potential solution might cause trouble later down the road though, but everything looks ok for me for now. DISM and SFC checks look good. I downloaded the upgrade package using the UUP dump tool. The tool downloads the files necessary and converts it into an ISO file. You can try the normal setup first by mounting the ISO file and running the setup executable. If it fails, use SetupDiag and see if the error is the same. If it's the same, you could try what I did. Here's where it could get tedious. I searched the sources folder and found a manifest file which contains some lines of configuration that look like this: <pluginclassId="{AE27C1A6-25F2-45FD-9A28-081B81F29E0A}"critical="Yes"file="Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll"offlineGather="Yes"offlineApply="Yes"/>So I figured I should try and modify that a bit. Particularly the "critical" value. Here, "critical" is set to "Yes". I think that states if the process is critical and if it fails somewhere, the whole setup needs to abort. If it's set to "No" instead, the process is not critical and if it fails somewhere, the setup just moves on. That's why this might not be 100% safe. Keep that in mind. I extracted the ISO file and located the manifest file. The manifest file is "\sources\replacementmanifests\appxdeploymentserver-replacement.man". I opened the file with Notepad++ and changed the "'Yes'" in front of "critical=" to "'No'", and saved the file. Then I use some ISO maker program (that allows me to do this for free) to make a new (barely) modified version of the installation ISO. It's time to install it. I paused Windows Update so that it doesn't interrupt the process (by automatically rebooting the PC which I don't want). I restarted my PC for good measure, and I mounted the new ISO and ran the setup executable. After a while (and after a buggy looking "Working on Updates" screen), my computer got past the error and upgraded successfully. I did a DISM and an SFC scan, and both resulted fine. But I'll see if there are any issues in UWP programs. Let me know if this works for any of you. Before doing this though, make sure you have a plan just in case the setup fails midway and can't roll back (such as a backup and a rescue media). Edit: UWP apps are not working. Settings app works, but a lot of other UWP apps are not working (including the store which is worrying). Can't fix it using PowerShell. Might want to roll back. I fixed the UWP situation. After searching for answers on the internet, broken apps are usable again. I took ownership of the WindowsApps folder inside Program Files and grant full control for my account and "ALL APPLICATION PACKAGES". This fixed the Microsoft Store. Then I opened Regedit and deleted all Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateChange subkeys (which I think acts as a blacklist for apps which failed the migration). This fixed the rest of the UWP apps. Edit: People have reported that the workaround is not fail-proof. Your UWP apps could get screwed up really bad. Microsoft has pulled 18362 from Windows Update. Please don't do the workaround as it is risky and might even raise the probability of doing a clean install later in the future. Thank you.

keaedwar https://www.uupdump.ml/

Aliffan I just update to version 18362.1 from 18356.16. Microsoft release 18356.21 early today. just click update from window. It take almost 2 hr update to 18362.1.

ioannispan I have the same problem, however I am able to go back to a previous version of Windows.

Upgrade from 18356.16 to 18362.1 fails | Microsoft Community Hub

35 Replies

Aliffan
Copper Contributor
Apr 03, 2019
Oh dear, I'm sorry for offering the bad workaround. Even though currently my computer's doing fine, I fear it might not be after the next upgrade hearing from Chaeska who failed the rollback. Taking ownership of the WindowsApps folder might not be wise at all.

I think it's best to wait for the next build to finish and roll out. Microsoft has pulled 18362 from Windows Update due to so many failing the upgrade. Again, I feel responsible for this and I'm sorry Chaeska TheNerdBoy. I'll be editing my previous reply to advise more people from using the workaround.
- TheNerdBoy
  Copper Contributor
  Apr 03, 2019
  AliffanNo worries from me, all is good. We do these things to make Windows better.
- Tony_Lin
  Copper Contributor
  Apr 03, 2019
  Aliffan
  I just update to version 18362.1 from 18356.16. Microsoft release 18356.21 early today. just click update from window. It take almost 2 hr update to 18362.1.
  - ioannispan
    Brass Contributor
    Apr 03, 2019
    Well, I was not offered any new update, neither have I seen any announcement about a new build.
    
    In the meantime while we wait for it, let's have a competition about how many times this last build was installed :-) Below mine - with updates paused in the past few days:
    
    Tony_Lin
Tony_Lin
Copper Contributor
Mar 26, 2019
One of my computer already upgrade to 18362.1 since this version release date. But my other two computers is unable to upgrade to 18362.1 I found most error message is like "Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9" Ｉam not sure which part cost failed issue ioannispan
ioannispan
Brass Contributor
Mar 25, 2019
With all the people reporting issues with the upgrade of this build, I'm wondering how it passed validation to become a 'slow ring' candidate...
Aliffan
Copper Contributor
Mar 25, 2019
Looks like a lot of these failures are caused by the same plugin (AppxUpgradeMigrationPlugin.dll) and the same process (Gather data, scope: EVERYTHING).

The process that the plugin is responsible to do is flagged as critical. When it fails to migrate just one app, the setup has to abort. I modified the ISO file so the process can be flagged as not critical, so the upgrade just continues even when it fails to migrate some apps.

But as I said in my previous reply, the migration really didn't work and a lot of apps (including the Microsoft Store) are broken after the upgrade (though some apps are fine). So I went through more difficult hoops to try and solve that issue, and now it's fixed.

Upgrading shouldn't be a hassle. Microsoft can only provide the same old troubleshooting steps which just doesn't work. I'm not sure if this is the fault of the plugin included in this upgrade package. The plugin might be unable to migrate some apps due to mess ups from previous upgrades. If you don't want to go through the tedious steps to try and upgrade to 18362.1, the next upgrade might not have the same problem and you could try and wait for it.
- rwa_trel
  Copper Contributor
  Mar 26, 2019
  Aliffan
  I have postponed updates for the coming 7 days and maybe MS comes with a new and working build.
rwa_trel
Copper Contributor
Mar 25, 2019
Hello,

I'm having the same issue.
SetupDiag gives the following report:

Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
System Information:
Machine Name = PROPHET
Manufacturer = Dell Inc.
Model = Latitude E5420
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20131226000000.000000+000
BiosVendor = A14
BiosVersion = A14
HostOSVersion = 10.0.18356
HostOSBuildString = 18356.1.amd64fre.19h1_release.190308-1607
TargetOSBuildString = 10.0.18362.1 (19h1_release.190318-1202)
HostOSLanguageId = 1043
HostOSEdition = Enterprise
RegisteredAV = Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,
FilterDrivers = bindflt,FsDepends,WdFilter,wcifs,wcifs,CldFlt,luafv,Wof,FileInfo,
UpgradeStartTime = 24-3-2019 08:24:53
FinalizeStartTime = 24-3-2019 09:52:12
UpgradeEndTime = 25-3-2019 10:50:31
UpgradeElapsedTime = 1.02:25:38
CV = iCeLZiTWEkqndoS3
ReportId = 8865774C-0CB0-4858-9400-947FFBA71ABF

Error: SetupDiag reports fatal migration plug-in failure.
Setup Operation: Gather data, scope: EVERYTHING
Plug-in Error: 0x000005B4
Plug-in Name and Action = Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll,{AE27C1A6-25F2-45FD-9A28-081B81F29E0A},Apartment.
Tony_Lin
Copper Contributor
Mar 25, 2019
I have download insider preview iso to my computer, I find these have two different version of build! one is 18361.1.190315-1726.19H1_RELEASE other one is 18362.1.190318-1202.19H1_RELEASE. I am still tried to upgrade 190318.
keaedwar
Copper Contributor
Mar 25, 2019
Same problem here too. It loops trying to update to 18362.1 which keeps failing.
ioannispan
Brass Contributor
Mar 24, 2019
Another thing is that it keeps trying to install it, just doesn't stop!
JoeEvil
Copper Contributor
Mar 24, 2019
ioannispan

Same problem here. Tried all the "standard" solutions, to no avail.

Also on a Lenovo. Thinkpad X1 tablet 3rd gen
Here's my log:

Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
System Information:
Machine Name = EVILONE
Manufacturer = LENOVO
Model = 20KJ0017US
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20190220000000.000000+000
BiosVendor = N1ZET73W(1.29 )
BiosVersion = N1ZET73W(1.29 )
HostOSVersion = 10.0.18356
HostOSBuildString = 18356.1.amd64fre.19h1_release.190308-1607
TargetOSBuildString = 10.0.18362.1 (19h1_release.190318-1202)
HostOSLanguageId = 1033
HostOSEdition = Professional
RegisteredAV = Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,Windows Defender,
FilterDrivers = WdFilter,wcifs,CldFlt,luafv,Wof,FileInfo,
UpgradeStartTime = 24/03/2019 05:23:16
FinalizeStartTime = 24/03/2019 05:45:38
UpgradeEndTime = 24/03/2019 16:13:25
UpgradeElapsedTime = 10:50:09
CV = qJ0Kvm20bkmbOA7W
ReportId = 8865774C-0CB0-4858-9400-947FFBA71ABF

Error: SetupDiag reports fatal migration plug-in failure.
Setup Operation: Gather data, scope: EVERYTHING
Plug-in Error: 0x000005B4
Plug-in Name and Action = Action,CMXEPlugin,C:\$WINDOWS.~BT\Sources\ReplacementManifests,Microsoft-Windows-AppX-Deployment-Server\AppxUpgradeMigrationPlugin.dll,{AE27C1A6-25F2-45FD-9A28-081B81F29E0A},Apartment.
Neil78785
Copper Contributor
Mar 24, 2019
have that problem aswell, have tried 3 times to update but nothing mines a asus though

Forum Discussion

Upgrade from 18356.16 to 18362.1 fails

35 Replies

Resources