Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When install windows 10 can't uncheck “Import VHDX Image” #3760

Closed
zhaozhiming opened this issue Mar 13, 2022 · 13 comments
Closed

When install windows 10 can't uncheck “Import VHDX Image” #3760

zhaozhiming opened this issue Mar 13, 2022 · 13 comments
Milestone

Comments

@zhaozhiming
Copy link

zhaozhiming commented Mar 13, 2022

Describe the issue

I follow the Windows 10/11 install instructions to install windows 10. When I follow the step 5: Uncheck “Import VHDX Image” and you should see the text above change to “Boot ISO Image”. Press “Browse” and select the ISO you built in step 1., I found I can't uncheck the Import VHDX Image checkbox. So the installation process cannot continue. Please help. Thanks.

image

Configuration
UTM Version: 3.1.5(53)
OS Version: mac bigSur 11.4
Intel or Apple Silicon? Apple Silicon

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here.

Debug log
For all issues, including crashes, you should attach a debug log. Open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.

Upload VM
(Optional) If possible, upload the config.plist inside the .utm. If you do not have this, you can upload the entire .utm but note this contains your personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.

@osy osy added this to the v3.2 milestone Mar 13, 2022
@osy
Copy link
Contributor

osy commented Mar 13, 2022

This will be fixed in v3.2.x but as a workaround you can select an empty file for the VHDX then open up the VM settings and delete the drive created from your empty file and create a new drive with 64GB and set it to "NVMe" as interface. Then you can save the VM, choose your ISO from the home screen, and boot the VM.

@osy osy closed this as completed in de78459 Mar 14, 2022
@zhaozhiming
Copy link
Author

This will be fixed in v3.2.x but as a workaround you can select an empty file for the VHDX then open up the VM settings and delete the drive created from your empty file and create a new drive with 64GB and set it to "NVMe" as interface. Then you can save the VM, choose your ISO from the home screen, and boot the VM.

When I boot the VM, it stop in the boot interface. How do I continue?

image

@osy
Copy link
Contributor

osy commented Mar 14, 2022

You may need to reorder your drives so the removable CD drive is first (before your created NVMe)

@zhaozhiming
Copy link
Author

I change the drives order and make the cd drive at the first, but when I start the VM, it still stop in the boot interface.
The ISO file is generated at the step1.

image

iso file:
image

when I go into the boot config system, I found the boot order is correct.

image

@osy
Copy link
Contributor

osy commented Mar 14, 2022

Can you post the name of your generated iso file?

@zhaozhiming
Copy link
Author

Can you post the name of your generated iso file?

The file name is 21390.1_MULTI_X64_EN-US.ISO. The file size is 3.8G.

@osy
Copy link
Contributor

osy commented Mar 14, 2022

So you specified that you are on a Apple Silicon computer but you downloaded the x86_64 ISO. Please make sure you are downloading ARM64.

(For future reference, please refer to troubleshooting in https://mac.getutm.app/gallery/windows-10)

@zhaozhiming
Copy link
Author

OK. Thanks. I will try the ARM64 ISO later

@zhaozhiming
Copy link
Author

@osy It works! Thanks.

@lemessdavi
Copy link

I hava the same problem, but using the ARM64...
Screen Shot 2022-03-18 at 21 01 04

@osy
Copy link
Contributor

osy commented Mar 19, 2022

Please use the workaround above #3760 (comment)

@lemessdavi
Copy link

Actually that's what I did, i also tried created directly by the "custom VM", both ended up at this boot interface.

@skol101

This comment was marked as off-topic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants