TR Forums

SO! i took ownership of my c:\ and then ran ccleaner, and like a pro, didn't back up the registry, and now i lost the ability to open the access control editor. DO NOT DO THIS. YOU WILL LOSE SYSTEM CONTROL. i have no restore points to return to, either.

error is "can't open acess contorl editor. The activation requires a display name to be present under the CLSID key."

i am unable to change any access to anything. i can still run tasks as an administrator, but i can't take control of any additional folders. I have been unable to find any assistance with this issue, besides a FEW people who have had it, but they don't have a fix. I looked to check the group policy folder, but it's empty, so
i am unable to reset the ownership of the drive, i can't make any changes to any of the properties. is there a way to do this via command line, or any of you hunks know a way to fix it?

EDIT: WELL. i found a work around. the context menu "take ownership" still works, so i installed it, and took back the stuff i couldn't use. yay!

I'm facepalming for you.

thanks man. i was fine till ccleaner wrecked my party ;(

TrustedInstaller is supposed to own C:\.

Taking ownership of the drive was the first mistake.

i know it is, but i don't want it to. it wasn't a mistake, i knew that before i started. I just didn't care. So maybe my first mistake was using computers?

Yeah, using computers is the mistake.

Playing with that setting is like playing with TNT.

sweatshopking wrote:

i know it is, but i don't want it to. it wasn't a mistake, i knew that before i started. I just didn't care. So maybe my first mistake was using computers?

So wait... you *knew* this was an important system setting, changed it anyway, then got annoyed when it broke stuff?

Consider the experience an opportunity to try out Win8's Refresh My PC or Restore My PC features....

You'd never make it on a *nix machine. Those operating systems will /let/ you do stupid reckless things without making you jump through such hoops first.

bthylafh wrote:

You'd never make it on a *nix machine. Those operating systems will /let/ you do stupid reckless things without making you jump through such hoops first.

Heh... yeah, the canonical one is typing "rm -rf *" into the wrong terminal window! (For the non-*NIX folks, that is a recursive deletion of all files and folders from the current folder on down. If typed into a terminal window with root privilege at the top of the file system hierarchy, it will dutifully scour the entire system clean!)

sweatshopking wrote:

like a pro, didn't back up the registry, and now i lost the ability to open the access control editor.

Real pros do back stuff up and have fall back plan. It is those amateurs thinking they are pros that don't.
(Is that sig worthy? )

just brew it! wrote:

bthylafh wrote:

You'd never make it on a *nix machine. Those operating systems will /let/ you do stupid reckless things without making you jump through such hoops first.

Heh... yeah, the canonical one is typing "rm -rf *" into the wrong terminal window! (For the non-*NIX folks, that is a recursive deletion of all files and folders from the current folder on down. If typed into a terminal window with root privilege at the top of the file system hierarchy, it will dutifully scour the entire system clean!)

"rd /s /q" is the Windows equivalent. Epic!

Flying Fox wrote:

"rd /s /q" is the Windows equivalent. Epic!

"del /s /q" is another fun one.

Flying Fox wrote:

"rd /s /q" is the Windows equivalent. Epic!

Ryu Connor wrote:

"del /s /q" is another fun one.

You guys shouldn't be giving sweatshopking any more stupid ideas to try out.

JustAnEngineer wrote:

Flying Fox wrote:

"rd /s /q" is the Windows equivalent. Epic!

Ryu Connor wrote:

"del /s /q" is another fun one.

You guys shouldn't be giving sweatshopking any more stupid ideas to try out.

He seems to enjoy trashing his system. What's wrong with giving him a little help?

just brew it! wrote:

He seems to enjoy trashing his system. What's wrong with giving him a little help?

I do enjoy it. i like messing it up, and then fixing it. it gives me something to do. it may surprise you, but i don't have that much going on. i take some moocs online, take care of my kids, and clean. a broken computer is a nice puzzle.
i wasnt mad about it either. i knew what i did to break it, and knew the consequences.

and i've mained linux for years. i'm reasonably familiar with it. not to the same level as I am on windows, which to be fair isn't that great, but it's certainly enough.