Windows 10: my professional gamer friends been having issues on his pc, metadata staging failed

so its been for some time, before these there were some issues with the system files, and he wanted to install windows on his ssd so I went through a full fresh windows install on his ssd as the primary hdd isn't connected now, I formatted the drives completely and deleted all partitions before the reinstall, and at least there's no more system file errors so there's that, but now we have the metadata issue, which I'm not sure how to fix. I saw some things online, but I had done most of them before I reinstalled. got some files attached for the GOATs that exist here on this thread. drive hea

:)

 

Metadata staging failed

Hello Kosta, thanks for your reply, I got a lot of success by following Sammy's advice at this link ==> Solved Continues Errors at startup - Page 3

 

Metadata staging failed, for Event ID:131

You didn't understand me, I'm using Windows 10 Professional 64bit, on which I have VMware Workstation installed (Forget I mentioned VMware, my OS is Windows 10 Pro 64bit)

Anyway, your way didn't work and the errors keep getting logged in the Event Viewer

Do you have any other suggestions on how to fix this error (Metadata staging failed, for Event ID:131) ?

 

Metadata staging failed


I have the same problem. Errors appear in following order:

The Network List Manager reports no connectivity to the internet.
A connection to the Windows Update service could not be established.
The Network List Manager reports no connectivity to the internet.
A connection to the Windows Metadata and Internet Services (WMIS) could not be established.
Metadata staging failed, result={00000000-0000-0000-FFFF-FFFFFFFFFFFF} for container '0x80070490'

I think all these errors are to be seen as one. For some reason the system reports no internet connection, and then rest of errors appears.

There is an option in Group Policy to tell windows to wait for internet before logon:
Computer Configuration\Administrative Templates\System\Logon
"Always wait for network at computer startup and logon"
However that doesn't work here. The error persists.

So, any ideas?