Share via

Problem related to DeviceSetupManager. Lots of errors and warnings.

Anonymous
2025-03-16T20:20:14+00:00

I have tried several ways to get rid of all warnings and errors in Event viewer. A registry hack seemed to help a little, but only for error 131. Now I have reinstalled again, hoping that a clean install could help, but no.

I understand this happens when Windows try to receive metadata for devices, and has a wrong address on server.

I don't want to choose never update drivers. Is there another solution?

I made my own event report, and this is only for this evening. Two screens with errors and warnings from DeviceSetupManager.

Windows for home | Windows 10 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
  1. Anonymous
    2025-03-27T01:07:39+00:00

    Thank you for your reply. I have voted for you. I hope the development team can check and fix it as soon as possible.

    In addition, if it is convenient for you, please rate my service. Please feel free to click yes or no. This will help other users in the community quickly locate this thread to get some information and vote for you to increase attention. Thank you again for your patience in reading and cooperation.

    Best regards

    Bobhe | Microsoft Community Support Specialist

    1 person found this answer helpful.
    0 comments

5 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-03-25T10:02:36+00:00

    Thank you for your reply, I think you have a very good point, this may also belong to the compatibility problem, in order to better fix, we suggest that you can also go to the feedback center at the same time to give feedback so that the development team to check.

    Microsoft attaches great importance to user experience, you can submit your ideas and suggestions through the Send feedback to Microsoft with the Feedback Hub app - Microsoft Support, and the development team will regularly review submissions for ideas or fixes. 

    Please share the feedback link here after submitting as it will allow others on the forum to vote for your submission, including me. More votes will lead to more visibility and higher priority to the development team. 

    Best regards

    Bobhe | Microsoft Community Support Specialist

    0 comments
  2. Anonymous
    2025-03-17T11:56:54+00:00

    HI! I have checked the drivers. I use HP Support Assistant, and it does not find any missing/old drivers. System tests show everything is OK.

    I went to Control Panel / Hardware and sound / Devices and printers, and discovered a small clock besides all devices. The clock disappeared after few seconds.

    At the same time 18 entries of Error 131.

    I think perhaps it is missing metadata, as several persons have mentioned earlier.

    0 comments
  3. Anonymous
    2025-03-17T09:43:10+00:00

    Thank you for answering!

    Yes, I can check all drivers and see what happens. It is an old HP machine, so perhaps I can try to install Win 11 instead.

    The error sound at startup is on another PC. Also a HP machine, but Windows 11. This is the most important ting to find out, because I mostly use this machine.

    It does not happen every time I startup, but often. As far I can see, not when I restart. Sometimes I have problems with entering PIN, too. Perhaps the system is busy, perhaps I have too many apps opening at startup? Or perhaps one app is misconfigured.

    List of errors and warnings at startup today:

    Loggnavn: Microsoft-Windows-Kernel-EventTracing/Admin

    Kilde: Microsoft-Windows-Kernel-EventTracing

    Dato: 17.03.2025 09:21:51

    Hendelses-ID: 3

    Oppgavekategori:Session

    Nivå: Feil

    Nøkkelord: Session

    Bruker: SYSTEM

    Datamaskin: Pavilion

    Beskrivelse:

    Økten PerfDiag Logger stoppet på grunn av følgende feil: 0xC0000188

    Hendelses-XML-fil:

    3

1

2

2

14

0x8000000000000010

183

Microsoft-Windows-Kernel-EventTracing/Admin

Pavilion

PerfDiag Logger

C:\WINDOWS\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl

3221225864

41943168

0

    *********************************************************************************************************************************************************************

    Loggnavn: Microsoft-Windows-Kernel-EventTracing/Admin

    Kilde: Microsoft-Windows-Kernel-EventTracing

    Dato: 17.03.2025 09:21:51

    Hendelses-ID: 4

    Oppgavekategori:Logging

    Nivå: Advarsel

    Nøkkelord: Session

    Bruker: SYSTEM

    Datamaskin: Pavilion

    Beskrivelse:

    Maksimal filstørrelse for økten PerfDiag Logger er nådd. Det kan føre til at hendelser kanskje går tapt (ikke blir logget) for filen C:\WINDOWS\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl. Maksimal filstørrelse er for øyeblikket satt til 20971520 byte.

    Hendelses-XML-fil:

    4

0

3

1

10

0x8000000000000010

182

Microsoft-Windows-Kernel-EventTracing/Admin

Pavilion

PerfDiag Logger

C:\WINDOWS\system32\WDI\LogFiles\ShutdownPerfDiagLogger.etl

3221225864

41943168

20971520

    *********************************************************************************************************************************************************************

    Loggnavn: Microsoft-Windows-Kernel-EventTracing/Admin

    Kilde: Microsoft-Windows-Kernel-EventTracing

    Dato: 17.03.2025 09:21:24

    Hendelses-ID: 2

    Oppgavekategori:Session

    Nivå: Feil

    Nøkkelord: Session

    Bruker: PAVILION\an-ma

    Datamaskin: Pavilion

    Beskrivelse:

    Økten Cloud Files Diagnostic Event Listener kan ikke starte på grunn av følgende feil: 0xC0000022

    Hendelses-XML-fil:

    2

0

2

2

12

0x8000000000000010

181

Microsoft-Windows-Kernel-EventTracing/Admin

Pavilion

Cloud Files Diagnostic Event Listener

3221225506

4194560

    *********************************************************************************************************************************************************************

    Loggnavn: Microsoft-Windows-User Device Registration/Admin Kilde: Microsoft-Windows-User Device Registration Dato: 17.03.2025 09:21:07 Hendelses-ID: 360 Oppgavekategori:Ingen Nivå: Advarsel Nøkkelord: Bruker: PAVILION\an-ma Datamaskin: Pavilion Beskrivelse: Klargjøring av Windows Hello for bedrifter blir ikke startet. Enhet er Microsoft Entra-tilkoblet (eller hybridtilkoblet): Not Tested Bruker har logget på med Microsoft Entra-legitimasjon: No Windows Hello for bedrifter-policy er aktivert: Not Tested Klargjøring av etterpålogging for Windows Hello for bedrifter er aktivert: Not Tested Lokal datamaskin oppfyller kravene til maskinvare for Windows Hello for bedrifter: Not Tested Bruker er ikke koblet til maskinen via Eksternt skrivebord: Yes Brukersertifikat for lokal godkjenningspolicy er aktivert: Not Tested Maskin er underlagt none-policyen. Skyklarering for lokal godkjenningspolicy er aktivert: Not Tested Brukerkontoen har Cloud to OnPrem TGT: Not Tested Se https://go.microsoft.com/fwlink/?linkid=832647 for å få mer informasjon. Hendelses-XML-fil: 360 0 3 0 0 0x8000000000000000 96 Microsoft-Windows-User Device Registration/Admin Pavilion Klargjøring av Windows Hello for bedrifter blir ikke startet. Not Tested No Not Tested Not Tested Not Tested Yes Not Tested none Not Tested Not Tested

    *********************************************************************************************************************************************************************

    Loggnavn: System

    Kilde: Microsoft-Windows-DistributedCOM

    Dato: 17.03.2025 09:21:06

    Hendelses-ID: 10016

    Oppgavekategori:Ingen

    Nivå: Advarsel

    Nøkkelord: Klassisk

    Bruker: LOKAL TJENESTE

    Datamaskin: Pavilion

    Beskrivelse:

    Innstillingene for programspesifikk-tillatelse gir ikke Lokal Aktivering-tillatelse til COM Server-programmet med CLSID

    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

    og APPID

    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

    til brukeren NT-MYNDIGHET\LOKAL TJENESTE SID (S-1-5-19) fra adressen LocalHost (bruker LRPC) som kjører i programbeholderen Ikke tilgjengelig SID (Ikke tilgjengelig). Denne sikkerhetstillatelsen kan endres med det administrative verktøyet Komponenttjenester.

    Hendelses-XML-fil:

    10016

0

3

0

0

0x8080000000000000

11978

System

Pavilion

programspesifikk

Lokal

Aktivering

{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

NT-MYNDIGHET

LOKAL TJENESTE

S-1-5-19

LocalHost (bruker LRPC)

Ikke tilgjengelig

Ikke tilgjengelig

    *********************************************************************************************************************************************************************

    Loggnavn: System

    Kilde: Microsoft-Windows-DistributedCOM

    Dato: 17.03.2025 09:21:06

    Hendelses-ID: 10016

    Oppgavekategori:Ingen

    Nivå: Advarsel

    Nøkkelord: Klassisk

    Bruker: LOKAL TJENESTE

    Datamaskin: Pavilion

    Beskrivelse:

    Innstillingene for programspesifikk-tillatelse gir ikke Lokal Aktivering-tillatelse til COM Server-programmet med CLSID

    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

    og APPID

    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

    til brukeren NT-MYNDIGHET\LOKAL TJENESTE SID (S-1-5-19) fra adressen LocalHost (bruker LRPC) som kjører i programbeholderen Ikke tilgjengelig SID (Ikke tilgjengelig). Denne sikkerhetstillatelsen kan endres med det administrative verktøyet Komponenttjenester.

    Hendelses-XML-fil:

    10016

0

3

0

0

0x8080000000000000

11977

System

Pavilion

programspesifikk

Lokal

Aktivering

{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

NT-MYNDIGHET

LOKAL TJENESTE

S-1-5-19

LocalHost (bruker LRPC)

Ikke tilgjengelig

Ikke tilgjengelig

    *********************************************************************************************************************************************************************

    Loggnavn: System

    Kilde: Microsoft-Windows-Time-Service

    Dato: 17.03.2025 09:21:05

    Hendelses-ID: 134

    Oppgavekategori:Ingen

    Nivå: Advarsel

    Nøkkelord:

    Bruker: LOKAL TJENESTE

    Datamaskin: Pavilion

    Beskrivelse:

    NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: Kjenner ingen slik vert. (0x80072AF9)

    Hendelses-XML-fil:

    134

0

3

0

0

0x8000000000000000

11973

System

Pavilion

Kjenner ingen slik vert. (0x80072AF9)

15

time.windows.com,0x9
    0 comments
  4. Anonymous
    2025-03-17T05:46:13+00:00

    Hello, AnitaM_863

    Welcome to the Microsoft Community.

    Thank you for your feedback here, it seems that you have encountered an error related to DeviceSetupManager.

    Since you've already done a fresh install and it's still there, it may be related to your current drivers. We recommend that you check your computer's updates, open Settings-Update and install the patches, and go to your computer's official website to download the main drivers for your computer, such as the graphics card driver and the motherboard driver.

    In addition, you can also double-click the red exclamation mark in your screenshot to share the content of the event here, of course, if you are convenient, you can also refer to the following thread to share the logs here, I will be for you to check.

    How to Save Event Logs1 - Host Integration Server | Microsoft Learn

    Also you seem to have a problem with the abnormal startup error sound, does it still exist after a fresh install.

    Best regards

    Bobhe | Microsoft Community Support Specialist

    0 comments