asked on

Warnings 200, 201, 202, and error 131 at startup

Getting these on every startup. No new hardware or software installed.

Log Name: Microsoft-Windows-DeviceSetupManager/Admin
Source: Microsoft-Windows-DeviceSetupManager
Date: 9/16/2019 3:45:47 PM
Event ID: 200
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: MN-PC
Description:
A connection to the Windows Update service could not be established.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}" />
    <EventID>200</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-16T19:45:47.239640500Z" />
    <EventRecordID>2013</EventRecordID>
    <Correlation />
    <Execution ProcessID="1360" ThreadID="2608" />
    <Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
  </EventData>
</Event>
--------------------------------------------------------------------------
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          9/16/2019 3:45:47 PM
Event ID:    [b]  202[/b]
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      MN-PC
Description:
[b]The Network List Manager reports no connectivity to the internet.[/b]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}" />
    <EventID>[b]202[/b]</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-16T19:45:47.242813900Z" />
    <EventRecordID>2014</EventRecordID>
    <Correlation />
    <Execution ProcessID="1360" ThreadID="2584" />
    <Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
  </EventData>
</Event>
--------------------------------------------------
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          9/16/2019 3:45:47 PM
Event ID:     [b] 201[/b]
Task Category: None
Level:         Warning
Keywords:      
User:          SYSTEM
Computer:      MN-PC
Description:
[b]A connection to the Windows Metadata and Internet Services (WMIS) could not be established.[/b]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}" />
    <EventID>201</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-16T19:45:47.268748600Z" />
    <EventRecordID>2019</EventRecordID>
    <Correlation />
    <Execution ProcessID="1360" ThreadID="2612" />
    <Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
  </EventData>
</Event>
-----------------------------------------------
Log Name:      Microsoft-Windows-DeviceSetupManager/Admin
Source:        Microsoft-Windows-DeviceSetupManager
Date:          9/16/2019 3:45:47 PM
[b]Event ID:      131[/b]
Task Category: None
Level:         Error
Keywords:      
User:          SYSTEM
Computer:      MN-PC
Description:
[b]Metadata staging failed, result=0x80070057 for container '{8750FE66-5DDD-5B54-98AF-0B10F4BE19EF}'[/b]
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-DeviceSetupManager" Guid="{fcbb06bb-6a2a-46e3-abaa-246cb4e508b2}" />
    <EventID>131</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2019-09-16T19:45:47.268394200Z" />
    <EventRecordID>2017</EventRecordID>
    <Correlation />
    <Execution ProcessID="1360" ThreadID="2584" />
    <Channel>Microsoft-Windows-DeviceSetupManager/Admin</Channel>
    <Computer>MN-PC</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="Prop_ContainerId">{8750FE66-5DDD-5B54-98AF-0B10F4BE19EF}</Data>
    <Data Name="HRESULT">2147942487</Data>
  </EventData>
</Event>

Open in new window

-------------------------------------------------------------------------------
I can access the internet. I can download and install updates. What I can't do is figure out what's generating these obviously linked errors.

Many thanks.

ASKER CERTIFIED SOLUTION

Member_2_231077

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

normanml

ASKER

Andy, those warnings and errors were piling up. I know: if it ain't broke, don't look at the event viewer. Troubleshooting, I found this: https://www.eightforums.com/threads/continues-errors-at-startup-metadata-staging-failed.53670/

And I tried this from one of the posts:

OK, after extensive research and trial and errors, I figured a work around for the issue.

It seems the issue is coming from Windows Update trying to retrieve info about the installed hardware from the internet and failing during startup.

To prevent this from happening do the following:

Go to Control Panel > Type in the search "device installation" > Click on "Change device installation settings"

Click on "No let me choose what to do" > choose the option "Never install driver software from Windows Update" and make sure that "Automatically get the device app and info provided by your device manufacture" is UNCHECKED. < This is the source of the issue

Restarted and shutdown a couple of times and the error is totally gone

.

I tried this on restart late this afternoon and it seemed to work, but shutdown tonight will be a better test. I don't see any consequences from changing the device installation settings, but you'd know better then me.

normanml

ASKER

Didn't work on fresh boot after shutdown. Ran sfc /scannow and it found corrupt files it could not fix. Ran it again in safeM; same story. Ran DISM. That got rid of Warnings 200, 201, 202, and error 131. We'll see if this holds up.

Update: Errors returned after I updated to 1903. I'm out of troubleshooting steps.

normanml

ASKER

See update above. Events 200 and 202 are back after an update.