Same one driver in system. And Microsoft-Windows-Common-RegulatedPackages-Package is also system package. LCU will update them automatically. They are already existent in system, so, why you have to deal with them manually?
How do you explain then my bluetooth earbuds sometimes not showing up or pairing (in LTSC) when I try to add it? Or this?
On my PC, there's also some unknown to Windows which has appropriate driver in system. Same situation. So I have to specify the driver manually. Yes, one or two, always. But you download (driver) and update (common-regualatedpackages-package) again which has already been done by system. That's why I asked why.
Now that I have the bluetooth MEDIA driver I'm hoping I won't have to re-add Common-RegulatedPackages anymore. I'm testing now
Latest Windows has not Thin PC. The most lite is Starter which is available for 15063.0 only. To make latest Windows in Starter style is OK, but this is cuscom image needing custom update - Off-Topic.
Q: 1904X.X PPIPro to 19044.X IoTEnterpriseS Conversion, work normally? A: No. Same restart loop issue (Desktop flash and restart).
Q: How to remove an updated package with Wrapper? Removing the package, the package and the Wrapper, or the Wrapper? Fact: The Wrapper is Parent of the package. LCU recognizes and handles the Parent Wrapper, not the package.
Q: How to remove an updated Edition? The Edition or its parent Wrapper or LCU? Fact: The Edition Wrapper is Parent of the Edition. And, the LCU is Parent of all Wrappers. LCU recognizes and handles the Parent Wrapper, neither the package nor the Edition.
Q: What's the difference between "sfc /scannow" and "dism /cleanup-image /scanhealth"? e.g. Windows Update works fine - sfc /scannow OK, but dism /cleanup-image /scanhealth shows "repairable" and could not restore. Only when both are OK, the System is really perfect. [sfc /scannow] Code: Windows resource protection could not find any integrity violations. [dism /cleanup-image /scanhealth] Code: No component store corruption detected. The key point is to Install\Uninstall a package completely. To install, should be of not a problem. But there is package divided into amd64 and wow64 parts. Both need to install separately to be complete.. To uninstall? Usually to uninstall the amd64 and the wow64 should be uninstalled along. This is for unupdated package. For updated package, the Wrapper, more complicated. Sometimes, the amd64 and wow64 are not updated at the same time. e.g. [unupdated] amd64-Package~19041.1.mum wow64-Package~19041.1.mum [updated] amd64-Package-Wrapper~19041.1415.mum amd64-Package~19041.1415.mum wow64-Package~19041.1.mum Usually, the error about "dism /cleanup-image /scanhealth" is caused by this incomplete uninstall. Mainly four parts: 1. File(s) in system 2. File(s) source in WinSxS 3. Package mum\cat in C:\Windows\servicing\Packages 4. Package registry (This is the common cause. When deleted, the error gone.) Q: How to correctly uninstall the updated package? PS: The LCU may not completely uninstall the package. (In such a case, we have to manually find out and delete the residual package registry. After all, this issue won't affect system functionalities once sfc /scannow is OK.) Q: How to trouble-shoot? A: dism /english /logpath:z:\ScanHealth.log /online: /cleanup-image /scanhealth. or dism /english /logpath:z:\ScanHealth.log /image:K: /cleanup-image /scanhealth. The answer will be in the ScanHealth.log. e.g. Code: ERROR_FILE_NOT_FOUND Microsoft-Windows-Printing-WFS-FoD-Package~31bf3856ad364e35~amd64~~10.0.19041.906.mum This registry residual is caused by LCU or dism /cleanup-image. And it is usually unrepairable unless the source install.wim has such update. (But why to restore the package when it is outdated and intended to be removed?)
Q: so how to make an 19041.1 LTSC sfc error free dism cleanup-image /scanhealth error free with the lastest LCU update an dism /cleanup-image resetbase A: 17763.1 LTSC do work this way is it possible ?.
Q: What is the easiest way to do Online-Switch? Manually, not very difficult. 1. Add 19041.1 Edition Specific packages and language related packages (Language pack, language fearures, and FOD language packs.) 2. Stage Old 1904X.XXXX Edition and Install New 19041.1 Edition 3. Restart (for New Edition to take effect) 4. Uninstall updates (i.e. Uninstall Old Edition) 5. Restart 6. Install updates 7. Restart Done. How about script? So many Restarts... No.