This time, both amd64 and arm64 have FusionDiff. So, for our own good, add it. Sometimes, Microsoft also makes mistakes, maybe by aprrentice. But this time, arm64 does not have Backup. By aprrentice? For our own good, add it.
No need to play hide and seek. Here is all blank folders for Next amd64 and arm64 Construction: [Windows] Temp [WinSxS] Code: Backup Catalogs FileMaps Fusion FusionDiff Manifests
[About ChromiumEdge Integration & Removal] e.g. amd64. 2-1. C:\Program Files (x86)\Microsoft 2-2. Registry keys of a. Edge b. EdgeUpdate c. EdgeWebView (optional)
Q: Is there official ChromiumEdge integration log? A: Yes, there was one, and only, for some build of Windows Server 2022.
Test manual Construction of 25387.1200 Windows 11 Enterprise amd64 en-US Code: C:\WINDOWS\system32>dism /english /logpath:z:\1.log /image:K: /apply-unattend:Z:\WinSxS\1.xml Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25387.1 Applying package servicing unattend [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /add-package:z:\2 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25387.1 Processing 1 of 6 - Adding package Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~10.0.25387.1 [==========================100.0%==========================] Processing 2 of 6 - Adding package Microsoft-Windows-LanguageFeatures-Basic-en-us-Package~31bf3856ad364e35~amd64~~10.0.25387.1 [==========================100.0%==========================] Processing 3 of 6 - Adding package Microsoft-Windows-LanguageFeatures-Handwriting-en-us-Package~31bf3856ad364e35~amd64~~10.0.25387.1 [==========================100.0%==========================] Processing 4 of 6 - Adding package Microsoft-Windows-LanguageFeatures-OCR-en-us-Package~31bf3856ad364e35~amd64~~10.0.25387.1 [==========================100.0%==========================] Processing 5 of 6 - Adding package Microsoft-Windows-LanguageFeatures-Speech-en-us-Package~31bf3856ad364e35~amd64~~10.0.25387.1 [==========================100.0%==========================] Processing 6 of 6 - Adding package Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~amd64~~10.0.25387.1 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /set-skuintldefaults:en-US Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25387.1 Set SKU default settings for: en-US The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /add-package:z:\3 Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25387.1 Processing 1 of 2 - Adding package Package_for_ServicingStack_1200~31bf3856ad364e35~amd64~~25387.1200.1.0 [==========================100.0%==========================] The changes due to package Package_for_ServicingStack_1200 requires the current servicing session to be reloaded. All the packages will be processed again. Processing 1 of 2 - Adding package Package_for_ServicingStack_1200~31bf3856ad364e35~amd64~~25387.1200.1.0 [==========================100.0%==========================] Processing 2 of 2 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~25387.1200.1.59 [==========================100.0%==========================] The operation completed successfully. C:\WINDOWS\system32>dism /English /image:K: /get-currentedition Deployment Image Servicing and Management tool Version: 10.0.19041.844 Image Version: 10.0.25387.1200 Current edition is: Current Edition : Enterprise The operation completed successfully. C:\WINDOWS\system32>
if InstallationType==Server ---> ApplicationPreLaunch: False Allow-AppLaunch-Container = 0 ? No. Q: How?
C:\Windows\Branding. Same folder, shared by both Client and Server. Q: How to eliminate or prevent sfc /scannow error which is caused by applied counterpart package? PS: The error, found and shown as unrecoverable, but coming update is still working fine because the applied files are genuine. e.g. C:\Windows\Branding. (installed, Client or Server, or mixed with Client and Server.) In C:\Windows\WinSxS and WinSxS\Manifests. There are two sets of different packages of Client and Server. Both genuine. So, one error found in C:\Windows\Branding, could not be repaired, because both packages in WinSxS are genuine. Backup & Copy. No problem. Yes, I know. But the Branding components do not have its own package. They are splitted in some other package. And you need to install this package for something to work. This situation is alike 19044 CMGE Wallpapers. Genuine CMGE Wallpapers' Hash mismatched with original manifests. Replaced with original Wallpapers, no more Hash error, but no more OEM.
[Solution] Delete Client counterpart. e.g. C:\windows\DiagTrack\Settings\telemetry.ASM-WindowsDefault.json in C:\Windows\Logs\CBS\CBS.log. Code: 2023-06-11 23:46:51, Info CSI 0000021a Hashes for file member [l:33]'telemetry.ASM-WindowsDefault.json' do not match. Expected: {l:32 ml:33 b:d70a06d54cc7b95479346b423f6ff4a26eee6ae9b29540c9dba3565acab53126}. Actual: {l:32 b:af09104e1c733613b16614c9339da9db879cbe2a56a40f545e8a8c3a91e37fe8}. 2023-06-11 23:46:51, Info CSI 0000021b [SR] Repairing file \??\C:\windows\DiagTrack\Settings\\telemetry.ASM-WindowsDefault.json from store [Client] C:\windows\DiagTrack\Settings\telemetry.ASM-WindowsDefault.json C:\Windows\WinSxS\amd64_microsoft-windows-u..tings-windowsclient_31bf3856ad364e35_10.0.20348.1_none_03ba83448cca2162 C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-u..tings-windowsclient_31bf3856ad364e35_10.0.20348.1_none_03ba83448cca2162.manifest and C:\Windows\System32\config\COMPONENTS Code: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-u..tings-windowsclient_31bf3856ad364e35_10.0.20348.1_none_03ba83448cca2162 [Server] C:\windows\DiagTrack\Settings\telemetry.ASM-WindowsDefault.json C:\Windows\WinSxS\amd64_microsoft-windows-u..tings-windowsserver_31bf3856ad364e35_10.0.20348.1_none_1fda67d18611f94c C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-u..tings-windowsserver_31bf3856ad364e35_10.0.20348.1_none_1fda67d18611f94c.manifest and C:\Windows\System32\config\COMPONENTS Code: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-u..tings-windowsserver_31bf3856ad364e35_10.0.20348.1_none_1fda67d18611f94c PS: This issue, no problem for Windows Update.