The wallet.dat file is a Bitcoin Core specific thing, just as the Electrum wallet format is an Electrum specific thing. In order to move your Bitcoin to Electrum, you will need to export your private keys by using the dumpprivkey RPC command. You must use this command for all of your addresses, including change. Then you can make a new Electrum wallet and go to Wallet > Private Keys > Sweep and sweep the Bitcoin into your new Electrum wallet. Sweeping makes a transaction that spends all of the Bitcoin from the private keys you specified and sends the Bitcoin to an address in your Electrum wallet.

This topic has been moved to Trashcan.

Begging

Can you post the raw transaction that you are trying to broadcast?

This topic has been moved to Trashcan.

Reflinks are not allowed

We also need the armorylog.txt file too.

Private keys are randomly generated. Downloading and installing the wallet software will on a new computer will always give you a new address, otherwise everyone would be getting the same addresses and that is not secure.

If you do not have the wallet file and do not have any backups of it, then there is nothing you can do, the Bitcoin is lost. Even knowing the password to your wallet does not help because your password is completely unrelated to the private keys that you need. The password is only for the wallet file and its encryption, but nothing to do with the contents of that file.

Transactions have a version number. There are currently two accepted (and considered standard) version numbers, 1 and 2. Bitcoin Core by default creates transactions with a version number of 2. It seems that blockchain.info is incapable of accepting transactions that have a version number of 2. Since you are using Bitcoin Core, I suggest that you use it to broadcast your transaction. Just use the sendrawtransaction command and it will broadcast your transaction to the network, so long as you are connected to it.

Bitcoin Core version 0.14.2 is now available from:

  <https://bitcoin.org/bin/bitcoin-core-0.14.2/>

This is a new minor version release, including various bugfixes and
performance improvements, as well as updated translations.

Please report bugs using the issue tracker at github:

  <https://github.com/bitcoin/bitcoin/issues>

To receive security and update notifications, please subscribe to:

  <https://bitcoincore.org/en/list/announcements/join/>

Compatibility
==============

Bitcoin Core is extensively tested on multiple operating systems using
the Linux kernel, macOS 10.8+, and Windows Vista and later.

Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
No attempt is made to prevent installing or running the software on Windows XP, you
can still do so at your own risk but be aware that there are known instabilities and issues.
Please do not report issues about Windows XP to the issue tracker.

Bitcoin Core should also work on most other Unix-like systems but is not
frequently tested on them.

Notable changes
===============

miniupnp CVE-2017-8798
----------------------------

Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness error
(present in MiniUPnPc v1.4.20101221 through v2.0) that allows remote attackers
(within the LAN) to cause a denial of service or possibly have unspecified
other impact.

This only affects users that have explicitly enabled UPnP through the GUI
setting or through the `-upnp` option, as since the last UPnP vulnerability
(in Bitcoin Core 0.10.3) it has been disabled by default.

If you use this option, it is recommended to upgrade to this version as soon as
possible.

Known Bugs
==========

Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
control and smart fee estimation does not reflect any change in target from the
smart fee slider. It will only present an approximate fee calculated using the
default target. The fee calculated using the correct target is still applied to
the transaction and shown in the final send confirmation dialog.

0.14.2 Change log
=================

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

### RPC and other APIs
- #10410 `321419b` Fix importwallet edge case rescan bug (ryanofsky)

### P2P protocol and network code
- #10424 `37a8fc5` Populate services in GetLocalAddress (morcos)
- #10441 `9e3ad50` Only enforce expected services for half of outgoing connections (theuni)

### Build system
- #10414 `ffb0c4b` miniupnpc 2.0.20170509 (fanquake)
- #10228 `ae479bc` Regenerate bitcoin-config.h as necessary (theuni)

### Miscellaneous
- #10245 `44a17f2` Minor fix in build documentation for FreeBSD 11 (shigeya)
- #10215 `0aee4a1` Check interruptNet during dnsseed lookups (TheBlueMatt)

### GUI
- #10231 `1e936d7` Reduce a significant cs_main lock freeze (jonasschnelli)

### Wallet
- #10294 `1847642` Unset change position when there is no change (instagibbs)

Credits
=======

Thanks to everyone who directly contributed to this release:

- Alex Morcos
- Cory Fields
- fanquake
- Gregory Sanders
- Jonas Schnelli
- Matt Corallo
- Russell Yanofsky
- Shigeya Suzuki
- Wladimir J. van der Laan

As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).

Mining is the process of including transactions in blocks to make them irreversible and permanent. Miners are rewarded for spending the time, electricity, and energy required to produce a block.

Bitcoin.com is not official in any way, shape, or form. There is no official Bitcoin website nor is there an official Bitcoin exchange. People use LocalBitcoins and other exchanges because they have existed far longer than any service provided by Bitcoin.com and are more trustworthy.

There are multiple ways to exchange Bitcoin, not just through Bitcoin.com. If you use LocalBitcoins, you can receive cash (either in person or by mail), money sent to a bank account, MoneyGram transfers, Western Union transfers, etc. There is no need to use PayPal. You can use other exchanges too like Bitstamp where you link a bank account directly to the exchange so you deposit and withdraw fiat via your bank account.

There are many different types of wallets. There are web wallets like coinbase and blockchain.info. There are also desktop wallets like Bitcoin Core, Electrum, and Armory. Web wallets are far less secure than desktop wallets. You are trusting the service to not steal your Bitcoin. You are relying on them to still provide the service so that you can access your Bitcoin. Furthermore, most web wallets do not provide you the level of control and advanced utility that many desktop wallets do. You get far more control over your Bitcoin by using a desktop wallet.

It's probably a scam.

Bitcointalk's default timezone is UTC. Melbourne Australia is UTC+10, so the forum will be 10 hours behind you. However, you can go into your profile settings and change the timezone (only for you) to your local timezone so all times will be your local time.

The PPA is built without upnp support (and a few other things). Instead of installing from the PPA, you should download the tar package from bitcoin.org and move the files to the right places.

The forum's search function is fairly poor and works very slowly. It is far better to use Google to perform your searches. This is easily done by appending site:bitcointalk.org to your search. This will limit the search to just pages on bitcointalk.

Blockchain.info could have yet another bug in their wallet (it's a common occurrence for their wallet to be full of bugs) which is displaying the incorrect private key.

Alternatively you are looking at the wrong address or the transactions to that address have not confirmed yet.

You can't. You can only see that info after you have clicked "Sweep" and it attempts to create the transaction. When that happens, you can review the transaction before it is signed and broadcast. Before that, it does not lookup any information about the private keys that you have entered. If it says that there are no inputs, then that means that you may not have the private key for the right address.

There is no import function in Electrum anymore, only sweeping. I presume you are sweeping? In that case, the address you see is not the address that you are importing but rather one that is in your wallet that Electrum will send all of the coins from your "imported" address to.

Are you sure you have entered the private key correctly? Make sure that you are not missing any characters and you don't have any extra characters (e.g. non-breaking spaces) in the private key that you entered. You can also try a different wallet and see if that wallet recognizes the private key.

What you are doing is interpreting the pubkey as a string. However a pubkey is not a string but rather a blob of binary data that is 33 bytes long. What you want to do is to convert your hex string into a vector of unsigned char first and then pass that to the CPubKey constructor.

It would be better for you to just initialize an array with your pubkey instead of performing a string conversion.

Edit:
Your code should look something like this:

IIRC having the commit hash at the end of the version number like you do here means that the binary wasn't compiled via gitian (the official release process) but rather something else. Either this is self compiled, or done by a software repository. This means that if whoever compiled it did not include the miniupnp library, your install of Core will not be able to us upnp.

Bitcoin Core has its own wallet functionality that is reasonably secure. Not all wallets are based on Core or use Core.

You can export the private key(s) and import them into another wallet which does not require the entire blockchain, like Electrum. Read the second paragraph of this post: https://bitcointalk.org/index.php?topic=1927293.msg19130832#msg19130832 for instructions for exporting.  Follow the instructions here: http://docs.electrum.org/en/latest/faq.html?highlight=sweep#can-i-sweep-private-keys-from-other-bitcoin-clients to sweep the keys into Electrum.