[DISCUSSION] Windows 10 Enterprise (N) LTSC 2019

Discussion in 'Windows 10' started by Tito, Feb 1, 2018.

  1. zbigniew59

    zbigniew59 MDL Senior Member

    May 14, 2016
    374
    171
    10
    Thank you. Now it is working
     
  2. canuckie

    canuckie MDL Novice

    May 17, 2019
    3
    0
    0
    #3682 canuckie, May 17, 2019
    Last edited: May 17, 2019
    This must've been answered before, but I'm probably too stupid to find the answer.

    - The "Windows.iso" file is what Microsoft's "mediacreationtool1809" has downloaded, en_US, x64.
    - ADK 1809 installed, "Deployment Tools" only.

    I've tried using Start.cmd first, and when that failed I tried PowerShell directly, but to no avail.


    What am I doing wrong here?
    i.imgur.com/aEFy6cx.jpg

    P.S. - it's because there's "install.esd" instead of "install.wim" within the ISO, isn't it?
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,005
    93,798
    450
    The windows.iso, created by the MCT won't be LTSC, this is the LTSC thread, not an optimizing thread either;)

    And yes, install.esd can't be serviced, needs conversion to install.wim first.
     
  4. canuckie

    canuckie MDL Novice

    May 17, 2019
    3
    0
    0
    Thank you for your reply.

    I realize it's not LTSC, but that's exactly why I need it.
    I'm currently running the Feb2019 LTSC, but it seems to have that 1809 bug of audio not working upon the system waking up without user interaction (i.e. schedule/LAN), which was fixed in the Consumer versions back in April but will probably never get fixed in LTSC. I really need my Foobar alarm :)
     
  5. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,005
    93,798
    450
    The fix in the consumer editions will be by CU, install/integrate the new SSU/CU in the LTSC iso you have.
     
  6. PsychedelicShaman

    PsychedelicShaman MDL Member

    Dec 4, 2017
    134
    318
    10
    -SourceImage is a wrong switch in your PowerShell window, use the -SourcePath switch instead, and yes, the .iso image has to contain install.wim file, not install.esd.

    Furthermore, the re-released .iso images are not good for optimizing, you should use the original 17763.1 image from the MVS, then use W10UI script by @abbodi1406 to integrate newest updates + .NET Framework 3.5 and perform DISM WinSxS Cleanup, and then lastly use Optimize-Offline script on the properly updated, re-created image.

    That's the recommended procedure. :)
     
  7. canuckie

    canuckie MDL Novice

    May 17, 2019
    3
    0
    0
    Thank you for your help, going to go keep trying to figure all of that out now :)

    On topic (of this thread): Has anyone else encountered the audio issue I have mentioned above while using LTSC? If you did, how did you solve it?
     
  8. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,005
    93,798
    450
  9. genuine555

    genuine555 MDL Expert

    Oct 3, 2009
    1,672
    88
    60
    Thanks for these mate !
     
  10. Simon Vaughn

    Simon Vaughn MDL Novice

    May 19, 2019
    2
    0
    0
    Alright, another dude who wants LTSC and needs help.
    I keep getting the "hash mismatch" when doing the MVS downloads with the tool.

    Latest eval from MS is .197.101029-1355
    .iso donwloaded by the tool is .1.180914-1434
    Target is LTSC 2019 v. "I don't care", preferably in german.

    Anyone able to help me with this ?
     
  11. KedarWolf

    KedarWolf MDL Addicted

    Mar 17, 2016
    977
    870
    30

    Deleted. I read it wrong.
     
  12. KedarWolf

    KedarWolf MDL Addicted

    Mar 17, 2016
    977
    870
    30
    In both the W10UI image and the Optimize Offline image you can't use DISM WinSXS cleanup as it says operations are pending.

    And in both images, there are zero reclaimable packages anyways so no need to use DISM WinSxS Cleanup.

    But I used the Cleanup System Image option in W10UI.

    Here's the output on both images in DISM.

    W10UI image.

    Code:
    C:\Windows\system32>DISM /Mount-Wim /WimFile:D:\2\sources\install.wim /Index:1 /MountDir:D:\Mount\BootWIM
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\system32>Dism /Image:D:\Mount\BootWim /Cleanup-Image /StartComponentCleanup
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Image Version: 10.0.17763.503
    
    
    
    Error: 0x800f0806
    
    The operation could not be completed due to pending operations.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\system32>DISM /Image:D:\Mount\BootWim /Cleanup-Image /AnalyzeComponentStore
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Image Version: 10.0.17763.503
    
    [===========================99.2%========================= ]
    
    Component Store (WinSxS) information:
    
    Windows Explorer Reported Size of Component Store : 6.60 GB
    
    Actual Size of Component Store : 6.56 GB
    
        Shared with Windows : 5.81 GB
        Backups and Disabled Features : 748.76 MB
        Cache and Temporary Data :  0 bytes
    
    Date of Last Cleanup : 2019-05-16 22:59:47
    
    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No
    
    The operation completed successfully.
    
    Optimize Offline Image.

    Code:
    C:\Windows\system32>DISM /Mount-Wim /WimFile:D:\4\sources\install.wim /Index:1 /MountDir:D:\Mount\BootWIM
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Mounting image
    [==========================100.0%==========================]
    The operation completed successfully.
    
    C:\Windows\system32>Dism /Image:D:\Mount\BootWim /Cleanup-Image /StartComponentCleanup
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Image Version: 10.0.17763.503
    
    
    
    Error: 0x800f0806
    
    The operation could not be completed due to pending operations.
    
    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
    
    C:\Windows\system32>DISM /Image:D:\Mount\BootWim /Cleanup-Image /AnalyzeComponentStore
    
    Deployment Image Servicing and Management tool
    Version: 10.0.17763.1
    
    Image Version: 10.0.17763.503
    
    [==========================100.0%==========================]
    
    Component Store (WinSxS) information:
    
    Windows Explorer Reported Size of Component Store : 6.61 GB
    
    Actual Size of Component Store : 6.57 GB
    
        Shared with Windows : 5.47 GB
        Backups and Disabled Features : 1.09 GB
        Cache and Temporary Data : 4.85 MB
    
    Date of Last Cleanup : 2019-05-16 22:59:47
    
    Number of Reclaimable Packages : 0
    Component Store Cleanup Recommended : No
    
    The operation completed successfully.
    
     
  13. staveley

    staveley MDL Novice

    Oct 7, 2007
    11
    4
    0
    Thinking of making LTSC 2019 the standard build for all my machines.
    Have got the full (non-eval) 17763.316 iso which installs fine on my main rig.
    However, on my Surface Pro 4 installation fails during the setup/file copy phase with error 0x80070002 (missing files).
    I have rebuilt the iso with integrated SPro4 drivers in both install.wim & boot.wim but error still occurs.

    Has anyone successfully installed LTSC 2019 on Surface Pro 4?
    Any tips, guides, how-to's?
     
  14. neofita

    neofita MDL Member

    Nov 27, 2013
    226
    205
    10

    https://forums.mydigitallife.net/posts/1508535


    regards
     
  15. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,005
    93,798
    450
    #3696 Enthousiast, May 19, 2019
    Last edited: May 19, 2019
    Can you show me a link to the .197 LTSC EVAL?

    Afaik only these 2 LTSC EVAL iso's are available:
    Code:
    b11efabfc38428b69042da841e1cb4b105be359b *17763.1.180914-1434.rs5_release_CLIENT_LTSC_EVAL_x86FRE_en-us.iso
    ba8e0184c61d88b92fb88046339f8ddc58a3b372 *17763.107.101029-1455.rs5_release_svc_refresh_CLIENT_LTSC_EVAL_x86FRE_en-us.iso
    
    And the svf2iso tool is not working anymore either. The needed svf files are gone..
     
  16. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    47,005
    93,798
    450
  17. jim_p

    jim_p MDL Senior Member

    Dec 11, 2013
    428
    165
    10
    Please excuse my offtopic spam.
    A couple of days ago, on a thread about ltsc here on mdl, I came accross a .reg file that does some more tweaks for it. I did not download it because I was not on my pc and I can't find it now. It was posted from an mdl member as an attachment and it was something like a "collection" he/she made, not something generic.
    Any info will be appreciated.
     
  18. adric

    adric MDL Expert

    Jul 30, 2009
    1,244
    1,303
    60
    #3699 adric, May 19, 2019
    Last edited: May 19, 2019