"Daz Studio cannot run with elevated permissions"

motoglyphsmotoglyphs Posts: 39

This Troll at the bridge has stood between me and my project for a lot of  hair-pulling hours now.

 

I installed the latest DS version without complications, until I tried to launch it, and repeatedly get

the error in the subject line.

 

From forum conversations of several years ago I learned what UAC is, and that it should be 

off or on, I tried every level.  That there's a checkbox to 'run as  admin' that shouldn't be checked.

It wasn't, it wasn't a shortcut, and my main account is the admin account, since I'm not administering a 

network.

  

But with no other clue I gathered from the language of the error, and the forum buzz, the problem seemed

to stem from trying to run as an admin.  Oh, and this was after logging out and in again, and restarting the computer,

and re-installing Daz again.  

 

So it seemed as if it was a problem that I was trying to run the program as an admin(?), so I created a new

account, gave it admin permission and took the account I've been building for 4 years with Daz off 

the admin list.  

 

Since neither account was able to launch DS without triggering 

this same eror, as the new Admin I un-installed and re-installed Daz again.

 

It was only then that I managed to get past this Troll for the first time, but only as my newbie Admin account.

I still can't access Daz from the account that has my workspaces, my links to content, my keyboard preferences,

my authorization for plug-ins, etc etc gathered over years.

 

Why, once I reinstalled, would I have a permission error as both admin and as a normal user?  And how do I fixi it?

 

I'm out of ideas on what to try next.

 

Thanks in advance for your helpful suggestions!

 

 

 

Post edited by motoglyphs on

Comments

  • Richard HaseltineRichard Haseltine Posts: 108,764

    You've already tried the things I would suggest, so I think you need to open a Support ticket.

  • motoglyphsmotoglyphs Posts: 39

    Thanks for your comment Richard.  BTW I found a workaround, not entirely satisfactory but I'm working again.

    I have been running with the installation on my D: drive, an SSD, reasoning that I'd get some benefit from it

    being faster.  Well I did the install on the C: drive, and it works!  

     

    So the takeaway, in case you see this issue with anyone else, is that it was not caused by UAC or Admin vs Normal user,

    since it worked both ways on my new user account.  And did not work either way on my default account.  

     

     

    Thanks again!

     

Sign In or Register to comment.