Author Topic: takes all night to apply fixes (Read 55659 times)

qaz · « **on:** July 28, 2016, 01:45:44 am »

hi

using latest all in one repair tool on win 7. [in safe mode] It took all night applying fixes and in morning i had to power off the pc with it still running

i restarted win7 and for a couple of mins after everything loaded it froze with the "working" symbol showing then everything was as normal

can anyone tell me what happened and if any fixes were actually applied and if so which ones. I cant recall the specific problem i wanted to fix as there were many, main problem was administrator permissions, no amount of forum help has been able to fix it. Also programs appear/disappear from task bar, sometimes start with windows/sometimes not

i still cant check win updates as there are controlled by system admin, so that did not get fixed
thanks

Boggin · « **Reply #1 on:** July 28, 2016, 02:47:22 am »

Can you run command prompt as an admin by going Start - type cmd - right click on cmd and select Run as administrator - accept the UAC and enter chkdsk /f

You will be prompted to type and enter y for it to run at the next restart.

Enter shutdown /r /t 00 to effect an immediate reboot and let it do its thing.

It won't take long to run and you will be able to see if it reports it has fixed any corruption and look to see if it reports any KBs in bad sectors.

If you don't get to read it all, go Start - type eventvwr and press enter.

When Event Viewer has read the data, expand Windows Logs - click on the name Application - Action - Find and in the Find box type chkdsk or wininit and press enter.

Cancel the Find box and read the report in the scrollable window.

However, if it reports no KBs in bad sectors and your system is really screwed up then I would consider a factory reset after backing up your personal stuff to external media.

Windows Repair can't fix everything.

qaz · « **Reply #2 on:** July 28, 2016, 03:02:12 am »

hi

the fix all repair program is running again, can i cancel that in order to effect ur instruction

thanks

Boggin · « **Reply #3 on:** July 28, 2016, 03:04:38 am »

Let it run to see it performs any better, but usually when WR takes a long time, it can be because of bad sectors on the HDD.

qaz · « **Reply #4 on:** July 28, 2016, 03:37:53 am »

ah thats interesting as the hd scan showed errors i didn't understand even after fixing some on first run. I didn't specify bad sector check....but will soon as current program finishes

would u be able to tell me how i can tell if any fixes were actually applied and if so which ones [so i will be able to see in future]

thanks

Boggin · « **Reply #5 on:** July 28, 2016, 03:49:48 am »

The chkdsk /f doesn't move anything from the bad areas but will report any bad sectors it finds.

A chkdsk /r will though but data can be lost, so if any bad sectors are found in the chkdsk /f then you should back up immediately, both with a full system image and with your personal stuff separate - you will also need to create a system repair disk as you will have to boot up with that to put your image onto a new HDD.

If you are using an OEM machine, then it may be too late to create the Recovery Disks which will be a copy of the Recovery Partition, unless you have already created them and then you would be able to factory reset the machine with those and then put your own stuff back on.

qaz · « **Reply #6 on:** July 28, 2016, 05:03:55 am »

thanks for clearing up the /r and /f options. Will post results here soon as poss

qaz · « **Reply #7 on:** July 29, 2016, 04:13:11 am »

hi

i did that and there are no bad sectors but it says to do chkdsk/r. So thats done now but and having trouble at the log viewer finding the report.

as i couldnt find the log i ran chkdsk again but in non repair mode, heres the log. Would be much appreciated if u could interpret any important parts

thanks

Log Name: Application
Source: Chkdsk
Date: 27/07/2016 11:17:54
Event ID: 26213
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: river
Description:
Chkdsk was executed in read-only mode. A volume snapshot was not used. Extra errors and warnings may be reported as the volume may have changed during the chkdsk run.

Checking file system on G:
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 New Volume.

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

CHKDSK is verifying files (stage 1 of 3)...
238848 file records processed.

File verification completed.
1049 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
Unable to locate the file name attribute of index entry reg_cfg.da0
of index $I30 with parent 0x24c9c in file 0x2065.

Index entry reg_cfg.da0 in index $I30 of file 150684 is incorrect.
Index entry reg_cfg.dat of index $I30 in file 0x24c9c points to unused file 0x20ab.
Index entry reg_cfg.dat in index $I30 of file 150684 is incorrect.
Unable to locate the file name attribute of index entry reg_cis.da0
of index $I30 with parent 0x24c9c in file 0x1a8.
Index entry reg_cis.da0 in index $I30 of file 150684 is incorrect.
The file reference 0xf40000000011c8 of index entry reg_cis.dat of index $I30
with parent 0x24c9c is not the same as 0xd70000000011c8.
Index entry reg_cis.dat in index $I30 of file 150684 is incorrect.
Unable to locate the file name attribute of index entry reg_mod.da0
of index $I30 with parent 0x24c9c in file 0x2067.
Index entry reg_mod.da0 in index $I30 of file 150684 is incorrect.
Index entry reg_mod.dat of index $I30 in file 0x24c9c points to unused file 0x20a5.
Index entry reg_mod.dat in index $I30 of file 150684 is incorrect.
306370 index entries processed.

Index verification completed.

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

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Chkdsk" />
<EventID Qualifiers="0">26213</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-07-27T10:17:54.000000000Z" />
<EventRecordID>28103</EventRecordID>
<Channel>Application</Channel>
<Computer>river</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on G:
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 New Volume.

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

CHKDSK is verifying files (stage 1 of 3)...
238848 file records processed.

File verification completed.
1049 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 3)...
Unable to locate the file name attribute of index entry reg_cfg.da0
of index $I30 with parent 0x24c9c in file 0x2065.

Index entry reg_cfg.da0 in index $I30 of file 150684 is incorrect.
Index entry reg_cfg.dat of index $I30 in file 0x24c9c points to unused file 0x20ab.
Index entry reg_cfg.dat in index $I30 of file 150684 is incorrect.
Unable to locate the file name attribute of index entry reg_cis.da0
of index $I30 with parent 0x24c9c in file 0x1a8.
Index entry reg_cis.da0 in index $I30 of file 150684 is incorrect.
The file reference 0xf40000000011c8 of index entry reg_cis.dat of index $I30
with parent 0x24c9c is not the same as 0xd70000000011c8.
Index entry reg_cis.dat in index $I30 of file 150684 is incorrect.
Unable to locate the file name attribute of index entry reg_mod.da0
of index $I30 with parent 0x24c9c in file 0x2067.
Index entry reg_mod.da0 in index $I30 of file 150684 is incorrect.
Index entry reg_mod.dat of index $I30 in file 0x24c9c points to unused file 0x20a5.
Index entry reg_mod.dat in index $I30 of file 150684 is incorrect.
306370 index entries processed.

Index verification completed.

Errors found. CHKDSK cannot continue in read-only mode.
</Data>
<Binary>00A50300EE2F03009ECF050000000000BB0300003C0000000000000000000000</Binary>
</EventData>
</Event>

Boggin · « **Reply #8 on:** July 29, 2016, 05:25:52 am »

That doesn't look too healthy if you've run that after a chkdsk /r

Are you sure it told you to run with the /r switch or was it with the /f switch ?

Go back into Event Viewer/Windows Logs/Application and scroll down until you see entries for wininit

Your latest in read-only mode will be the first one you see, but check lower down for one with the time stamp for when you ran the chkdsk /r

You'll know when you run a chkdsk /r because there are 5 stages as opposed to just the 3 when you use /f

Depending upon what the wininit log says, you could be looking at a factory reset or repair install.

qaz · « **Reply #9 on:** July 29, 2016, 06:01:16 am »

hi

i find the log viewer to difficult, i may will run chkdsk/r again tonight , but PLS can u tell how to see the results as a could not find then last time

am trying again to find the entry. what window should i be looking in for winit, is it the one with "level" colum on left , and almost 30,000 entry's and mostly named "information" . am i in the right place?

thanks again

Boggin · « **Reply #10 on:** July 29, 2016, 08:28:54 am »

When you go into Event Viewer, ensure that Event Viewer (Local) at the top of the left pane is highlighted then wait for it to read the data.

Use the arrow next to Windows Logs in the left pane to expand that section then click on Application.

They are listed as Information so it sounds like you are in the right place where you should see an entry for wininit or it may be listed as Chkdsk.

Click on it and the report will appear in the scrollable window below.

qaz · « **Reply #11 on:** July 29, 2016, 03:41:56 pm »

hi

thanks for the above

first i deleted all logs then ran chkdsk /r but it only took a short time to complete. This s what i got, would be very interested to know what u think as it has done no repairs and found no errors, i dont understand why this is as it was bad before, any ideas?

one problem i have is with the letter assigned to the system [only] hd, it cant be changed to "c" . Somewhere i screwed it up it seems
thanks :

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 29/07/2016 23:06:11
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: river
Description:

Checking file system on G:
The type of the file system is NTFS.
Volume label is New Volume.

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

CHKDSK is verifying files (stage 1 of 5)...
238848 file records processed.

File verification completed.
705 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
306112 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
238848 file SDs/SIDs processed.

Cleaning up 72 unused index entries from index $SII of file 0x9.
Cleaning up 72 unused index entries from index $SDH of file 0x9.
Cleaning up 72 unused security descriptors.
Security descriptor verification completed.
33633 data files processed.

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
238832 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
6944176 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

128024572 KB total disk space.
99800044 KB in 175743 files.
104432 KB in 33634 indexes.
0 KB in bad sectors.
343392 KB in use by the system.
65536 KB occupied by the log file.
27776704 KB available on disk.

4096 bytes in each allocation unit.
32006143 total allocation units on disk.
6944176 allocation units available on disk.

Internal Info:
00 a5 03 00 ec 31 03 00 9d d8 05 00 00 00 00 00 .....1..........
5a 03 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 Z...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

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="2016-07-29T22:06:11.000000000Z" />
<EventRecordID>28618</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>river</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on G:
The type of the file system is NTFS.
Volume label is New Volume.

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

CHKDSK is verifying files (stage 1 of 5)...
238848 file records processed.

File verification completed.
705 large file records processed.

0 bad file records processed.

2 EA records processed.

60 reparse records processed.

CHKDSK is verifying indexes (stage 2 of 5)...
306112 index entries processed.

Index verification completed.
0 unindexed files scanned.

0 unindexed files recovered.

CHKDSK is verifying security descriptors (stage 3 of 5)...
238848 file SDs/SIDs processed.

Cleaning up 72 unused index entries from index $SII of file 0x9.
Cleaning up 72 unused index entries from index $SDH of file 0x9.
Cleaning up 72 unused security descriptors.
Security descriptor verification completed.
33633 data files processed.

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

Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
238832 files processed.

File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
6944176 free clusters processed.

Free space verification is complete.
Windows has checked the file system and found no problems.

128024572 KB total disk space.
99800044 KB in 175743 files.
104432 KB in 33634 indexes.
0 KB in bad sectors.
343392 KB in use by the system.
65536 KB occupied by the log file.
27776704 KB available on disk.

4096 bytes in each allocation unit.
32006143 total allocation units on disk.
6944176 allocation units available on disk.

Internal Info:
00 a5 03 00 ec 31 03 00 9d d8 05 00 00 00 00 00 .....1..........
5a 03 00 00 3c 00 00 00 00 00 00 00 00 00 00 00 Z...<...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

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

Boggin · « **Reply #12 on:** July 29, 2016, 04:14:30 pm »

When you run chkdsk in read-only mode, if anything is being written to the HDD at the time then that can report false errors.

The reason WR was running slow could have been because the path to the system files would not have been C:

If this is an OEM machine you are using then I would suggest backing up your personal stuff to an external HDD and then factory reset.

This will take it back to out of the box and set the partition letters back to the way they should be.

It will be time consuming as you will have the likes of Adobe and Java products to uninstall and then go to www.adobe.com and www.java.com for the latest versions, your personal stuff to drag & drop back in and then there are Windows Updates which can be a PITA.

Following a factory reset on this machine prior to upgrading to Win 10, there were about 260 of them which totalled in excess of 1.3GB to download and install.

What were you doing to change the system partition to G: ?

qaz · « **Reply #13 on:** July 30, 2016, 01:01:27 am »

i cant understand why u suggest backing up your personal stuff to an external HDD and then factory reset. doesn't everything look ok now? or am i missing something

what do u see as being wrong in the log?

its not qem and is nothing to do with manufacturer now
personal data is always on usb disk
system backup is also saved, Aomei claims it can transfer to a new disc even on another machine
win 7

interesting what u say about WR running slow , it had crossed my mind
the system drive is called G , i was tyring to change the letters over a year back when i had 2 drives plus a usb one

id still like to know how i can tell if WR fixed anything

thanks

qaz · « **Reply #14 on:** July 30, 2016, 01:25:09 am »

Quote from: qaz on July 30, 2016, 01:01:27 am

i cant understand why u suggest backing up your personal stuff ....etc. doesn't everything look ok now? or am i missing something

what do u see as being wrong in the log?

if i right click on system drive windows explorer stops working, could this be a clue

i just tryed to change system drive letter again, i got parameter is incorrect

also system drive was not set as active, it is now

its not qem and is nothing to do with manufacturer now
personal data is always on usb disk
system backup is also saved, Aomei claims it can transfer to a new disc even on another machine
win 7

interesting what u say about WR running slow , it had crossed my mind
the system drive is called G , i was tyring to change the letters over a year back when i had 2 drives plus a usb one

id still like to know how i can tell if WR fixed anything

thanks

Boggin · « **Reply #15 on:** July 30, 2016, 02:00:56 am »

If you are happy with the way things are then you can leave it, but usually to get the system partition back to C: you would normally have to either factory reset or reinstall.

You say you are unable to resolve the Permissions issue regarding updates but not what the other problems were that you were trying to fix.

If they are still unresolved then going back to the beginning should resolve all of your problems.

qaz · « **Reply #16 on:** July 30, 2016, 02:30:06 am »

do u think the last scan fixed any thing

do u know how i can tell if WR fixed anything. Or do i waste time running it again. I keep asking this so could u please tell me that its either not an answerable question or not nessacary for me to know

Is there a way the change the drive letter without reinstall . I really don't want that

Boggin · « **Reply #17 on:** July 30, 2016, 05:26:46 am »

If you are no longer getting the problems you did prior to running WR then it will have fixed them, but Shane advises running WR twice.

As for changing the drive letter back to C: I came across this Google link with bcdedit commands in Post #6 which you may have to modify to suit your situation.

https://forum.acronis.com/forum/34337

It's also possible that a repair install may put it right which you could try.

http://www.sevenforums.com/tutorials/3413-repair-install.html

qaz · « **Reply #18 on:** July 30, 2016, 07:22:22 am »

thanks very much 4 your help and finding the articles, hopefully i can take it from here

mark

Boggin · « **Reply #19 on:** July 30, 2016, 07:25:00 am »

Okay, but let us know how you get on as your experience could help others.

qaz · « **Reply #20 on:** July 30, 2016, 01:11:12 pm »

boot manager broke earlier, i used win 7 disk to do a startup repair and now i have C drive. Can u say if i can put the os onto this c drive please

qaz · « **Reply #21 on:** July 30, 2016, 01:16:05 pm »

Boggin · « **Reply #22 on:** July 30, 2016, 01:38:46 pm »

No, you can't.

That is the system recovery partition and it shouldn't have a drive letter, besides, it's only 100MB.

You should remove the drive letter from there but I still don't think you will be able to change G to C

I'm just wondering if Startup Repair assigned that partition as C

You can use an install disk to boot up with and from the command prompt in there, you can use the bootrec commands to repair/rebuild the boot manager but I don't think it will assign it back to C.

http://www.sevenforums.com/tutorials/20864-mbr-restore-windows-7-master-boot-record.html

You may have to give those bcdedit commands a go or reinstall.

qaz · « **Reply #23 on:** July 31, 2016, 01:41:24 am »

yes it must have startup repair that assigned the c label , i didnt

ur right it still wont let me change it, i had thought that maybe i could just expand c: , stick the system backup on it that i have, and set it as active. ...i know thats a bit simplistic ha ha

the installation disc would not allow me to follow MS's own instructions to repair startup,[although im starting to wonder if it was just me] but by removing the disc at one point i got there. It took 2 goes to fix it. Am not keen to use it again as u suggest but will take a look

if i formatted and reinstalled windows do u think the AOMEI system backup [or a mirror image] could be put onto the partition to replace the new installation, thus giving me a c drive again and my old os intact

am glad to have windows back again, maybe its time to re install the os

will look at the link u gave me
thanks

Boggin · « **Reply #24 on:** July 31, 2016, 02:04:41 am »

I'm not sure if a repair install will do it because that just repairs the OS in situ as far as I know, so it could remain as G

You may need to wipe and do a clean install.