Developers

@xenorites please install the working branch. I was made aware of this and have since corrected it I believe.

Unsure how this is a bug.

Essentially the information is saying it cannot reach the destination. So it’s timing out. Not much I can do programmatically to fix this.

I’ve found this problem and have corrected it in the working branch. Thanks for reporting.

This would seem to indicate, to me, a potential hdd problem?

@Szeraax is correct. We do provide Snapin templates for both Powershell and Powershell 64 bit for this reason. Eventually when we allow the client to install as 64 bit on machines, then this problem won’t exist.

@irfan4701 - @sudburr is correct. Windows server 2012 is based on Windows 8 / is called Windows Server 8. Likewise, Windows server 2016 is based on Windows 10.

Is this on a host, or group? Can you give me a detailed, as much as possible, of how I can reproduce? If I can reproduce it reliably, I can usually fix it pretty quickly.

I’ve done some testing in an attempt to see if this problem is still occurring, and i’m not seeing anything wrong since my last push to the working branch.

If you’d be so kind as to repull and install, let me know if you’re seeing the same or still having an issue.

I’ve found a problem with how the storage node was being found during boot menu. I don’t know if this translates, still, to the location plugin or not, but hopefully it’s addressed. If not, please let me know and I can take a look at it more directly.

Please repull the working branch. I did a bunch of testing and found out the issue. I believe I’ve now addressed this particular issue appropriately.