Every few seconds a new .evtx file and a new .txt file appear in c:\windows\temp. Each .evtx file has nearly identical content (except for timestamps), ditto the .txt files.
The .evtx files are roughly 7 MB large and contain almost 3600 events each. As you can imagine, this is filling up the HDD rather quickly. We deleted ~30 GB worth of these files earlier today.
The entirety of the .txt files is:
Package full name = Microsoft.SurfaceHub_42.602.139.0_neutral_~_8wekyb3d8bbwe
AppXDeploymentServer version = 10.0.17134.1006
Result code = 0x80073CF6
Component failure code = 0x80080204
ETW Event ID = 7706
Deployment Operation = 4294967294
Package Manager State = 19
OSIM state = 2
Failed component name = windows.DeviceAccess
The .evtx files open in Event Viewer and mirror the sentiment of the .txt files: unable to install something or other related to the Surface Hub. Here's some excerpts:
The Appx package's manifest is invalid.: Cannot register package Microsoft.SurfaceHub because of a problem with Function element usage:FF0B 000C: Function requires a Device with a specific Id element, and cannot be used with an Id of "any"
AppxManifest.xml(98,10): error 0x80080204: Cannot register the Microsoft.SurfaceHub package because the following error was encountered while parsing the UnnamedExtensionHandler extension: The Appx package's manifest is invalid.
error 0x80080204: While preparing to process the request, the system failed to register the windows.DeviceAccess extension due to the following error: The Appx package's manifest is invalid.
I'm not sure where to start with this.
Can anyone point me in the right direction to begin troubleshooting this?
OS: Windows 10, latest
Hardware: Surface laptop
I can provide additional details on request.
Best Answer
We were able to resolve this by removing the "Surface" app via powershell:
Then reinstalling the "Surface" app from the Microsoft Store and rebooting a couple times.
Update:
The above method was a good first step, but after ~15 minutes the errors started coming back. Completely removing the "Surface" app and rebooting appears to have solved the issue.