i will try it...thanks...will let you know!
Main Topics
Browse All TopicsOur software (all .NET) installs and runs on XP PRO, Vista Ultimae (32 bit), but has a problem running on 64bit, either Visra or Windows 7....same error message
"License Manager has stopped working". I have tried moving the program for Programs to Programs (x86)...no differece. What do I need to do?
If you want to duplicate my problem download and install http://support.solomoninst
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I guess the installer is not putting the registry entries in the correct path. Please verify on a working system first
1) How does this license manager start - is it a service?
2) What are the corresponding registry entries (if any) like?
Now compare those findings to a 64 bit system. 32 Bit Software registry entries could be found at HKEY_LOCAL_MACHINE\SOFTWAR
A local group policy change can make it so that executables, when run as administrator, are automatically elevated without prompt, or the need to right-click.
From the search dialog on the 'Start Menu', type 'gpedit.msc'. This will open the local GPO.
Go to the following setting; Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options\User Account Control: Behavior of the elevation prompt for administrators in Admin Approval Mode.
Change the setting to 'Elevate without prompting'.
Close gpedit.msc
I recommend not to alter the UAC settings but to use a scheduled task that will start your app elevated. See http://www.experts-exchang
To tell you a little more, read http://www.experts-exchang
I would argue the validity of the UAC prompt, without a default password prompt, but that is for another forum. UAC is designed to run all processes in a low-privilege state. The prompt would let administrative users know something needs to run as such, and for non-admins, request administrative credentials. This system, though not perfect is much better than it was in XP. The BEST way to approach user rights and security is to have ALL users run as non-admins and elevate when necessary, i.e. sudo or wheel.
My suggestion does not disable UAC, just the silly prompt, letting the user know they are, in fact, doing what they set out to do. For non-admins, I set the prompt to deny elevation and therefore, access to the elevating process.
He can do it without doing anything to UAC and as you can see, it does not hurt to use scheduled tasks.
With UAC, security is argueably better than on xp. With auto approval, it is nearly equal to xp for reasons I wrote down on the linked thread.
Another example: take Windows 7. If you put the famous UAC security slider to the top (top secure) position and then afterwards use the setting you recommend, where does Microsoft automatically put the slider? To the very bottom.
The point you might be missing is that
> the silly prompt, letting the user know they are, in fact, doing what they set out to do
is only partwise correct. The autoelevate setting you recommend will not protect administrative users from *any* action that uses highest priviledges - no matter where it originates. The comment on the slider position that windows chooses to illustrate the remaining UAC protection reads:
Never notify me when
-I make changes to windows settings (*so far, so good*)
-programs try to install software or make changes to my computer (*is that really what you would like to recommend?*)
But let's settle it, I wouldn't like to go offtopic again any further on this UAC tweaking.
Business Accounts
Answer for Membership
by: FirebarPosted on 2009-10-31 at 17:38:08ID: 25712203
Have you tried running the .exe as an administrator (right-click, run as "Administrator")?