Share via

.Net runtime - There was a failure initializing profiling API attach infrastructure - 1022

tocguy 160 Reputation points
2025-09-29T18:01:19.36+00:00

Clean Win 11 install yesterday on

Mobo: MSI X870E with

CPU: AMD 9950X3D

Event Descriptions:

.NET Runtime version 4.0.30319.0: 2 occurrences separated by 6 seconds with no intermediate Admin events.

There was a failure initializing profiling API attach infrastructure. This process will not allow a profiler to attach. HRESULT: 0x80004005. Process ID (decimal): 3020. Message ID: [0x2509].

PID 3020: unknown; not present in Task Manager

These are the first occurrences of these errors; they were not present upon initial boot today. Instead, there were a plethora of Office 2016 events due to an apparent failed install despite the install declaring that it was successful yesterday. Sigh... Gave the same success declaration upon completion of the Repair today.

MS Office 2016 Alerts: 16 occurrences with unique Ids and spanning 30 seconds total

Failed to parse element: DefaultSettings

Ids (in chronological order of occurrence from earliest to latest)
8d7e6df0-d883-4d89-9ab5-e946d5483e03, DisplayName=Translate with Copilot, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
14c4d781-faf5-4d26-bb9a-b5672474332a, DisplayName=Copilot, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
7e2ca603-00d1-4fcd-8187-926a83703522, DisplayName=Unified Store, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
eecf68e0-a96e-4d50-b32a-0b2c2ce8ddfa, DisplayName=Content Assembly, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
a4095e33-d3f0-496e-a395-a3bbdc33d91b, DisplayName=OneNote Hosted Loop Experiences, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
bdb87fae-106b-4eb5-909b-a1075076d14d, DisplayName=Copilot (Preview), Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
a461341d-a650-485f-ad6a-38eb2921bc07, DisplayName=Initialization, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
14c4d781-faf5-4d26-bb9a-b5672474332a, DisplayName=Copilot, Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)
eecf68e0-a96e-4d50-b32a-0b2c2ce8ddfa, DisplayName=Content Assembly, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
8d7e6df0-d883-4d89-9ab5-e946d5483e03, DisplayName=Translate with Copilot, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
6e9c77d6-c929-49bc-b6ee-3cfa1be365a6, DisplayName=Copilot Slide Builder, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
a8661561-cbf6-4eb2-8c7d-8f7d1a5d9cfb, DisplayName=Copilot (Preview), Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
7e2ca603-00d1-4fcd-8187-926a83703522, DisplayName=Unified Store, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
a4095e33-d3f0-496e-a395-a3bbdc33d91b, DisplayName=OneNote Hosted Loop Experiences, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
d2f3318f-cdae-42cd-a24f-bd5ea940e721, DisplayName=Copilot Narrative Builder, Provider=Microsoft, StoreType=SdxRdx, StoreId=(null)
f100f45e-9e23-4411-b13a-8198563b8fef, DisplayName=Copilot (Preview), Provider=Microsoft Office Services, StoreType=SdxRdx, StoreId=(null)

P1: Apps for Office

P2: 16.0.12527.22286

P3: 0x8004323E

P4: New Document

Performed Online Repair of the Office Suite and rebooted. Office Alerts disappeared but were replaced with the .Net Runtime events. Errors appear heavily weighted towards issue with CoPilot.

Windows for home | Windows 11 | Performance and system failures
0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2025-09-29T23:03:57.4666667+00:00

    Dear tocguy,

    Thank you for reaching out to the Microsoft Q&A Forum.

    The core of the problem is a fundamental incompatibility between Microsoft Office 2016 and your modern Windows 11 ecosystem, especially with cloud-integrated features like Copilot.

    You could try these troubleshoots below to solve this issue:

    1. Disable the offending scheduled task:
      • Click the Start button and type Task Scheduler, then open it.
      • In the left-hand pane, navigate to Task Scheduler Library > Microsoft > Office.
      • You will likely see several tasks here. The most probable culprit is named something like Office Feature Updates, Office Telemetry Agent, or Office ClickToRun Service Monitor.
      • Right-click on each suspicious task and select Disable.
      • Reboot your computer and check the Event Viewer to see if the .NET errors have stopped.
    2. Use Autoruns to find and disable the process:
      • Download Autoruns directly from Microsoft.
      • Extract and run Autoruns64.exe as an administrator.
      • Wait for it to scan everything. In the filter box at the top, type Office.
      • Look through the entries under the Scheduled Tasks and Services tabs. Find any entries related to Office 2016 diagnostics, telemetry, or updates.
      • Uncheck the box next to the entry to disable it.
      • Reboot and check if the error is gone.

    For long-term recommendation, your hardware is the absolute latest for 2025. Running Office 2016, which exited mainstream support in 2020, on this platform is not a stable or secure configuration. You will likely continue to encounter strange issues like this.

    The only way to guarantee stability and proper functionality is to use a version of Office that is actively supported on Windows 11, such as Microsoft 365 or Office 2021/2024.

    Please understand that our initial reply may not always immediately resolve the issue. However, with your help and more detailed information, we can work together to find a solution. Thank you for your cooperation.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".  

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.