Server Manager shows "Configuration Refresh Message Error" & "Online - Data Retrieval Failures"

Adrian Forrester 20 Reputation points
2025-11-01T14:21:58.0966667+00:00

We have migrated a Tertiary Domain Controller, running Windows 2022 from VMWare to Hyper-V. The migration was successful, and the system appears to be operating. However, we have noted a concerning issue when examining Server Manager.

It shows the following errors, which, I am sure operationally, are fine, but I can't understand why it's having an issue.
User's image

User's image

Event Viewer has several errors relating to:

Failure opening metadata of the owning provider for channel: hLastResult = The system cannot find the file specified.]

With several services, but since nothing has changed regarding which services are enabled, I am unsure why this is happening as well.

Any suggestions would be appreciated.

Windows for business | Windows Server | User experience | Other
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Harry Phan 8,495 Reputation points Independent Advisor
    2025-11-01T14:50:53.6866667+00:00

    The error you're seeing in Event Viewer, “Failure opening metadata of the owning provider for channel: hLastResult = The system cannot find the file specified,” typically indicates that Windows is trying to access an event log channel whose metadata is missing or corrupted. This often happens when:

    The system was migrated across platforms (like VMware to Hyper-V)

    Certain services or features were removed or reconfigured

    Event log providers were not properly registered post-migration

    Here’s how you can address it:

    Rebuild Event Log Metadata

    • Open Command Prompt as Administrator
    • Run: powershell wevtutil.exe el | foreach {wevtutil.exe gl $_} *This will list all event logs and attempt to load their metadata. Logs that fail will help you identify which providers are broken.

    Re-register Affected Providers

    If you identify specific services (e.g., DNS, AD DS) with broken logs, you can re-register their event providers using:

    Powershell

    wevtutil.exe im <path-to-manifest>.man

    *You’ll need the .man file from the service’s installation directory.

    Check for Missing or Corrupt Log Files

    1. Navigate to C:\Windows\System32\winevt\Logs
    2. Look for missing .evtx files or unusually small ones
    3. You can delete corrupted logs (after backing up) and restart the service to regenerate them

    Review ServerManager-ManagementProvider Logs

    As noted in your Server Manager warning, check:

    code

    Event Viewer > Applications and Services Logs > Microsoft > Windows > ServerManager > Operational

    *This may give more insight into which logs or permissions are failing.

    Run SFC and DISM

    These tools can repair system file corruption:

    powershell

    sfc /scannow

    DISM /Online /Cleanup-Image /RestoreHealth

    These errors don’t usually affect domain controller functionality, but cleaning them up will improve monitoring and reduce noise in your logs. Let me know if you’d like help identifying specific providers or scripting the cleanup.

    And if this answer helped, feel free to hit “Accept answer” so others can benefit too 😊.


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.