Ddos 
Revamped "Start" Menu Interface
Microsoft has confirmed that the recently released September 2025 security updates have caused connectivity issues with Server Message Block (SMB) v1 shares. While the impact is most pronounced for enterprise environments, the number of individual users still relying on SMBv1 for file sharing is expected to be minimal.
The issue spans a wide range of operating systems, including all versions of Windows 11, Windows 10 22H2/21H2, and Windows Server 2022/2025. However, Microsoft clarified that the problem occurs only when connections are made via the NetBIOS over TCP/IP (NetBT) protocol.
In its support bulletin, Microsoft stated:
“After installing the September 2025 Windows security update (the Originating KBs listed above) or later updates, you might fail to connect to shared files and folders using the Server Message Block (SMB) v1 protocol on NetBIOS over TCP/IP (NetBT).”
As a workaround, Microsoft recommends that affected users allow traffic on TCP port 445. This forces Windows SMB connections to use direct TCP instead of NetBT, thereby restoring functionality until an official patch is released. A permanent fix is currently in development and is expected by the end of this month or early next.
Microsoft also reiterated that SMBv1 is an obsolete and insecure protocol, plagued with vulnerabilities and officially deprecated in 2014. Since Windows 10 version 1709, SMBv1 has no longer been installed by default.
For years, Microsoft has strongly advised organizations to migrate to SMBv2 or SMBv3, both of which are significantly more secure and actively maintained. Yet, a small number of enterprises continue to run SMBv1, leaving themselves exposed to heightened security risks. The latest disruptions serve as another reminder that moving away from SMBv1 is not only advisable but essential.
Donate