[Solved] Looking for a windows image iso or svf or esd, en-GB 1703 updated july 2017

Discussion in 'Windows 10' started by tnx, Aug 2, 2017.

  1. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    Going to be doing a new install and I have been looking for

    I have :
    and
    But i have taken a fancy to the en_GB versions and I like to use Pro and my digital licence.

    I have scoured a lot of threads and posts and cant seem to find an .iso image, .esd or a .svf patch.

    Does this image exist ?

    Cant even get on the MSDN library to even look.

    anybody point me in the right direction ?

    cheers..
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    8,391
    28,863
    270
    Only en-us gor updated ISO for all editions

    other languages only got updated Enterprise ISO
     
  3. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    Cheers for that info..
     
  4. MrMagic

    MrMagic MDL Guru

    Feb 13, 2012
    5,855
    3,957
    180
    There was only March and July afaik?

    MS released a refreshed ISO in June & another one in July?
     
  5. MrMagic

    MrMagic MDL Guru

    Feb 13, 2012
    5,855
    3,957
    180
    What was the point in that? They gonna release a refreshed ISO every month now?

    (Haven't been keeping up with the latest for a few weeks)
     
  6. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    #11 tnx, Aug 2, 2017
    Last edited: Aug 2, 2017
    (OP)
    Her's a question..

    I have
    If I intergrate onto an offline install.wim update
    ( Which i downloaded from M.Soft Update catalogue )
    Does this make a complete "July" updated image, which i believe is 1703 build 15063.502 or will there be other updates also required for this.

    FYI... Running Windows 7 but think its about time I switched to Windows 10. Might as well start with the latest Windows 10 image.
     
  7. superleeds27

    superleeds27 MDL Member

    Nov 24, 2007
    129
    4
    10
    I'm looking for the same thing actually.
     
  8. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    I will let you know how my test goes intergrating the update. So far though not having too much luck.

    On the june image once the Pro index is exported the install.wim file size is a little under 4gb. So this will push the size limet over what FAT32 can handle any way.

    It might be to just use June and have the update on the USB drive and install it manually post install. maybe.
     
  9. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,930
    23,008
    340
    Servicing 15063 images on 7 host: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-217#post-1361827
     
  10. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    Thanks for that info.

    I have bit the bullet and now Win 10 is my main OS. Just installed the en-GB 1703 updated to June image and then that ran the update file manually and now my system is at, v1703 build 15063.502.

    Probably have a go at integrating the update into the install.wim at some point, just gotta get my software back in first.
     
  11. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    Had a couple of goes at this but could not get the install.wim under 4GB.

    Until I decided to have at using the "MSMG" toolkit. I used it on the original iso image
    Integrated the update into the Pro Index
    then I exported the Pro Index and got an install.wim at roughly 3.9GB.

    Just done a fresh install onto my test rig and sure enough it installed as smooth as you like and got v1703 build 15063.502.

    What I am really wondering about now is what the toolkit is doing different to me and my DISM commands....I feel the need to find out.

    worked though.Which is nice.
     
  12. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    17,930
    23,008
    340
  13. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    @enthusiast

    Well. I have just checked how I have been doing it.

    Using the original image
    I extracted the files and took out the original install.wim.
    in my DISM folder structure i ran
    Code:
    @echo off
    color 1f
    title Get Image Info
    
    Dism /Get-ImageInfo /ImageFile:C:\DISM\install.wim\install.wim
    pause 
    To make sure indesx #1 was Pro, which it is.
    I mounted the image
    Code:
    @echo off
    color 1f
    title Mount install.wim
    
    
    dism /mount-wim /wimfile:%~dp0install.wim\install.wim /index:1 /mountdir:%~dp0mount
    
    pause
    
    Integrated the update
    using
    Code:
    @echo off
    color 1f
    title Integrate Updates
    
    dism /image:%~dp0mount /Add-Package /PackagePath:%~dp0updates
    I committed the changes
    Code:
    dism /unmount-wim /mountdir:%~dp0mount /commit
    
    pause
    then exported the Pro index
    Code:
    @echo off
    color 1f
    title Mount install.wim
    
    
    
    dism /Export-Image /SourceImageFile:%~dp0install.wim\install.wim /SourceIndex:1 /DestinationImageFile:%~dp0install.wim\Compressed\install.wim /compress:maximum
    
    
    pause 

    All works well but I end up with an image size of 4.4GB roughly.

    Now somewhere along the line my codes must be different to what the toolkit does.

    Any ideas of where I am going wrong in keeping it under 4GB ?
     
  14. mxman2k

    mxman2k MDL Developer

    Jun 20, 2007
    2,501
    5,327
    90
    Code:
    dism /Export-Image /SourceImageFile:%~dp0install.wim\install.wim /SourceIndex:1 /DestinationImageFile:%~dp0install.wim\Compressed\install.esd /compress:recovery
    Would export to the more compressed esd format. That should make the install file less than 4gb, it will take a while to make the esd.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. tnx

    tnx MDL Expert

    Sep 2, 2008
    1,624
    234
    60
    My option using the toolkit was to make an install.wim. Which was smaller than 4GB.

    I notice you put "/compress:recovery" I have not seen that bit of code before. What does that bit do ?