[chillinfart]

Even using my root account i cannot install diskeeper lite because the system says "you don't have enough privileges..." and cancel the installation. I tried in safe mode but wind*ws installer is not available.

What restrictions i have in root mode and how i can unlock them?
Im using win2000 pro spanish(SP4)

[adamt]

Turn on failure auditing for system events, object access and privilege use on the machine, then try again and see what's happening in the security log. That should give you some idea of which privs you're lacking.

The only one I can think of would be "Load and unload device drivers", and that's assuming diskeeper's defragging engine works as a device driver.

Run secpol.msc, open Local Policies, User Rights Assignment.

Administrators should be in the effective setting against "Load and unload device drivers".

Also have a quick look in the application and system logs to see if either the windows installer or diskeeper is writing any useful information to them.

Finally - you could try running filemon/regmon or procmon to see if perhaps it's just a matter of there being something you need to take ownership of and grant permissions to.

[RJARRRPCGP]

chillinfart, on Oct 5 2007, 09:30 PM, said:

Even using my root account i cannot install diskeeper lite because the system says "you don't have enough privileges..." and cancel the installation. I tried in safe mode but wind*ws installer is not available.

What restrictions i have in root mode and how i can unlock them?
Im using win2000 pro spanish(SP4)

A likely cause is malware. Have you scanned for malware?

[dirtwarrior]

Or one of the needed services disabled

[gosh]

Never touch the ntfs permissions on the root of the drive! You can seriously screw things up. If you can't install from the root you have other issues. Post the exact error you're getting. Make sure your logged in as admin, or right click on the exe and 'run file as'.

And again, as i mentioned before - when a program gives you a permission error it could be related to registry permissions! Check the registry permissions on HKCU\software\diskeeper and HKLM\software\diskeeper.

Something should be logged in event viewer and setupapi.log.

-gosh