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

fg2001gf11F · Oct 16, 2024

Stigg said:
But my "File and Printer Sharing (Restrictive)" wasn't checked even before or after KB5044384. See before and after images above.

Hello Stigg,
I just checked a second machine updated to 26100.2152 and in this one the "File and Printer Sharing (Restrictive)" was not set at all.
I had to set it manually to get the network working.
The question is:
Why was it enabled on one machine and not the other after the same update?
That definitely is the main cause for the problem, I had to manually enable that setting to get it to work.

I added more comments on my FBH report about this difference.

I also checked with Canary Build 27723 and "File and Printer Sharing (Restrictive)" is already checked for both Private and Public.
Still Canary works fine even if I uncheck "File and Printer Sharing (Restrictive)".

This was initially introduced with Build 25992.

Announcing Windows 11 Insider Preview Build 25992 (Canary Channel)

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 25992 to the Canary Channel. REMINDER: As builds released to the Canary Channel are “hot off the presses,” we will offer limited documentati

blogs.windows.com

I also had to turn on this to get rid of the yellow message.

fg2001gf11F · Oct 16, 2024

RFS said:
Beginning to suspect there's been a Known Issue Rollback, as when the update is first installed, the 3 dots FE issue does not occur, but does a few hours later.

The 3 dots menu problem is happening also with Dev Build 26120 and Canary Build 27723, not just 26100.
Yet, I had one machine with 26120 that did not fail and could not figure out the difference.

cereberus · Oct 16, 2024

fg2001gf11F said:
The 3 dots menu problem is happening also with Dev Build 26120 and Canary Build 27723, not just 26100.
Yet, I had one machine with 26120 that did not fail and could not figure out the difference.

PurSpyk!! · Oct 16, 2024

RFS said:
Beginning to suspect there's been a Known Issue Rollback, as when the update is first installed, the 3 dots FE issue does not occur, but does a few hours later.

This is what I experienced. Never had the issue, then yesterday it started.

fg2001gf11F · Oct 16, 2024

@Stigg,

More on the 24H2 file sharing issue on this thread, but they don't say which specific build.

Redirecting

"Annoyingly the 24H2 update seems to have broken the network sharing, and finding advanced sharing settings to enable file transfer isn't easy.
It's been working until this morning, but now I'm unable even to see other devices from the "un-updated" machine."

What's new in Windows 11, version 24H2 for IT pros

Learn more about what's new in Windows 11 version 24H2, including servicing updates, Windows Subsystem for Linux, the latest CSPs, and more.

learn.microsoft.com

SMB firewall rule changes
The Windows Firewall default behavior has changed. Previously, creating an SMB share automatically configured the firewall to enable the rules in the File and Printer Sharing group for the given firewall profiles. Now, Windows automatically configures the new File and Printer Sharing (Restrictive) group, which no longer contains inbound NetBIOS ports 137-139.
This change enforces a higher degree of default of network security and brings SMB firewall rules closer to the Windows Server File Server role behavior, which only opens the minimum ports needed to connect and manage sharing. Administrators can still configure the File and Printer Sharing group if necessary as well as modify this new firewall group, these are just default behaviors.

For more information about this change, see https://aka.ms/SMBfirewall. For more information about SMB network security, see Secure SMB Traffic in Windows Server.

bobkn · Oct 16, 2024

24H2 appears to have broken monitor profiling. (Some call it "calibration.")

A repost (modified) from a less appropriate (?) forum.

See "My Computer" System 1.

Additional:

nVidia Studio drivers, 561.09 (latest as of 10/15/2024) Set to 10 bit color, and to use nVidia color settings.

X-Rite i1 Display Pro Plus colorimeter

The monitor is identified properly in Device Manager. Its color space is set to Rec. 2020. (There is no "native" setting, so I picked the widest option. The monitor can't really display the full Rec. 2020 space.)

In the past, I've been able to use DisplayCal or Calibrite's Profiler software. The ICC profile was as expected for a wide-gamut OLED monitor.

Now, both programs produce a profile that doesn't completely cover the sRGB color space. I've tried reverting to nVidia drivers from a time when I got proper profiles, but that made no difference.

I presume that there's something new in 26100 that has caused the software to be unable to sense the monitor's capabilities.

I reverted to 26100.1591, thinking I'd been able to do a correct profile with that. No go.

It appears that 24H2 is preventing the software from determining the gamut capability of the monitor.

Seems like it should be a common issue, but a web search found nothing yet.

I'm not hopeful of getting a response - too specialized. But just in case...

Stigg · Oct 17, 2024

fg2001gf11F said:
@Stigg,

More on the 24H2 file sharing issue on this thread, but they don't say which specific build.

Redirecting

"Annoyingly the 24H2 update seems to have broken the network sharing, and finding advanced sharing settings to enable file transfer isn't easy.
It's been working until this morning, but now I'm unable even to see other devices from the "un-updated" machine."

What's new in Windows 11, version 24H2 for IT pros

Learn more about what's new in Windows 11 version 24H2, including servicing updates, Windows Subsystem for Linux, the latest CSPs, and more.

learn.microsoft.com

SMB firewall rule changes
The Windows Firewall default behavior has changed. Previously, creating an SMB share automatically configured the firewall to enable the rules in the File and Printer Sharing group for the given firewall profiles. Now, Windows automatically configures the new File and Printer Sharing (Restrictive) group, which no longer contains inbound NetBIOS ports 137-139.
This change enforces a higher degree of default of network security and brings SMB firewall rules closer to the Windows Server File Server role behavior, which only opens the minimum ports needed to connect and manage sharing. Administrators can still configure the File and Printer Sharing group if necessary as well as modify this new firewall group, these are just default behaviors.

For more information about this change, see https://aka.ms/SMBfirewall. For more information about SMB network security, see Secure SMB Traffic in Windows Server.

KB5044384 is a mess. I guess that's why we're Insiders.

HRPuffnstuff · Oct 17, 2024

When I ran sfc /scannow after installing this update nothing was found but now that a few days have passed I'm seeing corrupt files when I scan.

johnlgalt · Oct 17, 2024

Not sure if I would consider my self lucky or not, but this update has been trying (and failing miserably, I might add) to install itself for the better part of a week now.

bobkn said:
24H2 appears to have broken monitor profiling. (Some call it "calibration.")

I surely hope not, but if it does, I wonder if the fact that my monitors are already calibrated using software may be causing the installation issue in the first place.

I'm not about to give up my monitor calibrations, though lol. Not even to test the theory....

Zardoc · Oct 17, 2024

johnlgalt said:
Not sure if I would consider my self lucky or not, but this update has been trying (and failing miserably, I might add) to install itself for the better part of a week now.

I surely hope not, but if it does, I wonder if the fact that my monitors are already calibrated using software may be causing the installation issue in the first place.

I'm not about to give up my monitor calibrations, though lol. Not even to test the theory....

Out of context, John, what software do you use ? Thanks

bobkn · Oct 17, 2024

johnlgalt said:
Not sure if I would consider my self lucky or not, but this update has been trying (and failing miserably, I might add) to install itself for the better part of a week now.

I surely hope not, but if it does, I wonder if the fact that my monitors are already calibrated using software may be causing the installation issue in the first place.

I'm not about to give up my monitor calibrations, though lol. Not even to test the theory....

It's commonly recommended that the monitor be profiled very month or so for critical work. (Not that I do any critical work.) That's based on the expectation that the color correction will drift, slowly.

For the short term, I've gone back to the ICC profile provided by the monitor maker. (It's full gamut.)

johnlgalt · Oct 17, 2024

Yeah, I don't do critical work, but I *do* like my monitor to actually work as intended lol. I manually calibrate it using various software, and once calibrated it with my old X1 and an older version of Calibrite.

With my monitors being an off-brand, I have no native ICC profile, so I have to use the software to make one. I use this one from Microsoft:

Windows HDR Calibration - Free download and install on Windows | Microsoft Store

This app lets you calibrate your HDR display to optimize it for HDR games (including Auto HDR) and other HDR content on your Windows 11 PC. Go through a series of steps to set the minimum and maximum brightness levels, as well as color saturation level, to create a new color profile that's made...

apps.microsoft.com

bobkn · Oct 17, 2024

johnlgalt said:
Yeah, I don't do critical work, but I *do* like my monitor to actually work as intended lol. I manually calibrate it using various software, and once calibrated it with my old X1 and an older version of Calibrite.

With my monitors being an off-brand, I have no native ICC profile, so I have to use the software to make one. I use this one from Microsoft:

Windows HDR Calibration - Free download and install on Windows | Microsoft Store

This app lets you calibrate your HDR display to optimize it for HDR games (including Auto HDR) and other HDR content on your Windows 11 PC. Go through a series of steps to set the minimum and maximum brightness levels, as well as color saturation level, to create a new color profile that's made...

apps.microsoft.com

I've used that tool. It isn't for photo work. The HDR movie examples I've viewed in HDR tend to look like what AV fans refer to as "torch mode", which is the way HDR TVs tend to be set up at retailers to wow potential customers. I haven't seen what it does with a UHD HDR movie, although I have hardware and software that would enable me to view such movies on the PC. (Something the movie industry apparently has tried to prevent.)

bobkn · Oct 17, 2024

bobkn said:
It's commonly recommended that the monitor be profiled very month or so for critical work. (Not that I do any critical work.) That's based on the expectation that the color correction will drift, slowly.

For the short term, I've gone back to the ICC profile provided by the monitor maker. (It's full gamut.)

To reply to myself, I just went on live chat with MS support.

They claimed the bug is known to MS, and is being worked on. A fix is supposed to appear in a future (Windows) update.

I wish that I was completely certain that I wasn't being jollied along. Time will tell.

fg2001gf11F · Oct 17, 2024

HRPuffnstuff said:
When I ran sfc /scannow after installing this update nothing was found but now that a few days have passed I'm seeing corrupt files when I scan.

Did you check the CBS log to see which files were found?
It still ran clean here.

fg2001gf11F · Oct 19, 2024

Here is another discrepancy mess on one machine updated from 22631.4317 to 26100.2152.
One place showing set for "Private network" and the other place showing "Public networks" as "Current profile".

After the update the home network was not working, and I also noticed these contradictions:
At first the options for the network profile were missing on the Ethernet properties.
Then eventually they showed up, but they don't make much sense.
The Current profile shows "Public networks" while the Properties and the Setting show "Private network"
None of these discrepancies on this machine were showing before this upgrade.
Yet, 2 other machines at the same Build level do not show this problem.
Many users are reporting problems with the network after upgrading to 24H2.
This looks like a bug too.

Bree · Oct 19, 2024

fg2001gf11F said:
After the update the home network was not working, and I also noticed these contradictions:
At first the options for the network profile were missing on the Ethernet properties.
Then eventually they showed up, but they don't make much sense.
The Current profile shows "Public networks" while the Properties and the Setting show "Private network"

Odd, my System One's RTM 23H2 got 24H2 through Windows Update. It has no such discrepancies....

fg2001gf11F said:
Many users are reporting problems with the network after upgrading to 24H2.

Most of those are likely to be using local accounts with no password and hitting 24H2's tighter restrictions on insecure log in. That's by design, not a bug. It can be turned off though (as I had to).

Clean install of 24H2 causes unexpected changes - post #2

fg2001gf11F · Oct 19, 2024

Bree said:
Odd, my System One's RTM 23H2 got 24H2 through Windows Update. It has no such discrepancies....

Most of those are likely to be using local accounts with no password and hitting 24H2's tighter restrictions on insecure log in. That's by design, not a bug. It can be turned off though (as I had to).

Clean install of 24H2 causes unexpected changes - post #2

@Bree,
In my case the one that got the update from W.U. failed with 0xC1900101 with no subcode and rolled back.

Had to use the MS ISO to upgrade without that error.
I updated 3 machines from 23H2 to 24H2, only one has that discrepancy described earlier.
I wasted too many hours to try to figure out the difference, but I cannot find any valid explanation.

I just worked around the problem for now. There are many users reporting bugs with the network after upgrading to 24H2.
I hope MS cleans up the mess with one of next updates.

Bree · Oct 19, 2024

fg2001gf11F said:
There are many users reporting bugs with the network after upgrading to 24H2.
I hope MS cleans up the mess with one of next updates.

As I said, no 24H2 networking bug here - just the higher security requirements that by default won't allow insecure logins (but can be turned off).

fg2001gf11F · Oct 19, 2024

Bree said:
As I said, no 24H2 networking bug here - just the higher security requirements that by default won't allow insecure logins (but can be turned off).

I also said that 2 of my machines did not have any issue after the same upgrade.
Usual MS inconsistent results.

B.T.W.
I have not seen any issue with logins. All machines use local accounts, but with password and PIN.
Same settings on all, why the different behavior?

Many of the problems reported on the network with 24H2 have different symptoms, nothing to do with login.

Edit:
I found an old thread from 2022 about one of the problems, and it worked in my case too.

Redirecting

netsh winsock reset
netsh int ip reset
netsh advfirewall reset
ipconfig /flushdns

Restart the computer at the end of all commands.

After executing the commands above and rebooting, everything was back to normal and showing the profile type on the Ethernet which was missing completely right after the update.

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

Gradual rollout​

Normal rollout​

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Antidisestablishmentarianist

My Computers

Dazed & Confused

My Computer

Well-known member

My Computers

Antidisestablishmentarianist

My Computers

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

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

Similar threads

Gradual rollout

Normal rollout