Solved Windows cannot find files in WindowsApps folder

Okay, I did find the dll's... They are there where they are supposed to be. No issues at all. After wondering what the problem may be, I found that almost every file in the Microsoft.WindowsStore folder does not have an owner and that when trying to do anything with them you get "Access denied" error.

Time to see if I can work around this.

No dice. The program ran successfully, but the problems still persist.

Well, to be precise, I can get to the files and folders okay, but they're owned by someone that is higher than an administrator and therefor I cannot even view who owns them. I believe thanks to that, anything I do on the administrator account, even with PowerRun, will still result in access denied when trying to do anything.

RESOLUTION THOUGH: In the end, I did manage to get the Store working. I had to manually remove the store, download the store package, and manually reinstall it.

Also to note: I did this in a simple elevated PowerShell. The PowerRun program didn't let me install the package using it.


Next up: Maybe doing this for all the affected apps? Looking at the newly installed Store folder, the files are owned by SYSTEM with permissions for everyone accordingly. Hopefully not.

A new face on my thread! Hurray!

I went and double-checked that I'm logging in using a Microsoft account. There is a spot there that is asking me to verify my identity though.

As for the store, it was there previously, but the icon was gone and nothing happened when clicking it. I did get that to work basically the same way as what that last link you gave shows with downloading the store package and installing it with PS. (I was fairly tired last night when I was doing all that so I dont know how well my words came through. Whoops!) As that worked for the store, it would be an unruly task to hunt down packages for all the other affected apps I have and manually installing those myself. I can remember 4 of them from the top of my head that I've seen.

I did try icacls and reinstalling everything previously. Both of them are greeted with a whole slew of "access denied" errors. On the administrator account, PS does also give the error of not being able to do anything on a local account.

Okay. I'll do a short list of things I know are still not working. Found in the WindowsApps folder:

Microsoft.549981C3F5F10_3.2111.12605.0_x64__8wekyb3d8bbwe -> Win32Bridge.Server (from what I understood, this is Cortana)
Microsoft.GamingApp_2112.1001.10.0_x64__8wekyb3d8bbwe -> XboxAppServives (the xbox app)
NVIDIACorp.NVIDIAControlPanel_8.1.962.0_x64__56jybvy8sckqj -> nvcplui -> Nvidia Control Panel
Anything installed through the Xbox app (probably since the GamingApp doesn't work)
Start Menu Search (Cortana) doesn't actually search anything on my system, like programs (not even Edge!) probably thanks to Cortana being kaput

As I was googling things, I did read somewhere that a corrupt user profile may be a potential issue. If so, do you folks have a guide on how creating/deleting/transfering the main user profile works? Or better yet, if someone already created a handy program for it.

Alrighty! So the new account and deleting the old one seems to have done the trick! With a couple caveats though:

1: Even with the new account, some of the issues still persisted, but this time around I could re-register the apps using PowerShell to get them to work.
2: This included manually removing Microsoft Store and manually installing it. After that, re-registering using PowerShell worked for most other things.
3: I did have to manually remove the Nvidia Control Panel app and couple XBox related apps, but those I could reinstall through the Microsoft Store as I had it working
4: I am not 100% sure if this played a part in PowerShell working properly, but I went the extra mile to verify my Microsoft account so that I'm 100% not on a local account anymore.

Whether or not any of the take ownership or icacls resetting did anything, it does look like my problem was mostly related to my profile being messed up, and maybe not having a verified Microsoft account which might've been a pseudo local account. (If that makes any sense).

All in all, it was all a big headache, but thank you all for helping me out for couple days! Much obliged!

Oh, that's a neat program. I'll have to yoink that.

And yes. Everything seems to be in working order now. At least I haven't noticed anything not working yet, but everything I came here for is now fixed.