Windows Trace Preprocessor (tracewpp.exe)

Windows 10 1809 Language Packs Direct Download Full

Devices running Windows 10, versions 1903 or 1909 with the October 2019 cumulative update or later installed, must download the new 'Windows 10, version 1903 Local Experience Packs (LXPs) for LIP Languages (released Oct 2019)' file for the best LIP language experience. Proposed as answer by N A Malik Monday, November 18, 2019 8:59 AM. Microsoft.NET Framework 4.8 Language Packs for Windows 10 Version 1803 for x64 (KB4087642) Windows 10.

Updates include:

  • Now supports Unicode input (.ini, .tpl, and source code) files. Input files starting with a UTF-8 or UTF-16 byte order mark (BOM) will be read as Unicode. Input files that do not start with a BOM will be read using the current code page (CP_ACP). For backwards-compatibility, if the -UnicodeIgnore command-line parameter is specified, files starting with a UTF-16 BOM will be treated as empty.
  • Now supports Unicode output (.tmh) files. By default, output files will be encoded using the current code page (CP_ACP). Use command-line parameters -cp:UTF-8 or -cp:UTF-16 to generate Unicode output files.
  • Behavior change: tracewpp now converts all input text to Unicode, performs processing in Unicode, and converts output text to the specified output encoding. Earlier versions of tracewpp avoided Unicode conversions and performed text processing assuming a single-byte character set. This may lead to behavior changes in cases where the input files do not conform to the current code page. In cases where this is a problem, consider converting the input files to UTF-8 (with BOM) and/or using the -cp:UTF-8 command-line parameter to avoid encoding ambiguity.

Bit of a pickle here.
Preface: my environment has *zero* internet connectivity
I'm building a Windows 10 v1809 image and all is going well except... one item. SNMP. We still [sigh] have legacy things that need to poll SNMP off our machines and as such, I still have to install SNMP on said machines. No problem right? MDT. Add Roles/Features. SNMP. Done? Nope. Kaboom. Role/Feature does not exist. I dig some more into it and notice it is no longer listed on the old add/remove features we've had for uh... a very long time including prior revs of Win10. NOW it is a + button in the 'manage optional features' in the new Win10 Apps widget. Did I try the easy way and push the button? Yes. Fails. Error in the history says 'Contact your administrator to add this feature' ...
Ok whatever, I can Powershell/DISM this. Get-WindowsCapability returns the SNMP item I want. I go to add it via Add-WindowsCapability and... fail.
Add-WindowsCapability -Online -Name 'SNMP.CLIENT~~~~0.0.1.0'
Error code = 0x800f0954
Fine, let's try this another way as I found an article that said you can grab the CAB files for these and just install them as a package in MDT. I grab the CAB file, setup a package and try to deploy. Failed. Let's try ANOTHER way... DISM.
DISM /Online /Add-Package /PackagePath:Mirosoft-Windows-SNMP-Client-Package-[blob of numbers]~wow64~en~US~.cab
DISM runs. Operation succesful. Woot!
Next step, let's see if this turned it on [I'm a DISM noob] so I do a Get-WindowsCapability -Online -Name 'SNMP*' and.... State: NotPresent
Ok we got this... DISM again.
DISM /Add-Capability /CapabilityName:SNMP.Client~~~~0.0.1.0
DISM runs. 100% progress. Error: 0x800f0954 [again]
*insert screaming sounds here*
Let's look at the DISM log...

2019-02-20 13:26:17, Info DISM DISM Package Manager: PID=996 TID=11004 Processing the top level command token(add-capability). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2019-02-20 13:26:17, Info DISM DISM Package Manager: PID=996 TID=11004 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2019-02-20 13:26:17, Info DISM DISM Package Manager: PID=996 TID=11004 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2019-02-20 13:26:17, Info DISM DISM Package Manager: PID=996 TID=11004 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2019-02-20 13:26:33, Info DISM DISM Package Manager: PID=996 TID=4944 Error in operation: (null) (CBS HRESULT=0x800f0954) - CCbsConUIHandler::Error
2019-02-20 13:26:33, Error DISM DISM Package Manager: PID=996 TID=11004 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0954)
2019-02-20 13:26:33, Error DISM DISM Package Manager: PID=996 TID=11004 Failed processing package changes with session options - CDISMPackageManager::ProcessChangesWithOptions(hr:0x800f0954)
2019-02-20 13:26:33, Error DISM DISM Package Manager: PID=996 TID=11004 Failed to install capability. - CPackageManagerCLIHandler::ProcessCmdLine_AddCapability(hr:0x800f0954)
2019-02-20 13:26:33, Error DISM DISM Package Manager: PID=996 TID=11004 Failed while processing command add-capability. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0954)
2019-02-20 13:26:33, Info DISM DISM Package Manager: PID=996 TID=11004 Further logs for online package and feature related operations can be found at %WINDIR%logsCBScbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2019-02-20 13:26:33, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0954

1809Also noticed it said more in the CBS.log so grabbed snippets there too..
2019-02-20 13:26:33, Info CBS DWLD:Failed to do Windows update search [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS FC: WindowsUpdateDownloadFromUUP returns. [0x800F0954]
2019-02-20 13:26:33, Error CBS FC: CFCAcquirerWUClient::Download(136): Result = 0x800F0954
2019-02-20 13:26:33, Error CBS FC: CFCAcquirerWrapper::Execute(147): Result = 0x800F0954
2019-02-20 13:26:33, Info CBS Exec: Failed to download FOD from WU, make session retry candidate
2019-02-20 13:26:33, Info CBS Failed to get uup features from WU, sessionData: {'ModuleID':'FOD','Features':[{'name':'SNMP.Client~~1.0'}]} [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS Failed to download FOD from WU [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS Exec: Failed to retrieve FOD payload [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS Failed to download and plan capabilities [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS Failed to plan execution. [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0954 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT_WSUS]
2019-02-20 13:26:33, Info CBS WER: Generating failure report for package: Microsoft-Windows-SNMP-Client-Package~31bf3856ad364e35~amd64~~10.0.17763.1, status: 0x800f0954, failure source: CBS Other, start state: Absent, target state: Absent, client id: DISM Package Manager Provider
2019-02-20 13:26:33, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

Best I can tell, it can't find the files it needs.
We have WSUS. I have Features on Demand enabled for Windows 10. When I search my catalog I see FOD for NET 3.5, DirectX, Language Packs... but not SNMP, SSH, etc. I tried one trick noted online to tell WU to not use WSUS server but that just makes it try to talk to Windows Update [internet] which fails due to ... no internet. I have a feeling the CAB files might work and I'm just not doing something right with them.

Windows 10 1809 Language Pack Direct Download


Anyone gotten this [or any offline FOD installs] to work? I'm able to add .NET 3.5 just fine via MDT roles/features but that one also still shows on the 'legacy' add/remove features vs the new 'Apps' one.

Windows 10 1809 Language Packs Direct Download Windows 7


Windows 10 1809 Language Packs Direct Download Free

Thanks