Thanks... worked for me too. Works also on the new build 16179 .. so it should be the way to sort it out for all builds/
Some people report that simply searching for those package names in the registry and removing them gets the job done too, but others say that errors can re-appear unless you also move a system folder of that package to a different location, but that's equivalent of moving/deleting Cortana folder, which is possible and works to get rid of Cortana SearchUI, but also breaks the OS - Metro UI AND SFC /ScanNow can RESTORE the deleted/moved packages and the registry entries for them.. Such packages are meant to be de-coupled and uninstalled via a method similar to the one I provided if you want to reduce the risk of breaking the OS and want to make sure SFC /ScanNow does not restore those packages.
@ MonarchX good job dude I like to see members making search, test and sometimes breaking O.S. myself is one of them, sorry but is not more easy use MSMG Toolkit and simply remove only Apps desired I know because my O.S. don't have none metro applications and only for testing I make the same Dism command and when finished my O.S. don't have none error
I agree, but so far on my PC creation of MSMG Toolkit ISO (which includes adding NET Framework 3.5, some 700MB worth of drivers, and removing a TON of worthless Metro crap) results in an ISO with a WIM file larger than original (should not be possible) and during clean install it asks for 40-55GB worth of space on my SSD for installation to proceed, while official Creator's Update installs just fine on my 30GB partition... I am not sure I can trust that tool... yet...
ok well this is strange because in my job after all my ISO have 3,61GB; I also have SSD (240GB) I don't see none advice but I reserve all space for O.S. so when Windows are installed and running I open file explorer search User folder and change all locations as documents, musics, videos, downloads from C:\ROOT (SSD 240GB) to partition D:\ HOME (1HDD TB) also in gpedit.msc I configure correctly indicating where my files stay still in App settings I simply ignore any setting related with my changes until now no issues maybe in another fresh install try make so and see result
I do the same for testing purposes, and s**ts-and-giggles, and have never had that problem of requiring so large a partition for install. I usually test first in Hyper-V with only a 20 GB drive with no problems.
I did it all, step by step. Still didn't work for me. I'll try a do over and post if I get it to work. By the way, do you still have your windows.old directory? I cleaned my out.
I'm too busy to do all this, think I wait and hope/pray/beg/cry/scream/wait and see if MS will send us patch to fix this
Dude, it takes 5 minutes tops and aside from that, you'll learn how to remove packages, a need that may very much arise considering how MS is pushing more and more Store packages with each Windows 10 Update/Upgrade.
What did not work - the package removal or the DISM? If the packages and the registry entries are gone via the described method and DISM process fails, then there is simply a different cause and there can be many causes. Check out the DISM log and see if you can spot anything familiar in there.
I wonder if there is a more easy way to delete the following registry keys... Code: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~0.0.0.0 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageIndex\Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0
In cmd as admin Code: Reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall" /v "Microsoft-Windows-TestRoot-and-FlightSigning-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat" /f Reg.exe delete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\CatalogsToUninstall" /v "Microsoft-Windows-TestRoot-and-FlightSigning-WOW64-Package~31bf3856ad364e35~amd64~~10.0.15063.0.cat" /f