Wow, deja vu That was long ago that we had to explain the invisible ssu side install when cu's get installed by WU
Microsoft-Windows-Product-Data-EKB-Wrapper-Package*.mum Microsoft-Windows-UpdateTargeting-ClientOS-EKB-Wrapper-Package*.mum these packages are included with CU, and get staged by default if kb4517245 is already installed, or installed later, then these EKB package get installed Code: <parent integrate="delegate"> <assemblyIdentity name="Microsoft-Windows-1909Enablement-Package" version="10.0.18362.0" processorArchitecture="x86" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" /> </parent> Microsoft-Windows-Product-Data-EKB-Package changes: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion] "BuildLab"="18362.19h1_release.190318-1202" "BuildLabEx"="18362.1.amd64fre.19h1_release.190318-1202" "CurrentBuild"="18363" "CurrentBuildNumber"="18363" "ReleaseId"="1909" [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Version\Kernel] "KVB"=dword:00000001 [HKEY_LOCAL_MACHINE\SYSTEM\Software\Microsoft] "BuildLab"="18362.19h1_release.190318-1202" "BuildLabEx"="18362.1.amd64fre.19h1_release.190318-1202" Microsoft-Windows-UpdateTargeting-ClientOS-EKB-Package changes: Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Client.OS.rs2.x86] "Version"="10.0.18363.418" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Update\TargetingInfo\Installed\Windows.EmergencyUpdate.x86] "Version"="10.0.18363.418" yes, on x86, BuildLabEx is mistakenly changed to amd64fre, but it doesn't have effect anyway
Hi there I'm a little blocked. What KB do I need to upload in order to update from 1803 (18362.418) to 1809? I know that the build is still in Slow/RP but I want to give it a try. I was starting my studies so I didn't read all th new messages. My apologies for that
Offline, to iso (18362.1 + SSU + Flash (optional) + dotnetCU (optional) + 1909 EP + CU Online (18362.23x+), install the 1909 EP