Ticket #20769 (closed defect: fixed)

Opened 15 months ago

Last modified 5 months ago

Partitioning error message at unattended Windows 10 Pro installation

Reported by: isobot Owned by: gombara
Component: virtual disk Version: VirtualBox 6.1.30
Keywords: debian bullseye unattended windows Cc:
Guest type: Windows Host type: Linux


when running an unattended Win10 installation, the installation breaks with an error message (translated from German):

Could not create a partition on storage media "0". The error occured when applying the setting <DiskConfiguration> of the answer file for the unattended installation. Error code: 0x80042565


Unattended_Partition_Error.PNG Download (13.0 KB) - added by isobot 15 months ago.
error message screenshot Download (2.7 KB) - added by isobot 15 months ago.

Change History

Changed 15 months ago by isobot

error message screenshot

Changed 15 months ago by isobot

comment:1 Changed 15 months ago by gombara

  • Owner set to gombara
  • Status changed from new to assigned

comment:2 Changed 15 months ago by gombara

I cannot reproduce this problem. I am testing the script you have provided with some minimal changes such as ISO file location etc. Is it possible to give me the URL of the ISO file that you used? The one I use has the name Win10_21H2_EnglishInternational_x64.iso.

comment:3 Changed 15 months ago by klaus

You can save yourself a lot of typing effort in the script by using

VBoxManage createvm --name $vm_name --ostype Windows10_64 --default --register

This creates VM with default config, including storage controller (for Windows 10 it'll be AHCI) but without hard disk image (since you might want a different size than the default). You can of course change VM settings afterwards to you liking, like memory size and so on.

Since VirtualBox 6.1.30 you no longer need to specify options --script-template and --post-install-template, because the long standing packaging bug in the Linux deb and rpm packages has been fixed which caused the templates to be not found without those options.

Version 0, edited 15 months ago by klaus (next)

comment:4 Changed 15 months ago by klaus

Doh. What you see is actually a regression introduced in 6.1.28, and was fixed shortly after 6.1.30 was built. Suspect that's why it wasn't reproducible for gombara.

Will be fixed in 6.1.32.

If you need a quick workaround: configure the VM to use EFI. Not that it's the default config, but it avoids the bug. The partitioning failure is caused by VirtualBox creating a GPT partitioning unconditionally, not the MBR one which should be used for legacy BIOS.

comment:5 Changed 14 months ago by isobot

thank you very much for the fast update. I'm going to test 6.1.32 and give you feedback afterwards.

comment:6 Changed 5 months ago by aeichner

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use