Dependency install failing - 0x80073D02 currently in use + 0x80070003: The system cannot find the path specified + 0x80073cf6 error during updating

[ruthan]

Hi, im still somehow broken Store after disk image recovery - WIn10 UEFI 64x 22h2, i have tried a lots of things:

• complete store removal
• install by powershell / cmd
• install by winget NotSpecified: (C:\Users\RuThaN..bbwe.Msixbundle:String) [Add-AppxPackage], Exception
• alt installer
• removal and reinstall runtimes by ALT-APP installer
• take apps directories / registry ownership, and rights to user, trusted installer, system etc

Im able to install some apps which by alt-app, some install ok, but others install but at the end im getting dependency error, i have tried install from UPW or enable all Options -Advanced - Dependencies - both modes. Im running ALT APP installer as administrator, so it should be able to kill annoying apps, im not sure if Store itself could be run as admin and if would help.

But for some packages im getting dependency errors, because some apps are still running, i found out that when i add command-line to Taskmanager and sort it by it, im able to kill all one by one.. and after i can install some simple apps, but lots of apps have some internal first execution initialization 2nd wave installing for example XboxApp, Maps apps etc.. when they are reinstalling runtimes, because as i read runtimes has to be somehow glue to apps, and there is not possible to do killing.. Because app has to run to install 2nd wave i cant kill all app to get progress..

• exactly same problem is with updating apps, or installing new apps through the Store app, there is still something half broken, which block probably killing / or check, or update or installing runtimes through store..
• i have only Windows internal Defender on..
• i enabled everything in gpedit related to Apps, i even enabled Developer mode which some tutorials suggested
• i have tried all steps from here: https://www.reddit.com/r/XboxGamePass/comments/1fakql2/how_to_solve_content_failed_microsoft_store_not/
• wsreset / - i; reinstall apps through manifests

Error number is 0X80070005 but its really some in layer above error, real error is 0x80073D02 , in even log - is some message as in the full log.

So some apps (Clock / 3D Viewer) simply close after starting.

full log: command: Add-AppPackage "C:/Users/RuThaN_/Desktop/Microsoft.GamingApp_2508.1001.27.0_neutral_~_8wekyb3d8bbwe.Msixbundle"

Add-AppPackage : Deployment failed with HRESULT: 0x80073D02, The package could not be installed because resources it modifies are currently in use. error 0x80073D02: Unable to install because the following apps need to be closed Microsoft.GamingApp_2508.1001.27.0_x64__8wekyb3d8bbwe. NOTE: For additional information, look for [ActivityId] b3cdc482-105c-0005-cf30-ceb35c10dc01 in the Event Log or use the command line Get-AppPackageLog -ActivityID b3cdc482-105c-0005-cf30-ceb35c10dc01 At line:1 char:1

• Add-AppPackage "C:/Users/RuThaN_/Desktop/Microsoft.GamingApp_2508.100
  • CategoryInfo : NotSpecified: (C:\Users\RuThaN..bbwe.Msixbundle:String) [Add-AppxPackage], Exception
  • FullyQualifiedErrorId : DeploymentError,Microsoft.Windows.Appx.PackageManager.Commands.AddAppxPackageCommand_

Other similar problem is that system could not find manifest file:

Add-AppPackage : Deployment failed with HRESULT: 0x80073CF0, Package could not be opened.

error 0x80070003: Opening file from location: AppxManifest.xml failed with error: The system cannot find the path specified.NOTE: For additional information, look for [ActivityId] c6cfc3a3-1159-0007-84e1-cfc65911dc01 in the Event Log or use the command line Get-AppPackageLog -ActivityID c6cfc3a3-1159-0007-84e1-cfc65911dc01At line:1 char:1

• Add-AppPackage "C:\Programy\WindowsAppsAlternativeInstaller\altappins There is also 0x80073cf6 error - which is for example when i try to open Xbox app, on machine with broken install, its trying to update App, or install some additional packages / runtimes -

I installing through store its not working for all apps, any fold of fixing per App will not help, its some global settings problem to check, but you can at least be able to push installing of some apps through Alt app installer, but apps which needs as part of their execution download and install something will fail too. Apps will install only when you will and Apps running through Taska manager - Details add Collumn Commandline and sort by it.. and kill everything with C:\Program Files\WindowsApps and C:\Windows\SystemApps

So we know why error are happing, but how to solve them?

Other info (not magic solution, but at least something) which could help is info about how whole APPs structure works and which permissions are needed:

All apps should have these: // replace AppContainer is placeholder, you can find whole app names in C:\Program files\WindowsApp

1)Paths / Purpose /Access Requirements a) C:\Program Files\WindowsApps - Main installation directory for all MSIX/UWP app packages. Contains executables and resources. TrustedInstaller ownership; even Admins need permission elevation.

b) C:\Users\YourUserName\AppData\Local\Packages - Per-user app data, settings, and state for each installed package. Accessible to the user and system. You could have there some old data, which are messing with app. I had here some very old data.

c) C:\Users\YourUserName\AppData\Local\Microsoft\Windows\AppContainer Contains AppContainer profile manifests and virtualization layers. Accessible to the user and system.

2. Registry Keys -Virtualized Registry Hives HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer Stores per-app virtualized registry settings. Accessible to the user.

---

Expected solution ideas, i see 2 ways: a) ALT-app install - some additional check and fixing if all rights and settings are in state to successfully install all apps b) start in some enhanced mode, different than normal windows lick start, in which it would be able to handle installation properly

[mjishnu]

Im running ALT APP installer as administrator, so it should be able to kill annoying apps

no unfortunately alt app installer doesn't kill any process, you see alt app installer was designed to be run in non admin environment and just execute a PowerShell add appx command in the backend this command doesn't kill any apps. if the log say you need to close certain apps you need to kill them manually

All apps should have these: // replace AppContainer is placeholder, you can find whole app names in C:\Program files\WindowsApp

1)Paths / Purpose /Access Requirements a) C:\Program Files\WindowsApps - Main installation directory for all MSIX/UWP app packages. Contains executables and resources. TrustedInstaller ownership; even Admins need permission elevation.

b) C:\Users\YourUserName\AppData\Local\Packages - Per-user app data, settings, and state for each installed package. Accessible to the user and system. You could have there some old data, which are messing with app. I had here some very old data.

c) C:\Users\YourUserName\AppData\Local\Microsoft\Windows\AppContainer Contains AppContainer profile manifests and virtualization layers. Accessible to the user and system.

Registry Keys -Virtualized Registry Hives HKEY_CURRENT_USER\Software\Classes\Local Settings\Software\Microsoft\Windows\CurrentVersion\AppContainer Stores per-app virtualized registry settings. Accessible to the user.

by doing this did you have better chance of success?

a) ALT-app install - some additional check and fixing if all rights and settings are in state to successfully install all apps b) start in some enhanced mode, different than normal windows lick start, in which it would be able to handle installation properly

both of these issues require us to first identify what is causing the problem. and random killing by reading the logs is dangerous it could crash the system in some events

also, some things like xbox app require some store components i think and without which it doesn't function

[ruthan]

Ok i found where was the problem.. Some elevated mode to fix all rights and permission would make sense, or you maybe can at least point users that something is wrong with settup:

But is just for me some key pieces could be missing and some other settings could be needed and rights could be excessive.. Lots of people encountered these problem and they are point to doing sfc and dism silver bullets and other general really not working things like registering apps all over (which prints errors because scripts does not handle runtimes which have missing manifests).

Ok for me solution was set this: set full control for folder %USERPROFILE%\AppData\Local\Packages rights too: User System Administrators You still need to set owned and full control to trusted installer (in add rights dialog its added as NT service\trustedinstaller to C:\Programs files\WindowsApps

• I had here Trusted Installer - full controll, Administrators - full controll, Users - Read and execute creator - Full controll , application packagees - Read +Execute. All restricted application packages - Read + Execute. and there could be other rights in registry involved too and some rights above could too high.

[mjishnu]

Ok i found where was the problem.. Some elevated mode to fix all rights and permission would make sense, or you maybe can at least point users that something is wrong with settup:

But is just for me some key pieces could be missing and some other settings could be needed and rights could be excessive.. Lots of people encountered these problem and they are point to doing sfc and dism silver bullets and other general really not working things like registering apps all over (which prints errors because scripts does not handle runtimes which have missing manifests).

Ok for me solution was set this: set full control for folder %USERPROFILE%\AppData\Local\Packages rights too: User System Administrators You still need to set owned and full control to trusted installer (in add rights dialog its added as NT service\trustedinstaller to C:\Programs files\WindowsApps

• I had here Trusted Installer - full controll, Administrators - full controll, Users - Read and execute creator - Full controll , application packagees - Read +Execute. All restricted application packages - Read + Execute. and there could be other rights in registry involved too and some rights above could too high.

so, after you gave full access to C:\Programs files\WindowsApps the app installed fine?

[ruthan]

Yeah, but its not only that, there are other Apps folders where you need to have good enough rights and there some registry keys too, im unable to give you exact list. I guess that someone skilled with usage of Event logs or Sysinternal Regmon and Filemon could print exact list.. or even better Procmon, because Regmon and Filemon prints zillion of events and never was able to set good filter to find something, procmon should care about it, its for process and i hope that will work for some subproccesses started by main process.

Other way would be create some virtual machine, set rights to minimum and adding rights piece by piece..

[mjishnu]

i see thanks for the insight i will keep this issue open so people can refer it and if someone who knows better can also help out.

[ruthan]

Well you can et least someone how add some exception handling and maybe show some human friendly message instead, of dependency install fail. For some installs help just kill all running Xapps listed in Task manager-.Details - Custom comandline collumn, and sort by it.. After there are to User and System directories to kill all processes from it. So it some killing with elevated rights would help even with normal usage, because lots of apps seems to share runtimes.

[mjishnu]

as i said we cant just random kill apps some might crash the system

regarding the warning its is generic. most of the time when dependencies fail the app installs and runs fine so overwhelming the user is not the wise choice.

but some times as you have experienced it wont install or run in those case only should they need to investigate further they can do that by opening logs just like the warning tells them to. then manually kill the apps if its use or perform other methods like you mentioned

[ruthan]

Well Apps has to be framework to stop them properly, some api to stop them because of installing something new, Windows store has to do the same thing a guess.. Because its something else that installing app from *.exe or bundle which seems not to handle it properly.