No need to wait for ALL nodes to drop it. That's going to take a really long time. You only need to wait for most nodes to drop the transaction and they already did.
Just click the green ball at the bottom right, untick "Select servers automatically" if it is ticked and change your server. Wait a minute after changing server, if your transaction is still there then change to another server. Once you find a server that doesn't have your transaction you can create the transaction again with higher fee.

You need to wait for all the nodes to drop the transactio so the btc you sent will be sent back in your wallet and only then you can make a new transaction. Next time use a higher fee to avoid having problems with confirmation.

Wow, that is a huge sized transaction with a really low fee + very small change. It could take awhile before that transaction confirms, if it ever does. Blockchain.info says their node even rejected it due to the fee being too low.

Did you have the "Enable Replace-By-Fee" option enabled in Preferences->Fees? If so, this may make it fairly easy for you to include a higher fee. Otherwise you'll likely need to attempt to double spend it or wait for it to get rejected and fall off the network so you can respend them.

How low was the fee? I recommend using dynamic fees in the future to help ensure adequate fees are used for transactions.

You may be able to help push the TX through by creating a new transaction with the change of the first transaction and including a high fee. This sometimes encourages miners to include your transaction so that they can claim the fee of the new transaction.

Transaction ID? If no one is rebroadcasting the transaction it should have been dropped by most nodes already. Try switching servers.

Go to %appdata%/HyperStake and create file called HyperStake.conf. Add those nodes there by adding following lines addnode=<ip address>.

if you have even one active connection, it should find more. It's also, as mentioned above, easier to add them to your config file. If one goes bad it will be ignored, so a long list is not a big deal.