there is a bug of sorts when updating to a new CU. If you installed a previous CU and then ran a component cleanup using DISM, or a disk cleanup, or if the auto cleanup task has run. The next time you try to update to the latest CU you would get an error and be unable to install the CU/SS updates. It seems that Windows removes some files during its cleanup process that Windows updates need to install the new CU and thus breaks. This is the Fix if you are suffering this error: Code: https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-448#post-1544947
Strange ??? 18363.327 compiled on 8/21/2019 18363.329 compiled on 8/28/2019 Todays ISO 18363.327 compiled on 8/26/2019
Media Content: Code: Name: Windows10_InsiderPreview_EnterpriseVL_x64_en-us_18363.iso Size: 5250330624 bytes (5007 MiB) CRC32: 6AA99444 CRC64: D8CE6C8858D14E7E SHA256: 51E5FD9F6B585D14933A81BDC56821F3B10883F7B7390D371EF774E50A779CC5 SHA1: C5B0225D89B5532421F2EC21527C14593AC47C65 BLAKE2sp: F45AB7BC1BD9F8DA2A3C76B20276FAC67DA1C93E1892AE11DAE7B3ACBAC715A6 SKUs: Code: [01] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Education | Education [02] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Education N | EducationN [03] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Enterprise | Enterprise [04] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Enterprise N | EnterpriseN [05] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro | Professional [06] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro N | ProfessionalN [07] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro Education | ProfessionalEducation [08] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro Education N | ProfessionalEducationN [09] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro for Workstations | ProfessionalWorkstation [10] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro N for Workstations | ProfessionalWorkstationN Code: Name: Windows10_InsiderPreview_Client_x64_en-us_18363.iso Size: 5382371328 bytes (5133 MiB) CRC32: 1243D012 CRC64: C036014081179431 SHA256: C45A869339FD06CC857E951E192E1A91DDD04068A163B4CE76F6C975A7AC1C52 SHA1: B9E8BB7DB0265F70954955C7ED019FCF3F16C71B BLAKE2sp: DFBD1B7EF54119CC542FFED2AFB42318EC6AB292D32E640B118D44EECF65A427 SKUs: Code: [01] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Home | Core [02] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Home N | CoreN [03] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Home Single Language | CoreSingleLanguage [04] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Education | Education [05] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Education N | EducationN [06] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro | Professional [07] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro N | ProfessionalN [08] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro Education | ProfessionalEducation [09] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro Education N | ProfessionalEducationN [10] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro for Workstations | ProfessionalWorkstation [11] 8/27/2019 en-US x64 10.0.18362.327 Windows 10 Pro N for Workstations | ProfessionalWorkstationN Get-Packages: Code: Package Identity : Package_for_DotNetRollup~31bf3856ad364e35~amd64~~10.0.1.2994 State : Installed Release Type : Update Install Time : 8/26/2019 10:19 PM Package Identity : Package_for_KB4503308~31bf3856ad364e35~amd64~~10.0.1.1 State : Installed Release Type : Security Update Install Time : 8/26/2019 10:27 PM Package Identity : Package_for_KB4513661~31bf3856ad364e35~amd64~~10.0.1.14 State : Installed Release Type : Update Install Time : 8/26/2019 10:19 PM Package Identity : Package_for_KB4515530~31bf3856ad364e35~amd64~~18362.323.1.0 State : Installed Release Type : Security Update Install Time : 8/26/2019 10:19 PM Package Identity : Package_for_KB4517245~31bf3856ad364e35~amd64~~10.0.1.1 State : Installed Release Type : Update Install Time : 8/26/2019 10:26 PM Package Identity : Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.327.1.8 State : Installed Release Type : Update Install Time : 8/26/2019 10:26 PM
Sometimes after typing an user's password (it is the right one) on a VM (created by Hyper-V) it doesn't work and only after typing it for the 4th, 5th or 6th time (I don't know which one, exactly) the VM resets (or does something like that) and after typing the password I finally can enter my user. Will Microsoft fix that problem?