locked
Windows 10 computers showing on WSUS Server 2012 R2 as Windows Vista RRS feed

  • Question

  • Will there be a windows update for WSUS to fixit Windows 10 computers showing as Windows Vista?
    Thursday, July 30, 2015 3:25 PM

Answers

  • Hotfix available now:

    Update to enable WSUS support for Windows 10 feature upgrades


    Rolf Lidvall, Swedish Radio (Ltd)


    • Edited by Rolf Lidvall Monday, October 12, 2015 10:51 AM
    • Proposed as answer by Simon Franz Wednesday, October 21, 2015 10:01 AM
    • Marked as answer by SpaceCowboy_1958 Saturday, November 14, 2015 2:14 AM
    Monday, October 12, 2015 10:50 AM
  • known issue, wait for a wsus product update or hack through the database

    http://titlerequired.com/2015/07/22/windows-10-on-wsus-shows-as-windows-vista/

    • Proposed as answer by DonPick Saturday, August 1, 2015 8:27 AM
    • Marked as answer by Steven_Lee0510 Monday, August 10, 2015 3:18 AM
    Friday, July 31, 2015 5:34 PM
  • Same problem here. Oddly, the WSUS server is downloading and reporting on Windows 10 updates, it's just the clients that are reported wrong as Vista.

    Curt Kessler - FLC

    The SUSDB database consists of many tables. The "products" tables (which is how updates are categorised) is a different table than the "client OS" table. The "products" table is populated/updated during the sync to USS, but, the "Client OS" table is only populated/updated via an update package to WSUS itself.

    So, we wait for an update package for WSUS, or, we hack the db.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Wednesday, August 5, 2015 10:21 PM

All replies

  • Same problem for me on WSUS Server 2012 R2 and clients on final version of Windows 10 Pro.
    Friday, July 31, 2015 9:35 AM
  • known issue, wait for a wsus product update or hack through the database

    http://titlerequired.com/2015/07/22/windows-10-on-wsus-shows-as-windows-vista/

    • Proposed as answer by DonPick Saturday, August 1, 2015 8:27 AM
    • Marked as answer by Steven_Lee0510 Monday, August 10, 2015 3:18 AM
    Friday, July 31, 2015 5:34 PM
  • Same problem here. Oddly, the WSUS server is downloading and reporting on Windows 10 updates, it's just the clients that are reported wrong as Vista.

    Curt Kessler - FLC

    Wednesday, August 5, 2015 9:56 PM
  • Same problem here. Oddly, the WSUS server is downloading and reporting on Windows 10 updates, it's just the clients that are reported wrong as Vista.

    Curt Kessler - FLC

    The SUSDB database consists of many tables. The "products" tables (which is how updates are categorised) is a different table than the "client OS" table. The "products" table is populated/updated during the sync to USS, but, the "Client OS" table is only populated/updated via an update package to WSUS itself.

    So, we wait for an update package for WSUS, or, we hack the db.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Wednesday, August 5, 2015 10:21 PM
  • Looking for a solution for this as well.  I tried the hack but it's reverted.

    (I posted in the wrong place originally: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/wsus-shows-windows-10-clients-as-vista/a522bf5e-05e1-41e3-bff5-e2698c4d31df)

    Thursday, September 3, 2015 12:01 PM
  • Yep, the hack will revert when the PC in question running Windows 10 (or server running Server 2016 Tech Preview) gets a new round of updates.

    Speaking of Windows Server 2016 Tech Preview, try using its WSUS console to connect to your WSUS server(s).  You'll notice that it reports Windows 10 computers that haven't had the SQL DB hack applied  as "Windows (Version 10.0)".

    So there is a bit of truth in what I heard that the issue is with how the OS reports the new version of Windows.  However, I still think it's something that can be easily patched in WSUS, but Microsoft doesn't see this as a high priority right now.

    Maybe they'll have the patch out once Windows 10 RSAT is released. 

    ...or maybe Microsoft is going to use this to force people to upgrade to Windows 10 and Server 2016...

    We shall see...

    Thursday, October 1, 2015 5:48 PM
  • If they force enterprises to update to Server 2016 that would be very unkind and put a lot of IT departments under a great deal of stress. I cannot imagine they would do that as a lot of enterprises have only just upgraded from XP to Windows 7 / Server 2008r2 (and that took them a year to complete!)
    Monday, October 12, 2015 10:20 AM
  • Hotfix available now:

    Update to enable WSUS support for Windows 10 feature upgrades


    Rolf Lidvall, Swedish Radio (Ltd)


    • Edited by Rolf Lidvall Monday, October 12, 2015 10:51 AM
    • Proposed as answer by Simon Franz Wednesday, October 21, 2015 10:01 AM
    • Marked as answer by SpaceCowboy_1958 Saturday, November 14, 2015 2:14 AM
    Monday, October 12, 2015 10:50 AM
  • Hotfix available now:

    Update to enable WSUS support for Windows 10 feature upgrades


    Rolf Lidvall, Swedish Radio (Ltd)



    This hotfix is for Windows Server 2012 & 2012 R2. What about Windows Server 2008R2?
    Thursday, October 22, 2015 7:15 AM
  • Applying the hotfix worked for me on Windows Server 2012R2.
    Thursday, October 29, 2015 12:13 PM
  • Hotfix available now:

    Update to enable WSUS support for Windows 10 feature upgrades


    Rolf Lidvall, Swedish Radio (Ltd)



    This hotfix is for Windows Server 2012 & 2012 R2. What about Windows Server 2008R2?
    Is there a hotfix for Windows Server 2008R2 until now?
    Thursday, November 5, 2015 6:18 AM
  • There is no hotfix planned for Server 2008 R2 that I've been told.
    Wednesday, November 18, 2015 11:47 PM
  • There should be update for Windows Server 2008 R2 ... this system is still supported by Microsoft. It is unfair that users have to hack database to fix it ... supporting enterprise clients should't look like this :(
    Wednesday, November 25, 2015 11:19 AM
  • Same here, an undate for Windows 2008R2 is really needed! 

    Thanks!

    Friday, February 19, 2016 6:16 AM
  • Am 19.02.2016 wrote MikDima:

    Same here, an undate for Windows 2008R2 is really needed! 

    W2008R2 has only Exetended Support, it gets only Security Updates,
    not a Feature Upgrade. If you want to see Windows 10 in WSUS, you can run this Script daily:

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
    SET [OSDescription] = 'Windows 10'
    WHERE [OSMajorVersion] = '10'
    AND [OSMinorVersion] = '0'
    AND [OldProductType] = '1'
    AND ([OSDescription] <> 'Windows 10' or [OSDescription] IS NULL)

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Friday, February 19, 2016 2:33 PM
  • an undate for Windows 2008R2 is really needed!

    This script will update Server 2012 and windows 8.1 also

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
    SET [OSDescription] = 'Windows 10'
    WHERE [OSMajorVersion] = '10'
    AND [OSMinorVersion] = '0'
    AND [OldProductType] = '1'
    AND ([OSDescription] <> 'Windows 10' or [OSDescription] IS NULL)
    go

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
    SET [OSDescription] = 'Windows 8.1'
    WHERE [OSMajorVersion] = '6'
    AND [OSMinorVersion] = '3'
    AND [OldProductType] = '1'
    AND ([OSDescription] <> 'Windows 8.1' or [OSDescription] IS NULL)
    go

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]
    SET [OSDescription] = 'Windows Server 2012 R2'
    WHERE [OSMajorVersion] = '6'
    AND [OSMinorVersion] = '3'
    AND [OldProductType] <> '1'
    AND ([OSDescription] <> 'Windows Server 2012 R2' or [OSDescription] IS NULL)
    go

    Wednesday, March 9, 2016 8:31 AM
  • Hotfix available now:

    Update to enable WSUS support for Windows 10 feature upgrades


    Rolf Lidvall, Swedish Radio (Ltd)



    I'm on Server 2012 (not R2) and this KB is already installed.  WSUS still reports Vista.
    Thursday, March 24, 2016 8:50 PM
  • Likewise..

    Wednesday, May 11, 2016 9:08 PM
  • -- Adapted from https://windowsserveressentials.com/2015/07/22/windows-10-on-wsus-shows-as-windows-vista/

    -- This will have to be run again at a later stage to update DB if more clients are added

     

    --temp fix for Windows 8.1

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]

    SET [OSDescription] = 'Windows 8.1'

    WHERE [OSMajorVersion] = '6'

    AND [OSMinorVersion] = '3'

    AND [OldProductType] = '1'

    AND ([OSDescription] <> 'Windows 8.1' or [OSDescription] IS NULL)

     

    --temp fix for Windows Server 2012 R2

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]

    SET [OSDescription] = 'Windows Server 2012 R2'

    WHERE [OSMajorVersion] = '6'

    AND [OSMinorVersion] = '3'

    AND [OldProductType] <> '1'

    AND ([OSDescription] <> 'Windows Server 2012 R2' or [OSDescription] IS NULL)

     

    --temp fix for Windows 10 Professional

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]

    SET [OSDescription] = 'Windows 10 Professional'

    WHERE [OSMajorVersion] = '10'

    AND [OSMinorVersion] = '0'

    AND [OldProductType] = '1'

    AND [SuiteMask] = 256

    AND ([OSDescription] <> 'Windows 10 Professional' or [OSDescription] IS NULL)

     

    --temp fix for Windows 10 Home

    UPDATE [SUSDB].[dbo].[tbComputerTargetDetail]

    SET [OSDescription] = 'Windows 10 Home'

    WHERE [OSMajorVersion] = '10'

    AND [OSMinorVersion] = '0'

    AND [OldProductType] = '1'

    AND [SuiteMask] = 512

    AND ([OSDescription] <> 'Windows 10 Home' or [OSDescription] IS NULL)

     

    Wednesday, July 20, 2016 7:10 AM
  • Download this and issue resolved 

    https://download.microsoft.com/download/D/3/8/D3854613-B1DB-40A2-BB05-5FF9CCDEFB74/Windows8.1-KB3095113-v2-x64.msu

    Tuesday, October 18, 2016 12:15 PM
  • Download this and issue resolved 

    https://download.microsoft.com/download/D/3/8/D3854613-B1DB-40A2-BB05-5FF9CCDEFB74/Windows8.1-KB3095113-v2-x64.msu


    Yes, as posted by Rolf (October 12th 2015) https://support.microsoft.com/en-us/kb/3095113 addresses this issue for WS2012 & WS2012R2

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Tuesday, October 18, 2016 8:04 PM
  • Thanks Rolf Lidvall :)
    Thursday, June 8, 2017 8:58 PM
  • No problem!

    Rolf Lidvall, Swedish Radio (Ltd)

    Wednesday, June 14, 2017 12:27 PM
  • Download this and issue resolved 

    https://download.microsoft.com/download/D/3/8/D3854613-B1DB-40A2-BB05-5FF9CCDEFB74/Windows8.1-KB3095113-v2-x64.msu

    I just tried to install this patch, and it says it's not applicable.

    I confirmed that the prerequisite (KB2919355) is installed.

    Thursday, February 1, 2018 3:13 PM