This usually happens if siad died in the background, or if you changed your siad api port and didn't let the ui know. What happens if you run the consensus command in the Terminal plugin? Does it say it cannot connect to the daemon?
You can quit the UI (right click the Sia icon in your system tray and click "Quit Sia"), then navigate to your Sia directory and delete the wallet folder. In windows, this is located at %APPDATA%\Sia-UI\sia\wallet, in Mac OS X this is located at ~/Library/Application Support/Sia-UI/sia/wallet, and on linux this is located at ~/.config/Sia-UI/sia/wallet.
Wallet deletion and importation features are planned for a future UI release.
For others with the same problem, note that there was a bug in Sia-UI v1.0.0 where siad was not launched with admin privileges even if you launched Sia-UI as admin. This was fixed in Sia-UI v1.0.1. Another workaround is to launch siad from an admin command prompt, and then launch Sia-UI -- it will automatically connect to siad.
You should get the collateral back. There is some concern that the host is not properly tracking contracts as they go onto the blockchain, which would cause the host to 'drop' a contract but not get the collateral back.
I'm currently investigating this. There are some other issues that have been fixed with the host recently as well, the next release will have all of these fixes.
Hey, I believe that you've already seen the updates, but v1.0.1 fixes the issue you are reporting here. The price estimation tool was incorrectly using all of the hosts instead of just the cheapest few, and a single host placing their price at $1,000,000 / TB / Mo disrupted all of the estimations.
You don't want to be using v0.6.0 for mining, because there's a hardfork at block 100,000 which will disrupt all pre-1.0 clients. Everyone should upgrade as soon as possible to minimize the risk of coin loss and other issues during the hardfork date.
There are also several other security vulnerabilities that were fixed between v0.6.0 and v1.0.0, including things that affect the miner.
@ccster: I apologize that things aren't going smoothly for you. We're well aware of what the problem is and will be able to have a fix out in the next few weeks.
The large number of users we received upon the release of 1.0 was somewhat unexpected, and the software did not handle it entirely well. You should be able to start forming contracts over the next few days though, even without an update to the software.
It's a problem with using the Windows command line. If you have linux, that would work, or if you've got cygwin that should work as well. The password reader that we use for some reason doesn't work well with the Windows command line, and we don't have a good fix at the moment that we know of.
We'll be adding the same option to the GUI at some point in the near future (2-4 weeks), so that will eventually be another way to recover the funds.
I would like to apologize to everyone who is still waiting to get their funds from an old wallet. We've had to spend a lot of time preparing the host and renter for 1.0, and the wallet fell off of our shortlist. Development on the wallet features will begin shortly.