Lightning node on Windows - testing, get not connected

Ok after testing BTCPay, C-Lightning, LND on Ubuntu I said ok let's try also the Windows implementation, is just few clicks and done (as it is promoted).

So I followed this github guide that actually send you to this one.

OK, started Bitcoin-core client on Windows 7 x64, with an already synced data folder. Empty bitcoin.conf (none of guides says how to configure the conf file).
Wait until the client is full synced. And then launched the windows-node-launcher (from a subfolder inside Bitcoin folder).
All good, started slowly and a small popup appeared in systray saying Bitcoin node is syncing.
Reviewed the config of Bitcoin and LND through that little app in systray and saw that bitcoin.conf was already filled with some settings. Didn't change anything.
After 1 day (with the bitcoin blockchain already synced), the systray popup still says that is syncing and have a red dot.
In the tutorial says that we have to leave it to sync until is blue and then green.

I said, ok maybe it has more things to do. So I open that LND Output link, to see what is going on... And I see that LND is not well.
Says:
2019-04-06 21:11:29.772 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default
2019-04-06 21:11:29.772 [INF] LTND: Active chain: Bitcoin (network=mainnet)
2019-04-06 21:11:29.774 [INF] CHDB: Checking for schema update: latest_version=8, db_version=8
2019-04-06 21:11:29.808 [INF] RPCS: password RPC server listening on 127.0.0.1:10009
2019-04-06 21:11:29.808 [INF] RPCS: password gRPC proxy started at 127.0.0.1:8080
2019-04-06 21:11:29.808 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
2019-04-06 21:11:32.673 [INF] LNWL: Opened wallet
2019-04-06 21:11:33.183 [INF] LTND: Primary chain is set to: bitcoin
unable to create chain control: unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it.
2019-04-06 21:11:36.087 [INF] LTND: Shutdown complete
unable to connect to bitcoind: unable to subscribe for zmq block events: dial tcp 127.0.0.1:18502: connectex: No connection could be made because the target machine actively refused it.
2019-04-06 21:11:39.229 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta-rc3, build=production, logging=default

Now the bitcoin.conf have this:
printtoconsole=1
rpcallowip=::/0
whitelist=0.0.0.0/0
datadir=C:\Users\Admin\AppData\Roaming\Bitcoin
prune=0
txindex=1
server=1
disablewallet=0
timeout=6000
rpcuser=user
rpcpassword=defaultxzxxxxx
zmqpubrawblock=tcp://127.0.0.1:18502
zmqpubrawtx=tcp://127.0.0.1:18503
dbcache=2408

And LND.conf have this:
(#) Auto-Generated Configuration File
(#) Node Launcher version 6.0.2
debuglevel=info
restlisten=127.0.0.1:8080
rpclisten=127.0.0.1:10009
tlsextraip=127.0.0.1
listen=127.0.0.1:9735
alias=aliasme
color=#00aa7f
bitcoin.active=1
bitcoin.node=bitcoind
bitcoind.rpchost=127.0.0.1:8332
bitcoind.rpcuser=user
bitcoind.rpcpass=defaultxxxxx
bitcoind.zmqpubrawblock=tcp://127.0.0.1:18502
bitcoind.zmqpubrawtx=tcp://127.0.0.1:18503

So what is going on here? I will have to wait indefinitely? Somebody can give some help or explanation?
Is this LND node working on Windows Server 2008 or 2012?