smbv1 disabled automatically in Win10

Topic

New Reply

Just when I thought I’d seen the worst from Micro$oft, I got hit with a new one today.

It seems that there is a secret rule in Win10 that disables SMBv1 if not used for 15 days.  Trying to get PCs back on line after coronavirus shutdown, one of them apparently hit the limit and won’t access a shared directory on a Server 2003 server.  Could have taken me hours to fix.  Why can’t they provide a warning, maybe a notification?

Since I am on the subject, when you get an error pop up with a URL, why can’t you click on the URL or at least cut and paste it.

Thanks, now I feel better:

Reply | Quote

Replies

SMBv1 has been the subject of numerous warnings over recent years, including here.

This is the definitive article, from Microsoft’s Ned Pyle:
Stop using SMB1

1 user thanked author for this post.

Elly

Reply | Quote

steven.h.lutz wrote:

… when you get an error pop up with a URL, why can’t you click on the URL or at least cut and paste it.

Much depends on the software framework used to display the error window, try Ctrl+C to copy it, paste it (Ctrl+V) into Notepad to check before closing the notification.

Reply | Quote

If you absolutely need SMB 1.0 (despite the security risks), open the old Programs and Features via Control Panel, go to “Turn Windows features on or off” and under the SMB 1.0 category you’ll see “SMB 1.0/CIFS Automatic Removal”. Remove that and SMB 1.0 will stay installed.

Reply | Quote

[EP]

only recent versions of Win10 (I think starting with v1709) disable SMBv1 automatically when not used for many days
this does not occur with win10 v1703 & older as SMBv1 may stay installed & enabled and would have to be removed/uninstalled manually

• This reply was modified 3 years ago by EP.

Reply | Quote