This site makes extensive use of JavaScript.
Please enable JavaScript in your browser.
Live
PTR
10.2.7
PTR
10.2.6
Beta
Wowhead client on Windows 7
Post Reply
Return to board index
Post by
299324
This post was from a user who has deleted their account.
Post by
Malgayne
Is this still happening, or are you able to run the client now?
If not, are you running it as an administrator?
Post by
Wanderingfox
Is this still happening, or are you able to run the client now?
If not, are you running it as an administrator?
How, exactly do you expect us to run an application that auto-starts as admin? I shouldn't have to add a service task for the client just to get it to work properly :P
Just an FYI, I'm still having issues with the client on win7 x64. Specifically, the following:
1. Client launches at startup as it should, but it constantly asks me for the location of my wow directory. I assume this has to do with it not launching as admin when windows starts.
2. Client does not auto-upload when wow exits, even if it is running as administrator.
Post by
bwirum
I'm running win7 64, no problems at all, but then I don't have it autostarting upon windows startup.
Post by
Wanderingfox
I may just give up and add the service call for it, but I'd rather not if I don't have to.
Post by
GrayFox9420
Running Windows 7 64 bit also, client auto-runs on startup and does its thing, no drama at all.
I don't have WoW or the Wowhead client installed under C:\Program Files, though.
Maybe it's the protection W7 tries to apply to that directory that is screwing you around?
Post by
Wanderingfox
Running Windows 7 64 bit also, client auto-runs on startup and does its thing, no drama at all.
I don't have WoW or the Wowhead client installed under C:\Program Files, though.
Maybe it's the protection W7 tries to apply to that directory that is screwing you around?
Nope. It's running on an entirely separate drive.
Maybe it's some leftover config from a previous itteration of the client. I'll try blowing away the config info and reinstalling it...
Post by
Federalagent
Is this still happening, or are you able to run the client now?
If not, are you running it as an administrator?
How, exactly do you expect us to run an application that auto-starts as admin? I shouldn't have to add a service task for the client just to get it to work properly :P
Just an FYI, I'm still having issues with the client on win7 x64. Specifically, the following:
1. Client launches at startup as it should, but it constantly asks me for the location of my wow directory. I assume this has to do with it not launching as admin when windows starts.
2. Client does not auto-upload when wow exits, even if it is running as administrator.
Running the program as admin is easy. First, it does not need to auto-start, mine is manual. Second, just right click on the .exe file, and change the settings.
Right click .exe file
Select "Properties"
Click on "Compatibility" tab at the top
Check the option that says "Run this program as an administrator".
It should be that easy, and will always run as administrator.
as for your other issues about updating, and stuff, must be an issue with your installation. Im running win7 64bit and it updates perfectly fine, as long as the client is running before i open the game.
Post by
Wanderingfox
does not function if you use a shortcut to autostart the application as far as I know.
Post by
Federalagent
does not function if you use a shortcut to autostart the application as far as I know.
Just edit the shortcut then. Most programs dont use a shortcut to load anymore. Most programs these days are placed in the registry, in a key that is loaded when windows starts. All this does is execute the .exe file directly, so it should still work.
Post by
Wanderingfox
No, you don't follow me... Windows 7 has an updated UAC that will prompt you (unless the UAC is completely off) asking whether or not you want to allow the program to run as admin every single time it launches if you change that compatibility setting. Thus, I'll be presented a UAC prompt every single login. The only way around this is to use a service to start the application, which I've done in the past (to get rivatuner and my temp sensor to launch at startup silently for example).
I'm well aware of how applications can be launched at startup (I've had my CompTIA A+ cert for almost 7 years now). What I was getting at was that the behavior as to how starting programs that require elevated privileges are started has changed in windows 7.
edit:
I just created an elevated shortcut using the task scheduler service and threw that into startup instead of the default one the client makes and all is well.
Post by
Federalagent
Why not just disable the UAC service? Its only there to prevent inexprienced users from changing something improperly.
Post by
Wanderingfox
Ummm no it's not? The UAC acts in the same manner as the sudo command in linux, forcing the end-user to authenticate (or at least confirm) that they want to do something at root level. While I could disable it, if I did that then it would allow the unattended execution of root-level code on my user account, which is a bad thing.
Post Reply
You are not logged in. Please
log in
to post a reply or
register
if you don't already have an account.