Windows 10 on WSUS Shows as Windows Vista
July 22, 2015 48 Comments
Update: 15/10/2015
Please see below comment from Michael regarding Hotfix 3095113 which resolves this issue.
I noticed a thread on a forum regarding Windows 10 reporting to WSUS as Windows Vista. This was a problem if you recall for Windows 8 and Server 2012 simply reporting as Windows 6.3 or similar.
Since WSUS received no updates that i was aware of to fix that issue at the time, i found a SQL Command here that updated the WSUS DB to reflect the correct OS name.
Revisiting that now, It was easy enough to modify this to have WSUS report a Windows 10 machine, as Windows 10!
Granted, at this point it only appears that this is a useful workaround – not a permanent fix! (updated 05/08/2015)
The changes you need to add to the SQL cmd file are:
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)
Save this as part of your WSUS Maintenance Script, and run it.
Just a note on that, if you are running WSUS on Server 2012 or newer you will find your WSUS Database is at..
np:\\.\pipe\Microsoft##WID\tsql\query
not…
np:\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
that you may have used before.
When you go back into your WSUS Console you will see your machine now reflects the correct OS.
This has worked for me on the current build my Windows 10 lab machine is running on (Pro Insider Preview 1062) but i reserve the right to look silly if this does not work as expected on the full release version due in an excitingly imminent 7 days!
Whilst we are on the subject of WSUS maintenance, you did know about Invoke-WSUSServerCleanup didn’t you?
This allows you to run the Clean up wizard from PowerShell and better, means you can schedule it to run!
About Robert Pearman
Title (Required) 
Script won’t run – there’s no database instance called MICROSOFT##SSEE?
Figured it out – the SUSDB is stored under . Just specify and the script runs fine.
Now for ‘Invoke-WSUSServerCleanup’, didn’t know about that so I dug into it. But it seems the cmdlets are not available on Windows Server 2008 r2?
I suspect it is only a 2012 / 2012 R2 or newer cmdlet.
Hi Rob
There’s a typo in the script – the second last line should read
AND [OldProductType] = ‘1’
so that it picks up the desktop OS
John
Thanks for picking that up John.
How to start/use the script?! sqlcmd?
If you follow the link to http://www.vmwareandme.com/2014/03/Solved-Windows-8.1-Shows-as-Windows-6.3-in-WSUS-SP2.html this should give you the instructions you need. Then you get the WSUSMaintenance.Sql file and edit it with the additions posted here.
Then yes, use SQLCMD to run the script.
What about when using WID for WSUS???
What about servers running WID? I’m running a stand alone for just WSUS and WDS, and all my Windows 10 Machines show as Windows Vista on Server 2012r2. Any fix for that, as I don’t want to migrate to SQL due to not wanting to add other resources to the system
I am also using WID on my Server.
Have a look here, https://gallery.technet.microsoft.com/scriptcenter/6f8cde49-5c52-4abd-9820-f1d270ddea61 in the Q&A there is a lot of good information on how to run the script against your server. The path I put above works for the WID on my Server. (2012 non R2)
Script worked first (Client appeared as “Windows 10” in WSUS), but never gets updates. WSUS Cleanup Wizard started and rebootet after finishing. Client rebootet. Appears now again as “Windows Vista” :(
Server OS is 2012R2.
Seems there have to be done more…
Yes I have actually seen this myself.
Was waiting to see if it was just me. Will investigate!
Thanks for your work!
While this is a good workaround, I wouldn’t dare acknowledge this as a “fix”. Any time frame to address this issue in WSUS?
A good point well made, updated to reflect that.
No – no news on how WSUS will interact with Windows 10 after WUfB / Enterprise SKUs etc all shakes out.
Nothing I have seen anyway.
Is Microsoft at least aware of it?
Microsoft released KB3075853 today. Has something to do with WU-Agent, see http://www.eightforums.com/windows-updates-activation/69664-kb3075853-why-so-vague-microsoft.html
Approved it to my WSUS and rebootet…Client still appears as Vista :(
Kicked the Client from the WSUS Computergroup. Did wuauclt.exe /detectnow and wuauclt.exe /reportnow until my fingers bleed to force the client to re-appear in WSUS. It does not :(
I think there is nothing to be done until MS pulls the brown ring from the finger…what a shame…
Update: Client re-appaered in WSUS after rebooting client. Take a *very* long time. Again, its called Vista :(
Update: Client got really Updates for W10 today from WSUS, despite it´s shown as Vista. So it´s really only a cosmetic bug…sit back, stretch your sack and wait for a fix from MS…
Hey Chris,
Interesting news!
On my WSUS system I am seeing new registered Windows 10 clients show as Vista, until I run the ‘fix’, they then retain Windows 10 status. I am starting to wonder if it is actually something in the configuration for Windows Vista Clients that is making 10 show this way.
In any case, I suspect you are correct – waiting for MS is always the better idea… we just never know when they may get around to it.
There won’t be a fix from MS as they never fixed how 8.1 showed up in the console either.
They did. Did you try KB2938066 to install on the console system?
Is/was already installed on my WSUS. W10 Client still seen as Vista :(
That update only refers to the issue with Windows 8/8/1 (I guess MS will address 10 in the same fashion eventually). Also, needs to be installed on the SERVER, and any machines that have the CONSOLE installed.
I am still not receiving any KBs related to Windows 10 on my WSUSes. Is there anything specific I need to do? Many thanks.
Have you made sure to select it as a syncd product?
I set 10 as a synced product and then ran a sync. It showed 157 new updates in the sync log but no new updates are available to approve.
They’re not being auto approved by a rule?
They should be but that has never seemed to work reliably on any of the half dozen WSUS boxes I’ve seen. No new updates show for the Windows 10 PC when you check it’s status. It actually shows it needs a Windows 7 update like it did before I added the 10 sync.
Microsoft has released a hotfix for Windows 2012 and 2012 R2 that will enable support for Windows 10 Feature upgrades. This hotfix also corrects the Windows 10/Vista issue as well as the Windows 8.1 as Windows 6.3 display.
https://support.microsoft.com/en-us/kb/3095113
Hi,
I have Windows 2008 R2 (WSUS server downstream server), Windows 10 client shows as Vista. Is there any update to display Windows 10 correctly?
Patches already installed;
WSUS-KB2720211-x64
WSUS-KB2734608-x64
WSUS-KB2938066-amd64
Thanks Rob & Michael, I’ve just installed the hotfix Fix4511610 from Michael’s link above on my new WSUS server (2012 R2) and the Windows 10 clients are now showing as Windows (version 10.0)
You are quite welcome Diane!
Rob, Michael; Hotfix4511610 is for Server 2012 R2. Does anyone want to venture an opinion on whether it *might* work for 2008 R2?
(long shot, I know…)
I’ll venture, never.
so there’s no MS hotfix working for 2008 R2?
No, it does not work for WSUS 3.2 running on Windows 2008 R2 and unfortunately, I am not able to find any information indicating that Microsoft will put out a hotfix. However, I will say that Windows 10 updates are available and Windows 10 workstations do get the updates successfully… so it appears to be mostly a cosmetic issue with how the OS is displayed.
what´s about the Hotfix for Win Server 2008R2 ? Any News ?
worked like a charm on my windows 2008 standard, thank you! Was weird to see windows 10 beeing shown as win vista lol
What works? the hotfix or the procdeure
Does anybody have any news of an update on this for SBS 2011 /2008 R2?
Would be greatly appreciated…
Possibly useful, http://blogs.msmvps.com/bradley/2016/01/22/three-posts-of-interests-to-those-managing-smb-servers/
Great! Thanks.
Just a suggestion…. Updating the Query to use the SuiteMask allows you to more consistently address how Microsoft displayed older OSes Like XP, Vista, 7, etc.. It’s totally cosmetic, but, here it is.
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)
–not 100% tested for Win10 Home as I only own Professional.. It’s possible there’s a Basic, Starter, etc Editions as well
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)
And, as noted by other comments, Microsoft is suggesting you move to Server 2012 or higher since they are deprecating WSUS 3, and not adding full Win10 support to WSUS 3. :(
It’s kind of stupid since they have an OSMap table that they didn’t just use that for the OS mappings, but there are other changes in WSUS that pretty much force you to upgrade to Server2012+ for WSUS. Oh Well.
Steven
Hello,
can someone please post the contents of the tbosmap table, the last record with [osid] 255 from wsus 3.0 SP2?
Thx in advance