MonarchX seems to have missed all the new things happening And yes, 1809 recently got it's first refresh iso's of build 17763.107.
Did that include LTSC? Can you please link me to ISO (En-US) non-N? If I do get the latest/updated 17763.107 version, do I need to apply any of these: Windows10.0-KB4469041-x64 - NetFX Update Windows10.0-KB4469342-x64 - Cumulative Update Windows10.0-KB4470788-x64 - Servicing Stack Windows10.0-KB4471331-x64 - Adobe Flash
Why on earth do you need an ISO with an old superseded CU already integrated, specially when you are planning to try to integrate new updates?
... You said that 17763.107 is the latest... Can you please just explain what the latest LTSC ISO version is and which updates apply to it? I keep running around threads and getting more and more confused.... And will MSMG Toolkit 9.0 be able to add Edge and remove crap from 17763.107 ?
Get .107 iso. Add cu (kb4469342) and ss (kb4470788). LTSC installation does not include dotnet 3.5 so if you want it I would install netfx3 online then apply dotnet update (kb4469041). Not sure if it's necessary to install netfx3 before applying dotnet update, but that's what I'm doing. LTSC lacks many of the add-ons of the normal versions, no metro apps, no store, no game mode, no one-drive, etc. That's why I and others like it.
You need to learn to read, the info you ask for is at the OP in the downloadsection. The baseline 17763.1 iso is the one you need, when you are going to integrate the current updates. Don't use the 17763.107 iso, it already has an older superseded CU in.
Stop posting this misinformation, no windows 8.x or 10 install has dotnetfx3 pre-enabled. LTSC or every other windows 8.x and up ISO has the dotnetfx3 ondemand cab inside the "iso:\sources\sxs\" folder to use for enabling dotnetfx3. kb4469041 is a separate CU for updating dotnetfx.
Yeah, however, MSMG Toolkit only supports original vanilla versions, but the .1 didn't work MSMG Toollkit 8.9. It resulted in DISM Error 2. I was hoping that the .107 version and Toolkit 9.0 would work.
MSMG toolkit is known not work properly with refresh iso's, refresh iso's are the baseline iso with this CU pre-integrated by MSFT: KB4464455 (17763.107). This old CU is superseded/replaced by kb4469342 (17763.168.1.10).
So does it matter in end if you update the .107 image versus updating the baseline image? Not trying to argue, just need some education. If I should be updating the baseline I'll have to go back and do things a bit different.
For people who pre-integrate the updates themselves anyway, should start with the clean baseline 17763.1 iso.
Okay, I'll check into using the baseline iso, especially if it saves some file size, always battling with the 4G limit on fat32, I get over half a gig just in drivers, can split the image with dism, but it adds a step to the install where it has to extract and assemble the image.
Is there any way to stop Preview of Cumulative Updates ie KB4469041 from being offered/installing in windows update on LTSC apart from a singular KB exclusion? I don't mind installing CU's, but Preview seems too beta for me. I'd rather wait until they become rolled into a proper CU.
I would say it is somewhere in the middle. The preview updates are indeed production/retail grade, but if it is too inconvenient for some people and I guess this is true for most "regular" users (NOT MDL core users ) , then one monthly set of updates would do the job well enough.
Windows update is just fubar, the less one needs to deal with it, the better. I usually manually update myself, but for some clients it's easier to have it on. I never bothered with win7 Preview dotNet updates, but sometimes preview update rollups were useful.
Same problem KB4469342 Same W10_PRO_64 DISM /Mount-WIM /WimFile:"D:\WIM\install.wim" /index:5 /MountDir:"D:\WIM\IMMAGINE" DISM /Image:"D:\WIM\IMMAGINE" /Enable-Feature /FeatureName:NetFx3 /All /LimitAccess /Source:F:\sources\sxs DISM /image:"D:\WIM\IMMAGINE" /Add-Package /Packagepath:\WIM\UP\ DISM /Image:"D:\WIM\IMMAGINE" /Add-Driver /Driver:"D:\WIM\DRV_W10_Lite" /ForceUnsigned /Recurse copy d:\WIM\Installazione\LayoutModification.xml d:\WIM\IMMAGINE\Users\Default\AppData\Local\Microsoft\Windows\Shell\ DISM /Unmount-WIM /MountDir:"D:\WIM\IMMAGINE" /commit Dism /Export-Image /SourceImageFile:"D:\WIM\install.wim" /SourceIndex:5 /DestinationImageFile:"D:\WIM\install.esd" /Compress:recovery No Error!
Are you really saying it's to hard to read a post, containing all the needed url's to the updates, download them and run dism add-packages or any of the update integration scripts who do it automated, for todays MDL members? But they all seem to have the knowledge about telemetry, chopping or needing to use LTSC
how can i confirm that telemetry is off in my 17763.168 and that no key logger from microsoft is active.