HELP PLEASE BEFORE IS TOO LATE/RAN COMBOFIX DON'T KNOW WHAT TO DO

[REDACTED]

ESSEXBOY

I thought factory default should be the last option . only after everything fails. but that's what EXPERTS SAY. AT LEAST SOME. BUT OTHERS WHO HAVENT LOOKED AT THIS POOR MACHINE, GIVE IT AS FIRST OPTION. IS THE EASY WAY OUT.

FINE. I WILL GOOGLE AND LEARN, AND THEN FIX. WITHOUT YOUR HELP.

DONT FORGET THE HARM YOU HAVE CAUSED TO MY, SONY VAIO, THE "WONDER F.....TOOL" HAS FAILED TO SCAN 500.000 KB OF FILES AND RAN REPAIR OF REPARSE POINTS , WHICH THE TOOL SAID ARE MISSING, AND RAN ENVIRONMENT VARIABLES REPAIR WHICH COULD HAVE BEEN DIFERENT HAD THE F.....TOOL YOU GAVE ME SCANNED ALL FILES THAT CMD PROMPT IDENTIFIED.

TO EVERYONE ELSE - DONT LISTEN TO WINDOWS ALL IN ONE OR, SHOULD I SAY WHOEVER ASKS YOU TO UUSE THIS TOOL[/color]

[essexboy]

It is not the programme at fault but the fact that your system was corrupted as you have been told many times.  Use of registry cleaners and optimisers is what probably got you into this situation in the first place

When you have re-installed please do not use them

[Michael (alan1998)]

Right. Deleted.

[REDACTED]

Essexboy,

" It is not the programme at fault but the fact that your system was corrupted " Let me tell you something: HOW CAN YOU SAY CORRUPTED WHEN I HAVE BEEN RUNNING SFC AND CHKDSK SO MANY TIMES AND POSTING RESULTS WHERE CMD PROMPT CLEARLY SAYS "

"Windows has checked the file system and found no problems.". askey127 GAVE ME THE SAME EXCUSE, IS IT COMMON PRACTICE THAT WHEN YOU HAVE NO REASONABLE EXPLANATIONS FOR YOUR ERRORS YOU COME UP WITH THIS EXCUSE?

HERE:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>chkdsk
The type of the file system is NTFS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  296448 file records processed.
File verification completed.
  546 large file records processed.
  0 bad file records processed.
  0 EA records processed.
  81 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  352930 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  296448 file SDs/SIDs processed.
Security descriptor verification completed.
  28242 data files processed.
CHKDSK is verifying Usn Journal...
  36747208 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

 165824855 KB total disk space.
  77717428 KB in 136861 files.
     85136 KB in 28243 indexes.
         0 KB in bad sectors.
    404463 KB in use by the system.
     65536 KB occupied by the log file.
  87617828 KB available on disk.

      4096 bytes in each allocation unit.
  41456213 total allocation units on disk.
  21904457 allocation units available on disk.

C:\Windows\system32>

THERE IS NO CORRUPTION IN MY SYSTEM!!!!!!!!!!!!!!  YOUR TOOL HAS MESSED MY PC A LITLE BIT MORE, AND I HAVE ASKED YOU POLITELY :

HOW TO REVERT STEP 3. AND YOU DON'T HAVE THE ANSWER, NOR THE TIME. FINE, THEN!!!!!!

[/BUT DON'T SAY IS CORRUPTED, BECAUSE IT IS NOT!

.

NOTE: I RAN THE SFC AND CHKDSK FROM THE TOOL AND 3 SECONDS AFTER RAN SFC AND CHKDSK FROM COMMAND PROMPT, SO THERE WAS NO TIME FOR "SMALL FILES TO BE CREATED" MR TEACHER ESSEXBOY.YOU CALL 500.000 KB SMALL, FINE. I THINK EVEN IF IT 100 BYTES OF INFORMATION, A WHOLE SYSTEM MAY NOT BOOT. THE TOOL SAID , AFTER RUNNING CHKDSK - WINDOWS ALL IN ONE HAS FOUND CORRUPT FILES AND FIXED THEM" THERE WAS NO CORRUPTION ACCORDING TO CHKDSK RAN VIA CMD PROMPT.WHAT DID THE TOOL FIX??? OR MESSED?
[/b]

AND DISRUPTIVE FOR WHAT??? FOR KEEPING ESSEXBOY UPDATED? ARE WE NOT MEANT TO PROVIDE AS MUCH INFORMATION AS POSSIBLE? OH, I FORGOT, "YOU RATHER KNOW 2 SYMPTOMS AND SEND THEM HOME WITH PARACETAMOL", AND ARE WE NOT ALLOWED TO ASK QUESTIONS? OR YOU PREFER "DUMMIES" WHO KNOW NOTHING SO YOU CAN TELL THEM: "YOUR SYSTEM IS CORRUPTED, IS FROM THE REG USERS, IT WASN'T ME OR MY TOOL" EVEN THOUGH THE SFC WHICH MEANS - SYSTEM FILE CHECK IS SAYING "NO ERRORS" AND CHKDSK WHICH MEANS CHECK DISK IS ALSO SAYING WINDOWS HAS FOUND NO INTEGRITY ERRORS.

I HAVE ALL GOOD REASONS TO BE UPSET, WITH THE MAGIC TOOL ESSEXBOY HAS ASKED ME TO USE.
I HAVE WORKED FOR ONE YEAR DOUBLE SHIFTS (14HOURS SHIFTS) TO GATHER £800.00 TO BUY THIS MACHINE IN 2010. I HAD SEEN THE PRICE IN JANUARY 2009, IN DECEMBER I HAD THE MONEY SAVED, BUT I DECIDED TO WAIT TILL JANUARY 2010, AT WHICH POINT SONY PUT THIS MACHINE £300.00 DOWN. SO EVEN THOUGH I HAD THE £800.00 I PAID £500.00. I WORKED VERY HARD FOR IT, AND PUT UP WITH A LOT OF "SHIT FROM CO-WORKERS", AND WHEN I BUY SOMETHING I MAKE SURE I CARE FOR IT. I WILL FIX THIS POOR MACHINE, SHE WILL BE FINE. THANKS FOR MESSING HER A BIT MORE, THEN SHE WAS. I WILL MAKE HER WORK WITHOUT FACTORY RESTORE. FACT RESTORE MAY NOT EVEN WORK, BECAUSE OF MANY OLD PROGRAMS WHICH CANNOT BE RUN /UPDATED, BECAUSE SONY IS NO LONGER USING THEM.
19ROSH

[essexboy]

I only use a re-install as a last resort. I believe that I have used that maybe 5 times in the last 10 years when I have repaired mayhap a few thousand systems

You seem intent on blaming everyone but yourself..  Well so be it, I have broad shoulders. 

[REDACTED]

ESSEXBOY,

Right from the beginning I have accepted "I have combofix on my laptop and all I know Now is that I should have not used it unless instructed. " that we make mistakes, fine, I shouldn't have used the registry cleaners, I shouldn't have used the ComboFix, but that is why you are here, to help us. That is why we come here, to be helped. Not to leave from here with more problems. What on Earth were you thinking when you asked me to use that tool? You knew I had used Combofix and then used CTCleanit to get rid of it, you knew I had changed ownership, and permissions. Then everyone says you are the best and you know what you are doing, so I went ahead and went up to step 3 of the tool, but I felt great discomfort that the tool may not work, and then when I came across with the diference in chkdsk, I realized I should have not used the tool. Perhaps the tool DOES have some problem, which I am 100% sure it has. But you don't want to accept that. Try on your system, run sfc and chkdsk, and then run it from cmd prompt, and see if the number of files checked is the same. Would you actually run it if you had come across that difference in your own machine???

[essexboy]

At no stage were any significant changes made by the windows all in one

So the problems were pre-existant.  Chkdsk done by either windows or the all in one tool makes no difference as they both use the windows built in tool

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)>CD /D C:\

C:\>set path=%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem

C:\>chkdsk C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.
Volume label is OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...
Progress: 659456 of 659456 done; Stage: 100%; Total: 34%; ETA:   0:00:31 ...
                                                                                       
                                                                                       
  659456 file records processed.                                                       

File verification completed.
Progress: 7255 of 7255 done; Stage: 100%; Total: 30%; ETA:   0:00:36   
                                                                                       
                                                                                       
  7255 large file records processed.                                   

Progress: 0 of 0 done; Stage: 99%; Total: 30%; ETA:   0:00:36 . 
                                                                                       
                                                                                       
  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
Progress: 623476 of 756382 done; Stage: 82%; Total: 59%; ETA:   0:00:14 ..

Error detected in index $I30 for file 30.
Error detected in index $I30 for file 30.
Error detected in index $I30 for file 30.
Progress: 756382 of 756382 done; Stage: 100%; Total: 80%; ETA:   0:00:32 . 
                                                                                       
                                                                                       
  756382 index entries processed.                                                       

Index verification completed.

Errors found.  CHKDSK cannot continue in read-only mode.

C:\>

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk
The type of the file system is NTFS.
Volume label is OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

Stage 1: Examining basic file system structure ...


  659456 file records processed.

File verification completed.


  7255 large file records processed.


  0 bad file records processed.

Stage 2: Examining file name linkage ...


  756382 index entries processed.

Index verification completed.


  0 unindexed files scanned.


  0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.


  48464 data files processed.
CHKDSK is verifying Usn Journal...


  33647192 USN bytes processed.

Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

 483194879 KB total disk space.
 158787788 KB in 282503 files.
    155524 KB in 48465 indexes.
         0 KB in bad sectors.
    789591 KB in use by the system.
     65536 KB occupied by the log file.
 323461976 KB available on disk.

      4096 bytes in each allocation unit.
 120798719 total allocation units on disk.
  80865494 allocation units available on disk.

C:\WINDOWS\system32>

[REDACTED]

Errors found.  CHKDSK cannot continue in read-only mode.

C:\>
The above is quoted from your post. So How do you explain, (so that I can understand, and not get all worked up, due to lack of knowledge) that chkdsk ran twice , the day before I ran the tool and again just between step 2 and 3 (I think) I ran chkdsk from cmd prompt again, and then from the tool, How do you explain that one (cmd prompt) says there are no errors. Even the one I had ran the day before, said there was no errors/corruption, and then when ran from the tool, it says it has found corrupted files and fixed it? which message are you going to follow?put your trust in?the first or the second? both were run in between 3 seconds.

And, why the log says

CHKDSK is verifying Usn Journal...
99 percent complete. (0 of 35458368 USN bytes processed)       
100 percent complete. (35454976 of 35458368 USN bytes processed)       
  35458368 USN bytes processed.                                           

Usn Journal verification completed.
The master file table's (MFT) BITMAP attribute is incorrect.
The Volume Bitmap is incorrect.
Windows found problems with the file system. <----------------------------- NOTE
Run CHKDSK with the /F (fix) option to correct these.

 165824855 KB total disk space.
  73232624 KB in 138034 files.
     86400 KB in 28533 indexes.
         0 KB in bad sectors.
    403347 KB in use by the system.
     65536 KB occupied by the log file.
  92102484 KB available on disk.

      4096 bytes in each allocation unit.
  41456213 total allocation units on disk.
  23025621 allocation units available on disk.

The above is from Windows All In One Full Log. Why does it say to run chkdsk with F Option to Fix, when the tool gave me a message that it"has found corrupted files and fixed them"? Because that was the message it gave me straight after running chkdsk.
Can't you see there is something wrong with this tool? The tool FIXED the corrupted files, and is telling me to run it again with F Option?

Again, quote "Errors found.  CHKDSK cannot continue in read-only mode." the tool could not continue, meaning that to finish the process, it had to run the fix. So why is it telling me to run a Fix? Independent of this, there was no corrupted files run from cmd prompt!!!

[essexboy]

C:\>chkdsk C:
The type of the file system is NTFS.
The volume is in use by another process. Chkdsk
might report errors when no corruption is present.

The volume was still mounted and windows all in one only uses read mode

[REDACTED]

thank you for making it clear. If you had explained this to me 3 or 4 posts ago, it would have been much easier and avoided a lot of misunderstandings. So, the tool could very well be right...

I don't understand, If it could report errors when there is no corruption, then what did the tool FIX?

[essexboy]

Nothing was actually fixed at this stage

[REDACTED]

ok. fine. thank you for your time and patience.

hope you have a good weekend, God bless you.

The tool did give me a message saying that found corrupted files and they were fixed, but let's leave it , I will sort it out...
19rosh