Windows 11 version 24H2 has issues with file sharing

Topic

New Reply

I have a shared Windows 11 Pro 23H2 acting as a Server at a Customer. One of the users  updated to 24H2. After that update you can no longer access the File Shares on the Server Machine. The SHARES (Folders) are setup for Everyone and Password protected sharing is Turned OFF. Permissions are set for Everyone. Only way to get it to work again so far is to add Client PC User name and Password to the Server.  I understand improving security but we still should be able to control the network as we want to not dictated by Microsoft.

Seems others are having issues and Microsoft seems to know about it but in usual fashion is in NO rush to fix. The Client System upgraded itself to 24H2 and did not simply offer the update. Tired of being force fed by Microsoft and being there Beta testers !!!!!

Anyone have any other input.

Happy Holidays.

2 users thanked author for this post.

Ulti P. Uszer, Cybertooth

Reply | Quote

Replies

arbrich wrote:

The Client System upgraded itself to 24H2 and did not simply offer the update.

One option, you should have 10 days to uninstall the update and revert back to 23H2.

Reply | Quote

Yes, I can but the time I would have to charge to babysit and the chance of screw ups going back – it was easier to add ID and password to Server PC and get them working again. Customer’s choice. It is just infuriating that MS Forces all this stuff and seems to test nothing.

Reply | Quote

arbrich wrote:

It is just infuriating that MS Forces all this stuff and seems to test nothing.

I agree, I think non-security updates (like cumulative updates) should be optional.

That is a major reason this site suggests using update controllers like WUmgr or InControl or group policy edits. My choice is to have backup images in place ready to restore in 5 minutes.

That said, this particular Win11 24H2 update has not been consistent. It appears that MSFT is not offering it to every PC. Many of us had to download the .iso to install it over-the-top. Then there are a few cases where it gets automatically updated.

1 user thanked author for this post.

Cybertooth

Reply | Quote

Use the Incontrol tool.  Especially in a business setting you need to control, not Microsoft.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Check on the status of SMB v1 as that is disabled in Windows 24H2. What are the versions of the workstations connecting and are they using SMB v1 or V2?

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I added SMB v1 to the Client workstation 24H2 using control panel since it was not installed but still no luck.  Only worked when i added the Client id and password to the Server workstation even with SMB v1 removed from Client workstation.

Reply | Quote

Personally I think it’s wise to have a user account – sounds like you had guest access/no user account needed to access the server shares? Everyone full access/no password is not exactly the greatest way to prevent things like ransomware.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I do agree and have decided to implement that setup going forward no matter how small the network is. However it still is frustrating that Microsoft seems to be getting worse at testing updates they force out to users.  If there going to continue to offer the functionality then they should at least test it.

Reply | Quote

It’s tested – the problem it the lack of documentation.  You have to keep in mind they test for business scenarios.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

It may be the same issue I had with my Synology NAS. You need to set credentials.

click start, type windows credentials. Then add a credential with the IP or name of your server.

Reply | Quote

Having same issues here two PC’s will not connect after update. Also noticed on another is switched password ON!! was like what the! but still did not solve the issue. Been working fine for over 5 years! As usual microsoft push thinsg without testing.

Reply | Quote

Fond the soultion here guys

 

https://learn.microsoft.com/en-gb/windows-server/storage/file-server/enable-insecure-guest-logons-smb2-and-smb3?tabs=group-policy

Reply | Quote

THANK YOU, Chris – Your link provided the solution I couldn’t find.  It works perfectly after editing group policy to enable insecure guest logons, disable SMB signing and disable SMB encryption.  However, before editing group policy make sure SMB Direct is enabled because installation of 24H2 disables it by default.

Reply | Quote

I know this thread is getting ali’l old now but here are some mitigations that were posted on YouTube by computer repair tech Carey Holzman that may fix these Win11 drive sharing issues:

Turn off SMB Client Signing With PowerShell (for Windows 11 Home or Pro)

Step 1 – Type PowerShell in the Windows search box on your taskbar.

Step 2 – Hit the Run as administrator option under the Windows PowerShell section.

Step 3 – In the PowerShell command line window, type [or copy] the following command and press Enter to turn off the SMB signing requirement:

Set-SmbClientConfiguration -RequireSecuritySignature $false

Step 4 – Type Y to confirm the operation.

Enable guest fallback

Step 1 – In the PowerShell command line window, type [or copy} the following command:

Set-SmbClientConfiguration -EnableInsecureGuestLogons $true

Step 2 – Type Y to confirm the operation.

No reboot is necessary. Now see if you can access your shares!

 

2 users thanked author for this post.

huntpt, Cybertooth

Reply | Quote

footnotes:

smbv1 allows a guest mode, that is not possible in V2 etc, every user needs an account, possibly a shared account for low security shares, but not possible without a password.

smbv1 is easily brute forced, and should never be exposed to the net (yes this does happen)

enabling it may fix it, but now you doing that every user every update…just move on to hardware(and software) that has moved on, especially in enterprise.

 

 

Reply | Quote