Win11 24H2 Installed, now no network sharing

Tracian said:

But I don't need a test to know that on a clean system it is going to work! Of course millions of people have perfectly working setups... it's my particular hardware and software configuration that borks it all (and / or the downgrade from 24 to 23 leaving stuff behind) - so even if I lost one week to reinstall and reconfigure it all, I'd only come back to this unworking combination. My point is to find a fix for this specific configuration.

Click to expand...

Uh-huh. That said, you did state that it used to work so the scientific approach to rule out that it isn't the hardware is to duplicate the working scenario. That way you can rule out the remotest possibility that nothing went awry in the hardware. If 24 still won't work after that then you can reinstall 23 on that test drive and if it works well then you have your answer. Myself I have no recollection of Windows asking me if I would be networking with other PCs as it did with Windows 10 and I'm pretty sure 23H2 asked me if I would be sharing publicly or privately but I could be having false memories. Definitely have no recollection of this with 24H2. Perhaps the issue is somewhere there, where you initially set up your internet connection. How can we test this? I'm sure you've already gone through the msconfig route and you've likely tried to re-activate through services. Doubtless you have already done all the DISM commands so what's left? I wish I could be more help but I only have two PCs running 24H2 and both of them see the network. *


*They don't see the entire network like my wife's Windows 10 (via MS account) does but they see enough. Maybe avoid using a local account? Blah. I feel like I just gave you bad advice.

Tracian said:

After more days (and nights) of attempting everything and their dog, I came to the conclusion that my specific issue isn't even rooted in authentication, but in network discoverability issues: no matter what, the Network Discoverability toggle reverts to off as soon as I close the relevant Options panel

Of course I tried following every tutorial I could find about that specific matter, but once again... no joy at all. If you have any fix that you think might work (short of changing OS, factory reinstalling, and similarly humorous suggestions), I'm all ears.

Click to expand...

You are not alone. Here's a thread about the same build 26100.5074 networking mess.

mmm mine has, finally, been working fine with both my Main PC and the NUC with a DAS connected to it, after a LOT of effort and work to restore functionality.

For some reason my NUC can no longer access the Main PC, but works the other way around. It was fine. Windows 11 is just getting so difficult....



the above is using the NUC, in the loft, trying to access the Main PC on the LAN, it worked ok up to this afternoon.

I'll throw my hat into the ring here and yes, each update with Win seems to introduce new problems especially on the network front but it doesn't affect the majority or so it would seem. My other PC's/Laptops could access the main PC but I had one that wouldn't - it had the dreaded 0x80070035

It was to do with the security. All the shares on the main PC were there including 'everyone'. On the main PC on the right of Disk Sharing within Properties is Security - click on Advanced and mine was showing Owner as System. I changed this to Everyone and hey presto the thing suddenly worked. Now not advisable to leave as Everyone but if you can then access the main PC you are narrowing down the options. Why the other satellite PC's/Laptops were finding the main PC I have no idea - but the one stubborn one well.......

All I was trying to do was isolate the 'problem'.

It may work for you and may not but good luck.

6391mb said:

I'll throw my hat into the ring here and yes, each update with Win seems to introduce new problems especially on the network front but it doesn't affect the majority or so it would seem. My other PC's/Laptops could access the main PC but I had one that wouldn't - it had the dreaded 0x80070035

It was to do with the security. All the shares on the main PC were there including 'everyone'. On the main PC on the right of Disk Sharing within Properties is Security - click on Advanced and mine was showing Owner as System. I changed this to Everyone and hey presto the thing suddenly worked. Now not advisable to leave as Everyone but if you can then access the main PC you are narrowing down the options. Why the other satellite PC's/Laptops were finding the main PC I have no idea - but the one stubborn one well.......

All I was trying to do was isolate the 'problem'.

It may work for you and may not but good luck.

Click to expand...

You might be onto something. Only problem is: I cannot access the Properties of the NAS. The best I can do is to have it listed under Network - anything past that returns an error message.

What format is the NAS. Is it Linux or Windows based. On my stubborn problem I had to carry out the changes on a drive inside the main PC which is Win. If you've got Linux then it's outside of my pay grade.

6391mb said:

I'll throw my hat into the ring here and yes, each update with Win seems to introduce new problems especially on the network front but it doesn't affect the majority or so it would seem. My other PC's/Laptops could access the main PC but I had one that wouldn't - it had the dreaded 0x80070035

It was to do with the security. All the shares on the main PC were there including 'everyone'. On the main PC on the right of Disk Sharing within Properties is Security - click on Advanced and mine was showing Owner as System. I changed this to Everyone and hey presto the thing suddenly worked. Now not advisable to leave as Everyone but if you can then access the main PC you are narrowing down the options. Why the other satellite PC's/Laptops were finding the main PC I have no idea - but the one stubborn one well.......

All I was trying to do was isolate the 'problem'.

It may work for you and may not but good luck.

Click to expand...

Thanks for posting that :)

That was one amongst a whole load of things that I had changed, perhaps forgetting some, that did help. But not getting access at all to something that had worked fine, and is there to be seen under the networks is most baffling.

I did delete the credentials and remade those, so now instead of no longer being able to get access to "Main" I now get......



The credentials entered are correct, my MS online account, the only account and password used. It had worked previously and does work in the other direction, for the MAIN to connect to the NUC. It is the NUC that can no longer connect to the MAIN.

I would not mind but password sharing is disabled. I did try turning off the firewall for the Private Network, no joy.

It does note a security issue, not sure what had changed though to make that no longer work, in one direction.

Guys, I gotta tell you - you are more chaotic than a bunch of monkeys on crack.
This is supposed to be about one (or more) person asking for a solution, and another providing it. Maybe the first solution offered is not working, so someone else offers another. Repeat until it works.

Here I'm seeing people throwing half-remembered non-solutions around, irrelevant stuff (dude, no offense but you mentioned your wife's PC a hundred times. Nobody cares: this is about solutions, not personal problems), pointless complications ("try another PC", "if it's Linux I don't know" - let's please stick to the reality at hand), repetitions... Seriously, this has become impossible to follow.

So I'm flying my white flag here. Please stop "helping", unless anyone can state in a brief, complete and concise way how to make the Network Discovery toggle stay on. It's (probably) as simple as that.

Tracian said:

Guys, I gotta tell you - you are more chaotic than a bunch of monkeys on crack.
This is supposed to be about one (or more) person asking for a solution, and another providing it. Maybe the first solution offered is not working, so someone else offers another. Repeat until it works.

Here I'm seeing people throwing half-remembered non-solutions around, irrelevant stuff (dude, no offense but you mentioned your wife's PC a hundred times. Nobody cares: this is about solutions, not personal problems), pointless complications ("try another PC", "if it's Linux I don't know" - let's please stick to the reality at hand), repetitions... Seriously, this has become impossible to follow.

So I'm flying my white flag here. Please stop "helping", unless anyone can state in a brief, complete and concise way how to make the Network Discovery toggle stay on. It's (probably) as simple as that.

Click to expand...

Tracian. Criticizing people who are trying to help you is bad form. When working with tech part of the trouble shooting process involves establishing controls.
By establishing controls you can eke out the variables and work with each variable at a time until the issue is solved. If this has become "impossible to follow" as you say, then I advise you pack up your PC and take it to a technician. I would also advise brushing up on your reading skills and it wouldn't hurt to work on your comprehension while you're at it.

I mentioned my wife's PC on this thread what — twice? Why do you suppose I did that. A: Because she was doing something with her PC that evidently you were not. Her PC sees the entire home network and your PC is blind. Evidently you are the one with the "personal problem" here. I also mentioned something else about her PC that I think you haven't done. It isn't that nobody cares. It is more like you don't care to try taking the steps that just might fix your issue. Evidently this is not your only issue.

Stepping into a forum and mowing everyone down with an AK47 and waiving a white flag afterward will definitely get you less results. Frankly it is laughable. It would make for a great cartoon. You want short, simple, and concise? Try this:

I realize you're frustrated but sometimes there are no quick fixes. Sometimes you have to try different things until you find something that works. The people in this forum volunteer their time and energy because they care. So please don't say nobody cares. That said, I'm not nobody and now I no longer care.

6391mb said:

I'll throw my hat into the ring here and yes, each update with Win seems to introduce new problems especially on the network front but it doesn't affect the majority or so it would seem. My other PC's/Laptops could access the main PC but I had one that wouldn't - it had the dreaded 0x80070035

It was to do with the security. All the shares on the main PC were there including 'everyone'. On the main PC on the right of Disk Sharing within Properties is Security - click on Advanced and mine was showing Owner as System. I changed this to Everyone and hey presto the thing suddenly worked. Now not advisable to leave as Everyone but if you can then access the main PC you are narrowing down the options. Why the other satellite PC's/Laptops were finding the main PC I have no idea - but the one stubborn one well.......

All I was trying to do was isolate the 'problem'.

It may work for you and may not but good luck.

Click to expand...

Did you consider trying an owner with some authority such as Administrator first or was Everyone the first thing that you tried that worked?

Rollback_Jockey said:

Did you consider trying an owner with some authority such as Administrator first or was Everyone the first thing that you tried that worked?

Click to expand...

Yes I did but that didn't work. Everyone did so it was just a case of isolating. Weird but after deleting Administrator and Everyone I added back Administrator, rebooted and all was good.

6391mb said:

Yes I did but that didn't work. Everyone did so it was just a case of isolating. Weird but after deleting Administrator and Everyone I added back Administrator, rebooted and all was good.

Click to expand...

Good result there.



This morning I continued with what I was trying, to get the NUC in the loft to connect to the MAIC PC. I simply repeated what I had previously tried, then trying a Remote Connection. The RC worked, saves the credentials separately.
However, the connection to the MAIN then started to work with the previously made credentials that would fail....



The above shows the NUC, via Remote Desktop, being able to access the MAIN.

Whilst I am most pleased with that it seems somewhat of a hollow victory. I do not really know whey it is now working, nor why it failed previously after working.
So much was tried to resolve I am no longer sure of any one single thing that could have resolved it, or if it will continue to work.

I have created a restore point for both PC's, hoping they will not be needed. I have also deferred updates on both, might look at stopping feature updates for a couple of years and just allowing security ones.

Networking, for me anyway, is akin to alchemy.

Going back to coaxial cable and BNC type connectors, it did seem much easier then, lol...!

As noted. I have two machines on Home 24H2 26100.4946 and one legacy machine on Win 11 Lite 23H2.

The 26100.4946 MSU that I downloaded and installed did not contain the MS code that destroys Home networks that had no previous need of individual "credentials" for trusted network members. Upgrading to 26100.5074 found that nastiness for me. No suggested solutions worked to restore the network on 26100.5074 - not using gpedit.msc to enable "insecure logons", nor assigning "credentials" to each individual 24H2 machine. A lengthy internet search simply found these experiences repeated across the spectrum. [The Lite machine maintained normal two-way traffic with both 24H2 machines, as did my two Poco phones, no problems].

MS may eventually re-enable gpedit.msc's "insecure logons" function, but I doubt it.

I have no intention of re-installing the 26100.5074 version as a new OS and then going through the drudgery of recovering the full installations when 26100.4946 works perfectly as is. My gratitude to Macrium for reliable incremental full disc backups.

Given that, plus the fact I have no use for CoPilot (using Grok 2 is prefectly ok), updates are now paused for 20 years. (I won't last that long). Only security backups are to be considered. Seems a reasonable resolution.

ian50 said:

Given that, plus the fact I have no use for CoPilot (using Grok 2 is prefectly ok), updates are now paused for 20 years. (I won't last that long). Only security backups are to be considered. Seems a reasonable resolution.

Click to expand...

I totally relate.

I thought I'd post a reply here with my fix! (i'm super excited)

so it seems that when the computers are cloned, with the latest update, they can no longer talk to each other because the similar SID confuses windows. I found the fix on microsoft's forums:

in short, I had to run a SIDchg.exe program to change the SID id of one of my machines, and everything started working again!

priior said:

I thought I'd post a reply here with my fix! (i'm super excited)

so it seems that when the computers are cloned, with the latest update, they can no longer talk to each other because the similar SID confuses windows. I found the fix on microsoft's forums:

[24H2] Build 26100.5074 (KB5064081) – Release Preview Channel - Microsoft Q&A

I just had to uninstall KB5064081 from some production machines after spending some time trying to resolve a severe SMB / RDP issue. The update completely broke file sharing — no machine could access any other over the local network. My client reported…

learn.microsoft.com

in short, I had to run a SIDchg.exe program to change the SID id of one of my machines, and everything started working again!

Click to expand...

Yep that's why my network fell on it's face.