FS#61506 - [qemu] Windows 10 1809 post installation process stuck in a loop with OOBE* errors

Attached to Project: Arch Linux
Opened by Pygo (pygo) - Wednesday, 23 January 2019, 11:36 GMT
Last edited by David Runge (dvzrv) - Friday, 20 May 2022, 19:07 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Anatol Pomozov (anatolik)
David Runge (dvzrv)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Installing Windows 10 1809 (ISO from MS site) in Qemu, I'm getting the following errors at post installation process after choosing a region: OOBEKEYBOARD, OOBEZDP, OOBEREGION, OOBEEULA. Pressing "Skip" or "Retry" does not help — after waiting for some time, one of the mentioned errors occur again, neither forcefully shutting down a VM and starting it up again makes any changes (this is mentioned as a solution on MS site). Doing the last action, though, sometimes brings a different dialog, where I can choose the country, timezone, keyboard layout etc., then on the next screen Windows prompts that it may try to repair the error by downloading some update (the VM has network access), after agreeing with that and waiting for some time, I'm still getting one of those OOBE* errors.

The installation on VirtualBox had similar problems, but after several reboots and pressing few times "Skip" and "Retry" the installation proceeded (not sure why exactly, as I've changed some settings in VB during this).

Additional info:
Qemu version 3.1.0
Kernel: 4.19.16-1-lts

My configuration:
#!/bin/bash
qemu-system-x86_64 \
-machine q35 \
-enable-kvm \
-cpu host \
-m 2G \
-net nic -net bridge,br=virbr0 \
-vga std \
-soundhw hda \
-drive file=./windows10_1809,format=qcow2,media=disk,if=virtio,l2-cache-size=4M \
-usb

Steps to reproduce:
Install Windows 10 1809 in Qemu
This task depends upon

Closed by  David Runge (dvzrv)
Friday, 20 May 2022, 19:07 GMT
Reason for closing:  No response
Comment by Steve (dareme7) - Thursday, 28 March 2019, 09:41 GMT
I am also affected by this bug on the latest versions of the software and Windows.

I also feel like it is needed to mention this happens whether virtio is used for the install disk or not.

In my case, this does not occur with Virtualbox at all though. This might mean both of us might be doing something wrong with QEMU...?
Comment by David Runge (dvzrv) - Monday, 02 May 2022, 15:50 GMT
@pygo: Is this still a problem with qemu >= 7.0.0 (currently in testing)?

Loading...