Start a Conversation

Unsolved

This post is more than 5 years old

M

6716

January 11th, 2018 16:00

XPS 8900, BIOS 2.2.1

Dell has a list of BIOS updates (and dates they expect to be releasing BIOS updates) here. These updates are to counter Intel's Meltdown and Spectre problem. I have an  XPS 8900, and there's a new BIOS for it listed there, version 2.2.1. I've updated BIOS before and never had a problem. 'm not sure if I should update to 2.2.1, though, partly because of the message here. The poster had an XPS 8900 that was "rendered unusable" by the new BIOS. The last message written there, by RoHe, says partly "So even if you get an update from Dell for Spectre and Meltdown, you will still need a BIOS update from Dell for the ME issue, but if it were me, I'd hold off on flashing BIOS 2.2.1, at least for now".

Has anyone with an XPS 8900 updated their BIOS to version 2.2.1? If you did, was it a smooth update, or did you have problems?

5 Posts

February 10th, 2018 18:00

Dell updated Bios 2.2.1 Feb 6th. Having been caught by the initial fiasco and having my XPS8900 bricked I felt I had nothing to lose by applying this latest attempt at reversing the previous failures on Dell and Intels part. 

After applying this Feb updated Bios my computer is still bricked. I’ll now reinstate my old HP Destop that this XPS replaced and rebuild my digital world again. 

My warranty of course ran out a couple of months earlier and from other posts I see Dell is trying to wash their hands of this for those unfortunate to be out of warranty, shameful but predictable, share holders first.

Well, got to go and get my trusty old HP up and running. Had that one for so many years without a problem. I’ll go look for a replacement for this DELL brick and most likely another HP, good luck everyone.

here are the details of the Feb 2.2.1 update; 

Dell XPS 8900 System BIOS

 

This package provides the Dell System BIOS update and is supported on Dell XPS 8900 for Windows and DOS Operating Systems.

Fixes & Enhancements
Fixes:
- Update to the latest CPU Microcode to address CVE-2017-5715.
- Updated Intel ME Firmware to address security advisories INTEL-SA-00086 (CVE-2017-5705, CVE-2017-5708, CVE-2017-5711 & CVE-2017-5712) & INTEL-SA-00101(CVE-2017-13077, CVE-2017-13078 & CVE-2017-13080).
- Updated the handling of pre-boot authentication information by firmware.
- Updated UEFI variable input validation.
- Updated the handling of 3rd party Option ROM loading.
- Updated SPI flash command configuration settings.

Enhancements:
- N/A.
Version
Version 2.2.1, 2.2.1
Category
BIOS
Release date
06 Feb 2018
Last Updated
06 Feb 2018
Importance

Urgent

1 Rookie

 • 

3.2K Posts

February 11th, 2018 05:00

It seems I am missing something. How do you apply a BIOS update to a computer that is bricked? Was the motherboard replaced and now it is bricked again? A bricked computer usually means it will not even power on or enter the BIOS setup much less apply a BIOS update.

5 Posts

February 11th, 2018 05:00

Sorry for the confusion.

No, the motherboard has not been replaced. I guess it’s not completely dead. It’ll boot to the desktop but will take an hour or so. If I click on anything I walk away and come back later. It functions but of no use, it is extremely slow but yet working. It doesn’t crash, just takes forever to do anything. I guess it’s a boat anchor.

I’m transferring my files from the c drive at the moment, it’s been working all day and I’ve left it running overnight. Hopefully I’ll save what’s on the drive and then reformat it and start a fresh windows install. Nothing to lose I guess.

until the update a couple of weeks back the computer was running fine, since the update in January it has been of no use whatsoever, so, a brick, an anchor a door stop,

 

1 Rookie

 • 

3.2K Posts

February 11th, 2018 06:00

Your problem may have coincided with the BIOS update but not caused by it. There are other possibilities including a failing hard drive. I would do as you plan reformat, re-install Windows, and test the hard drive or you may wish to run a bootable hard drive test program first before doing the Windows install.

5 Posts

February 18th, 2018 13:00

Indeed, been awhile responding. Tried everything to recover the installation but ultimately replaced the HDD. Reinstallled a fresh Windows 10 and everything works fine. Your assessment was correct, just coincidental I guess. Thanks and take care.

5 Posts

February 18th, 2018 13:00

Indeed, been awhile responding. Tried everything to recover the installation but ultimately replaced the HDD. Reinstallled a fresh Windows 10 and everything works fine. Your assessment was correct, just coincidental I guess. Thanks and take care.

29 Posts

February 18th, 2018 14:00

I am not sure it was coincidental, after installing the 2.2.1 bios dell instructed by way of urgent update  on the screen, the same issue, except it toasted my processor also. When Dell fixed the unit, they replaced both the processor and the HD.

Just an FYI

5 Posts

April 3rd, 2018 06:00

I run a PC service center and had a recent experience with the BIOS 2.2.1 upgrade. Below is what I experienced while researching the issue and resolving the issue:

1. From reading forums, it appears there were multiple releases of the BIOS 2.2.1 with the last update being in the Jan - Feb 2018 time frame, all have the 2.2.1 release number. Having spent several years in Software Quality Assurance, I find using the same version number for multiple software releases is a poor industry practice.

2. From my own analysis and hands-on experience, this issue persist with MBR for Windows 7 process and not the UEFI (GPT). Dell 8900, and maybe other models, offered Windows 7 with some of it's shipments, possibly Windows 8 (I have not heard of any), and Windows 10 for certain. Typically, Windows 7 installs utilize MBR and Windows 8 and 10 use UEFI (GPT), this could explain why some people in these forums have not experienced this particular BIOS 2.2.1 upgrade issue with Windows "hanging" at the Starting Windows screen, the screen with the Windows pulsating color flag.

3.I contacted Dell Support about the BIOS 2.2.1 issue, got past the post-warranty person, and requested to speak to a Level 2 tech. After several minutes of explaining, and re-explaining the issue, there was no fix offered for the MBR issue. 

4. Windows 7 Workaround: After much trial-and-error, I did find a way to boot into Windows under MBR: Go into BIOS and set SATA to RAID mode (not AHCI). MBR mode will work with SATA set to the RAID mode. In general, I understand that if you are not installing a RAID drive configuration (more than one drive for redundancy), setting SATA to RAID mode is not recommended because it will create some performance issues. When possible, always use AHCI mode. I did set SATA to RAID. and after a longer Windows boot-up time (1 minute or more using an SSD, where AHCI booted in 20 seconds), Windows 7 functions appeared to work fine. There were some noticeable performance issues during some Windows 7 operations, but I considered them minor. This workaround is great for retrieving software licenses, using a tool like Belarc Advisior, and saving off personal data files, so you can convert to Windows 7 to UEFI, but I don't see this as a long-term solution without extensive testing.

5. Long-term, yet more time-consuming solution; Convert Windows 7 from MBR to GPT (UEFI). This required ten or more of my time, and I know my way around BIOS and Windows 7. NOTE: Using a USB docking station, I first had to retrieve all drive software product licenses and personal data files before re-installation and reusing a drive:

    a.) Reformatted the drive to GPT and set up a partition volume using the Windows "Create and format hard disk partitions" tool.

    b.) I next set BIOS to UEFI and SATA to AHCI (use F2 when Dell splash screen appears) then reboot.

    c.) Inserted a Windows 7 installation disk in the DVD player then reboot (I used an origianl Dell Windows 7 Pro Installation DVD). Force a boot to UEFI, not Legacy, by pressing F12 during the Dell boot-up splash screen then I select the UEFI DVD boot option)

   d.) After Windows reinstall process started, and getting past the first couple of screens, I selected the Custom Installation choice. This choice will produce a list of drives. i deleted the Primary partition then clicked Next to continue the installtion process. (NOTE: There might have been a way to not include a formatted Primary partition during the reformatting process, but I did not take the time to research that. This might have eliminated deleting the Primary partition in this step d.).

NOTES:

1. I spent over ten hours or more rebuilding the Windows 7 drive from scratch; requiring the recovery of several licenses, reinstalling an configuring applications, saving and restoring data files, and reconfiguring several email accounts in Outlook.

2. I made several attempts on trying to convert the MBR partition to GPT without success. Some of the tools used were the Command line gptgen tool and AOMEI Partition Assistant. Even if successful, I fear some obscure issue would later surface as a result of trying to shoehorn a MBR to GPT conversion, so I later opted out of trying to MBR to GPT convert.

3. You will encounter problems installing Windows 7 as a UEFI unless you have previously installed Windows 7 64-bit SP1.

I would be interested to hear if anyone also had success with the above workaround or changing MBR to UEFI.

1 Message

April 13th, 2018 12:00

Was doing updates last week to several computers at our office.  2 Dell XPS 8900s were rendered unusable by upgrading to BIOS 2.2.1.  I stopped the upgrades immediately after that.  Do NOT upgrade to this BIOS version

2 Posts

June 4th, 2018 16:00

I don't know how you got them to admit it and take care of it!  I just spent valuable time talking to "Amit Singh"

who said he is a Manager, and that I could not talk to any other manager, as there is no one above him.

 

He denied 100% that it is a known or Dell issue.  Though I sent him this link among others.  He said anyone can write anything on a forum.  I said the link is not a forum, but a Dell statement.

https://www.dell.com/support/article/us/en/04/sln308587/microprocessor-side-channel-vulnerabilities-cve-2017-5715-cve-2017-5753-cve-2017-5754-impact-on-dell-products?lang=en#affected_products

 

So, again, I'm here with a broken computer.  Been over a week.

2 Posts

June 4th, 2018 16:00

Well, I was one of the MANY unlucky ones.  Installed their 'criticial' BIOS update 2.2.1, completey CRASHED my system.  Have been on the phone with them over 5 times, hours on end, tried everything they said to do, and nothing worked.  Throughout this process, I've bought an extended warranty as they said this is the ONLY way they can help me.  Well, they still could not fix it.  Now they want me to buy ANOTHER copy of the OS the computer CAME with when I bought it DIRECTLY from them at Dell.  I said to them, you know I bought the computer from Dell directly (I have an account with them), you know it came with the OS, yet you want to charge me for ANOTHER copy of the OS, and you are saying that NOW, this is the only way to fix my computer caused 100% by YOUR BIOS UPDATE.

I am at my wits end.  This is unbelievable.  I feel like I'm in a dell purgatory.

14 Posts

June 6th, 2018 16:00

I had the same problem with my Dell XPS 8900. I had to go back to previous Bios and reinstall Windows 10 again. Problem solved.

No Events found!

Top