I'm not sure why so many people seem to be having trouble installing 18362.10015. I've had no issues whatsoever installing any of the released CU's. My installation and upgrade path follows... Clean installed 18362.10000 via USB installation media Updated to 18362.10005 via Windows Update Installed 18362.10006 SSU and CU cab files via DISM Updated to 18362.10012 via Windows Update Installed 18362.10013 SSU and CU cab files via DISM Updated to 18362.10014 via Windows Update Installed 18362.10015 SSU and CU cab files via DISM All of that with no issues. I'd really like it if all of these people having trouble installing cab files would post their dism.log and cbs.log files which are located in sub-directories in "C:\Windows\Logs" so maybe we can suss out some common denominators here.
After parsing your cbs.log file I can only concur with your conclusion that the failure in your case was do to disabling Cortana. Now if only others would post their logs.
Huh, I could've sworn you said that you used MRP to disable Cortana. Maybe that was in the other 18362 thread. Man keeping track of two 18362 branches is getting a bit dicey.
I used a reg file to disable Cortana as well as enable Cortana and ran 10015 cab with no luck... still getting error both ways. Someone posted converstation to hotfix here, so i look through and a couple users mentioned a bunch of KB files for non-security enabled and disabled because MS turned things off between CU updates... and even those came back as already installed or not needed for 10013 users. I would love to be able to get 10015 installed on my system... at this point I'm hoping MS pushes another CU for 19H2 (maybe 10016 or 10017) which will fix the issue. I noticed little wonky things between 10006-10013 but feel like things are getting better with each CU pushed out. Just don't want to be stuck on 10013 with no upgrade path to final 19H2 because of this issue (forcing me to clean install my system)!!!
@Enthousiast: According to the file name it is a v1803 and not a v1903 refresh. EDIT: The related post obviously has been deleted.
Probably the same error with the Cortana component listed before and on some systems apparently a issue with the .13 update though I'm sure a future update can fix it once Microsoft is aware of the problem and can roll it into a later cumulative for 19H2 which if it's widespread plus the other logging and telemetry it's probably been reported.
This is WEIRD!!! Since a couple of you guys said you went the 10014 route first and received errors only to be given 10015 afterwards... Both 10014 & 10015 are both the same KB names but with different SHA-1's: 10014: windows10.0-kb4508451-x64 [265 MiB] = daa64961299b0e8c7c81b7f872624eca12fe8048 windows10.0-kb4509452-x64 [14 MiB] = 176793e8f0a9cad9bb07b2266c3e5e8ab63e84f2 10015: windows10.0-kb4508451-x64 [277 MiB] = 28de485369391bd8c838d2ebad282f56fcab580a windows10.0-kb4509452-x64 [14 MiB] = 176793e8f0a9cad9bb07b2266c3e5e8ab63e84f2 Wouldn't MS name 10014 different from 10015 when it comes to KB naming??? Currently on 10013 and going to try upgrading to 10014 and see if it takes, and if it does try to jump to 10015 afterwards... will let you guys know if I have an luck.
kb4509452 + kb4508451 names are the same since 18362.10000 think of it as KB2919355 for Windows 8.1, it has many "internal" versions before it hit public
there have been a lot of reports in the feedback hub regarding this and MS is now looking into this issue. -andy-
finally the sandbox has been fixed! I installed the updates here and everything went well. !! pt-br version