Windows 10: Windows 10 not accessible on Workgroup

Hello
I have a workgroup of 3 computers
1 Windows 7
2 Windows 10
Same workgroup name for each computer
From My Windows 7 Machine I set-up the sharing

I have Amin Login/Password on each machine
So now I can acces and browse my Windows 7 machine from my Windows 10 machine
But if I try to acces the Windows 10 Machine from the W7 machines I get a Login Pasword form suggesting a domain which is the name of My W7 machine

But now way to access the Windows 10 machine with my usual Login Password

Thanks for any help

:)

 

Files not accessible in workgroup

None exists. I have several WiFi repeaters around the house, but I discarded that as a problem when I connected all three to the same source directly from the router. It made no difference. I can't connect all three to Ethernet. I need to order a network
switch for that, which I will today. Problem is that even if it worked with hard line connections, that is not what I need nor what I can do on an extended basis. If it works, it will just provide more basis for the conclusion that this is a MS bug which
they seem to care less about.

In the mean time, I have tried all suggestions I have found by researching the issue, and nothing. There are many with the same problem out there and I am appalled at MS' disregard of their customer's problems. I have contacted them twice: they put me
on the longest queue to a voice call when I started with the chat, the man who responded said he couldn't handle it and he was switching me to the "Windows 10 professional" team and then their very poor VoiP line cut off. I called again and this time, the
same thing, the man said he had to pass it on to the Windows 10 Professional team but that there would be a charge. Absurd! The product has been in my hands for 3 weeks, it doesn't work as it should, and MS wants me to pay them to fix what is highly probably
their bug! I have a (free) extended warranty from COSTCO; if their Concierge service can't make it work, which I see as doubtful without MS intervention to fix their bug, the laptop goes back to the store and I'll continue to manage with my older equipment.
I am not sure what your role is re. MS, but I appreciate your efforts to help me out. In my past career (now retired) I worked for major corporations and have never seen such an irresponsible attitude towards the customer. I should know something about it;
one of my roles was Corporate VP of Quality for a Fortune 500. Ignoring the customer is anathema to me. I can't imagine how MS can be successful with such attitude.

 

Files not accessible in workgroup

You should really copy your post and paste it in a more relevant thread and then delete it from this one. I realize that the only way to contact a specific Community member is to reply to a thread that a user has posted to and hope that they get an email
or notice, but we are asked not to "Divert or change a thread for your own purposes; just start a new thread with the subject you want to discuss."

______________________________________________________

The best way to guarantee a Windows build to install is if you can do a clean install to a blank partition. Since there are no ISO's provided for most Fast Ring builds, the only way to do that is to create your own ISO or install.wim. This is no longer as
simple to do as it used to be, but there are scripts (not recommended nor supported by Microsoft) to convert the downloaded Fast Ring Windows Update files to an install.wim or ISO. I have successfully used

uup-converter-wimlib-11.7z.

Build 16215 is failing to upgrade on many computers, so it is hard to know exactly why. I did one normal upgrade, but the rest were done by using DISM to apply the build 16215 install.wim.

 

I also experienced the same problem. Windows 7 can open share folder windows 10 .. but Windows 10 is unable to read folder share win 7 ... I think the share folder windows 10 can only share the same version. So, windows 10 is not good friend of windows 7 or XP..