[BUG] AME Beta x64 extracts TrustedUninstaller.CLI.exe as ARM64 on Windows 11 25H2 x64

### Before continuing... - [x] I agree to follow Atlas' [Code of Conduct](https://github.com/Atlas-OS/.github/blob/main/profile/CODE_OF_CONDUCT.md) - [x] I have searched our [issue tracker](https://github.com/Atlas-OS/Atlas/issues?q=is%3Aissue) to verify that the issue hasn't been reported already - [x] I have searched the [Atlas documentation](https://docs.atlasos.net) beforehand for a solution - [x] I am on the latest version of Atlas, and didn't do an unsupported upgrade ### Description AME Beta.exe is x64, but on my Windows 11 25H2 x64 system it extracts TrustedUninstaller.CLI.exe as ARM64 into %LocalAppData%\Temp\AME. Because of that, Windows reports that TrustedUninstaller.CLI.exe is valid but for a different computer type, and the Playbook to ISO process fails. I also get errors such as: System.IO.FileNotFoundException for TrustedUninstaller.Shared Node of level 'TrustedInstaller' has not been registered Fatal Playbook error: The operation has timed out This does not appear to be caused by Defender, UAC, or the Windows TrustedInstaller service itself. ### Steps to reproduce 1. Use Windows 11 25H2 x64 / AMD64 2. Launch AME Beta.exe 3. Start the Playbook to ISO flow 4. AME extracts files into %LocalAppData%\Temp\AME 5. The process fails with TrustedUninstaller related errors 6. Running %LocalAppData%\Temp\AME\TrustedUninstaller.CLI.exe manually shows that it is built for a different machine type ### Expected behavior AME Beta.exe should extract the x64 version of TrustedUninstaller.CLI.exe on AMD64 systems, not the ARM64 version. ### Actual behavior On a Windows 11 Pro 25H2 x64 system, AME Beta.exe starts, but during the Playbook to ISO process it extracts TrustedUninstaller.CLI.exe as ARM64 into %LocalAppData%\Temp\AME instead of x64. Because of that: 1. Running TrustedUninstaller.CLI.exe manually shows a Windows architecture mismatch error 2. AME fails during execution 3. The process reports errors related to TrustedUninstaller.Shared, TrustedInstaller node registration, and timeout Observed errors: System.IO.FileNotFoundException: Could not load file or assembly 'TrustedUninstaller.Shared, Version=0.8.4.0' Node of level 'TrustedInstaller' has not been registered Fatal Playbook error: The operation has timed out Important verification already done: 1. OSArchitecture = 64-bit 2. PROCESSOR_ARCHITECTURE = AMD64 3. AME Beta.exe machine type = x64 4. Extracted %LocalAppData%\Temp\AME\TrustedUninstaller.CLI.exe machine type = ARM64 This does not appear to be caused by Defender exclusions, Smart App Control, UAC, or a missing TrustedInstaller service. ### Atlas Version Atlas v0.5.0 for Windows 11 24H2 ### Desktop information - Processor: Intel Core i9-13900K - RAM: 64 GB DDR5 - Storage: 2 TB M.2 PCIe SSD - GPU: NVIDIA GeForce RTX 3090 Additional system info: - OS: Windows 11 Pro 25H2 - Build: 26200.8039 - Architecture: x64 / AMD64 - AME Beta.exe machine type: x64 - Extracted TrustedUninstaller.CLI.exe machine type: ARM64 - TrustedInstaller service: present and starts correctly ### Additional content Additional notes: - Defender exclusions were added for both C:\AME and %LocalAppData%\Temp, but the issue remained - Smart App Control is disabled - The TrustedInstaller service exists and starts correctly - The issue is reproducible consistently - Manually running %LocalAppData%\Temp\AME\TrustedUninstaller.CLI.exe shows an architecture mismatch error - This suggests AME Beta x64 is extracting the wrong internal CLI binary, ARM64 instead of x64, on this AMD64 system