We can correlate the screenshot from comment 1 with the virt-v2v source code:

convert/convert_windows.ml:

       add "Write-Host Removing any previously scheduled qemu-ga installation";
       add "schtasks.exe /Delete /TN Firstboot-qemu-ga /F";
       add "";
       add (sprintf
              "Write-Host Scheduling delayed installation of qemu-ga from %s"
              msi_path);
       add "$d = (get-date).AddSeconds(120)";
       add "$dtfinfo = [System.Globalization.DateTimeFormatInfo]::CurrentInfo";
       add "$sdp = $dtfinfo.ShortDatePattern";
       add "$sdp = $sdp -replace 'y+', 'yyyy'";
       add "$sdp = $sdp -replace 'M+', 'MM'";
       add "$sdp = $sdp -replace 'd+', 'dd'";
       add "schtasks.exe /Create /SC ONCE `";
       add "  /ST $d.ToString('HH:mm') /SD $d.ToString($sdp) `";
       add "  /RU SYSTEM /TN Firstboot-qemu-ga `";

In the screenshot, we can see

  ERROR: The network address is invalid

*between* "Removing any previously..." and "Scheduling delayed installation..."

In the script, there is only one command between those two "Write-Host" commands:

  schtasks.exe /Delete /TN Firstboot-qemu-ga /F

Therefore, we may believe that this "schtasks" command is what emits "ERROR: The network address is invalid".

... No, that makes absolutely no sense. "schtasks.exe" should not deal with the network at all.

Instead, this is effectively a duplicate of bug 2068361. I'm basing this in particular on my earlier comments <https://bugzilla.redhat.com/show_bug.cgi?id=2068361#c12> and <https://bugzilla.redhat.com/show_bug.cgi?id=2068361#c19>.

We have some general, obscure, deep breakage in the windows firstboot machinery, where not even the batch files that we queue strictly serially are executed serially. What happens here is that

  ERROR: The network address is invalid

comes from "v2vnetcf.ps1", even though it is not visible yet in the screenshot, and then issues with that break the whole thing. I can't make any progress on this until we get some deep analysis help from the Windows experts.

I do claim though that this symptom stems from the same root cause as bug 2068361, so I'm closing this one as a duplicate.

*** This bug has been marked as a duplicate of bug 2068361 ***

Wow, it could be the other way around. I've googled "ERROR: The network address is invalid", and many users do associate it with "schtasks.exe" (meaning that they also report that "schtasks.exe" emits this error message totally inexplicably). Of course, nothing on the web explains or solves the problem. So anyway, it's likely not "v2vnetcf.ps1" breaking the firstboot machinery, but "schtasks.exe" (with its unfathomable dependency on some network address?) breaking the firstboot stuff *including* "v2vnetcf.ps1".

Whichever way we spin it, we need help from the Windows guys to debug it.