Win11 24H2 Installed, now no network sharing

flhthemi · Oct 10, 2024

I've rolled back all mine with exception of one so I can see if MS fixes this trash.

Stigg · Oct 10, 2024

Three of my computers have Windows 11 24H2, but I've only noticed a problem with accessing shared folders on one of them after I installed KB5044384.

Stigg · Oct 10, 2024

Wolfzz said:
OK with 24H2 Pro 26100.1742 I had this problem.
My Windows 10 Pro could access Windows 11 24H2 through my network, however Windows 11 24H2 could not access my Windows 10 Pro or any earlier versions of Windows 11 Pro Computers this only happened since I went to 24H2.
To fix this issue I did both of these changes in Local Group Policy Editor. And Now all is happy including me. I hope this helps.

Computer Configuration, Windows Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.

Computer Configuration, Administrative Templates, Network, Lanman Workstation
Double click on "Enable Insecure Guest Logons"
Set this to "Enabled"
Click on OK.

You need to add another level to this.
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options

By the way...
"Microsoft Network Client: Digitally sign communications (always)" was already disabled on my computer.

Wolfzz · Oct 10, 2024

Stigg said:
You need to add another level to this.
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options

By the way...
"Microsoft Network Client: Digitally sign communications (always)" was already disabled on my computer.

Ok Done I must of missed that when I was Typing it in Thanks

Stigg · Oct 10, 2024

Wolfzz said:
Ok Done I must of missed that when I was Typing it in Thanks

I tried your settings, but sadly it didn't work for me. I see that it's helped some people though.

Wolfzz · Oct 10, 2024

Stigg said:
I tried your settings, but sadly it didn't work for me. I see that it's helped some people though.

Have you tried this
In admin PowerShell type in:
Set-SmbClientConfiguration -RequireSecuritySignature $false

Stigg · Oct 10, 2024

Wolfzz said:
Have you tried this
In admin PowerShell type in:
Set-SmbClientConfiguration -RequireSecuritySignature $false

No. I haven't tried that yet. Is there a Group Policy setting for that?

ian50 · Oct 10, 2024

From a comment made above by JJVilzu 4:45am:

... Home versions which do not have the Policy Editor thus the ability to edit all policies is not available

Just search for Enable Group Policy Editor in Win 11 Home.

There is a simple (enough) batch file available as freeware to enable gpedit.msc on Home, Win 11 22H2 and 23H2.

Also available is a similar freeware install for HyperV, Win 11 22H2 and 23H2 versions.

I've been running these add-ons for some years now, first on 22H2 and now on 23H2. O/S updates using the MSU file does not overwrite these, as they also don't overwrite font choices. If an update using the ISO file is done (not clean install, just update), then gpedit, hyperv and fonts (amongst other additions) have to be re-installed.

I haven't played with Win 11 24H2 in sufficient detail to comment. None of them may work in that version for all I know at the moment, but sufficient unto the day of evil thereof ...

Stigg · Oct 10, 2024

Bree said:
In 24H2 tighter security restrictions that were previously only enforced in Enterprise and above are now on by default in Pro. Insecure logins are not allowed by default, you now cannot connect to another PC if you have a local account with no password.

There are two ways to connect. The first is to create a Windows Credential for an account with a password on that other PC.

So, what does that first option actually mean and how do I do it? I tried the second option, and it doesn't work.
I assume you create a Windows Credential with Credential Manager. I already have a credential there.

I know this thread is about 24H2, which I have, but my problem started after installing KB5044384.

JJVilzu · Oct 11, 2024

flhthemi said:
Could any of these settings you all have mentioned be the reason why ONE NAS in my network is not showing up in the workgroup but I can access it via \\NASNAME? I just added it to the Quick Menu as a temp workaround. It's an old Zyxel NAS520. It is using a password/user name.

I tried Bree's suggestion in post#2 - No joy there.
I tried Wolfzz suggestions in post#5 - No joy there either

And now I've noticed, prior to these attempts, this PC isn't showing and none of the other 24H2 are either. What the heck!
You know MS really has made a mess out of networking for the average Joe.

I had to restart Windows on all machines and other devices a couple of times in the network after the upgrade to 24H2 to get all the devices in the network to show up. That was all I had to do.

Stigg · Oct 11, 2024

I restored a system image that I made before installing KB5044384, and my network shares are working again.

Bree · Oct 11, 2024

Stigg said:
So, what does that first option actually mean and how do I do it? I tried the second option, and it doesn't work.
I assume you create a Windows Credential with Credential Manager. I already have a credential there.

You need to create a credential for an account on the other PC that has a password, even with a credential if the account you used has no password 24H2 by default won't let you connect.

Stigg · Oct 11, 2024

I fixed my issue by restoring a system image created before KB5044384. I haven't yet installed KB5044384 again.

flhthemi · Oct 11, 2024

Bree said:
You need to create a credential for an account on the other PC that has a password, even with a credential if the account you used has no password 24H2 by default won't let you connect.

This might be my issue...I think the other PCs have local accounts. So I guess I need to use my Microsoft login on those as a local account just won't cut the mustard anymore for networking.

Bree · Oct 11, 2024

flhthemi said:
This might be my issue...I think the other PCs have local accounts. So I guess I need to use my Microsoft login on those as a local account just won't cut the mustard anymore for networking.

No, credentials for a local account on those other PCs will work. It just has to be one that has a password.

flhthemi · Oct 11, 2024

So I need to make all the changes outlined above and on each PC and I need login creds for all the other PCs on the network?

Lesoudeur · Oct 11, 2024

KB5044384 Windows 11 Insider Release Preview build 26100.2152 (24H2) - Oct. 10

UPDATE 11/14: https://www.elevenforum.com/t/kb5046740-windows-11-insider-release-preview-build-26100-2448-24h2-nov-14.30579/ Windows Blogs: Hello Windows Insiders, today we’re releasing Windows 11 Build 26100.2152 (KB5044384) to Insiders in the Release Preview Channel on Windows 11, version...

www.elevenforum.com

mccnavy · Oct 11, 2024

For me I had to go into credential manager, delete any old credentials associated with the network, and then add new ones. 24H2 didn't like something about the old ones. Entering new ones with usernames/passwords worked.

Stigg · Oct 11, 2024

This is for the KB5044384 network sharing breakage, but it would be interesting to see if it also fixes this issue.

KB5044384 Windows 11 Insider Release Preview build 26100.2152 (24H2) - Oct. 10

UPDATE 11/14: https://www.elevenforum.com/t/kb5046740-windows-11-insider-release-preview-build-26100-2448-24h2-nov-14.30579/ Windows Blogs: Hello Windows Insiders, today we’re releasing Windows 11 Build 26100.2152 (KB5044384) to Insiders in the Release Preview Channel on Windows 11, version...

www.elevenforum.com

flhthemi · Oct 12, 2024

Bree said:
You need to create a credential for an account on the other PC that has a password, even with a credential if the account you used has no password 24H2 by default won't let you connect.

Having done this I can access all the devices that show in my network. Key word being SHOW. I have about 7 that are not showing. They are all still on 23H one is an old Zyxel NAS520. Those on 23H show ALL devices. I have also gone into firewall settings and activated the options related to file sharing as pointed out by Lesouder post #37.

So really, all I need to do now is to get the MIA's to show themselves on 24H. I have NOT done the following:

Code:

Computer Configuration, Windows Settings, Local Policies, Security Options
Double click on Microsoft Network Client: Digitally sign communications (always)
Double click on Microsoft Network Client: Digitally sign communications (if server agrees)
Set both of these to "Disabled"
Click on OK.
Computer Configuration, Windows Settings, Security Settings, Local Policies, Security Options

So I wonder will it work....or is all this a bug introduced by Microsoft and I should just wait.

Win11 24H2 Installed, now no network sharing

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer