A Cloned Windows 10 to Windows 11 Computer

Thinking I could save a program that I purchased from a no longer in business company, I had a new computer built. I did a backup of a Win 10 computer and gave it to my builder. He restored that backup to my new computer than updated it to a Win 11 Pro computer. I lost the license anyway because it did not transfer into a workable program. That was my reasoning for what I did. The computer is functioning well except for one thing that has me puzzled and I cannot, even with my builders help, figure it out.

The names of the computer differ by me adding 2022, (year of purchase) to my last name, then - PC. The original Windows 10 is only my last name without any date, with - PC. When I open Windows File Explorer and look under Network, I can't see the original Windows 10 computer unless the new one is not turned on. As soon as I turn on the newer Windows 11 machine which was originally cloned, the original Windows 10 computer is no longer displayed in Windows File Explorer's Network tree. Please see the attachment, there should be the original Windows 10 computer displayed but, for some reason, it isn't.

What could be, in either one of the computers that I could change to allow all of them to be displayed. BTW the way, about the only option I wouldn't want to do is change the names from what they are now because I have too many mapped paths to both of them. That was probably a big mistake when I originally named the computers, but still, I don't want to change those now.

There is a possibility this had nothing whatsoever to do with a system being cloned. MS has not 100% mastered getting networking right. Windows has always had difficulties of one kime or another with networking. When it works, it works, but sometimes it's squirelly especially with mixed OSes.. Recognition on the network tree has been a recurring issue that has been reported here many times. For some, no matter the amount of troubleshooting, one/or more systems show in one system's tree and not the other. The general workaround, so far, has been to access the troublesome systems using ip or computer name.

For example in my case, I have one windows 10 system that I have accessed by ip address pinned to quick access for over 2 years. I never found the reason why it did not appear in the network tree as settings in all systems were verified may times. I did nothing and it magically appeared one day in the tree only to disappear again several months later. It was suggested I disable all networking and sharing in all my computers, set my router to default and completely set up my entire network and sharing from scratch. Since, I was able to access all shares everywhere using the workaround using the shortcut ip method, I decided it wasn't worth it, gave up, and decided to not depend on the network tree at all.
Now, every system in the house is set up this way and I've had no issues sharing everywhere.

I feel sure, once my troublesome system is ever replaced with an 11 machine, that networking will work as it is supposed to. I know this is not a solution to your question about the tree, but it's all I can offer from my personal experience with the same problem.

Thank you for the reply and the insight. I am not exactly doing things as you are but I have mapped a path to all my computers. Example \\computer name, that opens up all the shared folders on that specific computer for me. Those that do not show up in the tree can easily be accessed using that path. It's just another work around that should not have to be necessary.

HDL said:

Thank you for the reply and the insight. I am not exactly doing things as you are but I have mapped a path to all my computers. Example \\computer name, that opens up all the shared folders on that specific computer for me. Those that do not show up in the tree can easily be accessed using that path. It's just another work around that should not have to be necessary.

Click to expand...

Windows networking has always been a dog ever since Windows started providing for networked machines - such as Windows 3.11 for Workgroups. It always seems a bit random whether a) you can see any other computer on the network or b) networking functions at all.

In general though you need to enable file sharing, ensure SMB level is set to one that all computers can use (Earlier than Windows 10 you need SMB1), in the control panel under remote - enable allow connections to this computer (do that on all machines in your network), allow the stuff through any firewall and security programs, ensure the computers have the same workgroup name or belong to the same domain -- i.e not on different subnets ==> on a Home LAN probably better to use DHCP to let the router assign IP addresses.

If I boot a current W11 system (insider canary edition) I can't see any computers unless I manually type in \\servername. If I boot W10 all computers are visible -- "Go figure" !!!!!!.

Windows Networking IMO seems to have more Black magic and wizardry in it than Gandalf the Wizard in The Lord of The Rings.

Cheers
jimbo

jimbo45 said:

Windows networking has always been a dog ever since Windows started providing for networked machines - such as Windows 3.11 for Workgroups. It always seems a bit random whether a) you can see any other computer on the network or b) networking functions at all.

In general though you need to enable file sharing, ensure SMB level is set to one that all computers can use (Earlier than Windows 10 you need SMB1), in the control panel under remote - enable allow connections to this computer (do that on all machines in your network), allow the stuff through any firewall and security programs, ensure the computers have the same workgroup name or belong to the same domain -- i.e not on different subnets ==> on a Home LAN probably better to use DHCP to let the router assign IP addresses.

If I boot a current W11 system (insider canary edition) I can't see any computers unless I manually type in \\servername. If I boot W10 all computers are visible -- "Go figure" !!!!!!.

Windows Networking IMO seems to have more Black magic and wizardry in it than Gandalf the Wizard in The Lord of The Rings.

Cheers
jimbo

Click to expand...

I used to know what SMB and SMB1 were but that was years ago long before I ever thought I'd have a home network. I have been retired for almost 25 years now and that is the first I heard those terms. In any case, I have a fellow who builds my computers and my problem is I don't seem to junk older ones until they have run out of useful life. He also sets up the network for me and usually if I have a problem it is after a Windows update that changes permissions. If I can't figure out the problem, he will remote into the problem computer and get it working. He can't seem to solve the problem I started this post about.

Both computers show up in the network tree but not at the same time. If the old machine, which was used to clone from, is on it will show up in the network tree. However, if I turn the newer computer on, which was cloned, the older one disappears from the network tree. That is what is puzzling. But after reading the 2 posts here, I guess I should consider myself lucky that all my computers seem to show up in the network tree, just always missing one or the other. Thank you..