Here's the issue that we had with the first Surface Pro and it now appears to be the exact same issue with the replacement device.
When the tablet is in a dock and then turned off, it will not boot into Windows(gets stuck at black Surface logo screen) on while in the dock. I have to take it out of the dock and do a hard reset(hold power for 10-15 seconds). I had thought that it was just the dock that is part of the problem, but the same thing happens when I put it in a different dock. I have tried a reset of all power settings, disabling any power saving features, checked for updated firmware and a full reinstall of Windows.
Next I started disconnecting things from the dock one by one and found that the issue only happens when the display port adapter is plugged in to the dock. I have tried different display port adapters, different monitors and different docking stations and it doesn't change the issue.
We have 2 other Surface Pro's that were purchased at the same time and have the exact same setup and they do not have this issue.
It is very strange that we have the exact same issue on a replacement that Microsoft delivered.
When the tablet is in a dock and then turned off, it will not boot into Windows(gets stuck at black Surface logo screen) on while in the dock. I have to take it out of the dock and do a hard reset(hold power for 10-15 seconds). I had thought that it was just the dock that is part of the problem, but the same thing happens when I put it in a different dock. I have tried a reset of all power settings, disabling any power saving features, checked for updated firmware and a full reinstall of Windows.
Next I started disconnecting things from the dock one by one and found that the issue only happens when the display port adapter is plugged in to the dock. I have tried different display port adapters, different monitors and different docking stations and it doesn't change the issue.
We have 2 other Surface Pro's that were purchased at the same time and have the exact same setup and they do not have this issue.
It is very strange that we have the exact same issue on a replacement that Microsoft delivered.