If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
updating Adobe application manager
I've been having trouble updating Adobe Application Manager on Windows
10. I get an error message about not being the Systems Administrator. Since there is only one account and Windows 10 I should automatically be the administrator?! If not how do I set it up so I will be? Albert who installed Windows 10 yesterday and it's looking pretty good. |
Ads |
#2
|
|||
|
|||
updating Adobe application manager
Albert wrote:
I've been having trouble updating Adobe Application Manager on Windows 10. I get an error message about not being the Systems Administrator. Since there is only one account and Windows 10 I should automatically be the administrator?! If not how do I set it up so I will be? Albert who installed Windows 10 yesterday and it's looking pretty good. Contact Adobe Support. ******* Permissions are handled in a strange way on modern Windows. The "Program Files" folder should be owned by TrustedInstaller. TrustedInstaller runs as a service and is not an account you can log into, like your user account. When work needs to be done in there, the software uses "impersonation" to get the right ownership. Even as Administrator, if you run into something with TrustedInstaller as the owner, you won't be able to change it in a naive way. Administrator does not "overpower" a TrustedInstaller setting like "Queen takes Pawn". But Administrator calling software that has the TrustedInstaller token, can do it. You can use the "whoami" command to learn more about your capabilities when running in Command Prompt. Note that this is not going to help you with your current problem. But, it does show you what "being administrator" means. whoami /priv /user whoami /all Using those commands is also handy, if you have some third-party impersonation software, and in the "faked" command prompt window, you want to check your new capabilities. PSexec can be used to run as the "System" account, as an example of some impersonation software. And some other software makes it possible to run with the TrustedInstaller token. That means (again), you are not using a TrustedInstaller account, but like a magic wand, the token can be used to correct damage you might have done with some other command. The icacls command makes it possible to record the permissions of the entire C: drive. And restore them at a later date. But this is far from a convenient or assuring thing to watch. Since any new files you add, may not be in the large text file made with icacls. ******* I would guess, even if you enable the "hidden Administrator" account, this is not going to change the capabilities. It might use storage area on the disk, for Administrator file storage. So if you "watched a movie" as real Administrator, there would be an Administrator folder somewhere with the file in it. The stuff I've looked at so far, doesn't suggest this is magic. net user administrator /active:yes To test, you'd open a Command Prompt windows from that command, use whoami, compare the text output to the text output from the commands run as regular user or regular user with elevation (Run as Administrator). I wouldn't leave that account running for very long, without following the rules for using a password and so on. http://www.howtogeek.com/howto/windo...windows-vista/ That should still work on Win10. ******* So then, how to proceed ? 1) Let some Adobe support guy in India, take remote control of your computer for three hours, trying to get the software to work. 2) Run Process Monitor, watch the install run (collect a trace), and see if you can spot the problem ("Access Denied", then installer stops). This software isn't magic. I can collect a 200MB trace from just 40 seconds of the computer running, so you're looking for a "needle in a haystack". https://technet.microsoft.com/en-us/...rnals/bb896645 3) Try to remember whether you used the "TakeOwn" command on some folder already on the computer. It's considered bad to run such a command on the entire C: drive for example. Using TakeOwn in that manner, offers no ability later to undo what you've done. To repair a "TakeOwn" would require an icacls text output file collected for a rainy day. That's if you want to put everything back *exactly* as it was before you messed around with something. 4) Look for a log file, an entry in Event viewer, anything which gives a "standard" Windows error code. Note that the Adobe software (apparently) leaves no entry in Programs and Features or Add/Remove when you use it. So it is ill-mannered software. It also doesn't appear to use Windows Installer as such. It's done the "Adobe way". Adobe has a history of re-writing portions of the target OS. For example, if Windows had memory management, Adobe would write their own memory manager and use it instead. That's the "Adobe Way". It makes it hard to fix stuff, or deal with the side effects, if you're not getting Windows-flavored error codes to help you figure out just what needs to be fixed. So now you have some idea why I suggest Adobe Support as your best option. The forums at Adobe didn't have any pithy observations about the software (where it might fall down or not work right). Merely a few users claiming they were tricked into installing it, when it wasn't needed for the particular Adobe product they were using. It has something to do with license management for Creative Cloud. HTH, Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|