I just updated my first bios, actually two computer updates

[New Wrycuda]

Turns out most of you update your bios almost weekly, it's just standard practice. Different ways to live a computer life right?

A little exaggeration for clarity, maybe?

- Like a certain Presidential candidate?

I do Windows update weekly, usually on a friday when updates are available; sometimes BIOS updates are included.

I’ve found that, on checking for updates, minor updates are often ready to download despite the message that…

“You’re up to date”

 

[BobKnDP]

Turns out most of you update your bios almost weekly, it's just standard practice. Different ways to live a computer life right?

A little exaggeration for clarity, maybe?

- Like a certain Presidential candidate?

I do Windows update weekly, usually on a friday when updates are available; sometimes BIOS updates are included.

I’ve found that, on checking for updates, minor updates are often ready to download despite the message that…

“You’re up to date”

I tend to do updates when they're offered.

I rarely regret that.

Except now. Win 11 24H2 has somewhat messed up monitor profiling (with Calibrite Profiler or Displaycal/Argyll CMS). The monitor's gamut isn't detected; it defaults to sRGB. (Could be worse, but I paid for an OLED, dammit.) No date for a fix has been promised.

 

[BillyBobSenna]

I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.

 

[vett93]

Turns out most of you update your bios almost weekly, it's just standard practice. Different ways to live a computer life right?

A little exaggeration for clarity, maybe?

- Like a certain Presidential candidate?

I do Windows update weekly, usually on a friday when updates are available; sometimes BIOS updates are included.

I’ve found that, on checking for updates, minor updates are often ready to download despite the message that…

“You’re up to date”

I tend to do updates when they're offered.

I rarely regret that.

Except now. Win 11 24H2 has somewhat messed up monitor profiling (with Calibrite Profiler or Displaycal/Argyll CMS). The monitor's gamut isn't detected; it defaults to sRGB. (Could be worse, but I paid for an OLED, dammit.) No date for a fix has been promised.

Did Win 11 24H2 come up automatically in the update? Or you forced the update? It did not show up in any of my 4 PCs.

 

[vett93]

I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.

Do you find substantial improvements from these BIOS updates?

 

[BobKnDP]

Turns out most of you update your bios almost weekly, it's just standard practice. Different ways to live a computer life right?

A little exaggeration for clarity, maybe?

- Like a certain Presidential candidate?

I do Windows update weekly, usually on a friday when updates are available; sometimes BIOS updates are included.

I’ve found that, on checking for updates, minor updates are often ready to download despite the message that…

“You’re up to date”

I tend to do updates when they're offered.

I rarely regret that.

Except now. Win 11 24H2 has somewhat messed up monitor profiling (with Calibrite Profiler or Displaycal/Argyll CMS). The monitor's gamut isn't detected; it defaults to sRGB. (Could be worse, but I paid for an OLED, dammit.) No date for a fix has been promised.

Did Win 11 24H2 come up automatically in the update? Or you forced the update? It did not show up in any of my 4 PCs.

24H2 has supposedly been rolling out since 1 October. It's done in waves, so it may not be offered to all immediately.

I don't recall the precise path I took. There may have been an upgrade install (from an ISO) somewhere along the line. Most builds are available from uupdump.net.

26100.2161 arrived via Windows Update. I'm not enrolled in any Insider program.

I experimented with going back to 26100.1591. The bug seems to exist in that build, too.

As far as I know, 24H2 continues its roll out. Some machines have been blocked due to software incompatibilities.

I was in contact with Calibrite last week. Surprisingly, they aren't testing Profiler against 24H2 yet. (They must have a very small software development team.) None of their support people appear to have gotten 24H2 yet. (Their developers are in the UK. I'm not sure where their North American support is located, but it's somewhere in the EU.) I may have been the first to inquire about 24H2. They have since done a support ticket for another customer who provided ICC profiles that showed wide gamut monitors being profiled for the sRGB space, rather than the native space of the monitors.

As Profiler doesn't report the gamut it's working to, any number of customers with 24H2 may have re-profiled their displays and gotten the limited gamut, without realizing it. A cynic might say that would show the pointlessness of wide gamut displays for photo work.

For the moment, I'm using the profile provided by the monitor manufacturer (Philips). It appears to crush blacks a bit. Black level - Lagom LCD test

 

[BobKnDP]

I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.

Do you find substantial improvements from these BIOS updates?

Heh.

They're usually for stability improvements, and/or security patches.

If your PC already runs stably and hasn't suffered any attacks, no improvements would typically be noticeable.

 

[Austinian]

Did Win 11 24H2 come up automatically in the update? Or you forced the update? It did not show up in any of my 4 PCs.

None of my laptops nor the primary drive on the desktop PC has gotten 24H2.

I tried forcing the update with a Media Creation Tool on a Meteor Lake laptop, but after much processing the update failed; from what I've since read, I'd have to do a clean install; no thanks, just wondering if that'd work.

I already had 24H2 on the desktop's Dev Channel Insider drive, where it seems to be behaving itself, though I haven't tried a color profiling yet. Maybe later.

 

[BobKnDP]

Did Win 11 24H2 come up automatically in the update? Or you forced the update? It did not show up in any of my 4 PCs.

None of my laptops nor the primary drive on the desktop PC has gotten 24H2.

I tried forcing the update with a Media Creation Tool on a Meteor Lake laptop, but after much processing the update failed; from what I've since read, I'd have to do a clean install; no thanks, just wondering if that'd work.

I already had 24H2 on the desktop's Dev Channel Insider drive, where it seems to be behaving itself, though I haven't tried a color profiling yet. Maybe later.

I presume by "Media Creation Tool" you meant from an ISO, or from a bootable USB drive. (For those unfamilar: you couldn't boot from the USB drive to do an upgrade. Just run setup.exe.)

Is there something special about "Meteor Lake"?

The only reason I am familiar with that requires a clean install is going back to an older major version (say, from 24H2 to 23H2). I've installed an older 24H2 build over a newer one for testing.

I think that profiling works under the bug, but the monitor's gamut isn't detected, so it defaults to sRGB. I'd like more confirmation on that, though.

 

[Austinian]

Did Win 11 24H2 come up automatically in the update? Or you forced the update? It did not show up in any of my 4 PCs.

None of my laptops nor the primary drive on the desktop PC has gotten 24H2.

I tried forcing the update with a Media Creation Tool on a Meteor Lake laptop, but after much processing the update failed; from what I've since read, I'd have to do a clean install; no thanks, just wondering if that'd work.

I already had 24H2 on the desktop's Dev Channel Insider drive, where it seems to be behaving itself, though I haven't tried a color profiling yet. Maybe later.

I presume by "Media Creation Tool" you meant from an ISO, or from a bootable USB drive. (For those unfamilar: you couldn't boot from the USB drive to do an upgrade. Just run setup.exe.)

Yes. I should have been more specific; a bootable USB drive created with a Media Creation Tool. In my mind, they're synonymous, but of course that's not really the case.

Is there something special about "Meteor Lake"?

Not that I know of in this context, just mentioning it in case someone knows that might be a reason why the upgrade install failed.

The only reason I am familiar with that requires a clean install is going back to an older major version (say, from 24H2 to 23H2). I've installed an older 24H2 build over a newer one for testing.

I think that profiling works under the bug, but the monitor's gamut isn't detected, so it defaults to sRGB. I'd like more confirmation on that, though.

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

 

[BillyBobSenna]

I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.

Do you find substantial improvements from these BIOS updates?

 

[Austinian]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

 

[BobKnDP]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

 

[vett93]

I consider myself a computer building enthusiast. Maintaining the latest bios on my systems is standard practice. Most times I don’t even read what was updated. The process of updating the bios is nearly trivial when you perform this task once or twice a year.

Do you find substantial improvements from these BIOS updates?

Heh.

They're usually for stability improvements, and/or security patches.

If your PC already runs stably and hasn't suffered any attacks, no improvements would typically be noticeable.

My desktop PC is a Corsair prebuilt with MSI motherboard. I am waiting for Corsair to release the final version of Intel microcode for addressing Intel 13th/14th-gen CPU over voltage issues. Even though MSI has released the final version, Corsair has a lock on the BIOS update.

My desktop PC has been working fine for over a year. It does not have the crash problems that others reported. I think it is probably a good idea to update to that BIOS though.

--
"Keep calm and take photos"
Photography enthusiast, from 12mm to 600mm

 

[Austinian]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

 

[BobKnDP]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

Not expecting help.

Verification.

 

[Austinian]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

Not expecting help.

Verification.

Are you on build 26120.2200?

 

[BobKnDP]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

Not expecting help.

Verification.

Are you on build 26120.2200?

Nope, not a Dev build.

26100.2161. Available to non-Insiders.

 

[Austinian]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

Not expecting help.

Verification.

Are you on build 26120.2200?

Nope, not a Dev build.

26100.2161. Available to non-Insiders.

So any verification would be questionable, but I fixed the Dev drive's shutdown problem quickly, so I had a chance to install DisplayCAL from curiosity. So, FWIW, here's what DisplayCAL said in Profile info: I don't understand it, but perhaps you will.

Too long for one screenshot; does this tell you anything?

Also:

 

[BobKnDP]

The Dev drive isn't used for photo editing, so IDK for sure if I even have any profiling software on it, but I think I do

I'll look on the desktop's Dev drive tomorrow, if I remember. I'm on a laptop tonight.

I realized I don't have Profiler, just the low-rent ccStudio that AFAIK isn't telling me anything about what it thinks the monitor gamut is.

What I did was to run Profiler, and then check the gamut using the Profile Info utility of DisplayCal.

You should be able to do the same, with ccStudio. (Or DisplayCal, for that matter.)

Apparently the Dev drive doesn't have DisplayCAL, and I see no relevant info on ccStudio. If I get around to it after I finish working with the Dev drive today, perhaps I can try to install DisplayCAL (though none of this is likely to help with your problem). :-(

Not expecting help.

Verification.

Are you on build 26120.2200?

Nope, not a Dev build.

26100.2161. Available to non-Insiders.

So any verification would be questionable, but I fixed the Dev drive's shutdown problem quickly, so I had a chance to install DisplayCAL from curiosity. So, FWIW, here's what DisplayCAL said in Profile info: I don't understand it, but perhaps you will.

Too long for one screenshot; does this tell you anything?

Also:

That looks like it's profiling pretty much like the monitor is sRGB.

For comparison, this is the profile provided by Philips, compared to Adobe RGB:

This is what I get from my most recent Calibrite Profiler run:

Not exactly a lethal bug, but it's annoying.