In another thread [1] I discovered that setup.exe hasn’t logged anything to /var/log/setup.log since November 2014, despite running it occasionally during that time.
I have ruled out permission problems, since I can write to that file as both a normal user and from an admin shell. The latter should mimic the permissions setup.exe has while running under UAC, which is enabled on this box. I later removed the setup.log files, and they weren’t re-created. I thought the problem was that setup.exe doesn’t enable the logger when running elevated permissions (main.cc, line 290), but Achim Gratz dug deeper and says it should relaunch itself again and then enable the logger. Achim Gratz noted that my default permissions may be weird because I am running with a Microsoft Account rather than a local one. I have no particular need to run a MS account, I just took the default it pushed me into, since I upgraded this VM to Windows 10 to test Windows 10. Might as well use it with its defaults as much as possible, yes? No point testing a new OS if I’m just going to turn off everything that’s new about it. [1]: https://cygwin.com/ml/cygwin/2015-10/msg00179.html
