Nothing to see it will be sorted
Unlike Apple who regularly screw with Nas products.
Microsoft has overnight pushed out the latest of its ongoing preview builds for Windows 10, with this one carrying a warning that it could break your network file share connections. Redmond-watchers will know that the firm runs a Windows Insider programme where users can sign up to be guinea pigs get early access to features …
This problem has been ongoing since the anniversary release and it still isn't fixed by MS.
Pre-Anniversary Win10 killed off my NAS shares, but it was a matter of idiotic design rather than a bug. The NAS was a canary in the coal mine.
I'd configured one of my home machines with a local user account, and mapped several NAS shares. Everything worked fine until I naively signed in to an Outlook.com account with the Calendar app. Win10 took that as a clear sign that I now wanted to share all of my logins and private data with the M$ mother ship, and -- with no warning -- converted my carefully configured local account into a Microsoft account.
The first sign that this had occurred was that the above-mentioned shares disappeared due to an authentication error. Then, and only then, did I realize that Win10 had changed the user name, password, and account type without telling me.
So I put it all back the way I had it. Two days later, the Anniversary update borked all of my settings again. Thus ended my dalliance with Winblows 10.
In fact, network shares becoming inaccessible upon switching from a local a/c to an MS one is a bug that's been around since Win8.
Despite battling with this for hours on various occasions, only today I happened upon a 'fix'.
Before I continue, I must add that this is for Windows 8 & later boxes with a network share accessible to all ie without a password that previously worked but stops working when the user a/c is changed from a local one to a Microsoft one.
Check the permissions for the share. I found 'Everyone' was missing. So I added it with the required r/w settings.
Next, I tried to browse to the share over the LAN from another machine. I still got the dreaded password prompt. On a hunch, I typed in 'Everyone' for the username and left the password blank. It worked and continues to work just fine.
Yay.
But yes, some parts of Windows 10 suck. But I'm forcing myself to tame it. Not as bad as Win ME for flakiness, and the opposite of Vista for speed, but I've had to migrate to it for my main machine as the recently acquiree i7-6700K is definitely more responsive under 10 than 7.
@ fidodogbreath:
If that's how Win10 defaults to handling user accounts, exactly how will MS explain this fiasco to compliance regulators? "Yes, sir, when we migrated all the customer service desktops in Account Services to Win10 it unknowingly shared all our confidential logins with Microsoft, and after the hackers got access to Outlook that's how we lost 450,000 private account profiles?"
Oh, that won't go over well at all. :grabs the popcorn: I foresee a massive lawsuit and governmental grillings, not to mention the fact that, under these Win10 SOP, I cannot see Win10 ever making compliance approval at all.
Microsoft, you've thrown the baby out with the bathwater on this one!
"Unlike Apple who regularly screw with Nas products"
Erm, how?
I am genuinely interested, speaking as an experienced Apple user who owns a home network consisting of Macs and PC running various OSes, and also works in a department where I help manage a network of nearly 200 Macs and thousands of PCs, all running various OSes, and who has never had a problem with a NAS on a Mac that was caused by something Apple did.
Back when I still had Macs, they were terribly unreliable when it came to network shares. They would tend to stop working for no reason. It was avoidable but you had to mount things with command line tools. This included all manner of connections including Mac <-> Mac.
You do understand that this bug was on the ßeta version...
The bug exists in Windows Vista and more recent. The ßeta just contains the first pass fix which unfortunately has an unfortunate side effect.
Interestingly, if the MS release is to be believed, there is every reason to explain to the hospitals etc. because it is yet another reason why they should delay migrating from XP :)
Because you only find out if it will work today when you try and use the function.
Suggest the new strap line for MS
Microsoft Windows, What do you expect to work today ?
Hiding things for "security reasons" is called security by obscurity - as in its not proper MAC/DAC
> you have, for some bizarre reason, set your own network as a public one.
Windows 7, 8, and 10 are very happy not only to do that for you (as in CHANGE THE BLOODY SETTTING), but also render it very difficult for you to set it back to private/enterprise.
Who in their right mind would connect a windows box to a public network, hello ?????
"...for some bizarre reason, set your own network as a public one."
Or had it reset for you. Since last Patch Tuesday I've been been seeing problems caused by the network type being mysteriously reset from work to public on Home Prem installs (but not on Pro). Anyone else seeing this?
What do you call denying access to things that you don't have permission to access? I got the impression that that's what this change is about.
Windows gets slagged off for failing open. Looks like they're changing this to fail shut.
@sabroni
Hiding something does not secure it, whereas securing something works irrespective of it being visible or not.
If you can see it and don't have access, that's what the "Access denied" message tells you.
As I said before, security by obscurity.
Why the heck would anyone install a preliminary Industry Integration Test Version of software on a production computer?
The only fault I can see on MS's actions is not putting the text "Industry Integration Test Version" in big yellow letters on a bright read back ground on the desktop and start menu.
I suppose they figure if people don't read the warnings before installation they won't read the warnings later. But that overlooks that one person might install the test OS on the computer and an end user might come along later completely oblivious to it being a test system.
Rather that this is intentional. There's a long-standing security flaw that allows Windows to pass authentication details to SMB shares, even over the internet. That should not happen and if the fix for this issue is to make the network your NAS is on a trusted one, then it looks like they are fixing the older flaw.
About time.
Microsoft offers a fix for this; if you change your network to “private” or “enterprise”, it should start working again.
Wouldn't almost everyone have one or other of those set anyway in the kind of scenario where you'd be dealing with shared drives and NAS's? How many of those do you generally find on a public network?
I have no sympathy for journalists reporters who don't know what a test system is.
Why cross out where you note that people running Insider Rings have volunteered to be guinea pigs? Volunteering to be guinea pigs is exactly what they did.
They're running Industry Integration Test Versions of the operating system and they should darn well expect there to be bugs.
The only people I would feel sorry for are those end users who had a sysadmin unprofessionally install a test version on an end user computer for production use, and for readers subjected to the writings of reporters who don't know what test versions are.
Wait, so they know it's a problem, and put their patching energies into doing things that aren't fixing it?
I miss the days when software was released as a complete thing, instead of "meh, we'll fix it in a patch, ship it". And this is down in the "meh, we'll not fix it in a patch, ship it" range.
Eww.