Windows 10: Bizarre Windows File Sharing & Remote Desktop Connection Corrupt Data - Windows 10

I have a couple Windows 10 pro PCs, a Windows 7 pro PC, and a Windows 10 home laptop networked on my LAN, all via Ethernet instead of WIFI. The issue here is with the Windows 10 home laptop. I've had this configuration for a couple years, and the problem started a couple days ago with no notable configuration changes.


The problem is that when using Windows File Sharing, I can explore the other computers from my laptop with no issue, as well as open or copy files that are only a few KB in size. However, when I open larger files, it seems that the file header comes through but the rest of the data is corrupt. Same thing if I copy a file; it copies successfully, but is corrupted once opened. Pictures open as the correct resolution and without error, but the picture is just a bunch of colors marred together. Videos are the same story. Office files generally won't open due to an error about corruption. PDFs may open, but anything after the first page is missing or is garbage.


Furthermore, when I try to connect to any of the above PCs from this laptop via Remote Desktop Connection, I get the error: "Because of an error in data encryption, this session will end. Please try connecting to the remote computer again.”


A reboot or two of the laptop usually clears up the issue, but after a sleep / resume cycle it comes back. What’s really strange IMO is that I’d expect Windows File Sharing to use some sort of checksum to notice that the file is corrupt and abort opening / copying, but it seems to not notice.


I can connect between any of the other compturs via remote desktop connection or copy files with Windows File Sharing with no issues.


Anybody seen an issue like this? I really don’t to spend an entire day re-installing Windows and all my software, so hoping somebody has an idea of what might be causing this issue.


<UPDATE> I just unplugged my laptop from Ethernet so it fell back to Wifi - and the issue went away! Will see if it continues to work through a suspend / resume, but it looks like the issue may be related to the Ethernet connection of this laptop. Still, Windows should notice if data is corrupt... But maybe this sheds some light on where to hunt?

:)

 

Remote Desktop, Windows 10, Need help with how to set up sharing

You have to set remote desktop to allow remote connections. This is completely different from sharing settings and sharing files in Windows. You also need Windows 10 Professional on the computer you want to remote control. These settings are not in Windows 10 Home edition.

Also, do not share your primary drive! This is a very bad idea.

 

Remote Desktop, Windows 10, Need help with how to set up sharing

Yeah, I know it's a bad idea, but I was trying to get as open as I could to see if it was possible at all. It's back to only shared for my user now. Yeah, so that's it, this isn't a pro version of windows. Guess I'm back to the $350 KVM switch idea. My desk has no room for any more monitors.

 

Remote Desktop, Windows 10, Need help with how to set up sharing

I have 2 windows 10 home machines. I'd like to be able to remote into one from the other. I am using Remote Desktop Connection, I've put in the IPv4 of the machine I want to connect to, and my username (which is the same on both machines), but it's telling me it can't connect. What exactly do I need to allow in the machine I'm trying to remote into for this to work? If I go into explorer, and into Sharing, click Advanced, check Share, click Permissions, click Add, click Advanced, click Find Now, from there, what do I need to allow for Remote Desktop to be allowed in? I'm assuming I need to share the primary drive, correct? I currently only have sharing set up to allow HomeUsers, is there some other object I need to allow specifically for Remote Desktop? I've already allowed everything that said Remote anything through the firewall on the machine. I'm not sure what I've got turned off that's being the issue. I've disabled a lot of services on this machine in the past, could it be something in there or through AutoRuns I need to reauthorize? The machine I'm trying to get into is a 32 bit version, could that be the problem?