none
Don't see Windows 10 Updates when injecting updates into Win10 OS Image RRS feed

  • Question

  • Under Software Library – Operating Systems – Operating System Images when I right click on my Win10 image and select Schedule Updates I only see Windows 8 updates.  I don’t see any Windows 10 updates. 

    I’ve selected Windows 10 on my Software Update Point and resynchronized.  Windows 10 updates do show up under All Software Updates and I can push them to a collection, but they are not on the list of updates I can select from to inject into the image.  I’m not sure why they wouldn’t be there.  We’ve got SCCM 2012 R2 SP1 here.  Any help would be greatly appreciated!

    Friday, October 9, 2015 3:40 AM

Answers

  • As far as i know a hotfix is currently not available. I still encounter the problem for myself, but it doesn't really bother me because i install the Updates in my Capture Task-Sequence which creates my Reference Image. But still, it is not how it should be...

    The best way to get a hotfix or workaround is to contact CSS so that Microsoft can get a look at it and maybe we see a hotfix or a Workaround. As far as i know nobody has opened a case yet, and Microsoft can't provide Hotfixes for problems that they are unaware of.


    Simon Dettling | msitproblog.com | @SimonDettling

    Friday, October 9, 2015 11:39 AM

All replies

  • Hi

    This is a known issue in R2 SP1/SP2. It is solved by installing this hotfix: https://support.microsoft.com/en-us/kb/3089193

    And while you are at install this hotfix as well: https://support.microsoft.com/en-us/kb/3084586


    Friday, October 9, 2015 6:05 AM
  • This is a known issue in R2 SP1/SP2. It is solved by installing this hotfix: https://support.microsoft.com/en-us/kb/3089193



    The Hotfix you mentioned is if you don't see any updates at all in the Schedule Updates Wizard. Here we have the Problem that Configuration Manager thinks that the Windows 10 Image is a Windows 8 Image and so provides Windows 8 Updates.

    Simon Dettling | msitproblog.com | @SimonDettling


    Friday, October 9, 2015 6:08 AM
  • Simon - This looks like what's happening.  Our OS is being identified as version 6.2.10240.16384 even though it is Windows 10.  Have you seen a resolution or hotifx for this anywhere?
    Friday, October 9, 2015 11:31 AM
  • As far as i know a hotfix is currently not available. I still encounter the problem for myself, but it doesn't really bother me because i install the Updates in my Capture Task-Sequence which creates my Reference Image. But still, it is not how it should be...

    The best way to get a hotfix or workaround is to contact CSS so that Microsoft can get a look at it and maybe we see a hotfix or a Workaround. As far as i know nobody has opened a case yet, and Microsoft can't provide Hotfixes for problems that they are unaware of.


    Simon Dettling | msitproblog.com | @SimonDettling

    Friday, October 9, 2015 11:39 AM
  • Actually, the product team is aware of the issue of the captured image showing up as version 6.2.x. At this point though, there is no resolution or recommendation although I don't know if there are any negative ramifications. If you encounter any, certainly open a case with Microsoft.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Friday, October 9, 2015 1:45 PM
  • The negative ramification is that updates don't apply to the image so a deployed OS will be in an RTM state and then require the various (sizable) updates to be installed post-deploy which is far from ideal, especially given that these updates include fixes for the various critical Flash vulnerabilities in IE11.

    The updates also don't appear to be applied using the appropriate steps in the task sequence, but even if they did, adding half an hour to a task sequence that would otherwise only take 20 minutes _total_ is far from ideal.

    The odd thing is, I just did a build & capture on a clients system, and the version is reported correctly, so there may be other factors involved as as far as I can see they're running the same versions of everything that we are (SCCM 2012 R2 SP1 CU1 & Win 10 ADK).

    Tuesday, October 20, 2015 12:29 AM
  • My comment about negative ramifications was to whether the image showing as 6.2 in the ConfigMgr console had any negative ramifications or if this is just a cosmetic issue.

    As for time, if it takes 30 minutes to install the very small number updates available for Windows 10, then you've potential got bigger/other issues.


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, October 20, 2015 1:21 PM
  • Half an hour may be an exaggeration, but it certainly increases the overall deployment time significantly, even if running the updates phase in a task sequence and there are _no_ updates available. When there's a ~500MB CU available that adds some more time.

    Regardless, I'd definitely call not being able to use the "Schedule Updates" feature on a Windows 10 image at all due to this mis-reporting of the version a negative. It's definitely not just "cosmetic".

    Thursday, October 29, 2015 7:24 PM
  • But that's only for images captured in ConfigMgr. If you start with an image from the media, updates are injected fine and the image version number is reported correctly. That's my point.

    Jason | http://blog.configmgrftw.com | @jasonsandys


    Thursday, October 29, 2015 7:42 PM