[SOLVED] Any techie types able to help me save my comp? Hi, hoping some of you technically-minded folks on here might have some ideas that will help me. Basically, I can't run anything that requires administrator permissions, even though I am the administrator. This means I can't remove installed programs, can't use system restore, chkdisk, defragment, restore factory settings or anything else of the nature. It also means I can't install or run any programs designed to fix the problem. Error code: 0x8007000E And no, it's not to do with Outlook, which I don't even have. I suspect it's been caused by one of my programs corrupting system files. How it happened: I was playing Maple Royals, and suddenly my internet died and I dc-ed. I restarted my computer only to find that I was getting error messages about Comodo firewall. Uninstalled it and installed the latest version, only to have my comp be completely useless, as described above. OS: Windows 7 (Ultimate)
Do you not have Outlook as in you don't have an account and don't use it, or do you not have Outlook as in you've removed it from your computer? Anyway, if it's the former I think your reinstalling of Comodo Firewall may have integrated CF with Outlook. Remove/uninstall the integration part of CF and see what happens. If you're able to uninstall/remove it. And umm, on my shitty Vista OS sometimes it would ask for the administrator (even though I was) when I just clicked on something rather than right-clicking and selecting "Run as admin..." But yeah I'm not very techie, but until someone else with more knowledge comes along I thought I'd try to help.
*Huggles Toby* Thanks for trying to help, and as for Outlook, I don't think it was ever installed on my comp, as I didn't have any use for it. (I use Thunderbird or Gmail for email.) Can't Remove/Uninstall any part of CF, unfortunately, as I don't have the required permissions blah blah blah, ie it isn't recognising me as the administrator.
Type cmd in your start menu. Right click and run as admin (if this doesn't have permission let me know) Type : net user administrator /active Otherwise Boot in safemood (press f8 on boot usually.) Enter the admin account (should have no pass by default) Go to users and accounts and make your account a normal user, then an admin again. Also make a second admin account incase your account won't work. If these basics don't work, then we'll need to check for a virus or malware.
Sounds like your registry might be corrupt somehow. I don't know if you can but you should try to get CCleaner http://www.piriform.com/ccleaner to clean up your registry files.
I was actually looking into a similar problem the other day. Try looking into fixing corrupt user profiles if none of the above works for you. Let me know how it goes/if you need any help!
Feedback to follow shortly - right now, my illness is flattening me and I need to go to bed, but just wanted to let you all know I'm not ignoring you!
Apologies for the double post, and here's the feedback to recent advice: @Blink: Unfortunately, I can't run cmd as administrator. The comp won't let me run *anything* as administrator. >_< I've tried 3 different ways of trying to boot into safe mode, none of which work. =( F8, which I'm sure is the right key and which Windows help and support also suggests I use, sadly does nothing. Hitting esc as soon as the comp boots up brings up a menu of options, including "boot options". This, unfortunately, doesn't help, as the only options it gives me are which device to boot from. (If the worst comes to the worst, I guess this allows me to boot from the recovery CDs - at least I hope it does!). And then there's the option to select booting up in safe mode, prior to shutting the comp down, but guess what? Yup, I need to have admin priviledges to do this! >_< @Matt: downloaded it but can't install it as I need administrator priviledges to do so! Thanks anyway! @Faye: Most of the information about repairing corrupted user profiles that I've come across seems to only apply to non-administrator accounts. I've only got one account on this comp, and that's the administrator account. Any hints and tips you could give would be gratefully received! Thanks very much all 3 of you for your suggestions. My son, who has a degree in Computer Science and Maths (plus a postgraduate degree in Games Design) and currently works as a Games Programmer has also Googled extensively for answers and after trying assorted things, none of which worked, concluded that we should probably choose a goat to sacrifice to a deity of our choice!! Either that or call in the professionals, ie PC World. This is proving so frustrating, as almost every possible solution seems to be thwarted by the problem itself! >_<
I had this or a similar problem on my old pc. I created a new user profile. Migrated all my stuff to that one. And deleted the old one. Either that or I re-installed Windows.
Open my computer. Right click C: and go to properties. In the security tab go down and click advanced. Click the owner tab. If it's not you click edit and choose Administrators ("your pc name"/Administrators) and take ownership. Press okay close everything then open it all up and this time look at the permissions screen. Click change permissions and choose your admin account and click edit. Click full control and press okay. Restart your PC and you should have all admin permissions. This should definitely work because there's a very common malware which changes the owner of your PC. If it doesn't however, you'll have to migrate this account. You can do this more easily by typing UAC in your start menu and turning UAC off. Then run cmd as admin and type net user administrator /active:yes
@Blink - it won't let me do either of these things as I need admin priviledges to do them =( Thank you for trying to help, though!
Hopefully this will be the final update I need to add to this thread: Problem appears to be solved! I eventually managed to access System Restore by using the System Recovery disks that I created when the comp was new. I was then able to run CHKDSK and discovered that the likely cause of the problem was data in bad sectors. I checked the option marked "Scan for and attempt recovery of bad sectors", so hopefully Windows now knows not to allocate further data to these bad sectors.
