WSUS is not working after I move WSUS DB from C to E drive.

Yogesh Chaugule 1 Reputation point
2022-05-09T13:01:40.74+00:00

WSUS Synchronization is not working after I move WSUS DB from C to E drive.

I followed the below links :

https://answers.microsoft.com/en-us/windows/forum/all/move-wsus-database-from-root-partition-to-another/3885bb2e-3fdd-4e75-96d4-d2dbfe5a4e4c

https://4sysops.com/archives/move-wsus-database-and-content-updates-to-a-different-drive-or-folder/

But I am getting below error message

200351-image.png

OS - Windows Server 2019
DB - Windows Internal Database

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,612 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Rita Hu -MSFT 9,626 Reputation points
    2022-05-10T01:46:15.35+00:00

    @Yogesh Chaugule
    It seems that the you followed the above links try to move the Content folder. Am I right? Note that the Content folder is used to store the update files which are used to distribute to the devices. But the WID database files are placed into a named WID folder in the following path:
    C:\Windows\WID

    In my opinion, it is not allowed to move the WID database by default. The metadata which shown on the WSUS console are store into the SUSDB database.

    Please try to open the cmd as an administrator and navigate to the wsusutil.exe tool. Then try to run the wsusutil.exe postinstall command to fix it. It should be OK.
    200400-14.png

    wsusutil.exe postinstall content_dir=E\  
    

    Hope the above will be helpful. Please feel free to keep us in touch if there are any updates of the case.

    Best regards,
    Rita


    If the answer is the right solution, 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.

    0 comments No comments