Microsoft.VCLibs.140.00_14.0.30704.0_x64__8wekyb3d8bbwe.Appx A double click prompts a notice from windows that it cannot open this type of file Why ever not? cheers
APPX packages are installed using PowerShell (run as admin): Code: Add-AppxPackage -Path <path_to_the_appx_file>
It doesn't work like a MSU update. You have to add it with either DISM or powershell. The full verbose command is something like: Code: PS Add-AppxProvisionedPackage -Online -PackagePath Pathtofile\filename.appx -DependencyPackagePath Dependencyfilepath\Dependencyfilename.appx -LicensePath Pathtolicense\Microsoft.StorePurchaseApp_8wekyb3d8bbwe.xml With just the vclib, you could probably omit the dependency and license lines as vclib is a dependency itself.
And I thank you too for the extraordinarily detailed instructions. I had already gone with the not so verbose option and that has worked, cheers
One I found was USB audio devices work better for me. In LTSC 1809 usb audio had constant micro-dropouts/stutters. Major PITA for USB audio interfaces for home recording.
It is not possible to uninstall it because the image base has been resetted. i.e. updated initial packages are gone. Re-install, or install latest one, OK.
Not sure what you mean. Is KB5006670 the one that is included in the ISO normally? If so, they are impossible to remove. What are you trying to accomplish?
I can install the latest LCU(19041.1381) and remove this one. But then the latest LCU is not able to remove. Which I still can't get an 19041.1 image.
I reckoned so, then deleted it because of off-topic. Windows Editions Reconstruction Project https://forums.mydigitallife.net/threads/windows-editions-reconstruction-project.80939/ Watch the latest posts.
No such image available, MS only released the image with update already integrated. You will have to create such an image yourself from some other windows version.
It's not possible to remove MS updates from a MS compiled ISO, afaik. I'm not even sure the non-updated files are still present, and if they are, they are likely only present in a delta format for archiving. I'm not aware of any workarounds to get dism to "undo" the updates. You might try taking a 19041 image and just gutting the store out of it and seeing if you can make a few minor tweaks to make it more like ltsc if that's what you really want.
So I have solved pretty much all the issues I've had with NTSC except these few: 1. CloudStorage errors on boot: Code: Microsoft-Windows-CloudStore Error 0x80070422 occurred. See event details for more information. This appears to be an Explorer-related s**t: Code: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\CloudStore but I havent figured out what causes it. Deleting it resets your start menu customization and that's about it. 2. SettingsSync on boot Code: shell\roaming\settingsync\explorersettinghandler.cpp(<number>)\SettingSync.dll!00007FFCE1CE969A: (caller: 00007FF7D90FFA49) ReturnHr(4) tid(1058) 80070002 The system cannot find the file specified. SettingSync.dll is loaded dynamically by both User Profile Service and Explorer. I went through all possible options in Explorer and all possible policies in GPO related to sync and disabled them all yet it still happens no matter what. Dead end as well. 3. Thousands of errors per day for WMI/DAPI s**t like this: Code: Microsoft-Windows-Crypto-DPAPI "DPAPI Unprotect failed . Status: 0x8009000B ReasonForFailure: Could not get the master key" Microsoft-Windows-Crypto-DPAPI "Master key access failed. GUID: {e49edec0-f1f7-4167-84d4-4b08c6f5e071} Success: false Last error: 0x0 Master key disposition: 0x0" or this Code: Id = {4320A058-2BD9-49EF-8426-B39B9B4EC723}; ClientMachine = DESKTOP-RE487UR; User = NT AUTHORITY\SYSTEM; ClientProcessId = 2576; Component = Unknown; Operation = Start IWbemServices::DeleteInstance - Root\Rsop\Computer : RSOP_ExtensionStatus.extensionGuid="{FC491EF1-C4AA-4CE1-B329-414B101DB823}"; ResultCode = 0x80041002; PossibleCause = Unknown Piles up in hundreds and thousands per day. It is very much possible it just typical Winblows junk but it just annoying. ------- Other than that LTSC is running smoothly for me so far.