Last One To Post Wins [118]

GM Mike :)

will have to get my list of items to disable ready

paulsalter said:

GM Mike :)

will have to get my list of items to disable ready

Should also make a complete image backup too. :)

yup, i am all prepared

if things go wrong, then its a good reason to do a clean install, i am needing one, but too many apps to install and configure so keep putting it off

paulsalter said:

Morning All

Is this week the public release of Fall, Spring, Creators Update Part 2 or whatever its now called :)

Morning Paul. That's a definite maybe.

Apart from the SMB1 Issues that were expected, All three of my active system updated (Release Preview) without major issue, (old Test desktop took a couple of times to finish but its dodgy anyway ).

Network issues due to SMB1
Maybe due to the depreciation of the homegroup system, (which I had running for test purposes), the Computers group in the network scan in Windows File Explorer failed to show any content.

A little research suggested that this issue was due to Windows 10 use of the Computer Browser system from Windows NT that relies on SMB1 to work, (Homegroup may have taken up the slack previously when SMB1 was inactive), I expect some activity on this debacle soon as it's an important part of workgroup networking to be able to see the other systems on the network.
You can always use the FQDN (Fully Qualified Domain Name) system to access shares - \\Computer\Share

Also the mapped drives I had to my Network storage (nothing fancy just a couple of partitioned external drives connected to my router via USB), stopped working

All was corrected by simply re-enabling SMB1 in the Windows Features - I Am aware of the potential risk but windows 10 is fully patched and I also run Bitdefender Anti Ransomware, but would suggest that anyone consider their options before doing the same

Barman58 said:

Apart from the SMB1 Issues that were expected, All three of my active system updated (Release Preview) without major issue, (old Test desktop took a couple of times to finish but its dodgy anyway ).

Network issues due to SMB1
Maybe due to the depreciation of the homegroup system, (which I had running for test purposes), the Computers group in the network scan in Windows File Explorer failed to show any content.

A little research suggested that this issue was due to Windows 10 use of the Computer Browser system from Windows NT that relies on SMB1 to work, (Homegroup may have taken up the slack previously when SMB1 was inactive), I expect some activity on this debacle soon as it's an important part of workgroup networking to be able to see the other systems on the network.
You can always use the FQDN (Fully Qualified Domain Name) system to access shares - \\Computer\Share

Also the mapped drives I had to my Network storage (nothing fancy just a couple of partitioned external drives connected to my router via USB), stopped working

All was corrected by simply re-enabling SMB1 in the Windows Features - I Am aware of the potential risk but windows 10 is fully patched and I also run Bitdefender Anti Ransomware, but would suggest that anyone consider their options before doing the same

Well not quite sure yet Nigel, if I should turn off my SMB1 yet, I have 2 PC's networked together, printer is hooked up to my router, but not by a usb port. Homegroup does show up under my network in file explorer but its not used. Both PC's are hardwired. Also have Wi-Fi disabled. Suppose I could turn off SMB1 and test my networked computers at some point, to see if they still see each other. :)

Barman58 said:

Apart from the SMB1 Issues that were expected, All three of my active system updated (Release Preview) without major issue, (old Test desktop took a couple of times to finish but its dodgy anyway ).

Network issues due to SMB1
Maybe due to the depreciation of the homegroup system, (which I had running for test purposes), the Computers group in the network scan in Windows File Explorer failed to show any content.

A little research suggested that this issue was due to Windows 10 use of the Computer Browser system from Windows NT that relies on SMB1 to work, (Homegroup may have taken up the slack previously when SMB1 was inactive), I expect some activity on this debacle soon as it's an important part of workgroup networking to be able to see the other systems on the network.
You can always use the FQDN (Fully Qualified Domain Name) system to access shares - \\Computer\Share

Also the mapped drives I had to my Network storage (nothing fancy just a couple of partitioned external drives connected to my router via USB), stopped working

All was corrected by simply re-enabling SMB1 in the Windows Features - I Am aware of the potential risk but windows 10 is fully patched and I also run Bitdefender Anti Ransomware, but would suggest that anyone consider their options before doing the same

Yes I ran across that silliness. It's not limited to the Spring Creators Update. There is also a scheduled task to switch it off in the FCU after a period. You can disable that and enable the SMB1 Client in Windows Features.

The point is that if/when you upgrade to SCU 1803 Homegroup will be gone completely and SMB1 client will be turned off , (the SMB1 server stays active which is a little weird).

Upgrading this time will push the question of "do I take the Risk with SMB1" It's something that should not be happening, Microsoft have known about these issues or their potential for a long time and seem to have ignored them

Edit

@kado897 the automatic option is missing in the SCU, Windows Features - I do not know if that means that the automatic disabling is now not preventable or that it is not there anymore.

Will have to check the Scheduled tasks

Barman58 said:

The point is that if/when you upgrade to SCU 1803 Homegroup will be gone completely and SMB1 client will be turned off , (the SMB1 server stays active which is a little weird).

Upgrading this time will push the question of "do I take the Risk with SMB1" It's something that should not be happening, Microsoft have known about these issues or their potential for a long time and seem to have ignored them

Yes of course. I had forgotten that was the default in SCU. I've never used Homegroup but you still need SMB1 for File Explorer to browse devices on your network.

I've just checked the scheduled tasks on my system on 1803 SCU and although there is a section "SMB" there are no entries in the branch so it looks like the automatic timed switch off of SMB1 is no longer in use. So the system will retain what you decide and select - which is what it should do of course, It should warn but not decide