Move or Delete a WSUS 4 Windows Internal Database (WID) on Windows Server 2012 14

If you google  how to delete or move a WSUS database based on WID, you most likely will run into blog posts based on WSUS 3.0 and Windows 2008. But with Windows 2012, their advise is not valid anymore, because basically all these post are making use of SQL Server Management Studio 2005 or 2008 Express and the Server Name “\\.\pipe\Microsoft##SSEE\sql\query“.

For Windows 2012 you will need the following updated information:

  1. WSUS for Windows 2012 is up to version 4. If you read a blog post about 3 something you know (now?) the info is wrong.
  2. The WSUS 4 WID database is in the following location: C:\Windows\WID\Data\SUSDB.mdf. Delete or move this database at the file level is not an option, you have to use the SQL Management Studio.
  3. Install SQL Server Management Studio 2012 Express (Download SQLManagementStudio_x64_ENU.exe).
  4. Once installed run SQL Management Studio 2012 with Run As Administrator.
  5. Make the connection with Server Name: \\.\pipe\Microsoft##WID\tsql\query
  6. Now you can use most posts to delete or move the WSUS database.

14 thoughts on “Move or Delete a WSUS 4 Windows Internal Database (WID) on Windows Server 2012

  1. Reply AMRAAM Nov 11,2013 04:10

    Thanks a Bunch! Exactly what I was looking for.

  2. Reply Wade Apr 24,2014 12:23

    This makes no sense…

    Connect via Management Studio to ServerName\\.\pipe\Microsoft##WID\tsql\query ??

    What in the **** are you talking about?

    • Reply Cesare Auteri Apr 25,2014 15:11

      Make sure you start the SQL Management Studio as Administrator otherwise it will NOT work!
      In the server name field paste: “\\.\pipe\Microsoft##WID\tsql\query”. This way you can connect to the database.

  3. Reply Bob Hatcher Sep 12,2014 13:06

    Still unable to connect to the database. See attached message.

    TITLE: Connect to Server

    Cannot connect to \\.\pipe\Microsoft##WID\tsql\query.


    A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 – Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

    For help, click:


    The system cannot find the file specified



  4. Reply Singaravelan Oct 21,2014 17:11

    Very good post.. Its working for me

  5. Reply John Rolstead May 22,2015 15:29

    If you are moving a WSUS 4.0 instance from WID to SQL on a remote server, then the guidance for editing the registry is slightly different from W2K8 R2 to W2012. You only need to change the SQLSERVERNAME value.

    the wYukonInstalled and SqlInstanceIsRemote values don’t exist in W2012 WSUS 4.0

  6. Reply Sectify Sep 11,2015 22:40

    This ‘simple’ secret has saved a client of ours who is re-architecting their business. Made this reply to give a thumbs up to the author!

  7. Reply James Dec 23,2015 09:38

    It would be nice if there were an option to clear/remove the database when you uninstall WSUS, then this would be unnecessary. Thank you very much, you made my day a lot easier.

  8. Reply sccmsri Mar 1,2016 23:41

    Thanks a Ton

  9. Reply Hasan Köroğlu Apr 2,2016 20:33

    Thanks buddy.

  10. Reply Luiz Cataldo Oct 16,2016 12:35

    Hi Guys,
    I deleted WID folder with WSUS installed in my server 2012, my “server manager” stopped, It’s can’t add or removal features and functions. How I can to remove manually WID?

  11. Reply Luiz Cataldo Oct 16,2016 17:10

    I Solved, I recreated data folder with templates mdf.

Leave a Reply





This site uses Akismet to reduce spam. Learn how your comment data is processed.