UNSOLVED

Ben Mihalko

updated

2 months ago

BM

Ben Mihalko

1 Rookie

3 Posts

10 Points

0

337

June 11th, 2026 15:58

Tower Plus EBT2250, POST error

When my computer updated for BIOS firmware 1.16 on June 2, the computer shut off. When turned back on it will not make it through the POST sequence. It will give an alert saying that the CPU is not recognized and to restore it the 65W CPU. I made no hardware adjustments it was just an automatic update. In diagnostics it has no errors and recognizes off bios in the overview section. I've now updated to 1.17 but the issue still persists. I cannot boot windows. The Assist OS tool also freezes on the blue screen with no words and just shuts down. Can anyone think of what could have happened or causes. If I cannot get Windows Recovery to boot from recovery what are my next steps?

(edited)

  • DELL-Daniel V

    Community Manager

    665 Posts

    3763 Points

    0

    0

    Posted June 16th, 2026 20:54

    For any users returning to this thread with an EBT2250 receiving a "unsupported CPU" error after updating the BIOS to 1.16.0 or 1.17.0, please contact Support to get your issue escalated to the correct teams. Inform the Dell agent to review Dell article 000476168 for additional guidance. 

    Contact Dell GHN (Get Help Now) chat technical support Monday through Friday. Click the blue "Get Help Now" on the right to start a private live chat session. Share the private Service Tag with them so that they can verify the ownership and warranty status. This will also generate a unique Technical Support case for your unique Service Tag.

    DELL-Daniel V
    #IWork4Dell
    Digital Support Forum Liaison

    New to Community? Check our FAQ!

  • redxps630

    11 Legend

    16302 Posts

    82804 Points

    0

    0

    Posted June 11th, 2026 19:44

    Re: When my computer updated for BIOS firmware 1.16 on June 2, the computer shut off. When turned back on it will not make it through the POST sequence.

    sounds like that first bios update did not complete successfully.

    Re:  I've now updated to 1.17

    did you successfully complete the second bios update from the one-time boot menu?

    if yes but pc can not POST, consider downgrade BIOS to an earlier stable version

    BIOS Downgrade
    Allow BIOS Downgrade Controls flashing of the computer firmware to previous revisions.

    By default, the ON option is enabled.

     

    ALL BIOS Version
    Release DateStatus
    1.17.0
    05 Jun 2026 Latest Currently Viewing
    07 May 2026
    02 Apr 2026
    08 Dec 2025
    11 Nov 2025
    22 Oct 2025
    08 Sep 2025
    06 Aug 2025
    08 Jul 2025
    20 May 2025
    10 Apr 2025
    20 Mar 2025
    25 Feb 2025
    22 Jan 2025
    06 Jan 2025
    26 Dec 2024

    (edited)

  • Ben Mihalko

    1 Rookie

    3 Posts

    10 Points

    0

    0

    Posted June 11th, 2026 22:30

    @redxps630​ 

    yes 1.17 updated successfully. In the log 1.16 said installed successfully as well. I don’t have the exact time stamps memorized but it updated to 1.16 at say 12:01.50 and the computer shut off and gave the error code at 12:02.05. It was very short. 

    with that said. I tried downgrading to 1.15 since I know it was working. However, an error comes up saying downgrade is not allowed for security risks. I also tried 1.14 and 1.13 both had the same error. I also checked to make sure I could downgrade by having that enabled. 

    dell service is saying it’s a windows issue but I don’t quite understand how they know that without the machine posting. 

  • DELL-Daniel V

    Community Manager

    665 Posts

    3763 Points

    0

    0

    Posted June 12th, 2026 01:34

    @Ben Mihalko​ Just to confirm, you are entering the preboot SupportAssist OS Recovery tool via the F12 menu and the system is freezing there? If so, I'd call that a hardware failure of some kind. Normally tech support will go off of the preboot ePSA, but the OS recovery tool is still outside of the OS so I would see this as the same thing as freezing in the BIOS. Given that the issue started after a BIOS update, I presume this to be an issue with the motherboard rather than the CPU. 

    Contact Dell GHN (Get Help Now) chat technical support Monday through Friday to go through some additional testing. Click the blue "Get Help Now" on the right to start a private live chat session. Share the private Service Tag with them so that they can verify the ownership and warranty status. This will also generate a unique Technical Support case for your unique Service Tag. 

    DELL-Daniel V
    #IWork4Dell
    Digital Support Forum Liaison

    New to Community? Check our FAQ!

  • Ben Mihalko

    1 Rookie

    3 Posts

    10 Points

    0

    0

    Posted June 12th, 2026 02:27

    @DELL-Daniel V​ 

    you are correct with assumption. It will not loan the recovery at all. Locks on a plain blue screen. 

    I have a case opened with dell. After 90 minutes on the phone. Redoing most things I have already tried. They said it has to be a corrupted windows file. Which really doesn’t make total sense to me. But are forcing me to paid product support and it’s not I’m against paying. Thier hours are not the most conducive right now in my life. Currently I’m backing up all the data on the ssd. Then trying to make a flash os recovery stick. However when I put in my computer information the dell tool says no images exist. So I’m probably going to try to take off tomorrow to speak will dell in the morning. And hoping I can get moving forward in some way. 

  • DELL-Daniel V

    Community Manager

    665 Posts

    3763 Points

    0

    0

    Posted June 12th, 2026 02:43

    @Ben Mihalko​  I would reiterate that the system is freezing in the F12 menu. This has nothing to do with Windows as we're preboot, so paid support for software is unrelated. They may be getting confused with the standard windows supportassist application. 

    As to the OS recovery media creation tool not finding an image, there could be a few reasons for that. 

    1. The imaging server is down (unlikely, but would just try again later)
    2. Linux based images are unable to be created with our recovery tool (unrelated since you are using windows)
    3. The BIOS time of day is out of sync, impeding the imaging server from validating your service tag (the likely scenario)

    If you are able to enter the BIOS itself, I would double check that the Time of Day is set correctly. If it already is, then maybe it has something to do with the BIOS update issues. 

    As to troubleshooting with Support, that should have been no more than 15 minutes or so I'd say. The most I think we can really do here is attempt a hard reset, load the BIOS defaults, rerun the diags, and reseat internal components. Should you not get anywhere with that, feel free to let me know and I'll see what I can do. 

    DELL-Daniel V
    #IWork4Dell
    Digital Support Forum Liaison

    New to Community? Check our FAQ!

  • anne_droid

    5 Journeyman

    2055 Posts

    7641 Points

    0

    0

    Posted June 12th, 2026 09:02

    Hi

    I would introduce a fault, like removing any CMOS coin cell battery, and any RAM.

    Clear the CMOS if there is a jumper.

    How to clear CMOS on the EBT2250:

    1. Unplug the power cord

    2. Place the computer on its side and open the case

    3. Locate the coin-cell battery on the motherboard

    4. Push the battery-release lever to release and remove it

    5. Wait a few minutes, then reinstall the battery

    6. Reconnect power and boot up

    Removing the battery is the official and only documented method for clearing CMOS on this system.

    Then start again and boot up.  Then shut down and install the RAM. Re-Boot.

    Note anychanges.

      Kind Regards  

                                         

      anne_droid

  • redxps630

    11 Legend

    16302 Posts

    82804 Points

    0

    0

    Posted June 12th, 2026 12:53

    If your Dell computer blocks a BIOS downgrade with a security risk message, it is because newer versions contain critical fixes for security vulnerabilities. Dell permanently locks the system to prevent rolling back to vulnerable versions, and this restriction usually cannot be bypassed normally.

    traditional workarounds—such as using the /forceit command line parameter or utilizing standard BIOS recovery are typically blocked or ineffective on modern Dell models. 

    (edited)