We're good! It has indeed restored after taking some time over it :-)

Hi, I've downloaded the latest version of Bitcoin Core and got the indexing up to date bar about 30 minutes. I've tried a) importing the old wallet.dat by locating the backup version and copying and pasting it over the version in the bitcoin directory and b) by using the file/restore wallet function to do, as I understand it, essentially the same thing.
In both cases, the outcome is the same, when I try to open the wallet (which isn't passworded that I can recall) the opening wallet field flashes green in the same manner as the processing blocks field flashes green while it's updating and keeps on (and on and on) doing it.
Is that what I'm supposed to see? It's been years since I did this and from what I can remember once I'd loaded the backed up wallet then it would open straightaway. Of course the database is much, much bigger now which might be the problem... so am I using the right procedure here? 
Thanks :-)

Thanks to all who responded. I now have an up to date version of Bitcoin Core with the complete (bar 30 minutes or so) database on an external drive so I can port it between computers. I may well observe advice and set up a dedicated Linux box though as I have stuff lying around I can do that with. 
I now have trouble getting the wallet.dat file to play ball... but that's a new query so I'll start a new thread. Thanks everyone!

You have a point there, thanks.

It hasn't yet grown a wallet, the only wallet.dat I have on my system is my backup from earlier days which is parked in Dropbox. That might tell us something... like it isn't installing properly maybe. Crystal liked my E drive, isn't sure at all of my F drive and had no idea what to make of my SSD C drive. Hmmmm... I'm moving the index to the E drive and then I'll adjust the shortcut to accommodate the change and then see how that goes. Possibly I'll rebuild it there, it won't take too long. I may well find myself cloning the C drive too as that drive's been hinky for a while, though everything else works ok on it.

It's an internal HDD, never had a problem with it before. Could I run a test for that or does it need to be pulled out and have the connections checked physically? It's a good thought either way, thanks...

"Your debug.log is likely incomplete and thus doesn't show any hints why your Bitcoin GUI is killed or stops due to some unrecoverable error condition."
It says the same thing as shown over and over with a small gap in between.

No I'm not forcing Bitcoin Core to quit early, it does it for unknown reasons. I wondered about that too. Is it likely some other program could be stopping it running? It ran fine while it was updating the index so that seems unlikely I'd think...

bitcoind... in the absence of any immediate response here I've been floating round the other forums and found advice to see if bitcoind would run ok without promptly dying, so I tried it for a short time, and it worked OK. I thought I'd mention it before someone here suggested it. 

I tried running bitcoind.exe, that ran happily for a few minutes till I stopped it.

I found this (debug.log)
2023-10-01T14:07:28Z Bitcoin Core version v25.0.0 (release build)
2023-10-01T14:07:28Z Qt 5.15.5 (static), plugin=windows (static)
2023-10-01T14:07:28Z Static plugins:
2023-10-01T14:07:28Z  QWindowsIntegrationPlugin, version 331520
2023-10-01T14:07:28Z  QWindowsVistaStylePlugin, version 331520
2023-10-01T14:07:28Z Style: windowsvista / QWindowsVistaStyle
2023-10-01T14:07:28Z System: Windows 10 Version 2009, x86_64-little_endian-llp64
2023-10-01T14:07:28Z Screen: \\.\DISPLAY1 1600x900, pixel ratio=1.0
2023-10-01T14:07:29Z Using the 'sse4(1way),sse41(4way)' SHA256 implementation
2023-10-01T14:07:29Z Using RdRand as an additional entropy source
2023-10-01T14:07:29Z Default data directory C:\Users\bill\AppData\Roaming\Bitcoin
2023-10-01T14:07:29Z Using data directory F:\bitcoin
2023-10-01T14:07:29Z Config file: F:\bitcoin\bitcoin.conf (not found, skipping)
2023-10-01T14:07:29Z Using at most 125 automatic connections (2048 file descriptors available)
2023-10-01T14:07:29Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements
2023-10-01T14:07:29Z GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely…"
2023-10-01T14:07:29Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements
2023-10-01T14:07:29Z Script verification uses 3 additional threads
2023-10-01T14:07:29Z scheduler thread start
2023-10-01T14:07:29Z Using wallet directory F:\bitcoin
2023-10-01T14:07:29Z init message: Verifying wallet(s)…
2023-10-01T14:07:29Z Using /16 prefix for IP bucketing
2023-10-01T14:07:29Z init message: Loading P2P addresses…
2023-10-01T14:07:29Z Loaded 19003 addresses from peers.dat  94ms
2023-10-01T14:07:29Z init message: Loading banlist…
2023-10-01T14:07:29Z SetNetworkActive: true
2023-10-01T14:07:29Z Failed to read fee estimates from F:\bitcoin\fee_estimates.dat. Continue anyway.
2023-10-01T14:07:29Z Cache configuration:
2023-10-01T14:07:29Z * Using 2.0 MiB for block index database
2023-10-01T14:07:29Z * Using 8.0 MiB for chain state database
2023-10-01T14:07:29Z * Using 440.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2023-10-01T14:07:29Z init message: Loading block index…
2023-10-01T14:07:29Z Assuming ancestors of block 000000000000000000035c3f0d31e71a5ee24c5aaf3354689f65bd7b07dee632 have valid signatures.
2023-10-01T14:07:29Z Setting nMinimumChainWork=000000000000000000000000000000000000000044a50fe819c39ad624021859
2023-10-01T14:07:29Z Opening LevelDB in F:\bitcoin\blocks\index
2023-10-01T14:07:29Z Opened LevelDB successfully
2023-10-01T14:07:29Z Using obfuscation key for F:\bitcoin\blocks\index: 0000000000000000

Bitcoin Core version V25 the very latest

   Windows 10 Pro 64-bit
CPU
   Intel Xeon E5 v2 @ 3.00GHz   38 °C
   Ivy Bridge-EP/EX 22nm Technology
RAM
   16.0GB DDR3 (11-11-11-28)
Motherboard
   Dell Inc. 09M8Y8 (SOCKET 0)
Graphics
   HP E271i (1600x900@60Hz)
   1023MB NVIDIA Quadro K600 (NVIDIA)   58 °C
Storage
   238GB LITEONIT LCS-256L9S-11 2.5 7mm 256GB (SATA (SSD))
   2794GB Hitachi HUA723030ALA640 (SATA )   43 °C
   2794GB External USB3.0 SCSI Disk Device (USB (SATA) )   44 °C

Eager to remove my bitcoin from Nicehash before it closes in the UK, I thought I better update my Bitcoin Core database which I haven't indexed for some time. In the end, I had to delete the old database (it was corrupted, I gathered) and create a new one. This I did and Bitcoin Core worked fine throughout. So far as I'm aware it's up to date now. I did that while it was still V22. When I try to run it now though, and updating to the very latest version makes no difference, it runs for a few minutes saying "Loading block index" and then simply dies. It disappears. It goes away. It stops running. What to do? :-(

Thanks, I fixed it by defragging, which worked for a bit, that'd be a boot time defrag, and then when it crashed again later I moved the Bitcoin directory, copied it and pasted it elsewhere and changed the settings so Bitcore used the newer version. So, disk problems then! If yours keeps crashing in the same place, it's probably worth assuming it's the hard drive and trying another one if you have it or moving the directory. I'm up to 2 years and 7 weeks now so it's motoring along ok, Thanks for your reply :-)

It runs along happily for a while, then crashes, then crashes straight away when I try to restart it. I have to reindex after that. I believe it's version 13. I tried 14 but it didn't work well, can't remember why. I've seen threads saying that 14 will hammer your hardware and, well, it's an old machine. It's running on an old Dell which frankly I'm doubting is up to it. It's Windows 10 - the great unknown! There's plenty of available disk space. I've reindexed and restarted a few times and I have a suspicion that it's crashing at around the same period which suggests a disk problem. Next on my list is to note where it crashes and then try again with the bitcoin directory in a new location. At the moment it's got up to 2 years 48 weeks behind. Thanks for your response :-)

Keep getting this now :-) Drive problems, do we think? I've run checkdisk, all seems ok.

2017-04-21 07:12:17 Bitcoin version v0.13.1
2017-04-21 07:12:17 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-21 07:12:17 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-04-21 07:12:18 Default data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-21 07:12:18 Using data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-21 07:12:18 Using config file C:\Users\Dell\AppData\Roaming\Bitcoin\bitcoin.conf
2017-04-21 07:12:18 Using at most 125 connections (2048 file descriptors available)
2017-04-21 07:12:18 Using 2 threads for script verification
2017-04-21 07:12:18 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-04-21 07:12:18 Using wallet wallet.dat
2017-04-21 07:12:18 scheduler thread start
2017-04-21 07:12:18 init message: Verifying wallet...
2017-04-21 07:12:18 CDBEnv::Open: LogDir=C:\Users\Dell\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Dell\AppData\Roaming\Bitcoin\db.log
2017-04-21 07:12:18 Bound to [::]:8333
2017-04-21 07:12:18 Bound to 0.0.0.0:8333
2017-04-21 07:12:18 Cache configuration:
2017-04-21 07:12:18 * Using 2.0MiB for block index database
2017-04-21 07:12:18 * Using 8.0MiB for chain state database
2017-04-21 07:12:18 * Using 290.0MiB for in-memory UTXO set
2017-04-21 07:12:18 init message: Loading block index...
2017-04-21 07:12:18 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index
2017-04-21 07:12:19 Opened LevelDB successfully
2017-04-21 07:12:19 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-04-21 07:12:19 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate
2017-04-21 07:12:26 Opened LevelDB successfully
2017-04-21 07:12:26 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate: 0a172bbd222feac1
2017-04-21 07:12:47 LoadBlockIndexDB: last block file = 188
2017-04-21 07:12:47 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=58, size=17163518, heights=326460...326895, time=2014-10-22...2014-10-25)
2017-04-21 07:12:47 Checking all blk files are present...
2017-04-21 07:12:52 LoadBlockIndexDB: transaction index disabled
2017-04-21 07:12:52 LoadBlockIndexDB: hashBestChain=000000000000000003962f6d925b37f6b9405badc04785c39b0d982c7ae48b07 height=326828 date=2014-10-24 21:06:58 progress=0.272434
2017-04-21 07:12:52 init message: Rewinding blocks...
2017-04-21 07:12:55 init message: Verifying blocks...
2017-04-21 07:12:55 Verifying last 6 blocks at level 3
2017-04-21 07:12:55 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-04-21 07:13:07 No coin database inconsistencies in last 7 blocks (4052 transactions)
2017-04-21 07:13:07  block index           48473ms
2017-04-21 07:13:07 init message: Loading wallet...
2017-04-21 07:13:07 nFileVersion = 140000
2017-04-21 07:13:07 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2017-04-21 07:13:07  wallet                  274ms
2017-04-21 07:13:07 mapBlockIndex.size() = 462821
2017-04-21 07:13:07 nBestHeight = 326828
2017-04-21 07:13:07 setKeyPool.size() = 99
2017-04-21 07:13:07 mapWallet.size() = 3
2017-04-21 07:13:07 mapAddressBook.size() = 2
2017-04-21 07:13:07 ERROR: ReadBlockFromDisk: Errors in block header at CBlockDiskPos(nFile=187, nPos=117248446)
2017-04-21 07:13:07 *** Failed to read block
2017-04-21 07:13:07 init message: Loading addresses...
2017-04-21 07:13:07 torcontrol thread start
2017-04-21 07:13:08 Loaded 67646 addresses from peers.dat  1093ms
2017-04-21 07:13:08 init message: Loading banlist...
2017-04-21 07:13:08 init message: Starting network threads...
2017-04-21 07:13:10 Failed to connect best blockAddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)
2017-04-21 07:13:11 Discover: smallformten - 2001:0:4137:9e76:3420:2fda:ae92:dc1e
2017-04-21 07:13:11 init message: Done loading
2017-04-21 07:13:11 dnsseed thread start
2017-04-21 07:13:11 net thread start
2017-04-21 07:13:11 addcon thread start
2017-04-21 07:13:11 opencon thread start
2017-04-21 07:13:11 msghand thread start
2017-04-21 07:13:11 tor: Thread interrupt
2017-04-21 07:13:11 dnsseed thread interrupt
2017-04-21 07:13:11 net thread interrupt
2017-04-21 07:13:11 addcon thread interrupt
2017-04-21 07:13:11 opencon thread interrupt
2017-04-21 07:13:11 scheduler thread interrupt
2017-04-21 07:13:11 msghand thread interrupt
2017-04-21 07:13:11 Shutdown: In progress...
2017-04-21 07:13:11 torcontrol thread exit
2017-04-21 07:13:11 StopNode()
2017-04-21 07:13:11 Shutdown: done

How can I do that if I'm not connecting to any peers? I tried the connection check that one uses when first installing to check node connectivity and it appears I now have none. This is odd as it's the same machine, and the same router. I can't see how it would need to be set up again. I've got some interesting new errors in the logs too;
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28
2017-04-17 13:07:04 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=29
2017-04-17 13:10:27 GUI:   OpenType support missing for script 11
2017-04-17 13:10:27 GUI:   OpenType support missing for script 11
2017-04-17 13:10:27 GUI:   OpenType support missing for script 11
2017-04-17 13:10:27 GUI:   OpenType support missing for script 11
2017-04-17 13:10:27 GUI:   OpenType support missing for script 16
2017-04-17 13:10:27 GUI:   OpenType support missing for script 16
2017-04-17 13:10:27 GUI:   OpenType support missing for script 16
2017-04-17 13:10:27 GUI:   OpenType support missing for script 16
2017-04-17 13:12:18 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=30
2017-04-17 13:12:21 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462289, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:55863, peer=31
2017-04-17 13:16:43 ProcessMessages(version, 111 bytes) FAILED peer=32

Here's some new bits, with interesting info;
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12
2017-04-17 12:06:26 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=13
2017-04-17 12:11:30 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=14
2017-04-17 12:16:32 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=15
2017-04-17 12:18:03 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462281, us=81.109.35.225:54632, peer=16
2017-04-17 12:21:33 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=17
2017-04-17 12:26:35 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=18
2017-04-17 12:28:40 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462282, us=81.109.35.225:55058, peer=19
2017-04-17 12:30:05 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462282, us=81.109.35.225:55107, peer=20
2017-04-17 12:31:37 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=21
2017-04-17 12:31:38 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-04-17 12:36:38 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=22
2017-04-17 12:41:40 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=23
2017-04-17 12:51:59 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=24
2017-04-17 12:51:59 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-04-17 12:57:00 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=25
2017-04-17 13:02:03 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=26
2017-04-17 13:02:03 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-04-17 13:02:30 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2017-04-17 13:02:36 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462288, us=81.109.35.225:55732, peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes): Exception 'CDataStream::read(): end of data' caught, normally caused by a message being shorter than its stated length
2017-04-17 13:02:36 ProcessMessages(sendcmpct, 5 bytes) FAILED peer=27
2017-04-17 13:02:52 ProcessMessages(version, 100 bytes) FAILED peer=28

This doesn't look good :-( I'll be researching these error messages while I'm waiting to hear from anyone.

Windows 10, the new version which was updated just the other day, Bitcoin 14, the latest, an old Dell machine, I did have Bitcoin running ok earlier for a couple months, made successful transactions into the wallet which I have backed up, core started giving error messages, became a regular thing, I uninstalled it (it was v12 I think) and installed the latest, now it just says connecting to peers and simply sits there doing nothing. I uninstalled it again and reinstalled it, wondering if things had gone wrong, but it all seems ok except for it aint doing anything :-) Here's the log
 2017-04-17 11:42:58 Bitcoin version v0.14.0
2017-04-17 11:42:58 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-04-17 11:42:59 GUI: "registerShutdownBlockReason: Successfully registered: Bitcoin Core didn't yet exit safely..."
2017-04-17 11:42:59 Assuming ancestors of block 00000000000000000013176bf8d7dfeab4e1db31dc93bc311b436e82ab226b90 have valid signatures.
2017-04-17 11:43:01 Default data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using data directory C:\Users\Dell\AppData\Roaming\Bitcoin
2017-04-17 11:43:01 Using config file C:\Users\Dell\AppData\Roaming\Bitcoin\bitcoin.conf
2017-04-17 11:43:01 Using at most 125 automatic connections (2048 file descriptors available)
2017-04-17 11:43:01 Using 32 MiB out of 32 requested for signature cache, able to store 1048576 elements
2017-04-17 11:43:01 Using 0 threads for script verification
2017-04-17 11:43:01 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-04-17 11:43:01 Using wallet wallet.dat
2017-04-17 11:43:01 scheduler thread start
2017-04-17 11:43:01 init message: Verifying wallet...
2017-04-17 11:43:01 CDBEnv::Open: LogDir=C:\Users\Dell\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\Dell\AppData\Roaming\Bitcoin\db.log
2017-04-17 11:43:01 Bound to [::]:8333
2017-04-17 11:43:01 Bound to 0.0.0.0:8333
2017-04-17 11:43:01 Cache configuration:
2017-04-17 11:43:01 * Using 2.0MiB for block index database
2017-04-17 11:43:01 * Using 8.0MiB for chain state database
2017-04-17 11:43:01 * Using 290.0MiB for in-memory UTXO set (plus up to 286.1MiB of unused mempool space)
2017-04-17 11:43:01 init message: Loading block index...
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\blocks\index: 0000000000000000
2017-04-17 11:43:01 Opening LevelDB in C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate
2017-04-17 11:43:01 Opened LevelDB successfully
2017-04-17 11:43:01 Using obfuscation key for C:\Users\Dell\AppData\Roaming\Bitcoin\chainstate: 06cd9bb6457765a9
2017-04-17 11:43:22 LoadBlockIndexDB: last block file = 0
2017-04-17 11:43:22 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=4, size=1102, heights=0...1, time=2009-01-03...2009-01-09)
2017-04-17 11:43:22 Checking all blk files are present...
2017-04-17 11:43:22 LoadBlockIndexDB: transaction index disabled
2017-04-17 11:43:22 LoadBlockIndexDB: hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000
2017-04-17 11:43:22 init message: Rewinding blocks...
2017-04-17 11:43:24 init message: Verifying blocks...
2017-04-17 11:43:24  block index           22772ms
2017-04-17 11:43:24 init message: Loading wallet...
2017-04-17 11:43:24 nFileVersion = 140000
2017-04-17 11:43:24 Keys: 0 plaintext, 201 encrypted, 201 w/ metadata, 201 total
2017-04-17 11:43:24  wallet                  500ms
2017-04-17 11:43:24 setKeyPool.size() = 99
2017-04-17 11:43:24 mapWallet.size() = 3
2017-04-17 11:43:24 mapAddressBook.size() = 2
2017-04-17 11:43:24 mapBlockIndex.size() = 462281
2017-04-17 11:43:24 nBestHeight = 0
2017-04-17 11:43:24 torcontrol thread start
2017-04-17 11:43:24 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired
2017-04-17 11:43:25 AddLocal([2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333,1)
2017-04-17 11:43:25 Discover: smallformten - 2001:0:4137:9e76:3420:2fda:ae92:dc1e
2017-04-17 11:43:25 init message: Loading addresses...
2017-04-17 11:43:26 Loaded 66722 addresses from peers.dat  989ms
2017-04-17 11:43:26 init message: Loading banlist...
2017-04-17 11:43:26 init message: Starting network threads...
2017-04-17 11:43:26 net thread start
2017-04-17 11:43:26 dnsseed thread start
2017-04-17 11:43:26 addcon thread start
2017-04-17 11:43:26 opencon thread start
2017-04-17 11:43:26 msghand thread start
2017-04-17 11:43:26 init message: Done loading
2017-04-17 11:43:26 GUI: Platform customization: "windows"
2017-04-17 11:43:26 GUI: PaymentServer::LoadRootCAs: Loaded  50  root certificates
2017-04-17 11:43:37 Loading addresses from DNS seeds (could take a while)
2017-04-17 11:43:38 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54149, peer=0
2017-04-17 11:43:38 142 addresses found from DNS seeds
2017-04-17 11:43:38 dnsseed thread exit
2017-04-17 11:44:00 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54156, peer=1
2017-04-17 11:44:06 receive version message: /Satoshi:0.13.1/: version 70014, blocks=462280, us=81.109.35.225:54159, peer=2
2017-04-17 11:44:12 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54161, peer=3
2017-04-17 11:44:18 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54163, peer=4
2017-04-17 11:44:24 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=81.109.35.225:54166, peer=5
2017-04-17 11:44:53 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54176, peer=6
2017-04-17 11:45:10 receive version message: /Satoshi:0.14.0/: version 70015, blocks=462280, us=81.109.35.225:54180, peer=7
2017-04-17 11:45:47 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=8
2017-04-17 11:48:14 receive version message: /Satoshi:0.13.2/: version 70015, blocks=462280, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=9
2017-04-17 12:01:21 receive version message: /Snoopy:0.2.1/: version 70001, blocks=0, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:8333, peer=10
2017-04-17 12:04:11 receive version message: /Satoshi:0.14.0(UASF-SegWit-BIP148)/: version 70015, blocks=462281, us=[2001:0:4137:9e76:3420:2fda:ae92:dc1e]:54540, peer=11
2017-04-17 12:05:01 receive version message: : version 70001, blocks=469762048, us=127.0.0.1:8333, peer=12

None of which means a great deal to me :-) Is it too soon to worry or should I expect to wait a few hours? I had a look at Windows firewall and it says it's letting the core access both private and public networks so I guess that isn't the problem. Incidentally, is it true one can torrent the whole blockchain these days? Thanks! Let me know if I've missed out anything.