Unsolved

This post is more than 5 years old

Closed

40805

July 4th, 2007 19:00

Application Error 610 - Windows Error 2 when running BIOS Flash program D620_A08.EXE

I want to update my Bios of my Latitude D620 from version A07 to A08.
However the program tells me that it can not flash the new bios because of an unexpected error.
Rebooting and retrying doesn't solve this problem.
Application Error Return: 0x00000610
Windows Error Return: 0x00000002
 
What do I have to do to get rid of this error message and be able to flash the latest BIOS ?
 
Regards,
Johan
 

4.4K Posts

July 4th, 2007 23:00

Run the flash update program from a USB flash key from DOS.  It will then work and it is safer.
 
Instructions on how to create a bootable USB memory key can be found here.
 
 

July 5th, 2007 15:00

I followed your advice. Created a bootable USB stick en booted into DOS.
Then I ran the flash bios program and I got following error
"Cannot run under a protected environment.
Rom update not performed
Please reboot"
 
I do not know what is causing this protected environment.
Any idea ?
1 month ago I succeeded to go from A06 to A07 without any problems,
but the upgrade to A07 gives the same message now.
 
Regards,
Johan Jacobs

4.4K Posts

July 6th, 2007 01:00

Did you boot from the USB memory key?
 
It sounds like you didn't.
 
 

July 6th, 2007 06:00

Yes,
 
I booted from the USB key. Got the Win98 startup screen en the c:\ prompt.
I ran then D620_A08 and immediately got the errors I mentioned popping up.
It seems something is preventing access to the Bios.
 
Regards
Johan

26 Posts

July 8th, 2007 00:00

This solution came from another post and has worked for me and others in situations like this. Be careful with Regedit as you can mess up other things, but you're trying to get rid of some Dell BIOS update keys that were created by running the flash program once, but now prevent the program from running again:

1. Click on start then run and type "regedit" in the box and press enter. (without the quotes)
2. Expand and Look for: HKEY_LOCAL_MACHINE -> SYSTEM ->ControlSet001 -> Services -> DELLBIOS
3. Delete DELLBIOS folder
4. Restart the system
5. Re-flash BIOS

4.4K Posts

July 11th, 2007 00:00



E-Gizmo wrote:
This solution came from another post and has worked for me and others in situations like this. Be careful with Regedit as you can mess up other things, but you're trying to get rid of some Dell BIOS update keys that were created by running the flash program once, but now prevent the program from running again:

1. Click on start then run and type "regedit" in the box and press enter. (without the quotes)
2. Expand and Look for: HKEY_LOCAL_MACHINE -> SYSTEM ->ControlSet001 -> Services -> DELLBIOS
3. Delete DELLBIOS folder
4. Restart the system
5. Re-flash BIOS


AGAIN?
 

26 Posts

July 11th, 2007 04:00

Yes, the original poster complained about a "Windows" error (see the original post. Therefore this solution WILL work.

Aside: Bay Wolf, please stop complaining as many people have written back that this solution (which came from another post) has solved their BIOS update problem! Thanks.

July 11th, 2007 08:00

The proposed change in the registry by E-Gizmo indeed solved my problem,
so I succeeded to flash the latest bios version.
 
Thank you all folks.
Johan Jacobs

26 Posts

July 11th, 2007 15:00

Great! I'm glad it helped, and worked.

4.4K Posts

July 12th, 2007 01:00

It still doesn't change the fact that updating your BIOS through Windows is NOT a good idea.
 
Read these forums.  Most of the failed BIOS updates happened when flashing the BIOS in the Windows environment.  Facts are facts.
 
I prefer to help people PREVENT having a worthless piece of plastic instead of a working computer.
 
 

26 Posts

July 12th, 2007 01:00

Fair enough, I'm sure you're right that updating the BIOS from DOS or by bootable CD is better, and that the best thing of all is not to touch the BIOS if you don't have to. I just wanted people to know how to "fix" the issue when the Windows routine doesn't work - which can be extremely frustrating.

Sincerely,
Todd

1 Message

July 15th, 2007 12:00

Hi, Thanks for the info. The registry edit didn't seem to help, but doing it in DOS did the trick. Thanks again. gitsie

Top