Giolon
Member
Probably the usual appxbundlemanifest.xml and appxmanifest.xml files broke themselves. Something in the appcache is causing this bug.
Happened to me a few builds ago.
You can open up PowerShell as admin and run the following commands.
I forgot what I used, so this is what turned up on search. I had to type commands in as copy and paste weren't working either.
Command input is not case sensitive.
Code:Get-appxpackage -all *shellexperience* -packagetype bundle |% {add-appxpackage -register -disabledevelopmentmode ($_.installlocation + “\appxmetadata\appxbundlemanifest.xml”)}
Code:Get-AppXPackage | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Reboot afterwards.
I knew about that second command and gave it a try after the issues w/ app installation, but didn't know about the first command. Anyways, it's too late now unless MS will still let me upgrade to 10166 via ISO and then windows update to 10240. I'm not sure if it'll still recognize my prior activation. Thanks for the info though.