This error is windows specific and has been discussed .
You need to figure out which working file is corrupted and delete it...
Potential candidates are:
Maybe I'm mising the real one. But the consensus.db is the toughest to recreate, so you can try to delete the gateway folder, then try to start. If that does not help, delete the next one... until you have tried all but the consensus.
And, if you delete the wallet folder, you'll need to restore from seed.
checked a few logs that siad was writing to
saw this error message on the log:
upnp.go:99: WARN: could not automatically forward port 9981: no UPnP-enabled devices found: no UPnP-enabled gateway found
logged into router and enabled UPnP, and it now works, yay!
TBH having these error messages surfaced to the UI would be incredibly helpful for troubleshooting for less technical users of this wallet.
At the end it is "building from sources" for all platforms where prebuilt binaries are not offered.
You need golang to build sia (sia is written in go language).
And you need git so the golang can retrieve all the sources for you.
At the end you'll have 2 executable files- siad and siac. That's all you need to run sia... You can remove golang and git afterwards, though, you'll need them later to update your sia to the next latest version.
I built it on (in) one VM and copied these two files to my siahosting zone (aka jail).
Just create a startup script where you add the -d parameter (where the siad will put its working files- consensus, wallet etc.)
The first run takes a long time, you cannot use any commands (including wallet creation/unlocking) until it has started up.
I put this into my startup script to unlock the wallet for hosting:
curl -A "Sia-Agent" -d "encryptionpassword=<your wallet unlock password or seed here>" "localhost:9980/wallet/unlock"