Edited. What I posted was build 18363.329 that was posted on the uup-dump site that is/was dated as added on 09/05/19 as depicted in the img. Was no offered via WU I simply checked the uup-dump and saw this build with the date of 9/5. On a test system I tried to install the CU but failed with an error code but forgot to write it down. It was not the same error code as when you do a reset-base/component cleanup. I might rerun the test and screenshot it once I get home tonight. 1st test on a system with bare 18363.329 installed: Spoiler: Test on 18363.329 ============================================================ Running W10UI v7.1 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/3: windows10.0-kb4501374-x64.cab 2/3: windows10.0-kb4512940-x64.cab 3/3: windows10.0-kb4512941-x64.cab 4/3: windows10.0-kb4513661-x64.cab 5/3: windows10.0-kb4515530-x64.cab 6/3: windows10.0-kb4517245-x64.cab ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.18362.1 Image Version: 10.0.18363.329 Processing 1 of 1 - Adding package Package_for_KB4513661~31bf3856ad364e35~amd64~~10.0.1.16 [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ ============================================================ System restart is required to complete installation ============================================================ Press 9 to exit. Now running a test on a fresh install of 18363.295 with latest CU ( dated 9/5 from UUP-Dump) RP installed with W10UI 7.1 bringing the build number to 18363.329 stay tuned.
KB4513661 is a DU CBS update, but most likely not needed when the CU is integrated. I don't know what the test is?
difference is latest 19h2 is the 10019 and the 18363.xxx is still 1903 but the flipside of 19h2 testing for future upgrade to 1909 but i probably consider them both the same as i am not using any new features or have much hope for 1909 until 20h1 anyways stability and speed with optimization for hardware with OS is what i look for on any fairly new machine
i'm real liking 18362.10019 reason they handle CPU cores a lot better especially with my 12 core CPU which i don't see it in 18363.329 so what will it be MS September /October update RTM 18362.xxxx or 18363.xxx ?
It'll be a 18363 build with whatever features and fixes from the 18362.100xx builds they decide to include.
it will be 1909 but yes 18363.xxx; yes i agree when OS optimizes cpu/gpu cores, memory, i/o pipes and different types of storage mainly ssd and allows us control over utilizing those whether in upcoming powertoys, ms utilities, third party utilities or intel/hardware maker utilities will be another option going forward similar to how servers and enterprise software and workloads can be controlled
I was referring to the cleanup done with dism /online /cleanup-image /startcomponentcleanup and I also mentioned the servicing scheduled task which runs a variation of the same with some limitations.
May you elaborate on the improvements? What kinds of applications or tasks seem to have benefited the most? Any numbers? Benchmarks? What's your CPU Model? _ I haven't noticed anything major myself. But I have a 4 Core / 4 Thread CPU, so I guess that's why.
All leads to same result dism cleanup the components immediately the task wait 10 days (or maybe 30) before running the cleanup disk cleanup runs component cleanup only if it detected superseded updates (in 18362 case, RTM packages are always superseded)
Is it ok to delete these folders in "C:/Windows/Servicing/LCU" ? These seem to be some old CUs (apart from the latest one of course), taking about 2.2Gb of space (127.000 files) These are not cleaned when using system files cleanup. I tried on a VM and it seemed ok (and doing an in-place upgrade worked fine after cleaning these folders), but I prefer asking here just in case
Afaik, should be safe to delete but that's the pool where windows looks for when a reinstall of the cu is needed, when deleted, it will get redownloaded when needed.
My guess is that the updated CPU scheduler is for Ryzen 3000 CPU. I Also noticed some improvements with 19h2 (since 10013) on my r5 3600 compared to 1903.