| Author |
 Topic  |
|
|
yoda
Here To Stay
USA
280 Posts
Status: offline |
 Posted - 02/21/2010 : 9:43:10 PM
|
OK, now this is strange to me. I've just recently installed and patched Vista Ultimate to SP2. For a large number of multimedia apps such as Master Geneaologist, ThumbsPlus, Adobe Reader, Roxio 2010, DivX Player, I get an ABEND when I try to run the app logged in as admin. None of these apps require admin mode so I am not prompted via the UAC for admin approval. However, I can run them all when I run configure them to run as administator and consent to the UAC's elevation prompt. Strangely enuf, they ALL run just fine when logged in as an ordinary user.
All this apps advertise Vista compatibiity so I'm a bit stumped as to what is up. If anybody has a suggestion, I would be more then grateful.
---dave koehler
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 02/21/2010 : 11:18:34 PM
|
Most "abends" return a Dr Watson log; I'd look at that to get a clue about what went wrong.
(For the young folks out there, "abend" is an old mainframe abbreviation for "abnormally end of application or OS.") |
Mark
tweetin' at mminasi |
 |
|
|
don2007
Honorable But Hopeless Addict
1992 Posts
Status: offline |
Posted - 02/22/2010 : 08:36:00 AM
|
| I didn't know that. I feel 9, not 10, years younger now. Thanks. |
Dyslexic people untie. |
|
|
|
yoda
Here To Stay
USA
280 Posts
Status: offline |
Posted - 02/23/2010 : 11:38:08 AM
|
quote:
Originally posted by Mark Minasi
Most "abends" return a Dr Watson log; I'd look at that to get a clue about what went wrong.
Mark,
Well, the Dr. Watson log I had didn't say squat about it. Maybe that's because it was not configured as the post mortem debugger. I went about looking for the binary to make it that way, found c:\windows\system32\drwatson.exe, then tried to execute that with the appropriate options. Apparrently, this binary has no options or is not meant to be used from a command prompt as I got nothing but a buncha "it's ok" dialogs. Giving up on this, I set up WinDbg as the chosen abend debugger.
I thought I had this issue fixed when I restored my "boss" account to use a local rather than a relocated My Documents folder. Everthing started to work as it should, then I went and uninstalled my favorite ReGet download manager. From what WinDbg showed, both IE and Windows Explorer were tanking on an toolbar addin enabled via ReGet. I uninstalled the package, and voila, the Explorer's were back in action. Alas though, my initial problems with the multimedia apps returned. Currently, I ain't got a clue as to why.
Gotta 'nother question for ya'. Just what is different about running as an admin in non-admin approval mode vs. running in the approval mode. Is it just privilege levels or is got something to do with acl SIDs.
thanx much
|
--dave
|
|
|
|
Mark Minasi
Chief cook and bottle washer
USA
10658 Posts
Status: offline |
Posted - 02/23/2010 : 3:56:15 PM
|
"Approval mode" just means "I turned on UAC."
Turn it off, no UAC. Turn it on, UAC; it's as simple as that. |
Mark
tweetin' at mminasi |
|
|
|
yoda
Here To Stay
USA
280 Posts
Status: offline |
Posted - 03/02/2010 : 2:29:26 PM
|
Victory @Last!!
This glitch is now history tanx to a ton of patience and the use of Mark R's excellent ProcMonitor and ProcExplorer tools. As I said at the top of this thread, there were a number of applications that would just not run in my Vista admin account. They would run fine when runas administrator or as an ordinary user, but they ABEND, throwing an access denied exception when run without elevation. Initially, I persisted with using WinDbg as a post-mortem debugger, but that was getting me nowhere fast. I gave up on that route and began using ProcMonitor to watch what was happening when I fired up Adobe Acrobat, one of the affected programs. Much tinkering with the filters resulted in finally identifying the file and registry ops that where triggering the access denied issue. Turns out that for whatever reason the app was attempting to write into APPDATA directory of the SYSTEM profile, something that is obviously verboten. The question now evolved into why wasn't the admin profile being used as it should be. I validated a number of enviornment settings, registry keys and file system junction points and confirmed that they were spot on. A quick check of the permissions for all the accounts listed in the HKEY_USERS branch of the registry revealed that the admin account key did not have ANY permissions set. I quickly rectified that and rebooted. Voila, everything started working as it should.
Post-mortem on this suggests that the lack of correct permissions on the HKEY_USERS admin profile key cause the apps to have an access failure, after which they default to using the system profile.
---what a relief |
|
|
| |
Topic |
|
|
|
Vista Exception code 0x05 - access issue
