Windows 10 Showing as Vista in WSUS

1. You need the following patches on your server, if you are up to date then its not really needed.
support.microsoft.com/kb/2720211
support.microsoft.com/kb/2734608

2. You will need to install the following:
www.microsoft.com/en-in/download/details.aspx?id=36434
www.microsoft.com/en-in/download/details.aspx?id=36433

It gave me bollocks about having to restart the server, I didn’t bother…

3. Download and extract the SQL Script here and save it to your C: drive.

4. Open a command prompt prompt as Administrator and change directory to the default sqlcmd directory. You can just copy and paste this:

cd C:\Program Files\Microsoft SQL Server\Client SDK\ODBC\110\Tools\Binn

5. Run the sql command by copying and pasting this:

SQLCMD.EXE -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -i c:\SQL.sql >c:\output.txt

You can check the output file in the C drive, check the bottom of the file for:

Statistics for all tables have been updated.
Done updating statistics.2015-08-05 09:38:29.950

Then restart the “Update Services” on the server (click start and type services.msc)

Open WSUS and hit opens and run a server clean up. Then make sure you have chosen to install Windows 10 updates in the products and classifications section of options.

 

 

33 thoughts on “Windows 10 Showing as Vista in WSUS

  1. Hi Justin

    Thx, very nice article, but keep in mind that all those users with WSUS on a Server 2012 R2 and SQL 2012 will have to use another connection string:

    (Version 2003 – 2008) np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
    (Version 2012) np:\\.\pipe\MICROSOFT##WID\tsql\query

    Regards
    Marco

  2. I followed all the instructions and then ran this:

    SQLCMD.EXE -S np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query -i c:\SQL.sql >c:\output.txt

    it hangs on the command prompt. The output file simply says:
    Changed database context to ‘SUSDB’.

    1. Has it at all reverted back? For a few of us, it reverted back to Vista for Windows 10 and Windows 6.3 for Windows 2012 R2. I can run through the instructions and it temporally fixes. Not sure what is triggering it to revert back either.

  3. On Server 2008 R2, the following worked for me:

    sqlcmd -S \\.\pipe\MSSQL$WSUSDB\sql\query -i sql.sql >c:\output.txt

    The error output was erroneous “network error” messages, so I figured my system did not match Justin’s for whatever reason. To find the correct named pipe, I used the following PowerShell command:

    [System.IO.Directory]::GetFiles(“\\.\\pipe\\”)

    Pipelist.exe from SysInternals gave the same basic info, for those having trouble with the command in the original post.

  4. Does not work on WS2008R Standard if you use Server Manager to install WSUS. This is because it does not create the SQL directory which is specified in the command strings. It uses a Windows Internal Database.

  5. As there doesn’t seem to be an update to solve this in Windows Server 2008 R2 (WSUS 3.2) I tried your workplan and it works perfectly. Thanks a million!!!

  6. I’m late this info but grateful none the less. Easy to follow instruction. Worked well on my 2008 R2 WSUS server.

  7. The systems revert back every time the systems get polled. We have our wsus set up to assign groups using GPO, so that is when it’s happening for us. If you are manually assigning groups in wsus, this may not be an issue for you.
    There are a few ways you can mitigate this using the “Update SQL” solution path that I can think of.
    1) Run this script using either a sql job (for the DBA’s in the crowd) or a windows task scheduler task (for the System Admin folks).
    2) Create a trigger in SQL using the same logic in the SQL script to automatically change the data as machines are added or updated.

Leave a Reply

Your email address will not be published. Required fields are marked *