I've now discovered the apparent cause for this - the DAUpdater service will not start if configured to logon as the "Local System" account (which is the default).
Instead it must be setup to logon as a specific member of the Administrators group, and be provided with the password for doing so.
All fine and dandy, thinks I - I will just give it my own user account name. After all, I am an Administrator, and I don't use a password when logging on (This computer is in my house, after all, and frankly if someone stole it I doubt that having a password would make much of a difference).
Problem is, the service will not start if you provide it with a user account that has no password. "Logon failure."
So where do I go from here? I'm not changing my system setup so that I always have to provide a password; it's ridiculous to do that purely to get access to some DLC.
I suppose I can temporarily put a password on the account for as long as it takes to get my DLC, then disable it again.
Frankly it irritates me that I should have to do any of this. So is this happening because (a) I'm a fool for still using XP; (
I'm a fool for wanting my computer to logon automatically without prompting me for a password; or © Bioware made some strange choices in building their content updater module?
Retour en haut
