Yes, I opted out a long time ago, but on this one PC it kept pushing me to use 24h2. In fact, it was the only update option.
disable the firewall on mint now that you have run the first command and see if it is accessible
It's already disabled; I never enable it.
That security policy sets the same registry entry I gave in post #34. I had to find out the correct registry entry for that policy because I was working on 24H2 Home.SOLUTION Found.
I was searching for solutions on accessing my W11 23H2 Server from my W11 24h2 PC and found this suggestion from "GotNoRice" from a while back. I didn't try it then since I had reverted to 23H2, now that I'm back on 24H2 and still having the same issue I thought I would try it.
IT WORKS
View attachment 110004
Windows 11 cannot access other computers, but can be accessed by the other computers - post #34Bree said:
Sorry if I missed your earlier solution - I'm just happy this worked for me!
Yes, that 'Enable insecure guest logins' policy is the correct one to use. My registry edit is identical to applying the policy. I was just surprised that I had to do it in 24H2 Home too (the hard way, in Regedit). MS have said previously that this restriction was only for Pro and above.
SOLUTION Found.
I was searching for solutions on accessing my W11 23H2 Server from my W11 24h2 PC and found this suggestion from "GotNoRice" from a while back. I didn't try it then since I had reverted to 23H2, now that I'm back on 24H2 and still having the same issue I thought I would try it.
IT WORKS
View attachment 110004
This worked for me, after struggling with a reformatted windows 11 PC for 2 days. I tried everything under the sun but still couldn't access a shared folder on a Windows 10 machine. I added a new user account to the win10 machine with same username/PW as the win11 user and suddenly everything is good.
