Find out how to open bitcoind -daemon utilizing command line in Home windows?

I’ve created a conf file on the next path:

C:UsersNAMEAppDataRoamingBitcoinbitcoin.conf

After I run the Bitcoind file, nothing occurs. My command line window turns into unresponsive as if it is ready. I’ve waited ~1 hour, and my laptop is fairly highend (i7 processor, 16gb ram).

I wish to run the server and hearth some instructions on the bitcoind server.

I’ve the next conf file:

# bitcoin.conf configuration file. Traces starting with # are feedback.


 # Community-related settings:

 # Run on the check community as an alternative of the actual bitcoin community.
 #testnet=0

 # Join by way of a socks4 proxy
 #proxy=127.0.0.1:9050

 ##############################################################
 ##            Fast Primer on addnode vs join            ##
 ##  For instance as an illustration you utilize addnode=4.2.2.4          ##
 ##  addnode will join you to and inform you concerning the      ##
 ##    nodes related to 4.2.2.4.  As well as it'll inform ##
 ##    the opposite nodes related to it that you simply exist so     ##
 ##    they'll connect with you.                              ##
 ##  join is not going to do the above whenever you 'join' to it. ##
 ##    It would *solely* join you to 4.2.2.4 and nobody else.##
 ##                                                          ##
 ##  So if you happen to're behind a firewall, or produce other issues  ##
 ##  discovering nodes, add some utilizing 'addnode'.                ##
 ##                                                          ##
 ##  If you wish to keep non-public, use 'join' to solely      ##
 ##  connect with "trusted" nodes.                             ##
 ##                                                          ##
 ##  Should you run a number of nodes on a LAN, there is not any want for ##
 ##  all of them to open a number of connections.  As an alternative       ##
 ##  'join' all of them to at least one node that's port forwarded   ##
 ##  and has a number of connections.                            ##
 ##       Thanks goes to [Noodle] on Freenode.               ##
 ##############################################################

 # Use as many addnode= settings as you want to connect with particular friends
 #addnode=69.164.218.197
 #addnode=10.0.0.2:8333

 # ... or use as many join= settings as you want to attach ONLY
 # to particular friends:
 #join=69.164.218.197
 #join=10.0.0.1:8333

 # Don't use Web Relay Chat (irc.lfnet.org #bitcoin channel) to
 # discover different friends.
 #noirc=0

 # Most variety of inbound+outbound connections.
 #maxconnections=


 # JSON-RPC choices (for controlling a operating Bitcoin/bitcoind course of)

  server=1 #tells Bitcoin-QT to just accept JSON-RPC instructions.
 #server=0

 # You could set rpcuser and rpcpassword to safe the JSON-RPC api
 rpcuser=USERNAME_IVE_CHOSEN
 rpcpassword=PASSWORD_IVE_CHOSEN

 # What number of seconds bitcoin will wait for a whole RPC HTTP request.
 # after the HTTP connection is established. 
 #rpctimeout=30

 # By default, solely RPC connections from localhost are allowed.  Specify
 # as many rpcallowip= settings as you want to permit connections from
 # different hosts (and it's possible you'll use * as a wildcard character):
 #rpcallowip=10.1.1.34
 #rpcallowip=192.168.1.*

 # Pay attention for RPC connections on this TCP port:
 #rpcport=8332

 # You should use Bitcoin or bitcoind to ship instructions to Bitcoin/bitcoind
 # operating on one other host utilizing this selection:
 #rpcconnect=127.0.0.1

 # Use Safe Sockets Layer (also called TLS or HTTPS) to speak
 # with Bitcoin -server or bitcoind
 #rpcssl=1

 # OpenSSL settings used when rpcssl=1
 #rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
 #rpcsslcertificatechainfile=server.cert
 #rpcsslprivatekeyfile=server.pem


 # Miscellaneous choices

 # Set gen=1 to aim to generate bitcoins
 #gen=0

 # Use SSE directions to attempt to generate bitcoins sooner.
 #4way=1

 # Pre-generate this many public/non-public key pairs, so pockets backups will probably be legitimate for
 # each prior transactions and a number of other dozen future transactions.
 #keypool=100

 # Pay an optionally available transaction payment each time you ship bitcoins.  Transactions with charges
 # are extra possible than free transactions to be included in generated blocks, so might
 # be validated sooner.
 #paytxfee=0.00

 # Enable direct connections for the 'pay by way of IP deal with' characteristic.
 #allowreceivebyip=1

 # Consumer interface choices

 # Begin Bitcoin minimized
 #min=1

 # Reduce to the system tray
 #minimizetotray=1

Any concepts the right way to make the server work?