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

gadgetboyj · Sep 15, 2025

barreleye said:
Can anyone explain how to use sysprep to fix a system that's a copy of one that's been in use for years?

As for newsid, Sysinternals stopped supporting it back in 2021, and their web site says Microsoft has disavowed it.

NewSID - Sysinternals

Learn about the computer SID problem everybody has been talking about and get a free computer SID changer, NewSID.

learn.microsoft.com

As for the suggested alternative, sidchg, go to their web site and look at the numerous things it changes and the conditions it imposes to make those changes, including disabling Bitlocker and decrypting drives before using it. It's a non-starter for me.

SIDCHG SID Change Utility

I had a PC made from spare parts that I thought would be nice to configure as a ready-to-go backup PC after I built my new one, but dealing with either of those programs is beyond what I'm comfortable doing. I'll just restore an image of my main PC to it if the time should ever come, that is, unless someone can instruct me on how to use sysprep, because it seemed to me it's for use on fresh installs.

ETA: I see I've posted to a different thread on this subject than the one last week. Off to review what's been said here. :)

ETA2: OK, having reviewed the thread, I have nothing to add or change to my post.

If you want to go the sysprep route, the only command you need is sysprep /generalize but it also won't run unless you have BitLocker disabled, there is a technical reason that it must be shut off. Whatever method you use, you can immediately turn BitLocker back on after the fix.

Birk · Sep 15, 2025

I tried NEWSID on my Win11 Pro system and it seemed to go into a CPU loop (80 - 95% CPU usage) with no IO or Network activity. So I cancelled it after about 5 min.

BIG mistake. When my system rebooted it started going through all the initial Microsoft customization lunacy. I got through all that pretty quickly, and it was obvious all user settings I had set up long ago were gone. So rather than take the time to tweak everything back the way I am used to I did a Macrium restore from a fairly recent backup.

Needless to say I still can't connect to wife's Win10 PC on the same network, but i don't think I'll try this approach again. Hopefully MS will come out with a legit fix sometime soon.

gunrunnerjohn · Sep 15, 2025

Well, you can run the free trial of SIDCHG to do the job, and it's a currently supported utility.

Birk · Sep 15, 2025

gunrunnerjohn said:
gunrunnerjohn said:

you can run the free trial of SIDCHG

Click to expand...

I looked at that one, and frankly it looks even more dangerous than NEWSID. Does SIDCHG revert all my user settings to original MS default? I couldn't find any info about that.

Click to expand...

hetropin · Sep 15, 2025

Are you using SMB v1? Microsoft has announced that there are issues with SMB v1. Did the workaround below resolve the problem? Microsoft says: "You can work around this issue by allowing network traffic on TCP port 445."

Topic: September 2025 updates are out @ AskWoody

Rollback_Jockey · Sep 16, 2025

gunrunnerjohn said:
Well, you can run the free trial of SIDCHG to do the job, and it's a currently supported utility.

That's what i used to cure my SID issue.

HTA · Sep 16, 2025

Rollback_Jockey said:
That's what i used to cure my SID issue.

I used SIDCHG SID Change Utility too and the only thing I had to re-activate was Office.

Rollback_Jockey · Sep 16, 2025

HTA said:
I used SIDCHG SID Change Utility too and the only thing I had to re-activate was Office.

The only downside for me was having to select my Outlook Profile manually ONCE ,so no stress at all for me.

Birk · Sep 17, 2025

OK - I ran SIDCHG64 and rebooted. Everything came back ok - so that's the good news.

The bad news is I still can't connect to wife's PC - I get the same "Windows cannot access..." message as before. The odd thing is her PC (Win10) can see my PC (Win10 Pro) just fine, and can R/W files on my PC OK. Both systems have the same settings of Advanced Sharing. So I'm thinking it must be something else.

Perhaps a compatibility problem between Win10 and Win10 Pro?

gunrunnerjohn · Sep 17, 2025

Birk said:
OK - I ran SIDCHG64 and rebooted. Everything came back ok - so that's the good news.

The bad news is I still can't connect to wife's PC - I get the same "Windows cannot access..." message as before. The odd thing is her PC (Win10) can see my PC (Win10 Pro) just fine, and can R/W files on my PC OK. Both systems have the same settings of Advanced Sharing. So I'm thinking it must be something else.

Perhaps a compatibility problem between Win10 and Win10 Pro?

Since these are both Win10 machines, perhaps it's not a Win11 issue?

Birk · Sep 17, 2025

Darn! I must really be getting old. I typed Win10 and didn't even notice I meant Win11. Sorry about that.

What's interesting is that wife's PC sees mine ok.

gunrunnerjohn · Sep 17, 2025

Birk said:
Darn! I must really be getting old. I typed Win10 and didn't even notice I meant Win11. Sorry about that.

What's interesting is that wife's PC sees mine ok.

Actually, that's exactly what I had when I had both versions active here. Here's a list of fixes that are typically needed once you go to 24H2 or later.

In Control Panel\All Control Panel Items\Programs and Features\Turn Windows Features on or off.
Check if there are No Ticks are on SMB 1.0/CIFS Client and SMB 1.0/CIFS Server Only a tick on SMB Direct

Make Sure you are on a Private Network NOT Public

Next go into Group Policy (Pro Version Only) gpedit.msc

Computer Configuration, Windows Settings, Security 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.

Reboot

Birk · Sep 17, 2025

Here's a list of fixes that are typically needed once you go to 24H2 or later.

Those fixes worked. Many thanks. But good grief, to quote Ralph Cramden: What a revolting development this is.

All this leads to these questions:

1. Why does an end user have to go to those lengths to fix a problem that should not exist?
2. How could MS allow such a problem to get into the public domain?
3. Where did that set of obscure fixes come from, and how did you discover them?
4. What should we expect in the future?
5. Are all the previous postings about SID changes relevant to this issue?

gunrunnerjohn · Sep 17, 2025

Birk said:
Those fixes worked. Many thanks. But good grief, to quote Ralph Cramden: What a revolting development this is.

All this leads to these questions:

1. Why does an end user have to go to those lengths to fix a problem that should not exist?
2. How could MS allow such a problem to get into the public domain?
3. Where did that set of obscure fixes come from, and how did you discover them?
4. What should we expect in the future?
5. Are all the previous postings about SID changes relevant to this issue?

Well, I can't answer #1, #2, or #4, those are questions for Microsoft.

#3, the "obscure fixes" were from discussions right here, I collected them in a little text file after using the fixes to get my Win10 and Win11 systems talking.

#5, the SID changes don't have anything to do with this issue. I can't say in a large corporate network if the SID enters into the picture, but a simple peer home network has no issues with SID duplication.

pseymour · Sep 17, 2025

gunrunnerjohn said:
#5, the SID changes don't have anything to do with this issue. I can't say in a large corporate network if the SID enters into the picture, but a simple peer home network has no issues with SID duplication

It doesn’t, because IT folks [should] know to run sysprep. There are things that sysprep’s generalizing process “resets” that have nothing to do with the SID, and that if they aren’t generalized, will present issues. An old example is the unique IDs a machine gets when connecting to WSUS. If you don’t clear those properly before cloning, all of your machines appear the same in WSUS. I don’t know too many people using WSUS anymore, so that’s an old example as I said.

Actually, now that I think about it, I can’t recall one IT dept I know of that still clones. I’m sure they’re out there, but it seems to have gone away in my circle anyway.

Rollback_Jockey · Sep 18, 2025

gunrunnerjohn said:
#5, the SID changes don't have anything to do with this issue. I can't say in a large corporate network if the SID enters into the picture, but a simple peer home network has no issues with SID duplication.

This SID issue flopped all my machines on their faces, all 3 were clones without any previous sysprep on the source.

gunrunnerjohn · Sep 18, 2025

pseymour said:
It doesn’t, because IT folks [should] know to run sysprep. There are things that sysprep’s generalizing process “resets” that have nothing to do with the SID, and that if they aren’t generalized, will present issues. An old example is the unique IDs a machine gets when connecting to WSUS. If you don’t clear those properly before cloning, all of your machines appear the same in WSUS. I don’t know too many people using WSUS anymore, so that’s an old example as I said.

Actually, now that I think about it, I can’t recall one IT dept I know of that still clones. I’m sure they’re out there, but it seems to have gone away in my circle anyway.

I don't think WSUS is all that common as you say. Also, for the peer environment, it's doubtful anyone goes to the trouble to set that up.

pseymour · Sep 18, 2025

gunrunnerjohn said:
I don't think WSUS is all that common as you say. Also, for the peer environment, it's doubtful anyone goes to the trouble to set that up.

Okay? But you said large corporate environment. It was also just one example.

gunrunnerjohn · Sep 18, 2025

pseymour said:
Okay? But you said large corporate environment.

Well, it's certainly going to be a significantly sized environment to put in the effort to maintain the WSUS server. Also, when evaluating a query here, I look at the OP and his environment.

pseymour · Sep 18, 2025

gunrunnerjohn said:
Well, it's certainly going to be a significantly sized environment to put in the effort to maintain the WSUS server. Also, when evaluating a query here, I look at the OP and his environment.

Okay man. I was just responding to the part of your post I quoted, having experience in current large environments. Sorry if you don’t understand that.

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

New member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

New member

My Computer

Well-known member

My Computers

Active 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

Well-known member

My Computer

Well-known member

My Computers

putting the mental back in experimental

My Computer

Well-known member

My Computers

Well-known member

My Computers

putting the mental back in experimental

My Computer

Well-known member

My Computers

putting the mental back in experimental

My Computer

Similar threads