Solved Updated 24H2 to 26100.5074 Now Can't Connect to Other Computer

I am running build 26100.4946 Windows 11 Pro on both my main PC and the NUC media server. They have needed the correct Windows credentials being available within the Manager, as noted.
This was not needed on the media server when using the N54L, but that was running Windows 10 Pro.

glasskuter said:

I say again, Each computer should have a credential for each of the other computers

Click to expand...

I deleted and re-created the credentials on ALL my machines, it made zero difference.

As a test i switched from PIN login to Password, all local accounts.

My PC's all have static IP's from my router (also rebooted as a test), i also have HOSTS file resembling the static IP in each machine.

All machines shared folders have read permissions set for "Everyone" and also full permissions for myself.

I have Computer Browser service disabled on all but the main computer so this is the Master Browser. All relevant other services confirmed as active.

Hello everyone !

Exactly the same as everyone here : after updating ALL my PC's to 26100.5074 : "some" of my network shares are destroyed.
I'm on a home private network (wi-fi and ethernet are bridged, speed at 10Gbs, excellent Netgear managed switches) using 8 PC's, all on Windows 24H2 26100.5074, all using the same Microsoft account with the same pw. Three PC's, out of eight, are no longer reachable -"among themselves"-, they are encountering credential prompts. The error message points to "non identified username or pw" even when the correct credentials are entered (see my file credentials.jpg, in French but very easy to understand/translate).
These three PC's have "some" common points :
- identical motherboard Asus Rog Strix X570 gaming-E, last beta bios 5041 (back to bios 5031 does not solve the problem !!) ;
- all with AMD processors : either Ryzen 9 3900X, 9 5950X or 7 5800X.
I'm expecting Microsoft to quickly solve this VERY annoying problem.
I tried ALL the "classical" network help proposed solutions : full reinitiation of the network, gpedit modifications, all windows credentials deletion, using the Administrator account with the same pw, opening the windows sessions using the Microsoft account common pw, not the PIN....... NOTHING works !!!
After resoration back to a previous 24H2 26100.4770 version, which fortunately was recorded on backup images, NO LONGER ANY PROBLEM OF NETWORK SHARE for all these PC's connections.
Thanks for any new clever help !!

ylemoine said:

Hello everyone !

Exactly the same as everyone here : after updating ALL my PC's to 26100.5074 : "some" of my network shares are destroyed.
I'm on a home private network (wi-fi and ethernet are bridged, speed at 10Gbs, excellent Netgear managed switches) using 8 PC's, all on Windows 24H2 26100.5074, all using the same Microsoft account with the same pw. Three PC's, out of eight, are no longer reachable -"among themselves"-, they are encountering credential prompts. The error message points to "non identified username or pw" even when the correct credentials are entered (see my file credentials.jpg, in French but very easy to understand/translate).
These three PC's have "some" common points :
- identical motherboard Asus Rog Strix X570 gaming-E, last beta bios 5041 (back to bios 5031 does not solve the problem !!) ;
- all with AMD processors : either Ryzen 9 3900X, 9 5950X or 7 5800X.
I'm expecting Microsoft to quickly solve this VERY annoying problem.
I tried ALL the "classical" network help proposed solutions : full reinitiation of the network, gpedit modifications, all windows credentials deletion, using the Administrator account with the same pw, opening the windows sessions using the Microsoft account common pw, not the PIN....... NOTHING works !!!
After resoration back to a previous 24H2 26100.4770 version, which fortunately was recorded on backup images, NO LONGER ANY PROBLEM OF NETWORK SHARE for all these PC's connections.
Thanks for any new clever help !!

Click to expand...

The affected machines here are Dell with Intel processors so it doesn't look like AMD factors into it. Hopefully Microsoft will fix this very soon.

ylemoine said:

Hello everyone !

Exactly the same as everyone here : after updating ALL my PC's to 26100.5074 : "some" of my network shares are destroyed.
I'm on a home private network (wi-fi and ethernet are bridged, speed at 10Gbs, excellent Netgear managed switches) using 8 PC's, all on Windows 24H2 26100.5074, all using the same Microsoft account with the same pw. Three PC's, out of eight, are no longer reachable -"among themselves"-, they are encountering credential prompts. The error message points to "non identified username or pw" even when the correct credentials are entered (see my file credentials.jpg, in French but very easy to understand/translate).
These three PC's have "some" common points :
- identical motherboard Asus Rog Strix X570 gaming-E, last beta bios 5041 (back to bios 5031 does not solve the problem !!) ;
- all with AMD processors : either Ryzen 9 3900X, 9 5950X or 7 5800X.
I'm expecting Microsoft to quickly solve this VERY annoying problem.
I tried ALL the "classical" network help proposed solutions : full reinitiation of the network, gpedit modifications, all windows credentials deletion, using the Administrator account with the same pw, opening the windows sessions using the Microsoft account common pw, not the PIN....... NOTHING works !!!
After resoration back to a previous 24H2 26100.4770 version, which fortunately was recorded on backup images, NO LONGER ANY PROBLEM OF NETWORK SHARE for all these PC's connections.
Thanks for any new clever help !!

Click to expand...

I can't help you beyond what I and others have written in similar threads. But, have you considered now backing up your Windows 11 images and also use a utility to restrict MS updates..?
I am using one that will prevent for two years any feature updates, but still allow security ones. That can be reverted at any point, but MS feature updates can seem to break more things at times than resolve.

Been highly annoyed by the last two Windows updates, adding my two cents here.
I have 5 machines at home, all of which follow the same issues listed below.
Their a mixture of Intel and AMD systems, latest firmware, latest Secure boot keys.

WHAT WORKS:
Computer A (build 26100.6584) > Computer B (build 26100.4946)
Computer B (build 26100.4946) > Computer A (build 26100.6584)

So as long as one machine doesn't have the latest updates from today
or last patches a few weeks ago, it works.

WHAT FAILS:
Computer A (build 26100.6584) > Computer B (build 26100.6584)
Computer B (build 26100.6584) > Computer A (build 26100.6584)

If both machines are on the latest updates as of today or from
a week or two ago, doesn't work.

Both computers have a local account with the same profile name
and password. When trying to open a network share, opens without
any issues.

After update (KB5065426) (26100.6584), when trying to access network share.
Prompted to enter username and password. Entering in the good username and password
just recycles the prompt and isn't accepted.

Setting security to low in the GPOs doesn't fix anything either.
____________________

In the event viewer you can see failures on both machines with the latest patches giving
a generic login failure

An account failed to log on.

Subject:
Security ID: NULL SID
Account Name: -
Account Domain: -
Logon ID: 0x0

Logon Type: 3

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: GenXI
Account Domain: GENXIROG

Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xC000006D
Sub Status: 0x0

Process Information:
Caller Process ID: 0x0
Caller Process Name: -

Network Information:
Workstation Name: GENXIROG
Source Network Address: 192.168.50.7
Source Port: 35055

Detailed Authentication Information:
Logon Process: NtLmSsp
Authentication Package: NTLM
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

I was hoping this would be fixed today but it wasn't. Maybe next time...

I confirmed that after 26100.6584 today update, the network connection total deficiency between "some (-microsoft lock mystery)" Windows 24H2 PC's is indeed not yet solved !!
Still expecting a quick Microsoft solution, after all their worldwide advertised updates/release previews..... a small fix would be welcome.
Computers networks are sometimes crucial for some people/compagnies......not to be forgotten, please.

Can this issue be fixed just by uninstalling KB5065426 and KB5064081, or do I need to perform a System Restore?

ylemoine said:

Hello everyone !

Exactly the same as everyone here : after updating ALL my PC's to 26100.5074 : "some" of my network shares are destroyed.
I'm on a home private network (wi-fi and ethernet are bridged, speed at 10Gbs, excellent Netgear managed switches) using 8 PC's, all on Windows 24H2 26100.5074, all using the same Microsoft account with the same pw. Three PC's, out of eight, are no longer reachable -"among themselves"-, they are encountering credential prompts. The error message points to "non identified username or pw" even when the correct credentials are entered (see my file credentials.jpg, in French but very easy to understand/translate).
These three PC's have "some" common points :
- identical motherboard Asus Rog Strix X570 gaming-E, last beta bios 5041 (back to bios 5031 does not solve the problem !!) ;
- all with AMD processors : either Ryzen 9 3900X, 9 5950X or 7 5800X.
I'm expecting Microsoft to quickly solve this VERY annoying problem.
I tried ALL the "classical" network help proposed solutions : full reinitiation of the network, gpedit modifications, all windows credentials deletion, using the Administrator account with the same pw, opening the windows sessions using the Microsoft account common pw, not the PIN....... NOTHING works !!!
After resoration back to a previous 24H2 26100.4770 version, which fortunately was recorded on backup images, NO LONGER ANY PROBLEM OF NETWORK SHARE for all these PC's connections.
Thanks for any new clever help !!

Click to expand...

Do you mean it was fixed by "System Restore"?

hetropin said:

Do you mean it was fixed by "System Restore"?

Click to expand...

I read this...

After resoration back to a previous 24H2 26100.4770 version, which fortunately was recorded on backup images, NO LONGER ANY PROBLEM OF NETWORK SHARE for all these PC's connections.

Click to expand...

....as meaning they used something like Macrium Reflect Backup to previously create an image and then restore that as the Operating System.
There are plenty of YT tutorials etc if you are not familiar with that type of utility.

Vimes said:

I read this...




....as meaning they used something like Macrium Reflect Backup to previously create an image and then restore that as the Operating System.
There are plenty of YT tutorials etc if you are not familiar with that type of utility.

Click to expand...

omg............Thank you..........>_<

Does this mean that once KB5065426 or KB5064081 is installed even once, it cannot be fixed by uninstalling or using System Restore?

hetropin said:

omg............Thank you..........>_<

Does this mean that once KB5065426 or KB5064081 is installed even once, it cannot be fixed by uninstalling or using System Restore?

Click to expand...

I really do not know how successful or not it would be by doing that in this instance.
There is also a restore option, if available, that you refer to........ I have used that one with success with a different update.

When you do get to the point of resolving your issues you might then consider the use of something like Macrium.
Perhaps even start using that now, before making any changes, in my experience things do not always improve....!
At least make a restore point and label it meaningfully.

But...... Still have a concern regarding Windows updates and what you might need to do about them, in case this simply occurs again for you, without resolve.

for now I have deferred Windows updates.

Good luck.

Checking in, after the update which decided to install itself and just prompt me to reboot, even though I have the option unchecked for get latest updates as soon as available (just seems to get ignored). I have no issue logging in to Windows (local account) but I do have issues connecting to an SMB share on another machine.

I've tried the registry fixes already, no dice.
Went through the usual diagnostics too, unshare/reshare, change password on the share PC etc.

Ironically, I can connect to the SMB share on my Fedora machine with no issues whatsoever!
Looks like I'm going to have to revert back to a reflect image and hide/block yet another update!

Can anyone advise why these updates keep getting forced through to my machines?

BolteWasTaken said:

Checking in, after the update which decided to install itself and just prompt me to reboot, even though I have the option unchecked for get latest updates as soon as available (just seems to get ignored). I have no issue logging in to Windows (local account) but I do have issues connecting to an SMB share on another machine.

I've tried the registry fixes already, no dice.
Went through the usual diagnostics too, unshare/reshare, change password on the share PC etc.

Ironically, I can connect to the SMB share on my Fedora machine with no issues whatsoever!
Looks like I'm going to have to revert back to a reflect image and hide/block yet another update!

Can anyone advise why these updates keep getting forced through to my machines?

Click to expand...

That's what's happening here too. Two of the machines won't talk to each other but both can talk to a third one, and the third one can talk to them all. All on the same build.

HTA said:

That's what's happening here too. Two of the machines won't talk to each other but both can talk to a third one, and the third one can talk to them all. All on the same build.

Click to expand...

Luckily enough I have Rustdesk running on that machine, it's connected to a very noisy samsung book duo, so it's in another room away from my main setup. I just find it really ironic that Fedora Linux is happily allowing me to connect to it's SMB from this Windows install, but I can't connect to an SMB on another Windows machine.

When they screw up, they do it good!

Hello to all following this thread. I believe I have the fix for those experiencing this issue since installing the 26100.5074 (KB5064081) preview build or 26100.6584 (KB5065426) that was released to the public yesterday. This also affects RDP Remote Desktop. (Trying to list as many related terms as possible for SEO).

Take a look in your System Event Log on the target machine and see if you see the following error when you try to connect remotely:

If you're getting the above, download PsGetSid, included with PsTools and check the SID on all affected machines. They should all be different, but if any of them match each other, that is what's causing this issue to occur. This update seems to change the way auth hashes are mapped, and instead of using hostnames, it is now using the SID.

The SID can be changed using a utility called SIDCHG, which is not technically free, but they do allow for a 30-day evaluation using a trial key on that page that they appear to update monthly. It does it fairly nondestructively, moreso than sysprep, but it will wipe any credentials stored in your vault, and could affect some licensed software and the like, it may need to be reactivated (i.e. Adobe products).

sysprep /generalize will also accomplish an SID change, but will wipe a lot more (drivers, computer name, any encrypted files, some settings, and like above will also wipe vault credentials and can affect software activation etc.

For this reason, if you're having this issue across only 2 machines, you could always just change 1 instead of both, and choose to do it on the one that has less potential things to have to set back up (although depending on how you ended up with duplicate SIDs in the first place, not changing all affected PCs could lead to this happening again in the future if another new PC is introduced with that same SID).

In my case, the issue was occurring across 4 identical PCs that came from the same OEM at the same time. Not sure what they did in their imaging process to cause it, but all 4 did have identical SIDs. Properly sysprepped images should not have this happen, but this could definitely result from things like drive clones and restoring a different PC from anothers' full-drive backup.

gadgetboyj said:

Hello to all following this thread. I believe I have the fix for those experiencing this issue since installing the 26100.5074 (KB5064081) preview build or 26100.6584 (KB5065426) that was released to the public yesterday. This also affects RDP Remote Desktop. (Trying to list as many related terms as possible for SEO).

Take a look in your System Event Log on the target machine and see if you see the following error when you try to connect remotely:

Code:

LSA(LsaSrv) Event ID 6167 "There is a partial mismatch in the machine ID. This indicates that the ticket has either been manipulated or it belongs to a different boot session. Failing authentication."

Click to expand...

I think you just hit the nail on the head, all my systems are clones!

gadgetboyj said:

Hello to all following this thread. I believe I have the fix for those experiencing this issue since installing the 26100.5074 (KB5064081) preview build or 26100.6584 (KB5065426) that was released to the public yesterday. This also affects RDP Remote Desktop. (Trying to list as many related terms as possible for SEO).

Take a look in your System Event Log on the target machine and see if you see the following error when you try to connect remotely:

Code:

LSA(LsaSrv) Event ID 6167 "There is a partial mismatch in the machine ID. This indicates that the ticket has either been manipulated or it belongs to a different boot session. Failing authentication."

Click to expand...

I've spent hours researching the fix for this issue on my systems and this IS the cure for me. Many thanks.

Is this issue related to Microsoft disabling DES? Microsoft made the following specification changes.