This can happen for several reasons, mostly related to too much bogus traffic hitting your RDP port. It is best practice to only allow RDP access to a limited set of static IP's, only access via firewall or if the other two options are not possible change the default port for RDP access to help limit default bogus traffic.
With that said, the quickest way to solve this problem without a reboot is to simple disable the network adapter and reenable it.
Step by Step:
- Login to your Hyper-V manager
- Connect to the Guest VM in question
- Open the network manager and change adapter settings or Control Panel\Network and Internet\Network Connections
- Once on this screen simply right click the adapter and disable, then reenable.
Thats it, your issue should now be solved.
Pardon the Interruption Error: D7361-1253-80070015
In most cases this is caused by an audio issue like a bluetooth headset. You can simply disconnect your audio device and reconnect it in order to solve this issue.
You can quickly bypass this error by using robocopy,
use run as administrator to open a command prompt and do the following:
robocopy /e /is /v /eta [driveletter]:\sourcefolder [driveletter]:\destinationfolder
/e Copies all subdirectories.
/is Includes the same files.
/v Produces verbose output, and shows all skipped files.
/eta Shows the ETA of the copied files.
This error is caused because 3dm2 uses a no longer supported SSL cipher. Normally in order to fix this issue you would just issue an updated SSL cert but 3DM2 does not offer this option, so you will need to open up a legacy browser.
On windows you will need to run internet explorer
then open the local server address, https://localhost:888/
It is possible you will need to go into internet explorer > internet options > advanced and enable addition SSL protocols as well.
When adding, updating or replacing an SSL certificate you encounter the error "NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED"
This is most common with LetsEncrypt SSL as they seem to be overutilizing resources.
The issue happens when the LetsEncrypt servers are behind on pushing transparency proof logs and google chrome caches the cert info before those logs are in place. In most cases this will resolve itself within 5 minutes or so but may require you to close the browser and reopen it or even clear the cache on the affected browser. In some cases it can take much longer and may even require a reissue of the cert.