WinRM timeout on Win10

[qik33]

When executing win10_64_analyst and after waiting a while, WinRM gets a timeout:

==> virtualbox-iso: Waiting 10s for boot...
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Waiting for WinRM to become available...
==> virtualbox-iso: Timeout waiting for WinRM.
==> virtualbox-iso: Unregistering and deleting virtual machine...
==> virtualbox-iso: Deleting output directory...
Build 'virtualbox-iso' errored: Timeout waiting for WinRM.

==> Some builds didn't complete successfully and had errors:
--> virtualbox-iso: Timeout waiting for WinRM.

==> Builds finished but no artifacts were created.

packer completed with return code: 1
Packer failed. Build failed. Exiting...
PS C:\WINDOWS\system32>*

Running on Win10.

[obilodeau]

Can you re-run with -d (debug) in order to get more output.

[qik33]

More output:

2017/02/25 16:38:09 ui: ==> virtualbox-iso: Waiting 10s for boot...
==> virtualbox-iso: Waiting 10s for boot...
2017/02/25 16:38:19 ui: ==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Typing the boot command...
2017/02/25 16:38:19 packer.exe: 2017/02/25 16:38:19 Waiting for WinRM, up to timeout: 30m0s
2017/02/25 16:38:19 ui: ==> virtualbox-iso: Waiting for WinRM to become available...
==> virtualbox-iso: Waiting for WinRM to become available...
2017/02/25 16:38:24 packer.exe: 2017/02/25 16:38:24 [INFO] Attempting WinRM connection...
2017/02/25 16:38:24 packer.exe: 2017/02/25 16:38:24 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:39:39 packer.exe: 2017/02/25 16:39:39 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/w
sman: read tcp 127.0.0.1:63668->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:39:39 packer.exe: 2017/02/25 16:39:39 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:27
47/wsman: read tcp 127.0.0.1:63668->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote ho
st.
2017/02/25 16:39:44 packer.exe: 2017/02/25 16:39:44 [INFO] Attempting WinRM connection...
2017/02/25 16:39:44 packer.exe: 2017/02/25 16:39:44 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:40:59 packer.exe: 2017/02/25 16:40:59 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/w
sman: read tcp 127.0.0.1:63813->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:40:59 packer.exe: 2017/02/25 16:40:59 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:27
47/wsman: read tcp 127.0.0.1:63813->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote ho
st.
2017/02/25 16:41:04 packer.exe: 2017/02/25 16:41:04 [INFO] Attempting WinRM connection...
2017/02/25 16:41:04 packer.exe: 2017/02/25 16:41:04 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:42:19 packer.exe: 2017/02/25 16:42:19 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:63942->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:42:19 packer.exe: 2017/02/25 16:42:19 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:63942->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:42:24 packer.exe: 2017/02/25 16:42:24 [INFO] Attempting WinRM connection...
2017/02/25 16:42:24 packer.exe: 2017/02/25 16:42:24 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:43:39 packer.exe: 2017/02/25 16:43:39 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64086->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:43:39 packer.exe: 2017/02/25 16:43:39 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64086->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:43:44 packer.exe: 2017/02/25 16:43:44 [INFO] Attempting WinRM connection...
2017/02/25 16:43:44 packer.exe: 2017/02/25 16:43:44 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:45:00 packer.exe: 2017/02/25 16:45:00 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64232->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:45:00 packer.exe: 2017/02/25 16:45:00 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64232->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:45:05 packer.exe: 2017/02/25 16:45:05 [INFO] Attempting WinRM connection...
2017/02/25 16:45:05 packer.exe: 2017/02/25 16:45:05 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:46:20 packer.exe: 2017/02/25 16:46:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64387->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:46:20 packer.exe: 2017/02/25 16:46:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64387->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:46:25 packer.exe: 2017/02/25 16:46:25 [INFO] Attempting WinRM connection...
2017/02/25 16:46:25 packer.exe: 2017/02/25 16:46:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:47:40 packer.exe: 2017/02/25 16:47:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64527->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:47:40 packer.exe: 2017/02/25 16:47:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64527->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:47:45 packer.exe: 2017/02/25 16:47:45 [INFO] Attempting WinRM connection...
2017/02/25 16:47:45 packer.exe: 2017/02/25 16:47:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:49:00 packer.exe: 2017/02/25 16:49:00 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64666->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:49:00 packer.exe: 2017/02/25 16:49:00 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64666->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:49:05 packer.exe: 2017/02/25 16:49:05 [INFO] Attempting WinRM connection...
2017/02/25 16:49:05 packer.exe: 2017/02/25 16:49:05 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:50:20 packer.exe: 2017/02/25 16:50:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64810->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:50:20 packer.exe: 2017/02/25 16:50:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64810->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:50:25 packer.exe: 2017/02/25 16:50:25 [INFO] Attempting WinRM connection...
2017/02/25 16:50:25 packer.exe: 2017/02/25 16:50:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:51:40 packer.exe: 2017/02/25 16:51:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:64955->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:51:40 packer.exe: 2017/02/25 16:51:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:64955->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:51:45 packer.exe: 2017/02/25 16:51:45 [INFO] Attempting WinRM connection...
2017/02/25 16:51:45 packer.exe: 2017/02/25 16:51:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:52:59 packer.exe: 2017/02/25 16:52:59 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:65093->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:52:59 packer.exe: 2017/02/25 16:52:59 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:65093->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:53:04 packer.exe: 2017/02/25 16:53:04 [INFO] Attempting WinRM connection...
2017/02/25 16:53:04 packer.exe: 2017/02/25 16:53:04 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:54:20 packer.exe: 2017/02/25 16:54:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:65232->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:54:20 packer.exe: 2017/02/25 16:54:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:65232->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:54:25 packer.exe: 2017/02/25 16:54:25 [INFO] Attempting WinRM connection...
2017/02/25 16:54:25 packer.exe: 2017/02/25 16:54:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:55:40 packer.exe: 2017/02/25 16:55:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:65371->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:55:40 packer.exe: 2017/02/25 16:55:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:65371->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:55:45 packer.exe: 2017/02/25 16:55:45 [INFO] Attempting WinRM connection...
2017/02/25 16:55:45 packer.exe: 2017/02/25 16:55:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:57:00 packer.exe: 2017/02/25 16:57:00 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:65516->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:57:00 packer.exe: 2017/02/25 16:57:00 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:65516->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:57:05 packer.exe: 2017/02/25 16:57:05 [INFO] Attempting WinRM connection...
2017/02/25 16:57:05 packer.exe: 2017/02/25 16:57:05 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:58:20 packer.exe: 2017/02/25 16:58:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:49273->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:58:20 packer.exe: 2017/02/25 16:58:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:49273->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:58:25 packer.exe: 2017/02/25 16:58:25 [INFO] Attempting WinRM connection...
2017/02/25 16:58:25 packer.exe: 2017/02/25 16:58:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 16:59:40 packer.exe: 2017/02/25 16:59:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:49430->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:59:40 packer.exe: 2017/02/25 16:59:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:49430->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 16:59:45 packer.exe: 2017/02/25 16:59:45 [INFO] Attempting WinRM connection...
2017/02/25 16:59:45 packer.exe: 2017/02/25 16:59:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:01:00 packer.exe: 2017/02/25 17:01:00 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:49571->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:01:00 packer.exe: 2017/02/25 17:01:00 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:49571->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:01:05 packer.exe: 2017/02/25 17:01:05 [INFO] Attempting WinRM connection...
2017/02/25 17:01:05 packer.exe: 2017/02/25 17:01:05 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:02:20 packer.exe: 2017/02/25 17:02:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:49720->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:02:20 packer.exe: 2017/02/25 17:02:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:49720->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:02:25 packer.exe: 2017/02/25 17:02:25 [INFO] Attempting WinRM connection...
2017/02/25 17:02:25 packer.exe: 2017/02/25 17:02:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:03:40 packer.exe: 2017/02/25 17:03:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:49861->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:03:40 packer.exe: 2017/02/25 17:03:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:49861->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:03:45 packer.exe: 2017/02/25 17:03:45 [INFO] Attempting WinRM connection...
2017/02/25 17:03:45 packer.exe: 2017/02/25 17:03:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:05:00 packer.exe: 2017/02/25 17:05:00 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:50001->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:05:00 packer.exe: 2017/02/25 17:05:00 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:50001->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:05:05 packer.exe: 2017/02/25 17:05:05 [INFO] Attempting WinRM connection...
2017/02/25 17:05:05 packer.exe: 2017/02/25 17:05:05 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:06:20 packer.exe: 2017/02/25 17:06:20 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:50145->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:06:20 packer.exe: 2017/02/25 17:06:20 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:50145->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:06:25 packer.exe: 2017/02/25 17:06:25 [INFO] Attempting WinRM connection...
2017/02/25 17:06:25 packer.exe: 2017/02/25 17:06:25 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:07:40 packer.exe: 2017/02/25 17:07:40 [ERROR] connection error: unknown error Post http://127.0.0.1:2747/wsman: read tc
p 127.0.0.1:50284->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:07:40 packer.exe: 2017/02/25 17:07:40 [ERROR] WinRM connection err: unknown error Post http://127.0.0.1:2747/wsman: rea
d tcp 127.0.0.1:50284->127.0.0.1:2747: wsarecv: An existing connection was forcibly closed by the remote host.
2017/02/25 17:07:45 packer.exe: 2017/02/25 17:07:45 [INFO] Attempting WinRM connection...
2017/02/25 17:07:45 packer.exe: 2017/02/25 17:07:45 [DEBUG] connecting to remote shell using WinRM
2017/02/25 17:08:19 ui error: ==> virtualbox-iso: Timeout waiting for WinRM.
==> virtualbox-iso: Timeout waiting for WinRM.
2017/02/25 17:08:19 ui error: ==> virtualbox-iso: Step "StepConnect" failed, aborting...
==> virtualbox-iso: Step "StepConnect" failed, aborting...
2017/02/25 17:08:19 ui error: Build 'virtualbox-iso' errored: unexpected EOF
Build 'virtualbox-iso' errored: unexpected EOF
2017/02/25 17:08:19 Builds completed. Waiting on interrupt barrier...

2017/02/25 17:08:19 machine readable: error-count []string{"1"}
2017/02/25 17:08:19 ui error:
==> Some builds didn't complete successfully and had errors:
==> Some builds didn't complete successfully and had errors:
2017/02/25 17:08:19 machine readable: virtualbox-iso,error []string{"unexpected EOF"}
2017/02/25 17:08:19 ui error: --> virtualbox-iso: unexpected EOF
2017/02/25 17:08:19 ui:
==> Builds finished but no artifacts were created.
--> virtualbox-iso: unexpected EOF

2017/02/25 17:08:19 waiting for all plugin processes to complete...
==> Builds finished but no artifacts were created.
2017/02/25 17:08:19 C:\ProgramData\chocolatey\lib\packer\tools\packer.exe: plugin process exited
2017/02/25 17:08:19 C:\ProgramData\chocolatey\lib\packer\tools\packer.exe: plugin process exited
2017/02/25 17:08:19 C:\ProgramData\chocolatey\lib\packer\tools\packer.exe: plugin process exited
2017/02/25 17:08:19 C:\ProgramData\chocolatey\lib\packer\tools\packer.exe: plugin process exited

packer completed with return code: 1
Packer failed. Build failed. Exiting...

[obilodeau]

Can you post your config? I'm mostly interested to know if you are installing the trial version or not?

Can you connect to the VM (use VirtualBox GUI to open the Window) and run a netstat /a /n to see if WimRM is running? It's port TCP 5985. We faced it with Windows 7 and it might happen to Windows 10 too (see #33 and #43). You'll have to wait after the OS is installed before you can run commands.

Also, you'll see if the installer gets stuck for whatever reason.

How much memory do you have on your system? 4Gb is required for the VM build so at least a total of 7 Gb should be necessary for your Windows 10 host.

[qik33]

Took me a while to get back to it... Looks like something went wrong with the install when starting the VM from VirtualBox. I'll try again and report back.

http://imgur.com/1f9HMFY

[obilodeau]

I just built 2 Windows 10 VMs (trials) one x86 and the other x86_64 without a problem.

Can you try again and report back?

[k0l0ss]

same here, stuck at

==> virtualbox-iso: Creating floppy disk...
virtualbox-iso: Copying files flatly from floppy_files
virtualbox-iso: Copying file: /home/k0ss/.cache/malboxes/Autounattend.xml
virtualbox-iso: Copying file: /usr/local/lib/python3.6/dist-packages/malboxes-0.3.0.dev0-py3.6.egg/malboxes/installconfig/windows10_64/enablewinrm.ps1
virtualbox-iso: Done copying files from floppy_files
virtualbox-iso: Collecting paths from floppy_dirs
virtualbox-iso: Resulting paths from floppy_dirs : []
virtualbox-iso: Done copying paths from floppy_dirs
==> virtualbox-iso: Creating virtual machine...
==> virtualbox-iso: Creating hard drive...
==> virtualbox-iso: Attaching floppy disk...
==> virtualbox-iso: Creating forwarded port mapping for communicator (SSH, WinRM, etc) (host port 3682)
==> virtualbox-iso: Executing custom VBoxManage commands...
virtualbox-iso: Executing: modifyvm packer-virtualbox-iso-1499852518 --memory 4096
virtualbox-iso: Executing: modifyvm packer-virtualbox-iso-1499852518 --cpus 1
==> virtualbox-iso: Starting the virtual machine...
virtualbox-iso: The VM will be run headless, without a GUI. If you want to
virtualbox-iso: view the screen of the VM, connect via VRDP without a password to
virtualbox-iso: rdp://127.0.0.1:5971
==> virtualbox-iso: Waiting 10s for boot...
==> virtualbox-iso: Typing the boot command...
==> virtualbox-iso: Waiting for WinRM to become available...

I cannot connect with VirtualBox GUI to the machine.
It simply does not give the option to show screen.
Suggestion?

Thanks in advance

[obilodeau]

Are you building the VM on a server but this I mean a machine without a desktop graphical interface? If so, the way to access the machine is to create an SSH tunnel to the RDP/VNC port.

ssh -L 6666:localhost:5971 user@server

Then use a VNC viewer (I use tigervnc) to connect to localhost:6666.

I made a small troubleshooting guide about WinRM connection issues: https://github.com/GoSecure/malboxes/blob/master/docs/troubleshooting.adoc. Can you try these steps and report your results?

[k0l0ss]

I'm in a debian host with GUI. When I run the VB GUI I have no option to bring the screen foreground.
However I've noticed something, in the screen preview in VB manager, when the message "Waiting for WinRM to become available...", the machine is still installing the OS. That means the service WinRM won't be running. In fact, I've seen the machine takes for about 3-4min more to start (with couple or 3 restarts). (I can see all that in the VB Manager preview.)
Then after a while:

and finally can connect.

I think the message "Waiting 10s for boot..." should be wait for a while, and instead of waiting to connect to WinRM service should ping or some other type of (tool?) until the machine is fully booted.

I don't mean to be mean, just trying to help.. :D

Still at the VB manager can't get the screen, if I right clic the vm cant click "connect" and if I clic the preview screen, won't bring the creen fg. Is it supused to be like that? In other vm's in VB I can connect with them that way.

[obilodeau]

I think the message "Waiting 10s for boot..." should be wait for a while, and instead of waiting to connect to WinRM service should ping or some other type of (tool?) until the machine is fully booted.

This is the output of packer, we have no control over it.

Still at the VB manager can't get the screen, if I right clic the vm cant click "connect" and if I clic the preview screen, won't bring the creen fg. Is it supused to be like that? In other vm's in VB I can connect with them that way.

We run VBox in a headless mode due to some bugs we had previously with some versions of virtualbox. See #10. So not being able to open the screen during install is expected.

To connect to the headless environment use an RDP or VNC client and connect to the port specified during the build:

[obilodeau]

I'm going to close this one due to inactivity. If you can reproduce the issue with the recently released 0.5 please file a new issue.