Taking ownership is easy; my concern would be that other permissions were overwritten as well. Not all objects should be owned by a user, either. TrustedInstaller, for example, is the owner of most system files.
Maybe I've just gotten to where I don't tolerate quirky or odd machines. I will rebuild a system any time I have any reason to be suspect of it--and that includes any time it's infected with a piece of malware. Greg > > > Should be easy to fix... > > Start an elevated cmd > > then run: > > takeown /f <FULL FILE PATH> > > > Or if you prefer the GUI: > http://www.vistax64.com/tutorials/67717-take-ownership-file.html > > I like method 2 option 2. > > > Christopher Fisk > -- > Book: "That bad?" > Zoe: "Battle wounds are nothing new to me, preacher. I've seen men live > with a dozen holes in 'em this size." > Book: "That right?" > Zoe: "Surely is. Knew a man once who had a hole clean through his whole > shoulder. Used to keep a spare hankie in there." > --Episode #5, "Safe" > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean.
