Windows 10 Instalation in Hyper-V VM fails

Michal Žůrek 136 Reputation points
2020-05-20T17:34:12.91+00:00

I try to install Window 10 (Education, but I have tried other editions and nothing changes) in Hyper-V Gen2 based VM but instalation after reboot fails with following error (it is in Czech, in English it is: Windows could not complete the installation. To install windows on this computer, restart the installation.). But as you can expect, restarting instalation does not solve anything. Installer ISO is created using MediaCreationTool1909.exe and DISM says that presented version of Windows in that ISO is 10.0.18362, ServicePack build 592 and ServicePack level 0.

8450-win10inst.png

I found that installer stored a log in virtual disk at C:\Windows\Panther\UnattendGC\setuperr.log with the following content 

2020-05-20 19:08:07, Error                        [msoobe.exe] Failed to create the default account with hr=0x8007054B  
2020-05-20 19:08:07, Error                        [msoobe.exe] TASK: End failed running task PrepareUserOOBE with hr=0x8007054B.  
2020-05-20 19:08:09, Error                        [msoobe.exe] COMMIT: failed for plugin LocalUser Plugin with hr=0x80070490  
2020-05-20 19:08:11, Error                        [msoobe.exe] Failed user OOBE prep task with hr=0x8007054B  
2020-05-20 19:08:11, Error                        [msoobe.exe] Failed to run OOBE Host with hr=0x80004005  
2020-05-20 19:08:11, Error                        [msoobe.exe] OOBE failed with hr=0x80004005  
2020-05-20 19:08:11, Error                        [oobeldr.exe] OOBE UI failed with exit code [0x80004005]  
2020-05-20 19:08:11, Error                        [windeploy.exe] Command [%windir%\system32\oobe\oobeldr.exe /system] failed with exit code [0x80004005]  
2020-05-20 19:08:11, Error                        [windeploy.exe] Failure occured during online installation; cannot complete at this time [0x80004005]

I found that error 0x80004005 code means attemp to create user with invalid domain specified but have no idea whats wrong and how does msoobe creates users. Do you know any workaround how to install Windows 10?

Windows 10 Setup
Windows 10 Setup
Windows 10: A Microsoft operating system that runs on personal computers and tablets.Setup: The procedures involved in preparing a software program or application to operate within a computer or mobile device.
1,899 questions
Accepted answer
  1. Michal Žůrek 136 Reputation points
    2020-06-02T09:13:24.023+00:00

    I found an cause of issue. It was that I have set too restrictive firewall on network interface. Probably Windows API called using msoobe search for domain controller or something else over network and I have filtered it. I tested that in minimal configuration at leaset DHCP (UDP 67 out, UDP 67 in), DNS (UDP 53 out) and NetBios (TCP 137 and 138 in and out) must be allowed in these phase. 

    $vmn = "giraffe"
Add-VMNetworkAdapterExtendedAcl -Direction in -Action deny -VMName $vmn -Weight 100
Add-VMNetworkAdapterExtendedAcl -Direction out -Action deny -VMName $vmn -Weight 100

Add-VMNetworkAdapterExtendedAcl -Direction out -Protocol udp -RemotePort 67 -Action allow -VMName $vmn -Weight 101
Add-VMNetworkAdapterExtendedAcl -Direction in -Protocol udp -LocalPort 68 -Action allow -VMName $vmn -Weight 101

Add-VMNetworkAdapterExtendedAcl -Direction out -Protocol udp -RemotePort 53 -Action allow -VMName $vmn -Weight 102

Add-VMNetworkAdapterExtendedAcl -Direction in -Protocol tcp -RemotePort 137 -LocalPort 137 -Action allow -VMName $vmn -Weight 103
Add-VMNetworkAdapterExtendedAcl -Direction in -Protocol tcp -RemotePort 138 -LocalPort 138 -Action allow -VMName $vmn -Weight 104
Add-VMNetworkAdapterExtendedAcl -Direction out -Protocol tcp -RemotePort 137 -LocalPort 137 -Action allow -VMName $vmn -Weight 103
Add-VMNetworkAdapterExtendedAcl -Direction out -Protocol tcp -RemotePort 138 -LocalPort 138 -Action allow -VMName $vmn -Weight 104
    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Teemo Tang 821 Reputation points
    2020-05-22T02:10:43.067+00:00

    I notice that Failed to create the default account with hr=0x8007054B error appeared in setuperr.log, try the following in Hyper-V VM.

    Step 1. On the error screen, press Shift + F10 to display the command prompt.

    Step 2. Type the command "cd %windir%/system32/oobe/" (without quotes) and press Enter.

    Step 3. Type "msoobe" next and press Enter.

    Step 4. Set up an account and decent password there on the user account creation wizard that appears.

    Step 5. Restart VM.

    One more thing, if we want to use Education edition, the common procedure is:

    Just download and install windows 10 Pro iso without any product key and activate windows after installation by going to settings. Your Windows edition will automatically change to Education.