UNSOLVED

bulletmark

updated

6 years ago

Closed

B

bulletmark

1 Rookie

•

49 Posts

0

2486

February 10th, 2021 16:00

XPS 13 9300 BIOS update 1.4.1 new but same version?

I updated my XPS 13 9300 to BIOS 1.4.1 when it was released in very early December 2020. I just noticed it seems to have been updated on the Dell support site  with a date 09-Feb-2021 but it has the same 1.4.1 version number? Does anybody know what is going on? <ADMIN NOTE: Broken link has been removed from this post by Dell>

The new 1.4.1. release note mentions Intel security advisory INTEL-SA-00455 which is also dated 09-Feb so it does seem this is actually a new version.

  • fkubrick

    20 Posts

    1395

    0

    Posted February 11th, 2021 02:00

    I reported this issue to pro-support already, waiting for the fix to be released.

  • blob007

    1 Rookie

    •

    81 Posts

    1328

    0

    Posted February 14th, 2021 08:00

    The February 9th 1.4.1 is definitely a new version. I flushed it and not only it updated firmware for some of the devices, it also fixed a laggy/skippy bluetooth issue that I got from the "earlier" 1.4.1 BIOS...

  • bulletmark

    1 Rookie

    •

    49 Posts

    1308

    0

    Posted February 14th, 2021 14:00

    Dell really need to get their act together. This is frankly yet another embarrassing stuff-up which should have been fixed (i.e. quickly rename the new version as 1.4.2) within a few hours of it being reported here.

  • emapex

    19 Posts

    1438

    0

    Posted February 14th, 2021 21:00

    The file, XPS_13_9300_1.4.1.exe, which I retrieved on Dec 10, 2020 has MD5 = a45fe28eb5b30189b8de804d71ab3868.

    The Dell web site, says that the Feb 9 version of that file has the same MD5.

    <ADMIN NOTE: Broken link has been removed from this post by Dell>

     

  • blob007

    1 Rookie

    •

    81 Posts

    1435

    0

    Posted February 15th, 2021 07:00


    @emapex wrote:

    The file, XPS_13_9300_1.4.1.exe, which I retrieved on Dec 10, 2020 has MD5 = a45fe28eb5b30189b8de804d71ab3868.

    The Dell web site, says that the Feb 9 version of that file has the same MD5.

     


    Then it must be the same BIOS. I definitely still remember this number from a few days ago when I reflushed 1.4.1 on my laptop. This is really weird. When I first installed 1.4.1 long ago, it definitely gave me some errors during flushing (said that some of the firmware could not be updated). I also had more frequent bluetooth glitches after that (although this might be subjective, or unrelated, as I use different sets of devices over time). The recent update went on smoothly and updated firmware for several devices (though said some of them were already up to date). So maybe under some circumstances, it fails to flush properly and may have to be run twice/several times? Aren't we all excited about this guessing/investigation game Dell makes us play?

  • emapex

    19 Posts

    1255

    0

    Posted February 16th, 2021 15:00

    Using "cmp", the .exe file I retrieved on Dec 10, 2020 (and which is on a thumb drive) is identical to the file I just retrieved again in my Downloads folder.  I'm waiting for Dell to straighten this out.

  • bulletmark

    1 Rookie

    •

    49 Posts

    1405

    0

    Posted February 16th, 2021 15:00

    How can you guys possibly think the 2 x 1.4.1 releases are the same? Look at the new release notes <ADMIN NOTE: Broken link has been removed from this post by Dell>. At the very least, the newer 1.4.1 release on 09-Feb-21 includes a fix for Intel Security Advisory INTEL-SA-00455 which was released earlier that same day. Also, I updated the  new 1.4.1 over the 1.4.1 I installed in early December and although many/most components did not change, at least 2 of the components did update. @emapex must simply have made a mistake comparing the MD5 sums.

  • blob007

    1 Rookie

    •

    81 Posts

    1238

    0

    Posted February 16th, 2021 20:00


    @bulletmark wrote:

    How can you guys possibly think the 2 x 1.4.1 releases are the same? .


    Well, according to @emapex md5 and cmp produce same results for the two files. So the files are the same. It may be that, as it was in my case, it takes more than one flushing to properly update all the firmware though...

  • fkubrick

    20 Posts

    1184

    0

    Posted February 24th, 2021 08:00

    Definitely the same file. Support was also not believing me despite me sharing that the checksums were the same, this was the proof that they accepted that there was indeed an issue:

    AnCqzeSs.png medium.png

    The file was signed in November... They still haven't provided any update though.

  • fkubrick

    20 Posts

    640

    0

    Posted March 3rd, 2021 08:00

    Answer 3 weeks after raising the case:

    fkubrick_0-1614789480466.png