Windows Repair (All in One) v2.8.6 Released

Main Forum > Tweaking.com Support & Help

<< < (2/4) > >>

Shane:
Looks like for some reason something kept tweaking_ras.exe in the files folder from running and starting the cmd.exe under the system account.

Each time you see a repair being run under the system account that exe is ran, so if it ever has trouble it wont start the cmd.exe.

So the question is, why did it fail to start that time when it ran fine for all the repairs before it. Does the event viewer show any errors about that file?

Shane

TweakAS:
All I can see after v.2.8.7, and on win 7 pro 32-bit, is as follows:-

1) The RegBackup log_backup text file shows 'successful' for all

2) The Event Viewer for 'system' with errors (x 3 - about the time v2.8.7 ran) (via Control Panel) is copy pasted here:-

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 19/08/2014 08:25:02
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: DELL-9150\as
Computer: DELL-9150
Description:
The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{000C101C-0000-0000-C000-000000000046}
and APPID
{000C101C-0000-0000-C000-000000000046}
to the user DELL-9150\as SID (S-1-5-21-536513578-3564515113-194576785-1001) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-19T07:25:02.000000000Z" />
<EventRecordID>672992</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DELL-9150</Computer>
<Security UserID="S-1-5-21-536513578-3564515113-194576785-1001" />
</System>
<EventData>
<Data Name="param1">machine-default</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Activation</Data>
<Data Name="param4">{000C101C-0000-0000-C000-000000000046}</Data>
<Data Name="param5">{000C101C-0000-0000-C000-000000000046}</Data>
<Data Name="param6">DELL-9150</Data>
<Data Name="param7">as</Data>
<Data Name="param8">S-1-5-21-536513578-3564515113-194576785-1001</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
</EventData>
</Event>

Log Name: System
Source: Microsoft-Windows-DistributedCOM
Date: 19/08/2014 08:33:08
Event ID: 10016
Task Category: None
Level: Error
Keywords: Classic
User: SYSTEM
Computer: DELL-9150
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}
and APPID
{344ED43D-D086-4961-86A6-1106F4ACAD9B}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-DistributedCOM" Guid="{1B562E86-B7AA-4131-BADC-B6F3A001407E}" EventSourceName="DCOM" />
<EventID Qualifiers="49152">10016</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-19T07:33:08.000000000Z" />
<EventRecordID>673004</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>System</Channel>
<Computer>DELL-9150</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="param1">application-specific</Data>
<Data Name="param2">Local</Data>
<Data Name="param3">Launch</Data>
<Data Name="param4">{C97FCC79-E628-407D-AE68-A06AD6D8B4D1}</Data>
<Data Name="param5">{344ED43D-D086-4961-86A6-1106F4ACAD9B}</Data>
<Data Name="param6">NT AUTHORITY</Data>
<Data Name="param7">SYSTEM</Data>
<Data Name="param8">S-1-5-18</Data>
<Data Name="param9">LocalHost (Using LRPC)</Data>
</EventData>
</Event>

Log Name: System
Source: volsnap
Date: 19/08/2014 09:04:21
Event ID: 25
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DELL-9150
Description:
The shadow copies of volume C: were deleted because the shadow copy storage could not grow in time. Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="volsnap" />
<EventID Qualifiers="49158">25</EventID>
<Level>2</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-08-19T08:04:21.820825100Z" />
<EventRecordID>673175</EventRecordID>
<Channel>System</Channel>
<Computer>DELL-9150</Computer>
<Security />
</System>
<EventData>
<Data>\Device\HarddiskVolumeShadowCopy1</Data>
<Data>C:</Data>
<Binary>000000000200300000000000190006C0030000000000000000000000000000000000000000000000</Binary>
</EventData>
</Event>

I am not techie enough to decipher that and hope it helps you to fix it! I would say why fix version 2.8.5 when it worked OK, but I hear you say 'to make it better'!

Hoping to get to the better of this glitch soon.

Shane:
I have had multiple people report the repairs not running at random times. I think I have it traced down. The tweaking_ras.exe file is what I need to update. There are two reasons I found why it isnt running a repair and so I am working on a fix right now and will hopefully have an update out tomorrow :-)

This is a good thing that this is happening, because before the program never waited for the repairs to start and so if a repair failed to run for some reason it just kept on going, but missing that repair and who knows how many others. Now that I have the program wait for the repair to start I am finally seeing these issues and it is allowing me to get them fixed :-)

Shane

Shane:
Done!

I finished v2.8.8 BUT I need it tested before I release it tomorrow morning. So if you could try it out tonight and let me know by morning if you had any trouble with it. :cheesy:

If all goes well I will release it first thing tomorrow when I get in my office.

Take the 7-zip file I attached and extract the files out of it and replace the ones in the program folder with these new ones. (So grab the 2.8.7 version if you dont have it and once installed replace the files with the ones in the 7-zip file)

3 main files need replaced
Repair_Windows.exe
files\tweaking_ras.exe
files\tweaking_rati.exe

Here is the current change log for the new version

--- Quote ---v2.8.8
Updated the tweaking_ras.exe and Tweaking_rati.exe. These are both used to run repairs as the system account or trusted installer. To do this they create themselves as a service and run the command, then remove the service they created. The problem was that on some systems, Windows wasn't removing the service fast enough before the next one was called and created. Since the service name was the same, the next one created wouldn't be called (Since it was in the process of being removed by Windows) and the repair wouldn't start. Both of these programs now randomize their service name to keep this from happening.

The program now will try to start a repair up to 3 more times if it fails to start the first time (For a total of 4 times and 30 sec between each try). So now if there is ever a simple hiccup or problem that kept the repair from running then the program will try again and normally it will continue on. If it fails to run a repair 4 times then the repairs stop and the program tells you to let me know in the forums, where I will work with you to find out why they didn't run.

Fixed a bug where the program didn't close itself if you told it to reboot or shutdown the systems after the repairs.

--- End quote ---

Shane

TweakAS:
Hi Shane,

Followed your instructions, downloaded and replaced the 3 files in v2.8.7 today (already installed). Then tested in win 7 Home 32-bit VM, but in the end the same results.

The attached images shows the 3 attempts you mentioned and again the process stopped at task 19.

The System Event Viewer file is also attached (as too long to copy and paste here). This shows the 'before and after' events: 1) tweaking OK, 2) then the error, 3) then the 3 attempts.

If you still have v.2.8.5, to compare with later versions that would give a clue. :undecided: :sad:

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version