No worries - it's team effort and I hope we have managed to reach out to all that have the problem.

Moving forward, I can also confirm that if Xeams is running on WS2016 on the LTSB ring this issue does not happen.
The issue seems to only effect the Kernels related to Windows 7 / Server 2008 and Windows 8 / Server 2012.
Windows 10 and Server 2016 currently do not seem to have this issue.

With regards to uploading a VM, I would need to get permission from the client's site and that might involve Non-Disclosure Contracts and Agreements which would be a pain for all of us.

The only thing I can attempt to do is get a trial of Windows 2012R2 trial and do the full install there and then upload the VM.
In the mean time, you could potentially download a trial of Windows 2012R2 as a VM from here: https://www.microsoft.com/en-gb/evalcenter/evaluate-windows-server-2012-r2 and patch using WSUS to see how far you go and where it 'breaks' so to say.

Let me know how you get on.

Regards,
James