New Windows 10 Insider Preview Fast Build 17751 - August 31 Insider

kado897 said:

Not a new account for me, It's my MS account.

Edited the above post, i got a repro by killing shell experience host, it spawns and crashes.

This repro's in both my MSFT linked account a new one.

tbh, doesn't surprise me in the least that it won't occur for everyone.

but 17134 was working before moving onto insider and this seems to be working so ¯\_(ツ)_/¯

Strange 'update' yesterday. Woke comp from sleep to find it had rebooted (was at lock screen). It went instantly to the desktop. Looked at Update info and saw it had updated to 17751.1 which is what I thought it was already on.

Checked Event Viewer and there are only entries for 3 Sep. Windows.old was there dated 3 Sep.

Call me confused!!

[QUOTE=Eagle51;1452084]
Probably an exercise in futility, but I got nothing better to do right now :)

Just an observation ... Don't know if this might help or not and any input on this is appreciated.

In the Lanman Server/WorkStation Parameters registry key, I've been seeing the following two keys that are NOT always present or NOT set the same and according to what I've read so far, they should be. Mine are set to the following and no issues with network sharing with Win10Pro IP (17751) or Win10 Home (1803).

EnableSecuritySignature : 1
RequireSecuritySignature : 0


Thanks for the information on your network and the script.

EnableSecuritySignature : 1
RequireSecuritySignature : 0

Both of those entries are the same as what's in my registry. I also used your script to compare a PC that works and the one with 17551.1 on it. They were the same too. I'm hoping Microsoft knows what they changed in this build and fixes it.

Ztruker said:

@Looey, the networking probl3ems started with the 16299 Fall Creator's Update and has been bad since then.

Yes, it has been a problem for quite some time.
Here is my networking story:
Desktop, running Skip Ahead build 18219 as default (it is a dual boot system.) [x64 Pro]
Surface Pro 4, running Insider fast build 17751.1 [x64 Pro]
Current Surface Pro, running 1803 build 17134.254 [x64 Pro]
NuVision 7" tablet, running1803 build 17134.254 [x32 Home]

Network and Sharing Centre is set up identically on all 4 systems.
NuVision 7" tablet connects wirelessly, the other machines are connected (wired) to an ethernet switch. (Pro 4 via a Plugable Ethernet to USB converter, Surface Pro via a Surface Dock.
Registry LanMan keys are all set up as described by Eagle51 in post #75 Thanks, Eagle 51.

All machines have Internet access.

Desktop sees all my computers, but is unable to access the shared folders on Surface Pro 4. It can access the shared folders on the other machines.
Surface Pro 4 sees all machines, but cannot access the shared folders on the NuVision 7" tablet.
Current Surface Pro sees all my computers, but is unable to access the shared folders on Surface Pro 4 and NuVision 7" tablet. It can only access the shared folders on Desktop.
NuVision 7" tablet sees all my computers, but is unable to access the shared folders on Surface Pro 4. It can access the shared folders on the other machines.

I run Mouse without Borders, and it connects to all 4 machines. Sometimes I have to open the app & hit Apply to the machine I wish to connect to.

Hey lmod and looey,
Thanks for the feedback. I'd like to see your lanman-tcpip-smb.txt files, if you care to share :)


Note: I was thinking it these two settings not being the same or missing it might be causing SMB to not communicate properly. Was just a SWAG tho.
EnableSecuritySignature : 1
RequireSecuritySignature : 0

Eagle51 said:

Hey lmod and looey,
Thanks for the feedback. I'd like to see your lanman-tcpip-smb.txt files, if you care to share :)

Here on the forum ?
I have only run your script on the desktop, yet. I'll run it on the other machines later, don't want to interrupt what 'm working on ATM.