UTM: Can't install Windows 11 (22000.1098) arm64. Failed to extract .cab file
Describe the issue
Hello! Thank you for supporting this great product
But I faced with issues when installing Windows 11 (I tried to install Windows 11 (22000.1098) arm64 version).
I launched
bash uup_download_macos.sh
It downloaded all needed files but then I got error with extracting:
Status Legend:
(OK):download completed.
UUP Converter v0.7.2
Note: This script does not and cannot support the integration of updates.
Use the Windows version of the converter to integrate updates.
CAB -> ESD: Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-arm64
Failed to extract Microsoft-Windows-LanguageFeatures-Speech-en-us-Package-arm64.cab
Configuration
- UTM Version: Windows 11 (22000.1098) arm64
- macOS Version: Ventura 13.2 (22D49)
- chip M1 pro
Crash log
no
Debug log
no
Upload VM
no
About this issue
- Original URL
- State: open
- Created a year ago
- Reactions: 7
- Comments: 19
If you’re using latest brew you can’t install from github direct to downgrade - have to use brew extract to local ‘tap’. I used this resource -
https://cmichel.io/how-to-install-an-old-package-version-with-brew/
My cli here worked, then I could use uup-macosinstaller for Win ISO.
brew tap-new $USER/local-cabextractbrew extract --version=1.9.1 cabextract $USER/local-cabextractbrew install cabextract@1.9.1I already had cabextract installed based on earlier steps in the instructions provided and needed to remove it:
brew remove cabextractI had already followed the steps @cawhite6 has posted but got an error that 1.9.1 was already installed but not linked. I fixed that by following the suggested command:
brew link cabextract@1.9.1Hope this helps anyone else.
I have had the same problem. Downgrading the cabextract version to 1.9 works.
It was fixed by the
convert.shhttps://github.com/uup-dump/converter/issues/39#event-8503350459Can confirm that @ammar-faifi solution works, just add -k to extractcab in convert.sh at line 426
Just came here to say that cabextract 1.11, added to macports tree 2 days ago, fixed the issue for me.