Windows 10 We need a serious conversation concerning using a PIN to log on....

[Saltgrass]

I have just spent a couple of hours trying to figure out how to get my clean install of 10130 to see my network shares. For some reason, even though I had connectivity, I could not see either my other Windows 10 computer or my NAS.

For this build, I set up a PIN to log on to the system. I had not logged on with a Password and I did not want to change the current configuration while troubleshooting.

It seems using a PIN to log on restricts access to your LAN. My other system could see the shares fine and I was trying to compare the two systems to see why one was working and the other was not.

Well, after much wasted time I decided to go ahead in log on using the Microsoft Account Password. No problem at all, now, seeing the other shares.

So, I suppose I could ask what are the differences between using a password log on and a PIN log on, since obviously, there are some? Microsoft seems to think a PIN is more secure. Are they talking about a 4 digit PIN or a longer one. Why does it seem using a PIN to log on make a difference in the network connectivity?

Thanks..

 

[Saltgrass]

I don't red Gabe's tweets, but he probably said something like oh yes, we know about that, it will be fixed in a future build, yada, yada,yada..

It is never wasted when you learn something... I have a much better grasp of networking that I did before I started..

 

[Trouble]

Agreed... all such learning goes in the positive column.
My thoughts are (yes you practically nailed what he said "know about it / working on it") that in instances where the behavior that we're seeing, which seems to be different from one instance to another and is more or less attributable to a bug may be time ill spent until that particular bug is actually resolved and we see what the behavior is, post-fix.

 

[Saltgrass]

I sort of enjoy finding bugs., and if you have been keeping track, when they list known problems with a particular build, they usually leave many out. You would think, after 8 or 9 months, they could have correct some... Different configurations seem to have specific problems. Like the sound right now for a lot of folks. I realize Microsoft may have to wait for a driver from a Manufacturer, but some of the problems are all on Microsoft.

Most information provided to Microsoft is provided via the telemetry. The feedback program may only have limited effect. But you must remember, in prior beta testing, we got builds which actually had problems corrected. In these builds, particular problems are not even being addressed until later. I suppose the bottom line might be, we have a plethora of problems we can check for in the RC, that will be were the Rubber meets the Road..

 

[davehc]

As Trouble said in another thread. Some of us have been around for a while, on the bug fixing thing. I got my MVP status from bug fixing XP, but that is another story.
But, maybe because I am getting too old and meaner, I am bored with bug fixing and perusing help forums. I honestly think that every bug, (and here I am not really talking about bugs/errors on a Beta product, which, hopefully, will be rectified, I am only thinking of the big picture) has been discussed, somewhere and repeated ad infinitum over many forums. I have a huge "Dbase" on a spare HD, which has many of these solutions listed.
I believe that many have the same, or, if younger or more capable, committed to memory. My very poor attitude these days is , when I see a new complaint, wait a while and someone will take it up and offer a fix.
I am not suggesting this is a bad thing! But I can see a trend. Persons/users who are not so knowledgeable, or au fait, with browsing, can join a comprehensive and reliable forum such as this, and save themselves a lot of browsing heartache.