Nice to see it released and the update notes for it as well, seems it does still break on that bluetooth driver that was cleaned from .263 to .264 and later but eh there's always the next cumulative that might include the newer version again or if not that then a later build like 19H2 or the 20H1 builds when those are closer to finalization and release. Big update too from the update notes and not just security fixes and some smaller bug fixes before the next build of Windows 10 comes out. EDIT: Hmm wonder if this is identical to the insider (Release preview channel from a few days ago.) .267 update which if so would also break for the earlier two components listed "swenum" and that other one but perhaps .263 wasn't intended for distribution if that info for the 20H1 build was correct and they had some problems with the channels and how things ended up released that shouldn't have been, well I wouldn't know but it's not that big of a issue skipping one or two cumulative updates for a build especially when there's alternatives and newer ones will also be available sooner or later.
https://forums.mydigitallife.net/th...x-pc-19h1_release.79259/page-212#post-1538764 https://forums.mydigitallife.net/th...x-pc-19h1_release.79259/page-212#post-1538766
Weird, today I updated from 7763.615 to 7763.652 I fixed sfc and scanhealth problem happened in 615 when I installed that, but today again same thing happened(despite your test) Code: C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth Deployment Image Servicing and Management tool Version: 10.0.17763.1 Image Version: 10.0.17763.652 [==========================100.0%==========================] The component store is repairable. The operation completed successfully. C:\WINDOWS\system32>sfc/scannow Beginning system scan. This process will take some time. Beginning verification phase of system scan. Verification 100% complete. Windows Resource Protection found corrupt files but was unable to fix some of them. For online repairs, details are included in the CBS log file located at windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.
I was having error the the bt driver inf file too. But that was due to having unpacked the CU CAB with 7-zip. Try unpacking the .267 CU CAB with the standard expand.exe that's included with Windows: Code: EXPAND Windows10.0-KB4505903-x64_PSFX.cab -F * <destination_directory> "Unzip" windows10.0-kb4505903-x64.7z <destination_directory> # file in link below dism /online /Add-Package /PackagePath:<destination_directory>\update.mum That solved me the issue AFTER restoring those 2 initial missing 18362.1 WinSxS assemblies (swenum.inf and ufxchipidea.inf): Windows 10 Hotfix Repository Took me a VERY LONG day to figure out what I was doing wrong! At least I learned a lot of PowerShell XML handling and CAB IPD / PA30 file structure trying to manually fix those damn missing files!!!
Tested for short time but so far so good. As appointed in previous message, .267 now released to public.
Of course i know there were several iterations of this KB, I was discussing it with @Enthousiast , and the issues they presented, I meant if the official update has been re-released in the last hours or so, as implicated in several places on the web, which usually refer to the official KB, not the RP rings. As i saw no evidence of any issues with the "real" official update, or a re-issue of it, I assume they meant to the several RP iterations it had.
No just one, it got retracted and since they pushed it to WU, they republished it on catalog, now with working info links. They have the same content as the previously released 18362.267 cab's.