When copying text from a remote machine to the local machine the CRLF endings are translated to just LF. This makes pasting fail completely when going to notepad or any other application that requires standard Windows line endings. To test this I created a text file with a blank first line and then "Line two" and "Line three":

C:\>type c:\src\temp\testfile.txt

Line two
Line three

C:\>python c:\bin\hexdump.py c:\src\temp\testfile.txt
     0: 0d 0a 4c 69 6e 65 20 74 77 6f 0d 0a 4c 69 6e 65 ..Line two..Line
    10: 20 74 68 72 65 65 0d 0a

The next dump makes it particularly clear that there are CRLF line endings. I then copied/pasted from notepad on the remote machine to notepad on the client machine (both running Windows 10 16299). The text showed up on one line in notepad. When typed the text shows up fine (the type command can handle missing CR characters) but notepad cannot and the hex dump makes the missing CR characters obvious:

c:\>type c:\src\temp\testfile.txt

Line two
Line three

c:\>python c:\bin\hexdump.py c:\src\temp\testfile.txt
     0: 0a 4c 69 6e 65 20 74 77 6f 0a 4c 69 6e 65 20 74 .Line two.Line t
    10: 68 72 65 65 0a