How to overwrite the previews code uploaded to Arduino UNO

I'm getting tired of this, I'm to Arduino, but to programming. I've reading and everybody asking all the same question of the answer already provided. Can I get some actual help here, cause this is frustrating me and wonder why so many people are hip about this, when there are so many problems.

This should be a simple question, "What can I do to overwrite my previews code on my Arduino when uploading fails".

When I uploaded my first code to my Arduino ONE, no problem. I needed to do some ajustement, and boom, all I keep getting is this...

Sketch uses 4828 bytes (14%) of program storage space. Maximum is 32256 bytes.
Global variables use 93 bytes (4%) of dynamic memory, leaving 1955 bytes for local variables. Maximum is 2048 bytes.
avrdude: ser_send(): write error: sorry no info avail
avrdude: ser_send(): write error: sorry no info avail
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 1 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 2 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 3 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 4 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 5 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 6 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 7 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 8 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 9 of 10: not in sync: resp=0x32
avrdude: ser_send(): write error: sorry no info avail
avrdude: stk500_recv(): programmer is not responding
avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x32
the selected serial port avrdude: stk500_getsync() attempt 10 of 10: not in sync: resp=0x32
does not exist or your board is not connected

And yes I am connected to the correct com, and how do I know that, my device management tales me so. Oh and I could of just unpluge it and see which one dissapere. Besides, Arduino 1.8.9 automaticly connect to the com and board, and do I know that you might ask, it says it in the Arduino windows, on the lower right hand corner. I'm using windows 7 64bit.

Can anybody help, and from what I have seen from other help page here, can we PLEASE STAY ON TOPIC!

To replace the old code, upload successfully.

The problem is that 90% of the time the error is just the sync error - which means there is a serial port, it appears to be acting like a serial port, but when the computer uses it to program the board (by asserting DTR and then sending programming commands), it doesn't see the reply it expects. That's all it knows - it was expecting one specific character, and it saw something different. Troublshooting the sync error is very difficult. I tried to make a troubleshooting guide, but I don't feel like I've gotten it far enough to recommend it's use.

First and foremost, you are using the experimental, pre-release 1.8.9 version (the latest released version is 1.8.8 ). This version may have new and exotic bugs; you should not use it if you are not an expert.

Uninstall that, and download and install 1.8.8. That may just straight up fix the problem (though I doubt it).

In your case, you have a very rare error message:

avrdude: ser_send(): write error: sorry no info avail
avrdude: ser_send(): write error: sorry no info avail
avrdude: ser_send(): write error: sorry no info avail

This implies that the serial port is in a bad state. Unplug the arduino, disconnect any external hardware from it, and plug it back in. Try a different USB port, and a different USB cable (there are a lot of bad USB cables making the rounds lately), and also try rebooting the computer. One of these should probably change the behavior you're seeing. Let me know which one fixes it, or if the error shown changes, what it changes to - this will help me expand my troubleshooting guide!

My first upload to my Arduino ONE, was successful, but I had to do some corrections, and now my Arduino is keeping my port busy, I am unable to upload my update or anything for that matter.

Anybody have any tricks to bypass this problem?

Did you try all the solutions DrAzzy recommended?

This often works:

In the IDE, under File: Preferences, turn on Verbose outputs.

Start the download, and press & the Arduino Reset button.

When the see this occur:
Sketch uses 4828 bytes (14%) of program storage space. Maximum is 32256 bytes.

release Reset. That should let the Bootloader kick off and accept the new sketch. Might take a couple of tries to get the release timing down.

OMG! I have unplug it and re-plug it a thousand time, I have also unplug, press the reset switch and re-plug it in over hundred time. I also connected a switch to the reset and the ground, will pressing that, and pressing the other reset switch and connected the USB, and this is so stupid! The Arduino it self is cause the problem with upload new sketch. I don't get why this is so difficult, yet it seem to work fine with everyone else.

You still haven't answered my question.

Look, it's unfortunate that you're having a problem but this negative attitude of yours is not helpful at all and it will only serve to drive away the volunteers who want to help you.

In programming and electronics, problems like this are an inevitability, no matter if you're a beginner or an expert. The key is learning how to efficiently troubleshoot and resolve the issues so you can get back to your project without having a stroke. It's unreasonable to expect that such a complex undertaking as working with microcontrollers will happen without any speed bumps along the way.