Author Topic: Used Windows Repair now have issue (Read 19332 times)

kkay · « **on:** January 23, 2014, 08:31:37 pm »

I just used the Windows Repair for the first time. I had used it because I had corrupted files initially. I was having trouble with booting from anti virus rescue disks. I also had trouble with backups. I did a scan with sfc /scannow and it did show it fixed some corrupted files, but some it could not. So I decided to try the Windows Repair program. When I first restarted after it was over, the action center had messages. It said Windows Defender was off. If you click turn on, it takes you to a System 32 file, with folders. I have an anti-virus program, and it is running. (Eset Nod32) I also have Malwarebytes for a back up program. This issue of Windows Defender never came up before. I thought it was off, unless you didn't have an av program running. If you look at the action center flag, now it shows an X for a problem, which before it has always been white, with no warnings you could see, unless you ran over it with your mouse. I don't know yet how everything else is working. I plan to do another sfc /scannow and see what comes up. Any help would be appreciated.

I also wrote down the items Windows Repair had checked, before it started to repair them. I also saved the log, before I rebooted. I will attach that.

I ran the SFC /scannow It shows I still have corrupted files, which really didn't surprise me. But the Tweaking Registry Registry Backup did not start on it's own now. It comes up, but doesn't scan. I have to hit the Backup Now button on lower left. (the gray one) The Action Center says I have no antivirus installed. My Dell says the same thing too. ESET Nod32 is scanning as I type this. So something isn't right.

Update 1-24-14 I ran a chkdsk /scan, then a chkdsk /spotfix, then rebooted, and the spotfix ran. It was working on repairing errors before windows booted. It finished, then booted. I ran sfc /scannow again. Still showing corrupted files. I may have to repair windows with the manufacturer disk I burned. If that copy isn't corrupted, I might be alright. This copy was made after I updated at the store from Win8 to Win8.1 I highly suggested making an ISO file and use that, instead of updating at the store. Windows forced me into the 8.1 update, by graying out everything one day, BUT THE STORE UPDATE. I hope they have changed that policy by now. I don't know how to do a repair with windows dvd, but I am going to try to find out what I can on it.

Shane · « **Reply #1 on:** January 24, 2014, 09:36:12 am »

Can you post the log from the event viewer for the chkdsk? I want to see if there where any bad sectors.

In order to have chkdsk look for bad sectors you have to run the /r

chkdsk C: /r

The scan takes a long time depending on your HD size as it checks every sector. But if you do have bad sectors that would explain why you have corrupt files.

So before we dig in to much lets make 100% sure on whether or not you have bad sectors

Shane

kkay · « **Reply #2 on:** January 24, 2014, 10:08:12 am »

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 1/24/2014 9:54:26 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: ********
Description:

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
328960 file records processed.

File verification completed.
3387 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...
402414 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 2700 unused index entries from index $SII of file 0x9.
Cleaning up 2700 unused index entries from index $SDH of file 0x9.
Cleaning up 2700 unused security descriptors.
Security descriptor verification completed.
36728 data files processed.

CHKDSK is verifying Usn Journal...
41297408 USN bytes processed.

Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

963091455 KB total disk space.
200605844 KB in 195459 files.
118752 KB in 36729 indexes.
0 KB in bad sectors.
468591 KB in use by the system.
65536 KB occupied by the log file.
761898268 KB available on disk.

4096 bytes in each allocation unit.
240772863 total allocation units on disk.
190474567 allocation units available on disk.

Internal Info:
00 05 05 00 fe 8a 03 00 a9 9d 06 00 00 00 00 00 ................
f9 0b 00 00 57 00 00 00 00 00 00 00 00 00 00 00 ....W...........

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-01-24T15:54:26.000000000Z" />
<EventRecordID>59475</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>********</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
328960 file records processed.

File verification completed.
3387 large file records processed.

0 bad file records processed.

Stage 2: Examining file name linkage ...
402414 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 2700 unused index entries from index $SII of file 0x9.
Cleaning up 2700 unused index entries from index $SDH of file 0x9.
Cleaning up 2700 unused security descriptors.
Security descriptor verification completed.
36728 data files processed.

CHKDSK is verifying Usn Journal...
41297408 USN bytes processed.

Usn Journal verification completed.
CHKDSK discovered free space marked as allocated in the volume bitmap.

Windows has made corrections to the file system.
No further action is required.

963091455 KB total disk space.
200605844 KB in 195459 files.
118752 KB in 36729 indexes.
0 KB in bad sectors.
468591 KB in use by the system.
65536 KB occupied by the log file.
761898268 KB available on disk.

4096 bytes in each allocation unit.
240772863 total allocation units on disk.
190474567 allocation units available on disk.

Internal Info:
00 05 05 00 fe 8a 03 00 a9 9d 06 00 00 00 00 00 ................
f9 0b 00 00 57 00 00 00 00 00 00 00 00 00 00 00 ....W...........

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

kkay · « **Reply #3 on:** January 24, 2014, 10:10:42 am »

Thank you for trying to help me. You still want me to run the chkdsk C: /r ??? The event I posted was from this morning.

Shane · « **Reply #4 on:** January 24, 2014, 10:29:56 am »

If you would yes, those other 2 chkdsk dont check for bad sectors. And the scan will take a few hours at least. But at least that way we will know for sure if a bad sector is the cause or not and if there is no bad sectors then we can move on tot he next steps

Also I did find this, which may help you doing a repair install once we make sure there is no bad sectors

http://www.eightforums.com/tutorials/26095-repair-install-windows-8-a.html

Shane

kkay · « **Reply #5 on:** January 24, 2014, 10:49:32 am »

Thank you for that link. So I run it as chkdsk f/r exactly like that? Or is it chkdsk f/r/ ?

Shane · « **Reply #6 on:** January 24, 2014, 10:58:07 am »

OPen cmd.exe window as administrator and do
chkdsk /?

And it will tell you the options.

Quote

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

C:\WINDOWS\system32>chkdsk /?
Checks a disk and displays a status report.

CHKDSK [volume[[path]filename]]] [/F] [/V] [/R] [/X] [/I] [/C] [/L[:size]] [/B]
[/scan] [/spotfix]

volume Specifies the drive letter (followed by a colon),
mount point, or volume name.
filename FAT/FAT32 only: Specifies the files to check for
fragmentation.
/F Fixes errors on the disk.
/V On FAT/FAT32: Displays the full path and name of every
file on the disk.
On NTFS: Displays cleanup messages if any.
/R Locates bad sectors and recovers readable information
(implies /F, when /scan not specified).
/L:size NTFS only: Changes the log file size to the specified
number of kilobytes. If size is not specified, displays
current size.
/X Forces the volume to dismount first if necessary.
All opened handles to the volume would then be invalid
(implies /F).
/I NTFS only: Performs a less vigorous check of index
entries.
/C NTFS only: Skips checking of cycles within the folder
structure.
/B NTFS only: Re-evaluates bad clusters on the volume
(implies /R)
/scan NTFS only: Runs a online scan on the volume
/forceofflinefix NTFS only: (Must be used with "/scan")
Bypass all online repair; all defects found
are queued for offline repair (i.e. "chkdsk /spotfix").
/perf NTFS only: (Must be used with "/scan")
Uses more system resources to complete a scan as fast as
possible. This may have a negative performance impact on
other tasks running on the system.
/spotfix NTFS only: Runs spot fixing on the volume
/sdcleanup NTFS only: Garbage collect unneeded security descriptor
data (implies /F).
/offlinescanandfix Runs an offline scan and fix on the volume.

The /I or /C switch reduces the amount of time required to run Chkdsk by
skipping certain checks of the volume.

C:\WINDOWS\system32>

So all you need to do is

chkdsk C: /R

Windows will say the drive is in use would you like to schedule it, hit "Y" and enter and then the next time you restart it should do the check

Shane

kkay · « **Reply #7 on:** January 24, 2014, 11:07:03 am »

Got it, thank you!!!

kkay · « **Reply #8 on:** January 24, 2014, 06:19:47 pm »

Level Date and Time Source Event ID Task Category
Information 1/24/2014 7:51:44 PM Microsoft-Windows-Wininit 1001 None "

Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.

A disk check has been scheduled.
Windows will now check the disk.

Stage 1: Examining basic file system structure ...
328960 file records processed.
File verification completed.
3387 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
402920 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.

Stage 3: Examining security descriptors ...
Cleaning up 23 unused index entries from index $SII of file 0x9.
Cleaning up 23 unused index entries from index $SDH of file 0x9.
Cleaning up 23 unused security descriptors.
Security descriptor verification completed.
36981 data files processed.
CHKDSK is verifying Usn Journal...
36771984 USN bytes processed.
Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
328944 files processed.
File data verification completed.

Stage 5: Looking for bad, free clusters ...
189588328 free clusters processed.
Free space verification is complete.

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

963091455 KB total disk space.
204152620 KB in 199688 files.
121024 KB in 36982 indexes.
0 KB in bad sectors.
464499 KB in use by the system.
65536 KB occupied by the log file.
758353312 KB available on disk.

4096 bytes in each allocation unit.
240772863 total allocation units on disk.
189588328 allocation units available on disk.

Internal Info:
00 05 05 00 80 9c 03 00 b8 be 06 00 00 00 00 00 ................
ff 0b 00 00 57 00 00 00 00 00 00 00 00 00 00 00 ....W...........

Windows has finished checking your disk.
Please wait while your computer restarts.
"

kkay · « **Reply #9 on:** January 26, 2014, 07:35:29 pm »

I was told by someone to do these actions. This is what I did. It looks like most of my problems might be behind me. (at least the windows corrupted files!!)

dism /online /cleanup-image /checkhealth
It said no component store corruption detected.
The operation completed successfully.

sfc scannow shows corruption

then I did the
dism /online /cleanup-image /restorehealth
It said: The restore operation completed successfully.
The Component Store corruption was repaired. The operation completed successfully.

sfc scannow again:
then it says: Windows Resource Protection did not find any integrity violations!

Shane · « **Reply #10 on:** January 27, 2014, 11:52:21 am »

Very nice

Quote

dism /online /cleanup-image /restorehealth

That is a new option on in Windows 8 and 2012, it isnt in 7 or earlier.

How long did that take to run? I want to see about adding it to the Windows Repair

Shane

kkay · « **Reply #11 on:** January 27, 2014, 12:05:49 pm »

Shane, I cannot remember exactly. It was maybe 10-15 minutes. The chkdsk /r takes forever...about 3-4 hours, and it didn't fix it. So this method is much easier.

Shane · « **Reply #12 on:** January 27, 2014, 12:11:31 pm »

The chkdsk is for checking for hardware problems on the drive, the command you did was a image repair on Windows itself replacing the corrupt files when SFC couldnt. Since this repair is only for Windows 8 it would be easy to add and would give users the option when they dont know about it.

I just have to make sure it is a ok repair to run on a good working system

Shane

kkay · « **Reply #13 on:** January 27, 2014, 12:20:24 pm »

Sounds like a winner to me!

Shane · « **Reply #14 on:** January 28, 2014, 05:01:00 pm »

New version is out

Shane

kkay · « **Reply #15 on:** January 28, 2014, 05:22:27 pm »

Awesome Shane, thank you!