Armory on Windows 10

[unamis76]

I'm switching the machine controlling my Offline wallets, and this time I'm setting up Armory on Windows. I'll start off by saying that I've never setup Armory on Windows, so something really trivial might be escaping me.

I've installed everything without any issue, added a wallet, pointed Armory to my Bitcoin Core install and to my blockchain files as usual... But it simply doesn't get out of offline mode. I've tried using Armory 0.93.2 and Bitcoin Core 0.10 and Bitcoin Core 0.10.2.

I'll copy what I think are the relevant lines on the logfile

Code:

2015-07-28 19:40 (INFO) -- ArmoryQt.py:2508 - Setting satoshi datadir = D:\Bitcoin
2015-07-28 19:40 (INFO) -- SDM.pyc:282 - Total size of files in D:\Bitcoin\blocks is 38.5 GB
2015-07-28 19:40 (INFO) -- SDM.pyc:321 - Found bitcoind in the following places:
2015-07-28 19:40 (INFO) -- SDM.pyc:323 -    C:\Program Files\Bitcoin\daemon\bitcoind.exe
2015-07-28 19:40 (INFO) -- SDM.pyc:325 - Using: C:\Program Files\Bitcoin\daemon\bitcoind.exe
2015-07-28 19:40 (INFO) -- SDM.pyc:496 - Reading bitcoin.conf file
2015-07-28 19:40 (INFO) -- SDM.pyc:515 - Setting permissions on bitcoin.conf
2015-07-28 19:40 (INFO) -- SDM.pyc:524 - Setting permissions on bitcoin.conf
2015-07-28 19:40 (INFO) -- ArmoryUtils.pyc:600 - Executing popen: [u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'*******:F']
2015-07-28 19:40 (ERROR) -- ArmoryQt.py:2476 - Failed to setup SDM
Traceback (most recent call last):
  File "ArmoryQt.py", line 2471, in startBitcoindIfNecessary
  File "SDM.pyc", line 359, in setupSDM
  File "SDM.pyc", line 529, in readBitcoinConf
  File "armoryengine\ArmoryUtils.pyc", line 668, in subprocess_check_output
CalledProcessError: Command '[u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'*******:F']' returned non-zero exit status 5

Is it anything on Armory or this simply happens because Armory and Windows 10 still don't get along? I'm also posting this as a heads up for folks migrating tomorrow... There might be issues.

[doug_armory]

Do you have auto-manage enabled? You may want to disable it and manually start BC Core.

[unamis76]

Do you have auto-manage enabled? You may want to disable it and manually start BC Core.

Yes, I have. I disabled it, and it kept telling me it was offline, with the difference of now appearing a "Get online" button. I've setup bitcoind manually and it said Bitcoin-qt was running (even when I had disabled automatic management). Fiddled with settings and bitcoind, then remembered to reset Armory settings... Apparently that did the trick somehow. It appears to be building Armory databases now. Thanks for the help. I'll see if this syncs correctly.

[goatpig]

I'm switching the machine controlling my Offline wallets... But it simply doesn't get out of offline mode

Just nitpicking

CalledProcessError: Command '[u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'*******:F']' returned non-zero exit status 5

It failed to change privileges on bitcoin.conf, most likely because you user doesn't have the proper credentials to change access rights on that drive.

There are a few solutions available:

1) Start Armory with admin rights (I don't recommend this)
2) Turn off auto bitcoind management and run BitcoinQt yourself.
3) Start Armory with --disable-conf-permis (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L120). I don't exactly recommend this either
4) Give your user the proper permission. Right click on the D drive, go to the security tab, pick your user and give it full control over the drive.
5) Move your bitcoin folder into a path your user has full rights over (most likely C:\Users\*yourusername*)

[unamis76]

I'm switching the machine controlling my Offline wallets... But it simply doesn't get out of offline mode

Just nitpicking

CalledProcessError: Command '[u'icacls', u'D:\\Bitcoin\\bitcoin.conf', u'/inheritance:r', u'/grant:r', u'*******:F']' returned non-zero exit status 5

It failed to change privileges on bitcoin.conf, most likely because you user doesn't have the proper credentials to change access rights on that drive.

There are a few solutions available:

1) Start Armory with admin rights (I don't recommend this)
2) Turn off auto bitcoind management and run BitcoinQt yourself.
3) Start Armory with --disable-conf-permis (https://github.com/etotheipi/BitcoinArmory/blob/master/armoryengine/ArmoryUtils.py#L120). I don't exactly recommend this either
4) Give your user the proper permission. Right click on the D drive, go to the security tab, pick your user and give it full control over the drive.
5) Move your bitcoin folder into a path your user has full rights over (most likely C:\Users\*yourusername*)

Noticed I didn't change Bitcoin's home folder in Armory settings. it went right back to Offline mode. Started it in admin mode and it went right through. Why don't you recommend? The usage of this wallet is to create transactions for offline signing, only. I have no keys stored on Armory in online machines.

As for auto management, I'd like to leave it turned on. Very handy...

EDIT: to keep auto management and avoid running Armory as admin, I've changed permissions of my Bitcoin folder. I'll report back if something goes wrong.

[goatpig]

Why don't you recommend

It's bad practice. If you can fix the issue by only changing credentials on a folder, that should be the solution you go for. Giving system wide privileges to the process instead is not an acceptable work around, rather a way to verify this is a permission issue.

[unamis76]

Why don't you recommend

It's bad practice. If you can fix the issue by only changing credentials on a folder, that should be the solution you go for. Giving system wide privileges to the process instead is not an acceptable work around, rather a way to verify this is a permission issue.

That is correct. I just thought there was a particular reason for "running as admin" not to be recommended in what concerns handling private keys (hence why I said I have no keys online on Armory). Although Armory binaries and bitcoind are safe it's a good pratice not to do such a thing Thank you for all the answers, Armory now seems to be working.