Having an issue

[Soreloser]

I installed the all in one repair program last week and it seems to be doing a good job of repairing what was wrong with my system. I still have some problems and just don't know for sure what to do about them. One of the repairs is called "restore important windows services". When I looked at the repair logs, it said Error:  The system cannot find the file specified on the first line, Error:  The file or directory is not a reparse point on the second line, Error:  The system cannot find the file specified again on the third line, then Error:  The file or directory is not a reparse point the rest of the way down the page. I am wondering just what were the services that the repair was trying to restore, and how would they have been deleted, how is my windows working without these services, and how do I put them back? Lotsa questions huh? I appreciate any help you could give . Thanks, Soreloser.

[Shane]

You can ignore those errors in the logs. One of the commands I have it do is remove any junction points created on the windows defender folder and the service keys. Some viruses add junktion points to them so that they get redirected to a different location. So I try to remove them and if there are no junction links on them then you get that error in the log

What problems are you still having with windows?

Shane

[Soreloser]

Still having issues with freezing up during some programs. Picture Viewer sometimes loads very slow and sometimes quits. When I try to close it with task manager it says "com surrogate" has stopped responding. I have since found out that this is part of WMI, which on going back through the logs created by your program, is something it was trying to fix. I guess there isn't a way to reload these files without installing windows again? I am getting that these WMI files keep track of everything going on in windows. Could it be that there are too many services and programs running for it to keep up? I would appreciate any help. Thanks, Soreloser

Jun 23
 I'm back like a bad penny. I have another question. When I go to device manager and open the UMBus root enumerator, virtual drive enumerator,composite bus enumerator, iSCSI initiator, ancillary driver for winsock, and several more devices, (nearly all of the hidden ones) there is on the general screen a spot for location. All of those mentioned have unknown written in. Guess I'd like to know if that is causing me trouble? Thanks again, Soreloser

[Shane]

By any chance have you done a bad sector check on the drive yet?

Open a cmd.exe window as administrator and type in

chkdsk c: /f /r

It will come up and say the drive is in use and would you like to schedule it for next boot, hit Y and enter.

Now reboot the system, the chkdsk should start, if it doesnt try again. And the /r tells it to look for bad sectors. This scan can take a few hours depending on the size of the drive

Shane

[Soreloser]

I've run check disc from Windows and then your program does it also, but haven't run it in dos. I will give it a try and get back with you. Later, Soreloser. PS: Thanks again for taking time to help.

[Shane]

No problem, and let me know how it turns out. After the scan is done it will log the results in the event viewer

Shane

[Soreloser]

Hello Shane, Sorry it took so long to get back to you, but have finally made it. I ran the check disk like you told me and it said there were 48kb in bad sectors. I will send the event viewer report with this. Again I apologize for taking so long to return your message. I'm thinking that I may have big troubles. While I was in the event viewer I was checking some of the log files and there a whole lot of errors listed. I will name just a few as there too many to count. 1) Boot-start or System start drivers failed to load: cdrom and msdsm
2)Log Name:      Application
Source:        Application Error
Date:          6/26/2014 3:50:09 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      willie-PC
Description:
Faulting application name: svchost.exe_SysMain, version: 6.1.7600.16385, time stamp: 0x4a5bc100
Faulting module name: sysmain.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba10
Exception code: 0xc0000005
Fault offset: 0x00004a01
Faulting process id: 0x404
Faulting application start time: 0x01cf8fb1c33cb42b
Faulting application path: C:\Windows\System32\svchost.exe
Faulting module path: c:\windows\system32\sysmain.dll
Report Id: 758b825e-fd73-11e3-bda5-00238b28cc47
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-26T20:50:09.000000000Z" />
    <EventRecordID>15950</EventRecordID>
    <Channel>Application</Channel>
    <Computer>willie-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>svchost.exe_SysMain</Data>
    <Data>6.1.7600.16385</Data>
    <Data>4a5bc100</Data>
    <Data>sysmain.dll</Data>
    <Data>6.1.7601.17514</Data>
    <Data>4ce7ba10</Data>
    <Data>c0000005</Data>
    <Data>00004a01</Data>
    <Data>404</Data>
    <Data>01cf8fb1c33cb42b</Data>
    <Data>C:\Windows\System32\svchost.exe</Data>
    <Data>c:\windows\system32\sysmain.dll</Data>
    <Data>758b825e-fd73-11e3-bda5-00238b28cc47</Data>
  </EventData>
</Event>
3) Error occurred when iSCSI tried to log on.
4) MS Windows Winsock-AFD%4 operational...Log Name:      Microsoft-Windows-Winsock-AFD/Operational
Source:        Microsoft-Windows-Winsock-AFD
Date:          6/28/2014 11:55:17 PM
Event ID:      1015
Task Category: (1015)
Level:         Information
Keywords:      Datagram socket,Datagram socket,Datagram socket
User:          LOCAL SERVICE
Computer:      willie-PC
Description:
recvmsg: 1: Process 0x8656e030, Endpoint 0x85cfd110, Buffer Count 1, Buffer 0x1bf4090, Length 368, Addr [::1]:1900, Seq 4201, Status 0x0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Winsock-AFD" Guid="{E53C6823-7BB8-44BB-90DC-3F86090D48A6}" />
    <EventID>1015</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>1015</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000000015</Keywords>
    <TimeCreated SystemTime="2014-06-29T04:55:17.014402900Z" />
    <EventRecordID>134694573</EventRecordID>
    <Correlation ActivityID="{CE9DECC0-0000-0000-0000-000000000000}" />
    <Execution ProcessID="464" ThreadID="2892" />
    <Channel>Microsoft-Windows-Winsock-AFD/Operational</Channel>
    <Computer>willie-PC</Computer>
    <Security UserID="S-1-5-19" />
  </System>
  <EventData>
    <Data Name="EnterExit">1</Data>
    <Data Name="Location">4201</Data>
    <Data Name="Process">0x8656e030</Data>
    <Data Name="Endpoint">0x85cfd110</Data>
    <Data Name="BufferCount">1</Data>
    <Data Name="Buffer">0x1bf4090</Data>
    <Data Name="BufferLength">368</Data>
    <Data Name="Status">0</Data>
    <Data Name="AddressLen">28</Data>
    <Data Name="Address">1700076C000000000000000000000000000000000000000100000000</Data>
  </EventData>
</Event>
Those are just the handy ones to find. There are 2016 events in the winsock log alone. DCHP client over 2500, DNS client 2000. I was using Ready boost until today. Cache dumped due to repeated IO failure. Well you get the idea. I am kind of in awe that this thing is still running with so many faults. Gotta hand it to windows 7. It takes a lickin and keeps on tickin. Any advice except throw it all out and go get a new one? Any help is appreciated.
Thank you for your patience, Soreloser. PS I attached the event log file.

[Shane]

Ok good, now you know why the system is having problems. Any system file ends up on a bad sector then that file is corrupt and windows breaks.

Bad sectors means it is time for a new drive. Backup your important data as soon as possible to an external drive.

Then once you get a new drive installed you will install windows fresh and get your programs installed and then copy your data back over.

Shane