Share via

Anyone having issues with WID broken after January 9 Cumulative updates?

Anonymous
2024-01-18T12:48:37+00:00

After applying January Cumulative Updates to Windows Server 2016 and Windows Server 2019, Windows Internal Database is no longer functional. Rolling back the updates does NOT fix this issue. Error 7000

The MSSQL$MICROSOFT##WID service failed to start due to the following error:
The system cannot find the file specified.

We have seen this in both RDS and WSUS deployments where WID has been installed with said services. Redeployment of WID and said services have been the ONLY fix thus far.

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

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. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

8 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-01-19T08:21:45+00:00

    Hi Stan Halter,

    Which KB did you install on your machine?

    Regards,

    Lei

    0 comments
  2. Anonymous
    2024-01-19T12:45:03+00:00

    KB5034119

    0 comments
  3. Anonymous
    2024-01-22T08:42:00+00:00

    This issue has been reported by some users, and Microsoft is currently investigating it.

    In the meantime, you can try the following workaround:

    1. Open an elevated command prompt.
    2. Type "sc delete MSSQL$MICROSOFT##WID" (without quotes) and press Enter.
    3. Type "sc create MSSQL$MICROSOFT##WID binPath= "C:\Windows\system32\sqlservr.exe" -sMICROSOFT##WID" (without quotes) and press Enter.
    4. Type "sc start MSSQL$MICROSOFT##WID" (without quotes) and press Enter.

    This should recreate the MSSQL$MICROSOFT##WID service and start it. If this does not resolve the issue, I recommend you could uninstall KB5034119.

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2024-01-31T10:01:32+00:00

    This issue has been reported by some users, and Microsoft is currently investigating it.

    In the meantime, you can try the following workaround:

    1. Open an elevated command prompt.
    2. Type "sc delete MSSQL$MICROSOFT##WID" (without quotes) and press Enter.
    3. Type "sc create MSSQL$MICROSOFT##WID binPath= "C:\Windows\system32\sqlservr.exe" -sMICROSOFT##WID" (without quotes) and press Enter.
    4. Type "sc start MSSQL$MICROSOFT##WID" (without quotes) and press Enter.

    This should recreate the MSSQL$MICROSOFT##WID service and start it. If this does not resolve the issue, I recommend you could uninstall KB5034119.

    Hi, I have the same problem.

    I tried that procedure, but I dont have sqlservr.exe on my server (or on that path).

    0 comments
  5. Anonymous
    2024-02-19T09:28:17+00:00

    Hi,

    does the latest KB still have the same issue？

    0 comments