(08-19-2011, 01:16 PM)Kom Wrote: [ -> ]Ew >.> why would you send your stuff into geek squad... they know absolutely nothing at all.
If you could follow the steps were asking you to follow, we can sort this out (possibly)
run check disk if you can - chkdsk in command promt as admin
That's probably not going to do anything, that's more for hard drive related errors, specifically for corrupt sectors mainly is what that would be used for. System File Checker is the main guy you want to call at this point, but if something corrupted that, then you'll have to find another alternative.
(08-19-2011, 01:25 PM)Ace Wrote: [ -> ]That's probably not going to do anything, that's more for hard drive related errors, specifically for corrupt sectors mainly is what that would be used for. System File Checker is the main guy you want to call at this point, but if something corrupted that, then you'll have to find another alternative.
Well it's good to run just to make sure it's not his hard drive corrupting / has any bad sectors first =/
(08-19-2011, 01:16 PM)Kom Wrote: [ -> ]Ew >.> why would you send your stuff into geek squad... they know absolutely nothing at all.
If you could follow the steps were asking you to follow, we can sort this out (possibly)
run check disk if you can - chkdsk in command promt as admin
Dad made me but
http://snpr.cm/fyWwQp.png
Really? Take a look at your System32 folder, for chkdsk.exe. And also sfc.exe, and let us know if it's there. From what i'm seeing it's not seeing them.
I found "chkdsk.exe" and ran it, made "chkdsk.exe.mui".
Then "sfc.exe" and ran it, made "sfc.exe.mui".
They won't run like that, they need to be interpretted though a command line:
Try this:
Code:
C:\Windows\System32\sfc.exe /scannow
Same thing happened, it just loaded then closed.
Check the modification date to that file. Your system file checker is corrupt lol. Seems to be the same thing with most of your files in your folder there. You have an installation disk? Run that on boot and choose the option for CMD, and run a few commands through. Otherwise, use the System Repair option like I mentioned before, Reboot, and run it again for the changes to take effect. Run in Safe mode, and open a console for command prompt, and check to see if your system file checker will work. If it finds no integrity errors, then boot back into normal mode.
(08-19-2011, 02:02 PM)Ace Wrote: [ -> ]Check the modification date to that file. Your system file checker is corrupt lol. Seems to be the same thing with most of your files in your folder there. You have an installation disk? Run that on boot and choose the option for CMD, and run a few commands through. Otherwise, use the System Repair option like I mentioned before, Reboot, and run it again for the changes to take effect. Run in Safe mode, and open a console for command prompt, and check to see if your system file checker will work. If it finds no integrity errors, then boot back into normal mode.
1. It was around the same date I sent it to Geek Squad.
2. No inst. disc. was installed when we bought it like this.
Since it's on their hands, whoever you gave it to should be fired lol... I'd honestly rather give over my computer to my little nephew to play around with with my system32 folder open, because whatever the person did just proves that he/she had no f*ckin idea for what they were doing lol. Wow... Managed to completely screw up your System32 files somehow. Take it back and explain that to them, you should demand a refund. I don't know how you're going to get the files back to a clean state with no installation disk, do you have a disk given to you for a system recovery? With Windows 7 you can make your own, but that's meant to be done when you first get your computer so that all the files are in pristine condition.
Try saving this as a .bat on your desktop, run it, and return what your the newly created file says in your next post; sfc_log.txt.
Code:
@echo off
sfc /scannow > sfc_log.txt