Home

Upgrade from 18356.16 to 18362.1 fails

%3CLINGO-SUB%20id%3D%22lingo-sub-383004%22%20slang%3D%22en-US%22%3EUpgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-383004%22%20slang%3D%22en-US%22%3E%3CP%3EUpgrade%20fails%2C%20can't%20go%20back%20either.%20Such%20a%20mess.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMatching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%26nbsp%3B%3CBR%20%2F%3EManufacturer%20%3D%20LENOVO%3CBR%20%2F%3EModel%20%3D%2020AMS4FC00%3CBR%20%2F%3EHostOSArchitecture%20%3D%20x64%3CBR%20%2F%3EFirmwareType%20%3D%20UEFI%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020190219000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%20GIET95WW%20(2.45%20)%3CBR%20%2F%3EBiosVersion%20%3D%20GIET95WW%20(2.45%20)%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.18356%3CBR%20%2F%3EHostOSBuildString%20%3D%2018356.1.amd64fre.19h1_release.190308-1607%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.1%20(19h1_release.190318-1202)%3CBR%20%2F%3EHostOSLanguageId%20%3D%201033%3CBR%20%2F%3EHostOSEdition%20%3D%20Professional%3CBR%20%2F%3ERegisteredAV%20%3D%20Windows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2C%3CBR%20%2F%3EFilterDrivers%20%3D%20bindflt%2CFsDepends%2CWdFilter%2Cwcifs%2Cwcifs%2CCldFlt%2Cluafv%2CWof%2CFileInfo%2C%3CBR%20%2F%3EUpgradeStartTime%20%3D%2023.03.2019%2008%3A00%3A19%3CBR%20%2F%3EFinalizeStartTime%20%3D%2023.03.2019%2008%3A31%3A52%3CBR%20%2F%3EUpgradeEndTime%20%3D%2023.03.2019%2009%3A25%3A27%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%2001%3A25%3A08%3CBR%20%2F%3ECV%20%3D%20aJ3n%2B4%2FzaUCcm10J%3CBR%20%2F%3EReportId%20%3D%208865774C-0CB0-4858-9400-947FFBA71ABF%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20SetupDiag%20reports%20fatal%20migration%20plug-in%20failure.%3CBR%20%2F%3ESetup%20Operation%3A%20Gather%20data%2C%20scope%3A%20EVERYTHING%3CBR%20%2F%3EPlug-in%20Error%3A%200x000005B4%3CBR%20%2F%3EPlug-in%20Name%20and%20Action%20%3D%20Action%2CCMXEPlugin%2CC%3A%5C%24WINDOWS.~BT%5CSources%5CReplacementManifests%2CMicrosoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%2C%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%2CApartment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401148%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401148%22%20slang%3D%22en-US%22%3E%3CP%3EUpdating%20to%2010.0.18362.30%20now...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUPDATE%3A%20everything%20is%20working....%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-401144%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401144%22%20slang%3D%22en-US%22%3ESame%20with%20me.%3CBR%20%2F%3EOn%202019-04-03%20Update%20Installed%2010.0.18356.16%3CBR%20%2F%3EOn%202019-04-04%20Update%20Installed%2010.0.18362.30%3CBR%20%2F%3ENow%20everything%20is%20up%20to%20date%20and%20working.%20Back%20on%20track.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-396163%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-396163%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307804%22%20target%3D%22_blank%22%3E%40TheNerdBoy%3C%2FA%3E%26nbsp%3BA%20miracle%20happened!%2018362.30%20just%20rolled%20out%20today%20and%20it%20fixed%20everything...%20My%20standard%20apps%20are%20back%2C%20the%20Store%20works%20-%20some%20Apps%20failed%20updating%20due%20to%20some%20weird%20errors%20but%20after%20reinstalling%20them%20they%20now%20work%20just%20fine.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394105%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394105%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3BGot%20the%20update%20as%20well%20since%20I%20rolled%20back%20from%20the%20botched%20%22hacked%22%20update.%20It%20installed%20successfully%20but%20it%20obviously%20didn't%20fix%20my%20FUBAR%20WindowsApps.%3C%2FP%3E%3CP%3EI'll%20have%20to%20reinstall%20at%20some%20point%20when%20I%20actually%20have%20the%20time%20and%2For%20the%20messed%20up%20Apps%20start%20impacting%20me.%3C%2FP%3E%3CP%3ELuckily%20I%20didn't%20have%20anything%20critical%20installed.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394096%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394096%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20I%20switched%20back%20to%20the%20Slow%20ring%20to%20get%20the%20%22good%20state%22%20update...%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394059%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394059%22%20slang%3D%22en-US%22%3E%3CP%3EBtw%2C%20I%20just%20read%20the%20announcement%20%3CA%20href%3D%22https%3A%2F%2Fblogs.windows.com%2Fwindowsexperience%2F2019%2F03%2F20%2Fannouncing-windows-10-insider-preview-build-18362%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehere%3C%2FA%3E%20but%20I%20don't%20understand%20why%20they%20only%20mention%20the%20Slow%20ring%20-%20what%20about%20us%20who%20are%20on%20the%20Fast%20ring%20and%20we%20have%20upgrade%20issues%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E%3CSTRONG%3EUPDATE%204%2F2%3A%3C%2FSTRONG%3E%26nbsp%3BWe%20have%20released%20Build%2018356.21%20(KB4496796)%20to%20Windows%20Insiders%20%3CSTRONG%3Ein%20the%20Slow%20ring%3C%2FSTRONG%3E%20who%20are%20currently%20on%20Build%2018356.16.%20This%20update%20will%20get%20Insiders%20who%20are%20on%20Build%2018356.16%20back%20into%20a%20good%20state%20so%20they%20can%20update%20to%20Build%2018362.%20We%20are%20allowing%20a%20few%20days%20for%20this%20update%20to%20roll%20out%20before%20offering%20Build%2018362%20%E2%80%93%20so%20that%20means%20Insiders%20will%20still%20not%20see%20Build%2018362%20offered%20after%20updating%20to%20Build%2018356.21.%20But%20stay%20tuned!%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-394049%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394049%22%20slang%3D%22en-US%22%3E%3CP%3EWell%2C%20I%20was%20not%20offered%20any%20new%20update%2C%20neither%20have%20I%20seen%20any%20announcement%20about%20a%20new%20build.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20meantime%20while%20we%20wait%20for%20it%2C%20let's%20have%20a%20competition%20about%20how%20many%20times%20this%20last%20build%20was%20installed%20%3A)%3C%2Fimg%3E%20Below%20mine%20-%20with%20updates%20paused%20in%20the%20past%20few%20days%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307106%22%20target%3D%22_blank%22%3E%40Tony_Lin%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393993%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393993%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3ENo%20worries%20from%20me%2C%20all%20is%20good.%20We%20do%20these%20things%20to%20make%20Windows%20better.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393767%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393767%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20update%20to%20version%2018362.1%20from%2018356.16.%20Microsoft%20release%2018356.21%20early%20today.%20just%20click%20update%20from%20window.%20It%20take%20almost%202%20hr%20update%20to%2018362.1.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393624%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393624%22%20slang%3D%22en-US%22%3E%3CP%3EOh%20dear%2C%20I'm%20sorry%20for%20offering%20the%20bad%20workaround.%20Even%20though%20currently%20my%20computer's%20doing%20fine%2C%20I%20fear%20it%20might%20not%20be%20after%20the%20next%20upgrade%20hearing%20from%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F312724%22%20target%3D%22_blank%22%3E%40Chaeska%3C%2FA%3E%20who%20failed%20the%20rollback.%26nbsp%3BTaking%20ownership%20of%20the%20WindowsApps%20folder%20might%20not%20be%20wise%20at%20all.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20think%20it's%20best%20to%20wait%20for%20the%20next%20build%20to%20finish%20and%20roll%20out.%20Microsoft%20has%20pulled%26nbsp%3B18362%20from%20Windows%20Update%20due%20to%20so%20many%20failing%20the%20upgrade.%20Again%2C%20I%20feel%20responsible%20for%20this%20and%20I'm%20sorry%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F312724%22%20target%3D%22_blank%22%3E%40Chaeska%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307804%22%20target%3D%22_blank%22%3E%40TheNerdBoy%3C%2FA%3E.%20I'll%20be%20editing%20my%20previous%20reply%20to%20advise%20more%20people%20from%20using%20the%20workaround.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393389%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393389%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20key%20is%20disabling%20Windows%20Search%20in%20services.msc%20then%20applying%20the%20update.%26nbsp%3B%20It%20will%20work%20fine%20then.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393327%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393327%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F312724%22%20target%3D%22_blank%22%3E%40Chaeska%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20tried%20the%20windows%20folder%20permission%2C%20auditing%2C%20etc.%20I%20even%20went%20as%20far%20as%20deleting%20the%20WindowsApps%20folder%20and%20copying%20it%20from%20a%20laptop%2C%20as%20well%20as%20the%20registry%20key.%20I%20ran%20Ubuntu%20from%20a%20flash%20drive%20to%20do%20that.%3C%2FP%3E%3CP%3ERolling%20back%20to%20the%20previous%20build%20did%20nothing%20but%20make%20things%20worse%20for%20me.%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20is%20something%20in%20the%20code%20of%20the%20OS%20that%20is%20written%20differently%20than%20before%20that%20is%20cause%20this.%3C%2FP%3E%3CP%3EFor%20now%2C%20updates%20are%20on%20pause.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393170%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393170%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307804%22%20target%3D%22_blank%22%3E%40TheNerdBoy%3C%2FA%3E%26nbsp%3BThanks%20for%20the%20confirmation%20that%20I%20wasn't%20being%20the%20only%20silly%20person%20to%20have%20failed%20in%20such%20a%20way.%3C%2FP%3E%3CP%3EIsn't%20there%20any%20way%20of%20getting%20the%20Windows%20Store%20package%20from%20a%20healthy%20installation%20and%20then%20installing%20it%20manually%3F%20I%20feel%20that%20would%20solve%20the%20problem.%3C%2FP%3E%3CP%3EMeanwhile%20I%20rolled%20back%20to%20the%20previous%20version%20of%20Windows%20and%20needless%20to%20say%20that%20didn't%20help%20either...%3C%2FP%3E%3CP%3E%3CSTRONG%3EUpdate%3A%3C%2FSTRONG%3E%26nbsp%3BSomething%20very%20weird%20is%20going%20on%20with%20the%20WindowsApps%20folder.%20No%20matter%20what%20permissions%20I%20set%20on%20it%20I%20cannot%20do%20anything%20with%20it%20-%20create%2C%20modify%20files%20or%20anything...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393132%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393132%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20certainly%20wrong%20as%20well.%20I%20did%20get%20it%20to%20upgrade%20and%20did%20get%20%3CEM%3Esome%20%3C%2FEM%3Ewindows%20apps%20to%20work%20again.%20But%20still%20couldn't%20get%20the%20Store%20to%20work.%20Plus%20from%20that%2C%20it%20messed%20up%20a%20few%20other%20things%20as%20well%20-%20all%20things%20Abode.%20I%20ended%20up%20having%20to%20do%20a%20fresh%20install%20to%20just%20get%20things%20working%20again.%20That%20was%20a%20pain.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThough%20this%20new%20build%20did%20present%20some%20really%20nice%20things%2C%20like%20the%20file%20folder%20sorting%20is%20much%20much%20displayed.%20But%20for%20anyone%20reading%2C%20I%20HIGHLY%20recommend%20DO%20NOT%20upgrade%20to%20this%20new%20build%2C%20wait%20for%20MS%20to%20fix%20it.%20They%20did%20pull%20the%20build%20from%20the%20servers%20already.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-393120%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-393120%22%20slang%3D%22en-US%22%3E%3CP%3ESo%2C%20I%20managed%20to%20Upgrade%20to%2018362.1%20after%20having%20had%20the%20same%20problem%20everyone%20discussed%20but%20now%20I%20seem%20to%20have%20messed%20up%20my%20WindowsApps%20beyond%20repair%20-%20at%20least%20none%20of%20the%20solutions%20listed%20worked%20for%20me%20so%20far.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20I%20did%20was%3A%20Used%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.uupdump.ml%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.uupdump.ml%2F%3C%2FA%3E%26nbsp%3Bto%20get%20a%20dump%20of%20the%20update%2C%20edit%20the%20manifest%20file%20as%20described%20in%20the%20thread%2C%20repackage%20the%20ISO%2C%20mount%20it%2C%20install%20the%20update%20et%20voila.%20So%20far%20so%20good.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20my%20UWP%20got%20messed%20up%2C%20so%20I%20ran%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EGet-AppXPackage%20-AllUsers%20%7C%20Foreach%20%7BAdd-AppxPackage%20-DisableDevelopmentMode%20-Register%20%E2%80%9C%24(%24_.InstallLocation)%5CAppXManifest.xml%E2%80%9D%7D%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3Eas%20an%20admin%20and%20this%20fixed%20SOME%20of%20the%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%2C%20Microsoft%20Store%20wasn't%20working%2C%20e.g.%20the%20Calculator%20app%20among%20others%20wasn't%20starting%20(only%20getting%20vague%20error%20messages%20like%20%22There%E2%80%99s%20a%20problem%20with%20Calculator.%20Contact%20your%20system%20administrator%20about%20repairing%20or%20reinstalling%20it.%22)%26nbsp%3B%20and%20so%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EChanging%20permissions%20(taking%20ownership%2C%20modifying%20access%20control)%20on%20WindowsApps%20didn't%20help.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EModifying%20the%20registry%20(deleting%20everything%20under%26nbsp%3B%3CSTRONG%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CAppModel%5CStateChange)%26nbsp%3B%3C%2FSTRONG%3Eas%20described%20above%20seems%20to%20have%20made%20the%20situation%20worse%20-%20some%20apps%20that%20were%20working%20before%20stopped%20working%20and%20now%20I%20basically%20have%20to%20re-apply%20the%20PowerShell-command%20I%20mentioned%20every%20time%20to%20semi-fix%20everything.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMicrosoft%20Store%20and%20all%20non-working%20apps%20are%20greyed-out%20in%20the%20Start%20Menu...%20Tried%20purging%20the%20MS%20Store%20cache%20but%20it%20gives%20me%20an%20error%20that%20it%20cannot%20start%20the%20Store.%20Creating%20another%20user%20account%20didn't%20fix%20it%20either.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDISM%20and%20SFC%20don't%20recognize%20any%20problems...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20slowly%20running%20out%20of%20ideas%20how%20to%20fix%20the%20apps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389738%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389738%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F302308%22%20target%3D%22_blank%22%3E%40keaedwar%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fwww.uupdump.ml%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.uupdump.ml%2F%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389702%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389702%22%20slang%3D%22en-US%22%3EWhere%20does%20uup%20come%20from%3F%20I%20can't%20find%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-389136%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-389136%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20suggestions...%26nbsp%3B%3C%2FP%3E%3CP%3EI%20downloaded%2018362.1%20using%20uup%20and%20created%20iso%20on%20usb%20thumb%20drive...%3C%2FP%3E%3CP%3EModified%20Manifest%20file%20to%20%22No%22...%3C%2FP%3E%3CP%3ERan%20%22Setup%22%20on%20usb...%3C%2FP%3E%3CP%3EUpdated%20without%20problems...%3C%2FP%3E%3CP%3ERan...%20SFC%20and%20DISM...%20shows%20NO%20corrupt%20System%20Files...%3C%2FP%3E%3CP%3EEverything%20seems%20to%20WORK%20OK.!!!%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20Again.!!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20NOTE...%26nbsp%3B%3C%2FP%3E%3CP%3EFound%20a%20few%20app%20problems....%20and%20another%20%22solution%22...%3C%2FP%3E%3CP%3ESo...%20I%20changed%20the%20manifest%20file%20answer%20back%20to%20%22YES%22%20on%20the%20thumb%2Fflash%20drive%20(iso)...%3C%2FP%3E%3CP%3Ethen...%20I%20Applied%20%22solution%22%20from%20Conversation...%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306954%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Esjfwhite0823%26nbsp%3B%3C%2FA%3E%26nbsp%3B%3CSPAN%3Ereplied%20to%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F307804%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3ETheNerdBoy%3C%2FA%3E%3CSPAN%3E%26nbsp%3B--%26nbsp%3B%3C%2FSPAN%3E%3CSPAN%20class%3D%22DateTime%20lia-message-posted-on%20lia-component-common-widget-date%22%3E%3CSPAN%20class%3D%22local-friendly-date%22%3Eyesterday%20(04%2F02%2F2019)%3C%2FSPAN%3E%3C%2FSPAN%3E%3C%2FP%3E%3CDIV%20class%3D%22lia-quilt-row%20lia-quilt-row-header%22%3E%3CDIV%20class%3D%22lia-quilt-column%20lia-quilt-column-12%20lia-quilt-column-right%20lia-quilt-column-header-right%22%3E%3CDIV%20class%3D%22lia-quilt-column-alley%20lia-quilt-column-alley-right%22%3E%3CDIV%20class%3D%22lia-menu-navigation-wrapper%20lia-menu-action%20lia-component-message-view-widget-action-menu%22%3E%3CDIV%20class%3D%22lia-menu-navigation%22%3E%3CDIV%20class%3D%22dropdown-default-item%22%3Ewhich%20stated...%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CDIV%20class%3D%22lia-quilt-row%20lia-quilt-row-main%22%3E%3CDIV%20class%3D%22lia-quilt-column%20lia-quilt-column-18%20lia-quilt-column-left%20lia-quilt-column-main-left%22%3E%3CDIV%20class%3D%22lia-quilt-column-alley%20lia-quilt-column-alley-left%22%3E%3CDIV%20class%3D%22lia-message-body%20lia-component-message-view-widget-body%20lia-component-body-signature-highlight-escalation%20lia-component-message-view-widget-body-signature-highlight-escalation%22%3E%3CDIV%20class%3D%22lia-message-body-content%22%3E%3CP%3E%22The%20key%20is%20disabling%20Windows%20Search%20in%20services.msc%20then%20applying%20the%20update.%26nbsp%3B%20It%20will%20work%20fine%20then.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20time%20Rerunning%20and%20%22ReInstalling%22%20the%20(unmodified)%2018362.1%20%22Update%22%20(was%20unable%20to%20go%20back%20to%2018356.16)...%20Completed%20without%20error...%26nbsp%3B%20Seems%20to%20be%20working%20OK...%26nbsp%3B%3C%2FP%3E%3CP%3Eexcept%20for%20apps%20%22won't%20open%22%20error%20for...%20%22Paint%203D%22%2C%20%22Tips%22%2C%20%22Voice%20Recorder%22%2C%20and%20%22XBox%22...%20!%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway...%20It's%20About%20time%20for%20a%20Windows%20Fresh%2FClean%20Install.!%3F%26nbsp%3B%20%3AD%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388522%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388522%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20postponed%20updates%20for%20the%20coming%207%20days%20and%20maybe%20MS%20comes%20with%20a%20new%20and%20working%20build.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388422%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388422%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20of%20my%20computer%20already%20upgrade%20to%2018362.1%20since%20this%20version%20release%20date.%20But%20my%20other%20two%20computers%20is%20unable%20to%20upgrade%20to%2018362.1%20I%20found%20most%20error%20message%20is%20like%20%22Matching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%22%26nbsp%3B%EF%BC%A9am%20not%20sure%20which%20part%20cost%20failed%20issue%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388393%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388393%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3E%2C%20that%20mostly%20worked%20for%20me.%20I%20did%20get%20it%20upgrade%20with%20the%20critical%20%3D%22no%22.%20Now%20I'm%20having%20issues%20with%20Microsoft%20apps.%20I%20did%20what%20you%20suggested%2C%20but%20there%20keeps%20coming%20up%20files%20that%20I%20don't%20have%20access%20to.%20But%20ah%20haaaa.%20I%20put%20this%20is%20PowerShell%20as%20admin%20and%20it%20now%20all%20works%3A%20%3CSTRONG%3EGet-AppXPackage%20-AllUsers%20%7C%20Foreach%20%7BAdd-AppxPackage%20-DisableDevelopmentMode%20-Register%20%E2%80%9C%24(%24_.InstallLocation)%5CAppXManifest.xml%E2%80%9D%7D%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386993%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386993%22%20slang%3D%22en-US%22%3E%3CP%3EWith%20all%20the%20people%20reporting%20issues%20with%20the%20upgrade%20of%20this%20build%2C%20I'm%20wondering%20how%20it%20passed%20validation%20to%20become%20a%20'slow%20ring'%20candidate...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386775%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386775%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20a%20lot%20of%20these%20failures%20are%20caused%20by%20the%20same%20plugin%20(%3CSPAN%3EAppxUpgradeMigrationPlugin.dll)%3C%2FSPAN%3E%20and%20the%20same%20process%20(%3CSPAN%3EGather%20data%2C%20scope%3A%20EVERYTHING)%3C%2FSPAN%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20process%20that%20the%20plugin%20is%20responsible%20to%20do%20is%20flagged%20as%20critical.%20When%20it%20fails%20to%20migrate%20just%20one%20app%2C%20the%20setup%20has%20to%20abort.%20I%20modified%20the%20ISO%20file%20so%20the%20process%20can%20be%20flagged%20as%20not%20critical%2C%20so%20the%20upgrade%20just%20continues%20even%20when%20it%20fails%20to%20migrate%20some%20apps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20as%20I%20said%20in%20my%20previous%20reply%2C%20the%20migration%20really%20didn't%20work%20and%20a%20lot%20of%20apps%20(including%20the%20Microsoft%20Store)%20are%20broken%20after%20the%20upgrade%20(though%20some%20apps%20are%20fine).%20So%20I%20went%20through%20more%20difficult%20hoops%20to%20try%20and%20solve%20that%20issue%2C%20and%20now%20it's%20fixed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpgrading%20shouldn't%20be%20a%20hassle.%20Microsoft%20can%20only%20provide%20the%20same%20old%20troubleshooting%20steps%20which%20just%20doesn't%20work.%20I'm%20not%20sure%20if%20this%20is%20the%20fault%20of%20the%20plugin%20included%20in%20this%20upgrade%20package.%20The%20plugin%20might%20be%20unable%20to%20migrate%20some%20apps%20due%20to%20mess%20ups%20from%20previous%20upgrades.%20If%20you%20don't%20want%20to%20go%20through%20the%20tedious%20steps%20to%20try%20and%20upgrade%20to%26nbsp%3B18362.1%2C%20the%20next%20upgrade%20%3CEM%3Emight%26nbsp%3B%3C%2FEM%3Enot%20have%20the%20same%20problem%20and%20you%20could%20try%20and%20wait%20for%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386643%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386643%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20having%20the%20same%20issue.%3C%2FP%3E%3CP%3ESetupDiag%20gives%20the%20following%20report%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EMatching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%20PROPHET%3CBR%20%2F%3EManufacturer%20%3D%20Dell%20Inc.%3CBR%20%2F%3EModel%20%3D%20Latitude%20E5420%3CBR%20%2F%3EHostOSArchitecture%20%3D%20x64%3CBR%20%2F%3EFirmwareType%20%3D%20UEFI%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020131226000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%20A14%3CBR%20%2F%3EBiosVersion%20%3D%20A14%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.18356%3CBR%20%2F%3EHostOSBuildString%20%3D%2018356.1.amd64fre.19h1_release.190308-1607%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.1%20(19h1_release.190318-1202)%3CBR%20%2F%3EHostOSLanguageId%20%3D%201043%3CBR%20%2F%3EHostOSEdition%20%3D%20Enterprise%3CBR%20%2F%3ERegisteredAV%20%3D%20Windows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2C%3CBR%20%2F%3EFilterDrivers%20%3D%20bindflt%2CFsDepends%2CWdFilter%2Cwcifs%2Cwcifs%2CCldFlt%2Cluafv%2CWof%2CFileInfo%2C%3CBR%20%2F%3EUpgradeStartTime%20%3D%2024-3-2019%2008%3A24%3A53%3CBR%20%2F%3EFinalizeStartTime%20%3D%2024-3-2019%2009%3A52%3A12%3CBR%20%2F%3EUpgradeEndTime%20%3D%2025-3-2019%2010%3A50%3A31%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%201.02%3A25%3A38%3CBR%20%2F%3ECV%20%3D%20iCeLZiTWEkqndoS3%3CBR%20%2F%3EReportId%20%3D%208865774C-0CB0-4858-9400-947FFBA71ABF%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20SetupDiag%20reports%20fatal%20migration%20plug-in%20failure.%3CBR%20%2F%3ESetup%20Operation%3A%20Gather%20data%2C%20scope%3A%20EVERYTHING%3CBR%20%2F%3EPlug-in%20Error%3A%200x000005B4%3CBR%20%2F%3EPlug-in%20Name%20and%20Action%20%3D%20Action%2CCMXEPlugin%2CC%3A%5C%24WINDOWS.~BT%5CSources%5CReplacementManifests%2CMicrosoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%2C%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%2CApartment.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386527%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386527%22%20slang%3D%22en-US%22%3EI%20have%20download%20insider%20preview%20iso%20to%20my%20computer%2C%20I%20find%20these%20have%20two%20different%20version%20of%20build!%20one%20is%2018361.1.190315-1726.19H1_RELEASE%20other%20one%20is%2018362.1.190318-1202.19H1_RELEASE.%20I%20am%20still%20tried%20to%20upgrade%20190318.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386500%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386500%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20problem%20here%20too.%26nbsp%3B%20It%20loops%20trying%20to%20update%20to%2018362.1%20which%20keeps%20failing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386465%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386465%22%20slang%3D%22en-US%22%3E%3CP%3EAnother%20thing%20is%20that%20it%20keeps%20trying%20to%20install%20it%2C%20just%20doesn't%20stop!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20534px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F99081i493E16C4861526E1%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Picture1.png%22%20title%3D%22Picture1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386445%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386445%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20problem%20here.%20Tried%20all%20the%20%22standard%22%20solutions%2C%20to%20no%20avail.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAlso%20on%20a%20Lenovo.%20Thinkpad%20X1%20tablet%203rd%20gen%3C%2FP%3E%3CP%3EHere's%20my%20log%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EMatching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%20EVILONE%3CBR%20%2F%3EManufacturer%20%3D%20LENOVO%3CBR%20%2F%3EModel%20%3D%2020KJ0017US%3CBR%20%2F%3EHostOSArchitecture%20%3D%20x64%3CBR%20%2F%3EFirmwareType%20%3D%20UEFI%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020190220000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%20N1ZET73W(1.29%20)%3CBR%20%2F%3EBiosVersion%20%3D%20N1ZET73W(1.29%20)%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.18356%3CBR%20%2F%3EHostOSBuildString%20%3D%2018356.1.amd64fre.19h1_release.190308-1607%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.1%20(19h1_release.190318-1202)%3CBR%20%2F%3EHostOSLanguageId%20%3D%201033%3CBR%20%2F%3EHostOSEdition%20%3D%20Professional%3CBR%20%2F%3ERegisteredAV%20%3D%20Windows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2C%3CBR%20%2F%3EFilterDrivers%20%3D%20WdFilter%2Cwcifs%2CCldFlt%2Cluafv%2CWof%2CFileInfo%2C%3CBR%20%2F%3EUpgradeStartTime%20%3D%2024%2F03%2F2019%2005%3A23%3A16%3CBR%20%2F%3EFinalizeStartTime%20%3D%2024%2F03%2F2019%2005%3A45%3A38%3CBR%20%2F%3EUpgradeEndTime%20%3D%2024%2F03%2F2019%2016%3A13%3A25%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%2010%3A50%3A09%3CBR%20%2F%3ECV%20%3D%20qJ0Kvm20bkmbOA7W%3CBR%20%2F%3EReportId%20%3D%208865774C-0CB0-4858-9400-947FFBA71ABF%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20SetupDiag%20reports%20fatal%20migration%20plug-in%20failure.%3CBR%20%2F%3ESetup%20Operation%3A%20Gather%20data%2C%20scope%3A%20EVERYTHING%3CBR%20%2F%3EPlug-in%20Error%3A%200x000005B4%3CBR%20%2F%3EPlug-in%20Name%20and%20Action%20%3D%20Action%2CCMXEPlugin%2CC%3A%5C%24WINDOWS.~BT%5CSources%5CReplacementManifests%2CMicrosoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%2C%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%2CApartment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386435%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386435%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3Bhave%20that%20problem%20aswell%2C%20have%20tried%203%20times%20to%20update%20but%20nothing%20mines%20a%20asus%20though%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386424%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386424%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306954%22%20target%3D%22_blank%22%3E%40sjfwhite0823%3C%2FA%3E%3C%2FP%3E%3CP%3EI%20also%20have%20a%20Lenovo%20(Thinkpad%2011e).%26nbsp%3B%20But%20the%20failed%20upgrade%20went%20back%20to%20the%20previous%20Insider%20build.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMatching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%2011E-THINKPAD%3CBR%20%2F%3EManufacturer%20%3D%20LENOVO%3CBR%20%2F%3EModel%20%3D%2020GB000LUS%3CBR%20%2F%3EHostOSArchitecture%20%3D%20x64%3CBR%20%2F%3EFirmwareType%20%3D%20UEFI%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020180119000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%20R0AET37W%20(1.20)%3CBR%20%2F%3EBiosVersion%20%3D%20R0AET37W%20(1.20)%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.18356%3CBR%20%2F%3EHostOSBuildString%20%3D%2018356.1.amd64fre.19h1_release.190308-1607%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.1%20(19h1_release.190318-1202)%3CBR%20%2F%3EHostOSLanguageId%20%3D%201033%3CBR%20%2F%3EHostOSEdition%20%3D%20Professional%3CBR%20%2F%3ERegisteredAV%20%3D%20Norton%20Security%2CNorton%20Security%2CNorton%20Security%2CNorton%20Security%2CNorton%20Security%2CNorton%20Security%2CNorton%20Security%2CNorton%20Security%2C%3CBR%20%2F%3EFilterDrivers%20%3D%20BHDrvx64%2CeeCtrl%2CSRTSP%2CSymEFASI%2Cwcifs%2Cluafv%2CWof%2CFileInfo%2C%3CBR%20%2F%3EUpgradeStartTime%20%3D%2024-Mar-19%2011%3A18%3A23%3CBR%20%2F%3EFinalizeStartTime%20%3D%2024-Mar-19%2012%3A10%3A50%3CBR%20%2F%3EUpgradeEndTime%20%3D%2024-Mar-19%2012%3A46%3A48%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%2001%3A28%3A25%3CBR%20%2F%3ECV%20%3D%20En%2FFtpVx7kahUj3r%3CBR%20%2F%3EReportId%20%3D%208865774C-0CB0-4858-9400-947FFBA71ABF%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20SetupDiag%20reports%20fatal%20migration%20plug-in%20failure.%3CBR%20%2F%3ESetup%20Operation%3A%20Gather%20data%2C%20scope%3A%20EVERYTHING%3CBR%20%2F%3EPlug-in%20Error%3A%200x000005B4%3CBR%20%2F%3EPlug-in%20Name%20and%20Action%20%3D%20Action%2CCMXEPlugin%2CC%3A%5C%24WINDOWS.~BT%5CSources%5CReplacementManifests%2CMicrosoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%2C%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%2CApartment.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386421%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386421%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F306929%22%20target%3D%22_blank%22%3E%40Aliffan%3C%2FA%3E%26nbsp%3BI%20hate%20being%20%22that%20guy%22%20but%20I%20have%20the%20same%20problem%20with%20a%20Lenovo%20Yoga%20920%20updating%20from%26nbsp%3B18356.16%20to%2018362.1%20with%20the%20same%20error%20message%20in%20the%20setupdiag%20log.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20no%20rollback%20build%20to%20go%20to...%20no%20idea%20how%20that%20worked.%26nbsp%3B%20However%2C%20I%20have%20a%20week%20old%20Acronis%20backup%20to%20restore.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386377%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386377%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRIKE%3EUpdate%20to%20my%20previous%20reply%3C%2FSTRIKE%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CSTRIKE%3EI%20might've%20found%20a%20solution.%20I've%20upgraded%20successfully%20to%2018362.1%20just%20now.%20This%20potential%20solution%20might%20cause%20trouble%20later%20down%20the%20road%20though%2C%20but%20everything%20looks%20ok%20for%20me%20for%20now.%20DISM%20and%20SFC%20checks%20look%26nbsp%3Bgood.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EI%20downloaded%20the%20upgrade%20package%20using%20the%20UUP%20dump%20tool.%20The%20tool%20downloads%20the%20files%20necessary%20and%20converts%20it%20into%20an%20ISO%20file.%20You%20can%20try%20the%20normal%20setup%20first%20by%20mounting%20the%20ISO%20file%20and%20running%20the%20setup%20executable.%20If%20it%20fails%2C%20use%20SetupDiag%20and%20see%20if%20the%20error%20is%20the%20same.%20If%20it's%20the%20same%2C%20you%20could%20try%20what%20I%20did.%20Here's%20where%20it%20could%20get%20tedious.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EI%20searched%20the%20sources%20folder%20and%20found%20a%20manifest%20file%20which%20contains%20some%20lines%20of%20configuration%20that%20look%20like%20this%3A%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3E%3CSTRIKE%3E%3CPLUGIN%3E%3CBR%20%2F%3EclassId%3D%22%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%22%3CBR%20%2F%3Ecritical%3D%22Yes%22%3CBR%20%2F%3Efile%3D%22Microsoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%22%3CBR%20%2F%3EofflineGather%3D%22Yes%22%3CBR%20%2F%3EofflineApply%3D%22Yes%22%3CBR%20%2F%3E%2F%26gt%3B%3C%2FPLUGIN%3E%3C%2FSTRIKE%3E%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CSTRIKE%3ESo%20I%20figured%20I%20should%20try%20and%20modify%20that%20a%20bit.%20Particularly%20the%20%22critical%22%20value.%20Here%2C%20%22critical%22%20is%20set%20to%20%22Yes%22.%20I%20think%20that%20states%20if%20the%20process%20is%20critical%20and%20if%20it%20fails%20somewhere%2C%20the%20whole%20setup%20needs%20to%20abort.%20If%20it's%20set%20to%20%22No%22%20instead%2C%20the%20process%20is%20not%20critical%20and%20if%20it%20fails%20somewhere%2C%20the%20setup%20just%20moves%20on.%20That's%20why%20this%20might%20not%20be%20100%25%20safe.%20Keep%20that%20in%20mind.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EI%20extracted%20the%20ISO%20file%20and%20located%20the%20manifest%20file.%20The%20manifest%20file%20is%26nbsp%3B%22%3CSTRONG%3E%5Csources%5Creplacementmanifests%5Cappxdeploymentserver-replacement.man%3C%2FSTRONG%3E%22.%20I%20opened%20the%20file%20with%20Notepad%2B%2B%20and%20changed%20the%20%22'Yes'%22%20in%20front%20of%20%22critical%3D%22%20to%20%22'No'%22%2C%20and%20saved%20the%20file.%20Then%20I%20use%20some%20ISO%20maker%20program%20(that%20allows%20me%20to%20do%20this%20for%20free)%20to%20make%20a%20new%20(barely)%20modified%20version%20of%20the%20installation%20ISO.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EIt's%20time%20to%20install%20it.%20I%20paused%20Windows%20Update%20so%20that%20it%20doesn't%20interrupt%20the%20process%20(by%20automatically%20rebooting%20the%20PC%20which%20I%20don't%20want).%20I%20restarted%20my%20PC%20for%20good%20measure%2C%20and%20I%20mounted%20the%20new%20ISO%20and%20ran%20the%20setup%20executable.%20After%20a%20while%20(and%20after%20a%20buggy%20looking%20%22Working%20on%20Updates%22%20screen)%2C%20my%20computer%20got%20past%20the%20error%20and%20upgraded%20successfully.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EI%20did%20a%20DISM%20and%20an%20SFC%26nbsp%3Bscan%2C%20and%20both%20resulted%20fine.%20But%20I'll%20see%20if%20there%20are%20any%20issues%20in%20UWP%20programs.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3ELet%20me%20know%20if%20this%20works%20for%20any%20of%20you.%20Before%20doing%20this%20though%2C%20make%20sure%20you%20have%20a%20plan%20just%20in%20case%20the%20setup%20fails%20midway%20and%20can't%20roll%20back%20(such%20as%20a%20backup%20and%20a%20rescue%20media).%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRIKE%3EEdit%3A%20UWP%20apps%20are%20not%20working.%20Settings%20app%20works%2C%20but%20a%20lot%20of%20other%20UWP%20apps%20are%20not%20working%20(including%20the%20store%20which%20is%20worrying).%20Can't%20fix%20it%20using%20PowerShell.%20Might%20want%20to%20roll%20back.%20I%20fixed%20the%20UWP%20situation.%20After%20searching%20for%20answers%20on%20the%20internet%2C%20broken%20apps%20are%20usable%20again.%26nbsp%3BI%20took%20ownership%20of%20the%20WindowsApps%20folder%20inside%20Program%20Files%20and%20grant%20full%20control%20for%20my%20account%20and%20%22ALL%20APPLICATION%20PACKAGES%22.%20This%20fixed%20the%20Microsoft%20Store.%20Then%20I%20opened%20Regedit%20and%20deleted%20all%20%3CSTRONG%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CAppModel%5CStateChange%3C%2FSTRONG%3E%20subkeys%20(which%20I%20think%26nbsp%3Bacts%20as%20a%20blacklist%20for%20apps%20which%20failed%20the%20migration).%20This%20fixed%20the%20rest%20of%20the%20UWP%20apps.%3C%2FSTRIKE%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEdit%3A%20People%20have%20reported%20that%20the%20workaround%20is%20not%20fail-proof.%20Your%20UWP%20apps%20could%20get%20screwed%20up%20really%20bad.%20Microsoft%20has%20pulled%2018362%20from%20Windows%20Update.%20Please%20don't%20do%20the%20workaround%20as%20it%20is%20risky%20and%20might%20even%20raise%20the%20probability%20of%20doing%20a%20clean%20install%20later%20in%20the%20future.%20Thank%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386352%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386352%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20been%20having%20the%20same%20issue%20since%2018342.%20Every%20time%20I%20try%20to%20update%20and%20restart%2C%20the%20screen%20gets%20stuck%20on%20%22Restarting%22%20for%20hours.%20I%20upgraded%20to%2018351%20and%20then%20to%2018356%20using%20the%20uupdump%26nbsp%3Btool%2C%20but%20now%20even%20that%20method%20doesn't%20work.%20The%20setup%20stays%20on%20%22Your%20PC%20will%20restart%20in%20a%20few%20moments%22%2C%20then%20throws%20an%20error%20message.%20I%20only%20knew%20what's%20the%20cause%20of%20the%20problem%20after%20running%20SetupDiag.%20I've%20been%20searching%20all%20day%20but%20no%20troubleshooting%20steps%20have%20worked%20so%20far.%20Deleting%20my%20account's%20appx%20cache%20didn't%20work.%20Now%20I'm%20really%20stuck%20and%20I'm%20very%20sure%20I%20don't%20want%20a%20clean%20install.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECuriously%20enough%2C%20you're%20also%20using%20a%20Lenovo%20PC.%20Also%2C%20here's%20my%20SetupDiag%20results%20just%20in%20case%20if%20someone%20wants%20to%20take%20a%20look.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CBLOCKQUOTE%3E%3CP%3EMatching%20Profile%20found%3A%20MigrationAbortedDueToPluginFailure%20-%20D07A24F6-5B25-474E-B516-A730085940C9%3CBR%20%2F%3ESystem%20Information%3A%3CBR%20%2F%3EMachine%20Name%20%3D%20LENOVO%3CBR%20%2F%3EManufacturer%20%3D%20LENOVO%3CBR%20%2F%3EModel%20%3D%2080TU%3CBR%20%2F%3EHostOSArchitecture%20%3D%20x64%3CBR%20%2F%3EFirmwareType%20%3D%20UEFI%3CBR%20%2F%3EBiosReleaseDate%20%3D%2020180409000000.000000%2B000%3CBR%20%2F%3EBiosVendor%20%3D%203JCN30WW%3CBR%20%2F%3EBiosVersion%20%3D%203JCN30WW%3CBR%20%2F%3EHostOSVersion%20%3D%2010.0.18356%3CBR%20%2F%3EHostOSBuildString%20%3D%2018356.1.amd64fre.19h1_release.190308-1607%3CBR%20%2F%3ETargetOSBuildString%20%3D%2010.0.18362.1%20(19h1_release.190318-1202)%3CBR%20%2F%3EHostOSLanguageId%20%3D%201033%3CBR%20%2F%3EHostOSEdition%20%3D%20CoreSingleLanguage%3CBR%20%2F%3ERegisteredAV%20%3D%20Windows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2CWindows%20Defender%2C%3CBR%20%2F%3EFilterDrivers%20%3D%20WdFilter%2Cwcifs%2CCldFlt%2Cluafv%2CWof%2CFileInfo%2C%3CBR%20%2F%3EUpgradeStartTime%20%3D%203%2F24%2F2019%204%3A23%3A00%20PM%3CBR%20%2F%3EFinalizeStartTime%20%3D%203%2F24%2F2019%205%3A05%3A26%20PM%3CBR%20%2F%3EUpgradeEndTime%20%3D%203%2F24%2F2019%205%3A34%3A12%20PM%3CBR%20%2F%3EUpgradeElapsedTime%20%3D%2001%3A11%3A12%3CBR%20%2F%3ECV%20%3D%20w47b6GCyOkexqdWA%3CBR%20%2F%3EReportId%20%3D%208865774C-0CB0-4858-9400-947FFBA71ABF%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%3A%20SetupDiag%20reports%20fatal%20migration%20plug-in%20failure.%3CBR%20%2F%3ESetup%20Operation%3A%20Ensure%20suspended%20services%20are%20stopped%3CBR%20%2F%3EPlug-in%20Error%3A%200x000005B4%3CBR%20%2F%3EPlug-in%20Name%20and%20Action%20%3D%20Action%2CCMXEPlugin%2CC%3A%5C%24WINDOWS.~BT%5CSources%5CReplacementManifests%2CMicrosoft-Windows-AppX-Deployment-Server%5CAppxUpgradeMigrationPlugin.dll%2C%7BAE27C1A6-25F2-45FD-9A28-081B81F29E0A%7D%2CApartment.%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386341%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386341%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20the%20exact%20same%20issue%2C%20and%20run%20through%20the%20troubleshooting%20steps%20to%20no%20avail.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fwindows%2Fdeployment%2Fupgrade%2Fquick-fixes%23windows-update-troubleshooter%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fwindows%2Fdeployment%2Fupgrade%2Fquick-fixes%23windows-update-troubleshooter%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20sure%20what%20plug%20in%20they%20are%20speaking%20of...any%20ideas.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-386339%22%20slang%3D%22en-US%22%3ERe%3A%20Upgrade%20from%2018356.16%20to%2018362.1%20fails%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-386339%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F270074%22%20target%3D%22_blank%22%3E%40ioannispan%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20problem%2C%20however%20I%20am%20able%20to%20go%20back%20to%20a%20previous%20version%20of%20Windows.%3C%2FP%3E%3C%2FLINGO-BODY%3E
ioannispan
Occasional Contributor

Upgrade fails, can't go back either. Such a mess.

 

Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
System Information:
Machine Name = 
Manufacturer = LENOVO
Model = 20AMS4FC00
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20190219000000.000000+000
BiosVendor = GIET95WW (2.45 )
BiosVersion = GIET95WW (2.45 )
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 = bindflt,FsDepends,WdFilter,wcifs,wcifs,CldFlt,luafv,Wof,FileInfo,
UpgradeStartTime = 23.03.2019 08:00:19
FinalizeStartTime = 23.03.2019 08:31:52
UpgradeEndTime = 23.03.2019 09:25:27
UpgradeElapsedTime = 01:25:08
CV = aJ3n+4/zaUCcm10J
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.

35 Replies

@ioannispan 

 

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

Have the exact same issue, and run through the troubleshooting steps to no avail.

 

https://docs.microsoft.com/en-gb/windows/deployment/upgrade/quick-fixes#windows-update-troubleshoote...

 

Not sure what plug in they are speaking of...any ideas.

 

@ioannispan 

I've been having the same issue since 18342. Every time I try to update and restart, the screen gets stuck on "Restarting" for hours. I upgraded to 18351 and then to 18356 using the uupdump tool, but now even that method doesn't work. The setup stays on "Your PC will restart in a few moments", then throws an error message. I only knew what's the cause of the problem after running SetupDiag. I've been searching all day but no troubleshooting steps have worked so far. Deleting my account's appx cache didn't work. Now I'm really stuck and I'm very sure I don't want a clean install.

 

Curiously enough, you're also using a Lenovo PC. Also, here's my SetupDiag results just in case if someone wants to take a look.

 

Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
System Information:
Machine Name = LENOVO
Manufacturer = LENOVO
Model = 80TU
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20180409000000.000000+000
BiosVendor = 3JCN30WW
BiosVersion = 3JCN30WW
HostOSVersion = 10.0.18356
HostOSBuildString = 18356.1.amd64fre.19h1_release.190308-1607
TargetOSBuildString = 10.0.18362.1 (19h1_release.190318-1202)
HostOSLanguageId = 1033
HostOSEdition = CoreSingleLanguage
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 = 3/24/2019 4:23:00 PM
FinalizeStartTime = 3/24/2019 5:05:26 PM
UpgradeEndTime = 3/24/2019 5:34:12 PM
UpgradeElapsedTime = 01:11:12
CV = w47b6GCyOkexqdWA
ReportId = 8865774C-0CB0-4858-9400-947FFBA71ABF


Error: SetupDiag reports fatal migration plug-in failure.
Setup Operation: Ensure suspended services are stopped
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.

@ioannispan 

Update to my previous reply

I 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:

 

<plugin
classId="{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.

@Aliffan I hate being "that guy" but I have the same problem with a Lenovo Yoga 920 updating from 18356.16 to 18362.1 with the same error message in the setupdiag log.

 

I have no rollback build to go to... no idea how that worked.  However, I have a week old Acronis backup to restore.  

@sjfwhite0823

I also have a Lenovo (Thinkpad 11e).  But the failed upgrade went back to the previous Insider build.

 

Matching Profile found: MigrationAbortedDueToPluginFailure - D07A24F6-5B25-474E-B516-A730085940C9
System Information:
Machine Name = 11E-THINKPAD
Manufacturer = LENOVO
Model = 20GB000LUS
HostOSArchitecture = x64
FirmwareType = UEFI
BiosReleaseDate = 20180119000000.000000+000
BiosVendor = R0AET37W (1.20)
BiosVersion = R0AET37W (1.20)
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 = Norton Security,Norton Security,Norton Security,Norton Security,Norton Security,Norton Security,Norton Security,Norton Security,
FilterDrivers = BHDrvx64,eeCtrl,SRTSP,SymEFASI,wcifs,luafv,Wof,FileInfo,
UpgradeStartTime = 24-Mar-19 11:18:23
FinalizeStartTime = 24-Mar-19 12:10:50
UpgradeEndTime = 24-Mar-19 12:46:48
UpgradeElapsedTime = 01:28:25
CV = En/FtpVx7kahUj3r
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.

 have that problem aswell, have tried 3 times to update but nothing mines a asus though 

@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.

Another thing is that it keeps trying to install it, just doesn't stop!

 

Picture1.png

Same problem here too.  It loops trying to update to 18362.1 which keeps failing.

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.

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.

 

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.

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, that mostly worked for me. I did get it upgrade with the critical ="no". Now I'm having issues with Microsoft apps. I did what you suggested, but there keeps coming up files that I don't have access to. But ah haaaa. I put this is PowerShell as admin and it now all works: Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

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" Iam not sure which part cost failed issue @ioannispan 

@Aliffan 

I have postponed updates for the coming 7 days and maybe MS comes with a new and working build.

@Aliffan 

Thanks for your suggestions... 

I downloaded 18362.1 using uup and created iso on usb thumb drive...

Modified Manifest file to "No"...

Ran "Setup" on usb...

Updated without problems...

Ran... SFC and DISM... shows NO corrupt System Files...

Everything seems to WORK OK.!!! 

Thanks Again.!!!

 

Please NOTE... 

Found a few app problems.... and another "solution"...

So... I changed the manifest file answer back to "YES" on the thumb/flash drive (iso)...

then... I Applied "solution" from Conversation... sjfwhite0823  replied to  TheNerdBoy -- yesterday (04/02/2019)

"The key is disabling Windows Search in services.msc then applying the update.  It will work fine then."

 

This time Rerunning and "ReInstalling" the (unmodified) 18362.1 "Update" (was unable to go back to 18356.16)... Completed without error...  Seems to be working OK... 

except for apps "won't open" error for... "Paint 3D", "Tips", "Voice Recorder", and "XBox"... !?  

 

Anyway... It's About time for a Windows Fresh/Clean Install.!?  :D 

 

 

 

Where does uup come from? I can't find it.

So, I managed to Upgrade to 18362.1 after having had the same problem everyone discussed but now I seem to have messed up my WindowsApps beyond repair - at least none of the solutions listed worked for me so far.

 

What I did was: Used https://www.uupdump.ml/ to get a dump of the update, edit the manifest file as described in the thread, repackage the ISO, mount it, install the update et voila. So far so good.

 

Now, my UWP got messed up, so I ran 

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register “$($_.InstallLocation)\AppXManifest.xml”}

as an admin and this fixed SOME of the problems.

 

Still, Microsoft Store wasn't working, e.g. the Calculator app among others wasn't starting (only getting vague error messages like "There’s a problem with Calculator. Contact your system administrator about repairing or reinstalling it.")  and so on.

 

Changing permissions (taking ownership, modifying access control) on WindowsApps didn't help.

 

Modifying the registry (deleting everything under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\AppModel\StateChange) as described above seems to have made the situation worse - some apps that were working before stopped working and now I basically have to re-apply the PowerShell-command I mentioned every time to semi-fix everything.

 

Microsoft Store and all non-working apps are greyed-out in the Start Menu... Tried purging the MS Store cache but it gives me an error that it cannot start the Store. Creating another user account didn't fix it either.

 

DISM and SFC don't recognize any problems...

 

I'm slowly running out of ideas how to fix the apps.

I was certainly wrong as well. I did get it to upgrade and did get some windows apps to work again. But still couldn't get the Store to work. Plus from that, it messed up a few other things as well - all things Abode. I ended up having to do a fresh install to just get things working again. That was a pain.

 

Though this new build did present some really nice things, like the file folder sorting is much much displayed. But for anyone reading, I HIGHLY recommend DO NOT upgrade to this new build, wait for MS to fix it. They did pull the build from the servers already.

@TheNerdBoy Thanks for the confirmation that I wasn't being the only silly person to have failed in such a way.

Isn't there any way of getting the Windows Store package from a healthy installation and then installing it manually? I feel that would solve the problem.

Meanwhile I rolled back to the previous version of Windows and needless to say that didn't help either...

Update: Something very weird is going on with the WindowsApps folder. No matter what permissions I set on it I cannot do anything with it - create, modify files or anything...

@Chaeska 

I have tried the windows folder permission, auditing, etc. I even went as far as deleting the WindowsApps folder and copying it from a laptop, as well as the registry key. I ran Ubuntu from a flash drive to do that.

Rolling back to the previous build did nothing but make things worse for me. 

There is something in the code of the OS that is written differently than before that is cause this.

For now, updates are on pause.

The key is disabling Windows Search in services.msc then applying the update.  It will work fine then.

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.

@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.

@AliffanNo worries from me, all is good. We do these things to make Windows better.

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 

Btw, I just read the announcement here but I don't understand why they only mention the Slow ring - what about us who are on the Fast ring and we have upgrade issues?

 

UPDATE 4/2: We have released Build 18356.21 (KB4496796) to Windows Insiders in the Slow ring who are currently on Build 18356.16. This update will get Insiders who are on Build 18356.16 back into a good state so they can update to Build 18362. We are allowing a few days for this update to roll out before offering Build 18362 – so that means Insiders will still not see Build 18362 offered after updating to Build 18356.21. But stay tuned!

So, I switched back to the Slow ring to get the "good state" update... 

 

 

 

 

@ioannispan Got the update as well since I rolled back from the botched "hacked" update. It installed successfully but it obviously didn't fix my FUBAR WindowsApps.

I'll have to reinstall at some point when I actually have the time and/or the messed up Apps start impacting me.

Luckily I didn't have anything critical installed.

@TheNerdBoy A miracle happened! 18362.30 just rolled out today and it fixed everything... My standard apps are back, the Store works - some Apps failed updating due to some weird errors but after reinstalling them they now work just fine.

Same with me.
On 2019-04-03 Update Installed 10.0.18356.16
On 2019-04-04 Update Installed 10.0.18362.30
Now everything is up to date and working. Back on track.

Updating to 10.0.18362.30 now...

 

UPDATE: everything is working....

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
30 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
29 Replies