New
#11
Are you able to install or move apps to non-C: (Windows) drive locations then?
I actually did a repair install of Windows by installing it from the USB I'd created using the Media Creation Tool within Windows v1607 itself and although the installation went fine I found that the Store and all the other apps would point-blank refuse to open. They didn't even open then quickly close but acted as if I was not even allowed to open them!!! There was no errors in the event log for this either. In the end I had to restore the backup I thankfully did before I attempted the repair install.
I was hoping the repair install would fix the 0x80070005 Store error.![]()
P.S. EFS stands for Encrypting File System. EFD is Enterprise Data Protection.
I'm not sure if I'm barking up the wrong tree here but this error may be related to the Windows Store which, I believe, uses some kind of encryption when installing its apps and games (which prevents anyone, who isn't signed into the Microsoft account that bought or downloaded them, from using them).
I suspect this is a bug of some kind, possibly connected with installing apps and games to other drives besides C:. Then again I am most likely completely wrong...![]()
I uninstalled my sole Windows App that was installed on the D drive, and now I no longer get the Event ID 4401 EFS error in my Event Viewer.
The Event ID 24 VmmsWmiEventProvider error eludes me though, I do believe it at least has something to do with Hyper-V, and I am actually running 3 Hyper-V VM's on my machine, but their operation doesn't have any problems after the Anniversary edition update.
I am also having the same issue. I have forza 6 apex installed on drive D only and since I moved it back to Drive C the error went away. However this is not ideal solution for me since the game is around 20GB and I have limited space in Drive C.
I also noticed the WindowsApps folder in Drive D is accessible and I can browse the content of Forza 6 apex app. I guess EFS is not encrypting the folder which causes the error to show up in event viewer
If anyone can help with a solution I would really appreciate it.
Hi
I've got the same issue running with clean install pro version 14393.10.
The strange thing I found is that the users I have 3 folders <My account> <default (hidden)> <defaultuser0>
it's normal?
While in the updated version is not present <defaultuser0>.
Error in clean install:
evnt error: Search id 3104 Gatherer
Could not enumerate the user sessions for the generation of the filter pooh.
Details: (HRESULT: 0x80040210) (0x80040210)
and
DistributedCOM id 10016
Settings specific permissions settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
e APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY \ SYSTEM SID (S-1-5-18) address LocalHost (via LRPCs) running in the CIS of the applications container Not Available (Not Available). To change the security clearance, you can use the Component Services administrative tool.
Error in the updated version:
Event ID 4401
Source: EFS
Message: 7,488: The EFS service could not run the provisioning of a user for enterprise data protection.
Error code: 0x80070005. (I have no one game or app. on another drive that is referenced by the C)
and:
DistributedCOM id 10016
Settings specific permissions settings do not grant Local Activation permission for the COM Server application with CLSID
{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
e APPID
{F72671A9-012C-4725-9D2F-2A4D32D65169}
to the user NT AUTHORITY \ SYSTEM SID (S-1-5-18) address LocalHost (via LRPCs) running in the CIS of the applications container Not Available (Not Available). To change the security clearance, you can use the Component Services administrative tool.
Thank you
Last edited by alpha45; 06 Aug 2016 at 04:58.
Hi,
Yes, that's normal.The strange thing I found is that the users I have 3 folders <My account> <default (hidden)> <defaultuser0>
it's normal?
While in the updated version is not present <defaultuser0>.
The DCOM errors are also typical and occur on every install I've seen so far.
They're easy to fix if you follow the guidelines described in this thread.
Cheers,![]()