The normal progress will show exactly what's done. Extract the sources ISO to a folder (i use "17763.1_Work_x64_US") and put the updates in a folder (i use "17763.1_Updates_x64") or leave the repo settings on default, and set the cmd like this: Code: :: enable debug mode, you must also set target and repo (if updates are not beside the script) set _Debug=1 :: when changing below options, recommended to set the new values between = and " marks :: target distribution, wim file or offline image :: leave it blank to update current online os, or automatically detect wim file next to the script set "Target=%~dp017763.1_Work_x64_US" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=%~dp017763.1_Updates_x64" Now it will run in debug mode: Code: Running in Debug Mode... The window will be closed when finished
Okay, thank you for the info. I made a folder on my desktop "UPDATES" which contains all the updates I wanted to integrate and the W10UI. I usually mount the image as "E:\", but wanted to try your method, so I extracted the ISO to the Folder "NOV" on my desktop. I fired the cmd, just changing the paths in your example to mine, but it didn't work out the way it was supposed to do. Where can the mistake be located? Thank you
Dunno why it is not working for you, but here is my debug log (i accidentally ran it in debug mode on an install.wim with 4 indexes, took all night to finish with my settings) Settings: Code: :: enable debug mode, you must also set target and repo (if updates are not beside the script) set _Debug=1 :: when changing below options, recommended to set the new values between = and " marks :: target distribution, wim file or offline image :: leave it blank to update current online os, or automatically detect wim file next to the script set "Target=%~dp017763.1_Work_x64_US" :: updates location :: leave it blank to automatically detect the current script directory set "Repo=%~dp017763.1_Updates_x64" :: dism.exe tool custom path (if Host OS is not Win10 and no Win10 ADK installed) set "DismRoot=dism.exe" :: enable .NET 3.5 feature set Net35=1 :: optional, specify custom "folder" path for microsoft-windows-netfx3-ondemand-package.cab set "Net35Source=%~dp017763.1_SXS_x64" :: Cleanup OS images to "compress" superseded components (might take long time to complete) set Cleanup=1 :: Rebase OS images to "remove" superseded components (warning: break "Reset this PC" feature) :: require first to set Cleanup=1 set ResetBase=0 :: update winre.wim if detected inside install.wim set WinRE=1 :: 1 = do not install EdgeChromium with Feature Update Enablement Package set SkipEdge=0 :: optional, set directory for temporary extracted files (default is on the same drive as the script) set "_CabDir=c:\W10UItemp" :: optional, set mount directory for updating wim files (default is on the same drive as the script) set "MountDir=c:\W10UImount" set "WinreMount=c:\W10UImountre" :: start the process directly once you execute the script, as long as the other options are correctly set set AutoStart=0 :: # Options for distribution target only # :: convert install.wim to install.esd :: warning: the process will consume very high amount of CPU and RAM resources set wim2esd=0 :: create new iso file :: require Win10 ADK, or place oscdimg.exe or cdimage.exe next to the script set ISO=1 :: folder path for iso file, leave it blank to create in the script current directory set "ISODir=" :: delete DVD distribution folder after creating updated ISO set Delete_Source=0
I loved the LTSC edition 2019. Recently i built a pc with ryzen 3 3100. The problem is the older ltsc have scheduler problem which is rectified from builds 1903. I want to use ltsc but it is lagging and giving problems. Recently i came to know about the latest enterprise edition which is built on 2009. But it is eval version which cannot be activated. IS there a way to update the ltsc 2019 with latest updates of 2009 or is there a way to activate enterprise 2009 eval edition. Please help me in this regard. sorry for my bad english( i know it is not possible, but hoping to find a positive answer).
No, you can't update 2019 LTSC, which is 1809 based, with 2009/20H2 updates. And no, you can't activate any EVAL edition beyond it's EVALuation period.
@BAU When attempting to use Universal Media Creation Tool to create a w10 1909 [19H2] Enterprise (VL) -x64 the Downloading Windows 10 progress window FAILS to go beyond 10%... I've tried this 4 times using a LTSC-2019 Host PC...
Technically it does not fail. MCT will keep at it until it succeeds, even if it takes it one week to download it. It's one of it's strong points! What's happening is probably your government / isp / microsoft servers having an issue atm / temporarily banning you. It should recover later on. Try to work around US timezone and attempt it either in the late evening or early morning in the US. For example downloading from TR or IR atm is horrible. Even for me in Europe it's on the slow side. You can always try to download the esd you need from the sticky ESD Repository via browser / download manager, then use ESD2ISO script like I've already mentioned. Tough I feel you're gonna bump into the same issue downloading..
Thanks for your feedback... I will attempt this again late in the evening or very early morning... Edit: Per your suggestion, I was able to D/L the 18363.1139.201008-0514.19h2_release_svc_refresh_clientbusiness_vol_x64fre_en-us_6e83a5e8f3ca99b74467e51cc9f5cf4f8e5de476 I will test this later today...
Apart from what already has been said, the question implies that 1809 LTSC has an issue with Zen 2 based processors. This is however not the case. At most, 1809 is missing the optimizations for Zen 2. There is actually no significant difference in performance. You may still get better performance on LTSC even without the scheduler update when comparing to later builds. In my opinion, missing scheduler updates are a non-issue on LTSC. Cheers.
LTSC is a piece of crap on every CPU. 1507 and 1607 simply blows it away by most performance and usability metrics on potatoes, and 1903+ does the same for this era hardware. Using a crap Windows 10 version just because you're incapable of dealing with updates and apps (cough! Education cough!) is just silly.
Bold statement. Hope you can back this up with some real data? From what I've seen, the differences are rather small. LTSC is certainly not "crap" in the sense that it has some specific use cases. Otherwise it's just a cut-down 1809 enterprise. Fact that it's obsolete by some standards doesn't make it crap. I'd like to try your suggestion though. Silly me. Cheers.
Can you please add more to substantiate this saying please? A member like you should know more than your statement Thank you
Some MDL members have PC's that are Faaaaaaaaaaaaaaaaaster than Potatoes... Just say'n Regardless, what is your recommended Enterprise VL edition newer than 1809 with the least amount of ISSUES?
I'm an ordinary member just like you. And if this guy can get away with this unsubstantiated bulls**t because it's just his opinion: Then consider my response just my opinion as well. Even tough this should never be a matter of opinion, but hard facts backed by Microsoft and AMD, you know, the people that make Windows, and Zen 2 respectively. Zen 2 aside, my personal experience with literally hundreds of potatoes and not so potatoes have confirmed my "bias" like clockwork. I've seen plenty of devices unable to run above 1507, 1511, 1607 or 1703 (very few), but none unable to run above 1809. That's the only LTSx criteria in my book. From updating to defender scanning to indexing and searching to opening powershell or event viewer, I see 1909 / 2004 faster in daily usage than 1809. If only people would give it a bit of time to settle after install (and complete exfiltrating the data and cache all the candy crush and chredge, mind you). Happy with 1809? Get freaky with it. But if I see any of you posting in the upcoming LTS* thread, you better be sure I'm gonna call you out if I'm still around..
So is the latest version of windows enterprise 20H2 is recommended or any other preference or suggestion of windows version youre gonna give for Zen 2 cpus