I discovered that MS balanced a bowl of water on the door for home network users upgrading to 10 who don't use homegroups but naively followed the recommended 'use your MS account details' for an ID and password.
It may not hit that many users, but from Windows 8 onwards if you use an MS account to log on and you want to view shares on other PCs on a home network that are also at 8 or above, Windows imposes a sort of bodged domain network model. You are required to enter an ID and password to view shares, your 'domain' is the name of your PC, and it royally screws things like network drives mapped to shares.
I never noticed this before because I had a mixture of boxes at 7 and 8. It's a pain to work round in 8 and 8.1 but relatively easy to switch to a local user in 10 if you know what the problem is and that this is the way to fix it. It wasn't something I'd ever seen publicised, and judging from the other bewildered users floundering around with half-arsed fixes, I'm not alone.
The issue is compounded because the 'join a domain or workgroup' wizard is broken for many users but in a way that gives the impression that something other than the wizard is broken - i.e. when you check the radio button to indicate that this is mainly a home PC and not business, the wizard hangs for a bit, tells you to restart (without asking what workgroup of domain you want), sets your work group back to the default 'workgroup' and when you restart you find that it's defaulted back to 'this PC is part of a business network'.never trust a man in a blue trench coat, never drive a car when you're dead |
