Share via

Can't perform update on windows server 2022

CBS tech - 001 0 Reputation points
2026-04-21T14:08:42.34+00:00

Cannot connect to VMI provider. you have permission or the ser is unreachable. I'm not able add on roles on windows server 2022

Windows for business | Windows Server | Directory services | Other
0 comments No comments

3 answers

Sort by: Most helpful
  1. Jason Nguyen Tran 17,430 Reputation points Independent Advisor
    2026-04-26T00:56:52.15+00:00

    Hi CBS tech - 001,

    I’m following up to check whether the issue has been resolved. Feel free to reply if you need further information. If the information provided was helpful, please click "Accept Answer" to help others in the community. Thank you!

    Was this answer helpful?

    0 comments No comments

  2. Jason Nguyen Tran 17,430 Reputation points Independent Advisor
    2026-04-21T15:04:50.3066667+00:00

    Hi CBS tech - 001,

    The error message about not being able to connect to the VMI provider usually points to issues with the Windows Management Instrumentation (WMI) service or related permissions. Here are a few steps you can try:

    • First, confirm that the Windows Management Instrumentation service is running. You can check this in Services.msc and restart it if necessary.
    • Run winmgmt /verifyrepository from an elevated command prompt to check the health of the WMI repository. If it reports corruption, you can rebuild it with winmgmt /salvagerepository.
    • Ensure that your account has local administrator rights, as adding roles and features requires elevated privileges.
    • If the server is domain-joined, verify that group policies are not restricting access to WMI or blocking role installation.
    • Check for pending updates or partially installed updates that may have left the system in an inconsistent state. Completing or rolling back those updates can restore functionality.
    • If the issue persists, running sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth can help repair system components that WMI depends on.

    In short, restarting WMI, verifying repository health, and ensuring proper permissions usually resolve this error. If corruption is too deep, an in-place repair upgrade with the Windows Server 2022 ISO may be required to restore full functionality.

    If you find this answer helpful, please consider clicking Accept Answer so others can benefit too.

    Jason.

    Was this answer helpful?

    0 comments No comments

  3. Q&A Assist
    2026-04-21T14:08:55.1833333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The error message indicates a problem with the WMI provider, which is required by Server Manager to query the system and add roles/features. To address both the permission and connectivity aspects, follow these steps:

    1. Verify administrative permissions
      • Sign in with an account that is a member of the local Administrators group on the Windows Server 2022 machine.
      • Membership in local Administrators is required to add roles and features in Server Manager.
    2. Confirm basic prerequisites for adding roles/features
      • Ensure the server is running normally and not in a failed or decommissioned state.
      • If adding roles/features on a remote server or offline VHD, confirm:
        • The account used is an administrator on the target server or VHD host.
        • The VHD (if used) matches the OS version of the host and is not mounted elsewhere.
        • For VHDs on a network share, the computer account of the mounting server has Read and Write permissions on the share.
    3. Try adding roles/features again via Server Manager
      • Open Server Manager.
      • Select ManageAdd Roles and Features.
      • Use Role-based or feature-based installation.
      • Select the local server (or correct remote server/VHD) and proceed.
      • If prompted for source files (for example, .NET Framework 3.5), specify a valid source path (such as a feature store or installation media) that grants Read permissions to the server’s computer account.
    4. If the issue involves an offline source/feature store
      • Ensure the side-by-side store (for example, \\server\share\sxs) exists and contains the Sources\SxS folder copied from Windows Server installation media.
      • Verify the share permissions grant Read to the server’s computer account (not just user accounts).
    5. If the WMI error persists
      • Because the error is specifically about the WMI provider, and the context here only covers WMI repair for SQL Server’s WMI provider (via recompiling a MOF file), do not apply that SQL-specific MOF procedure to the OS WMI provider.
      • At this point, focus on confirming:
        • The account is truly local admin.
        • The server is reachable if managed remotely.
        • No group policy or security hardening is blocking WMI or Server Manager operations.

    If, after confirming admin rights and prerequisites, the error still appears for all role/feature operations, further WMI-specific repair steps for the OS (outside the SQL-specific MOF guidance in the context) would be required, which are not covered in the provided material.


    References:

    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.