here homegroup or whatever name it has can be accessed like with any other windows version before, talking about 10162 build mounted on a tablet edit: wait I was talking about workgroup. Homegroup also fails
even in windows explorer, clicking network. its visible but cannot be accessed. Once I connect with the Wifi (still connected to Eth) then everything works. So I just did that and then disconnected from the Wifi leaving only the Eth and homegroup FAILS lol. Keep Eth and WiFi both connected and Homegroup and Network shares are visible -ed- and accessible
I use Workgroup only for any networks I connect to. That works all times for me, just need to have an account on the other computer or an valid username and password.
yeah that is what I was hoping to do. Fixed it by connecting both Eth and Wifi to the network. It wont work for me if its just Eth. Silliness!
It is working with only wifi enabled and eth disabled now. It wouldn't earlier. I am thinking because wifi was always enabled, but had never connected to anything (I hadn't used it at all), it needed initialized or something. With that, I still cannot just use Eth and disable wifi *sigh* but it works anyway, so Im good with that, just a hell of a hassle.
On my Acer Laptop, which run with 10162, I could just switch off WiFi and Networks works, same as if the ETH Cable is not not connected, WiFi On, Networks work!
While installing Windows, I always directly key in the WiFi Password too while the machine is running on ETH. But I never use Homegroup because I use the machine all times in several different networks on a day, I need that for my work. Never had problem with Network. On my old Laptop, even an Acer, I had some problems. That were because of the Intel WiFi Module and after changing that to an Qualcom Atheros never had such problems again.
I never use Homegroup either, but I thought since I could not use workgroup, I would try homegroup. Both failed until wifi was connected. I will need to remember to enter the wifi into installs even if its not going to be used.
ESD files have much smaller size than ISOs. Some people here have poor internet connection. So, they prefer ESD to save their data & time.
Smaller download - some ppl on low speed connection or restricted bandwidth? Edit: Apologies @ AtomR - Posted at same time.
Curious: had you try the old way: connect via Explorer/File Manager using the IP Address of the target? Or even try to PING the Target via CMD?