the easiest way is to roll back to a backup that should be done (always recommended) before you start the upgrade and finish the update correctly.
If you didn\\\’t a backup we have variant B - to finish the update manually.
To do this, each file that appears in the text of the error it is necessary to comment out the code that responsible for creating the tables.
For the error given earlier:
Error in file: “C:\\\\wamp\\\\www\\\\magento\\\\app\\\\code\\\\core\\\\Mage\\\\Catalog\\\\sql\\\\catalog_setup\\\\upgrade-188.8.131.52.9-184.108.40.206.10.php” - SQLSTATE[42S01]: Base table or view already exists: 1050 Table ‘catalog_product_entity_group_price’ already exists
in the file ...sql\\\\catalog_setup\\\\upgrade-220.127.116.11.9-18.104.22.168.10.php you should comment the creating catalog_product_entity_group_price table.
Then, for each new error that will appear it is necessary to do the same action. The process is is quite laborious, but it\\\’s possible to finish it in 1h.
This method helped to restore Magento after failing several times.
P.s.: the problem most likely is that after all the updated tables Magento didn\\\’t updated version of each module in core_resources table, so the setup file starts again and again that occurs the errors.