I am using Windows 7 64-bit Professional on an AMD FX-8120 eight-core CPU, 16GB RAM, 120GB SSD dedicated solely to the operating system. Anything that I store, goes on an external 3TB hard drive.

I have found from Steve1943: Add --data-dir "path/to/blockchain" to the launch command. Here is an example for Windows: monerod.exe --data-dir "D:\My Documents\bitmonero"

This addresses the problem of the daemon downloading the blockchain onto the C:\ drive and allows one to download the data elsewhere.

My problem is that I do not know how to access the launch command. Apparently this is something very basic; but I still have no idea as to where to begin.

Good news! I just kept saving and exiting the daemon a few times. Then I happened to check the Wallet GUI and it was not only synchronizing (which it has claiming to do for quite some time), but the "Blocks Remaining" were counting down at a rather fearsome pace. Meanwhile, the daemon keeps repeating at times: Transaction must abort, has a child, or is invalid. I don't dare touch either the daemon or the Wallet. It looks as though I am on my way to receiving my Moneroj... which is a very good thing as the amount is rather sizable. Now I need to look into a cold wallet to get my Moneroj completely off-line. That'll entail another transfer and a fee, which doesn't matter.

Once again, my "Blocks Remaining" has come to a standstill, even though the Wallet GUI says it's synchronizing. And here is the latest from the daemon:

←[0m 2017-07-25 16:44:16.798 [P2P6] INFO global src/cryptonote_protocol/cryptonote_protocol_handler.inl:293 [80.232.241.110:18080 OUT] Sync data returned a new top block candidate: 202154 → 1362286 [Your node is 1160132 blocks <1049 days> behind]

SYNCHRONIZATION started

2017-07-25 16:44:47.123 [P2P6] ERROR blockchain
src/cryptonote_core/blockchain.cpp:3383 Error adding block with hash: <6f0dca866420b58864282e662d39cd298543103d6f6e7013f8996befa8da647e> to blockchain, what = Error adding spent key image to db transaction: MDB_CORRUPTED: Located page was wrong type

2017-07-25 16:44:02.491 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid

2017-07-25 16:45:02.491 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid

2017-07-25 16:45:08.156 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 DB error attempting to fetch block index from hashMDB_BAD_TXN: Transaction must abort, has a child, or is invalid

2017-07-25 16:45:16.188 [P2P6] WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:71 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid

Error messages similar to the above kept coming while my "Blocks Remaining" were counting down as in my last report.

I can only assume that these are not fatal errors, but just temporary.

I have tried restarting the daemon several times and also just left it alone for hours on end.

I would really appreciate a response from someone in-the-know.

 The GUI wallet now says that it is connected but not synchronizing and still 0.00 balance. I got the line-command wallet to load 94717 blocks. But it seems to have stopped doing anything. I attempted to refresh it to no avail. I'm going to restart everything to see what happens.

http://ensignlineargenerator.tripod.com/webonmediacontents/Monero Wallet 12.jpg http://ensignlineargenerator.tripod.com/webonmediacontents/Monero Wallet 12a.jpg

I have observed that when my daemon displays as in the above picture, it was actively counting-down the "Blocks Remaining" on my GUI Wallet.

Now it still displays as shown with the "Blocks Remaining" standing still, yet still "Synchronizing".

What can I do to get my "Blocks Remaining" to count-down?

Latest update: It's been five weeks since I sent my Moneroj from Poloniex to my GUI wallet. The "Blocks Remaining" has counted down four times, each time for less than twenty minutes. The other fifty-plus times I have opened my GUI wallet, the "Blocks Remaining" has risen from what it read the last time that I opened it. I have changed the block size from the default 200 to 20 and I have changed the daemon address to node.moneroworld.com, leaving the port at 18081. But I cannot tie any of these changes directly to any occasion of the blocks counting down. And not one fraction of my Moneroj has shown up in my GUI wallet. About half-way through all of this, the daemon started to work from the GUI wallet and I have not had to run monerod.exe manually. What do I need to do to get all the blocks?

I'm having a similar problem. Is it really the case that there is no actual support for the GUI wallet? We're left to post here and get no response, weeks after losing our monero??

@gwendolyn: On another forum, I was advised to use the GUI wallet on Linux; then they would be able to help me. I've gone to the trouble of installing Linux Manjaro in a dual boot on my Windows 7 computer and finally got the GUI wallet to run. However, in less than ten minutes, it stopped counting down. So, I'll be back at the other forums trying to get more help. I just find it hard to believe that Monero is being this difficult to work with; I have bought and transferred nine other crypto-currencies and I encountered zero hang-ups with them. I almost wish that I hadn't begun with Monero in the first place. But I have to get it into my wallet or else I'll never get it.

@DoctorCarlo1955 Have you tried the solution suggested here?

https://monero.stackexchange.com/questions/3122/how-do-i-delete-the-wallet-cache/3123#3123

@gwendolyn: I'll give that a try.

good news.your question is same as mine. tnx for any useful responses.