Event ID 131 Metadata errors happening lately.

Page 2 of 2 FirstFirst 12

  1. Posts : 434
    10
    Thread Starter
       #11

    sportsfan148 said:
    Just to update anyone else who is having this issue. For nearly a week since I did a clean installation Ive been seeing 16 DeviceManagerSetup Event ID 131 errors every time I boot up my PC. Yesterday that number reduced to 11. Ive just booted up my PC and I have only one error now. I haven't done anything at all to try and fix this because last time it resolved itself after a few days without me doing anything. My gut feeling tells me it has to be something to do with Microsoft's servers but I don't know for sure
    I got a few yesterday but none today.

    - - - Updated - - -

    Funny enough I rebooted my laptop a few times this week and upon every reboot I get the error and no connectivity to the internet warning.
      My Computer


  2. Posts : 985
    Windows 10 Home 21H1
       #12

    2 days later and several shutdown and bootups...Im still seeing just one Event ID 131 DeviceSetupManager error. I expect that this error will also disappear on its own soon but I haven't got a clue why this happens. I went from 16 of these errors a week ago. Then it went down to 11 errors...and now just one. All this without any input whatsoever from me. Event viewer application logs show that when these errors are triggered it seems to be just a timing issue, probably caused by Microsoft Servers because straight afterwards the event is actioned. Very strange!
      My Computer


  3. Posts : 434
    10
    Thread Starter
       #13

    sportsfan148 said:
    2 days later and several shutdown and bootups...Im still seeing just one Event ID 131 DeviceSetupManager error. I expect that this error will also disappear on its own soon but I haven't got a clue why this happens. I went from 16 of these errors a week ago. Then it went down to 11 errors...and now just one. All this without any input whatsoever from me. Event viewer application logs show that when these errors are triggered it seems to be just a timing issue, probably caused by Microsoft Servers because straight afterwards the event is actioned. Very strange!
    It still happens even after patch Tuesday reboot.
      My Computer


  4. Posts : 37
    Windows 10 pro
       #14

    I downloaded the 1909 iso and upgraded from 1903 to 1909 and I have not seen this error so far today.
      My Computer


  5. Posts : 985
    Windows 10 Home 21H1
       #15

    sportsfan148 said:
    2 days later and several shutdown and bootups...Im still seeing just one Event ID 131 DeviceSetupManager error. I expect that this error will also disappear on its own soon but I haven't got a clue why this happens. I went from 16 of these errors a week ago. Then it went down to 11 errors...and now just one. All this without any input whatsoever from me. Event viewer application logs show that when these errors are triggered it seems to be just a timing issue, probably caused by Microsoft Servers because straight afterwards the event is actioned. Very strange!
    Update:
    On patch Tuesday CU KB4524570 was automatically installed on version 1903. I now have Build 18362.476. I have the option also to download and Install 1909 feature update but I haven't done so yet. Im holding off for a couple of weeks to verify that feedback on here shows that it is stable before I upgrade to 1909.
    After the CU KB4524570 installation Im now seeing no DeviceManagerSetup 131 errors at all
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 01:36.
Find Us




Windows 10 Forums