Microsoft appear to be migrating .appxbundle files to .msixbundles. I've been installing updates for codecs and the Realtek Audio control with DISM. For example; Code: DISM.exe /Online /Add-ProvisionedAppxPackage /PackagePath:RealtekSemiconductorCorp.RealtekAudioControl_1.51.331.0_neutral_~_dt26b99r8h8gj.AppxBundle /DependencyPackagePath:Microsoft.VCLibs.140.00_14.0.33519.0_x64__8wekyb3d8bbwe.Appx /skiplicense How do I install an .msixbundle? Unless I missed something, toolkit doesn't seem to make any distinction?
The changelog says Win11 23H2 is supported, I thought that was build 22631.3235. What is the final 23H2 build number?
i don't such thing will be needed it will not auto start, until you enable it and with bio lock like finger ... so .. and also once you disable AI feature it also disable.
I believe it will, also haven't looked into latest 11 release but it maybe as simple as removing few packages using for example cbsenum to make recall dissappear. also im on win11 22h2 which works great from it will be moving to win 11 iot ltsc no ai and bloat likely recall aint included either
Use dism++ to do sxs etc cleaning. That's what I been using for ages, Also before cleaning run dism scanhealth and sfc scannow so you know if there aren't any errors already.
MS reversed the decision, that this feature should be enabled by default. With the controversy generated, I believe that this feature will become available, but disabled by default. The same should happen with Copilot. Supposedly, I think this is why 26100.712 update isn't available anymore.
Yesterday tested toolkit against 11 26100.1 iot ltsc and managed to remove defender and other apps no problem and no dism scanhealth errors no resetbase errors. going to be my next OS
I don't trust Microsoft enough not to discretely enable Recall later on. I would prefer to completely remove Recall, disable it and also some mechanisms to prevent it from being installed and/or enabled in the future.
Yes, build 26100 can be rebased without any component store or file integrity violations even after removal of many components with DISM most of the time. Sometimes store and file integrity are damanaged after rebasing, but "DISM Restorehealth" and "SFC Scan" commands fully resolve corruption. The core of 26100 builds is the best out of all Win10 and Win11 builds out there. Its the optional Copilot and AI Recall components + minor bugs give build 26100 a bad reputation.
Yes, I agree with you. But now is exactly the time to experiment with it, including with my custom DISM list for removing components, and further testing the final result, which is what I'm doing. And by the way, I would like to take this opportunity to try the CBSEnum utility you suggested to remove packages from the online system.