That don't work.. gives error when trying to install apps even on official Windows Server Datacenter (Core) from uup dump. Code: 612ad442b8740f4c57b8c84e6bf465ba4699118c *Microsoft.NET.Native.Framework.x64.2.2.appx e1a85885fd4453165061351651289cce8f8590c4 *Microsoft.NET.Native.Runtime.x64.2.2.appx ff12cb1e307e94bbc3482efe7641d46c0848327b *Microsoft.SecHealthUI_8wekyb3d8bbwe.appx 90625ac619a06189ff9a36b0423203b53911f28e *Microsoft.UI.Xaml.appx 91d4534ed68121c4e212bfb4d22dcca863df420b *Microsoft.UI.Xaml.x64.2.4.appx 89251f149ebc266690e4cd3ff223856296eb8829 *Microsoft.UI.Xaml.x64.2.8.appx 9c0f20cda41eceea9989f9a0c0999d82b7c05f19 *Microsoft.VCLibs.x64.14.00.UWPDesktop.appx 6e15245aed25ee83b027521f9cf9ea812c9d016d *Microsoft.VCLibs.x64.14.00.appx
What error? + the script depend on AggregatedMetadata to determine referenced Apps build 25398 doesn't specify any app, therefore, Framework apps will be skipped
I will fix it myself, uup-converter-wimlib-104 was fine until these changes were made on spiteful monkey say so... thanks for nothing.
uup-converter v105u small revision - AddDrivers & UpdtBootFiles added to Configuration Options menu - Fix: apps CustomList option has no effect if enabled via the menu (thanks to @Clusterhead for reporting)
uup-converter v105z W10UI v10.42z Another minor update - Extracted SSU cab from LCU msu wim for Windows 11 26052+ may not named correctly (thanks to @Enthousiast)
Small general question to the scripts. On my laptop (Windows 10 19045), the scripts work great except the colors. Instead of colored lines, I just get the literal ANSI escape sequences printed out. Is this a general problem of the legacy console (I don't think so, worked earlier)? Or is there a toggle I accidentally disabled? Example lines: Code: ←[100;97m=== Running UUP Converter v105z ===←[0m ←[44;97m=== Checking UUP Info . . .←[0m ←[44;97m=== Configured Options . . .←[0m
Does it run in command prompt or Windows Terminal? the script check for ForceV2 registry if disabled and fallback to Powershell for coloring do you have "HKEY_CURRENT_USER\Console\Command Prompt" key? or similar key for hardcoded cmd.exe path?
That would be the reason but i just found out that the check code has a bug (that's why it didn't fallback to powershell) search for ForceV2 in convert-UUP.cmd and change first %_Null% to %_Nul2%