Tweaking.com WIndows Repair v2.9.0 Windows 7 Volume Shadow Copy Service Repair

[mpbalda]

Running Tweaking.com Windows Repair v2.9.0 on Windows 7. When it gets to the Volume Shadow Copy Service Repair, it fails to start and it states that so,mething is keeping the repir from running.

Tweaking.com - Windows Repair v2.9.0
--------------------------------------------------------------------------------

System Variables
--------------------------------------------------------------------------------
OS: Windows 7 Professional
OS Architecture: 64-bit
OS Version: 6.1.7601
OS Service Pack: Service Pack 1
Computer Name: OWNER-PC
Windows Drive: C:\
Windows Path: C:\Windows
Program Files: C:\Program Files
Program Files (x86): C:\Program Files (x86)
Current Profile: C:\Users\Owner
Current Profile SID: S-1-5-21-2950464786-718825967-2645322811-1000
Current Profile Classes: S-1-5-21-2950464786-718825967-2645322811-1000_Classes
Profiles Location: C:\Users
Profiles Location 2: C:\Windows\ServiceProfiles
Local Settings AppData: C:\Users\Owner\AppData\Local
--------------------------------------------------------------------------------

System Information
--------------------------------------------------------------------------------
System Up Time: 01 Day 01:42:12

Process Count: 87
Commit Total: 4.20 GB
Commit Limit: 16.00 GB
Commit Peak: 5.79 GB
Handle Count: 46092
Kernel Total: 696.98 MB
Kernel Paged: 558.35 MB
Kernel Non Paged: 138.64 MB
System Cache: 4.27 GB
Thread Count: 1870
--------------------------------------------------------------------------------

Memory Before Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 8.00 GB
Memory Used: 2.14 GB(26.6982%)
Memory Avail.: 5.86 GB
--------------------------------------------------------------------------------

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 8.00 GB
Memory Used: 1.93 GB(24.1702%)
Memory Avail.: 6.07 GB
--------------------------------------------------------------------------------

Starting Repairs...
   Started at (9/26/2014 4:00:20 PM)

19 - Repair Volume Shadow Copy Service
   Start (9/26/2014 4:00:27 PM)
   Running Repair Under Current User Account
   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account

The current repair has failed to start for over 30 sec.
Trying Again....

   Running Repair Under System Account
   Done (9/26/2014 4:02:55 PM)

   Done, but failed, at (9/26/2014 4:02:55 PM)
   Total Repair Time: 00:02:36

The current repair has failed to start 4 times.
Something is keeping the repair from running.
Please post in the Tweaking.com forums for support.

[Shane]

The program runs the repair under the system account, which the file tweaking_ras.exe in the files folder is used for that. Check to make sure that your antivirus isnt blocking that exe, you can also check the event viewer to see if there is any errors as well.

But the most common reason is a user didnt disable their AV and it is getting in the way

Shane

[siddiquimab]

Tweaking.com - Windows Repair v2.9.2
--------------------------------------------------------------------------------

System Variables
--------------------------------------------------------------------------------
OS: Microsoft Windows XP
OS Architecture: 32-bit
OS Version: 5.1.2600
OS Service Pack: Service Pack 3
Computer Name: NTSERVER
Windows Drive: C:\
Windows Path: C:\WINDOWS
Program Files: C:\Program Files
Current Profile: C:\Documents and Settings\Intellihub
Current Profile SID: S-1-5-21-1547161642-1979792683-839522115-1003
Current Profile Classes: S-1-5-21-1547161642-1979792683-839522115-1003_Classes
Profiles Location: C:\Documents and Settings
Profiles Location 2: C:\WINDOWS\ServiceProfiles
Local Settings AppData: C:\Documents and Settings\Intellihub\Local Settings\Application Data
--------------------------------------------------------------------------------

System Information
--------------------------------------------------------------------------------
System Up Time: 0 Days 03:21:42

Process Count: 66
Commit Total: 2.58 GB
Commit Limit: 5.25 GB
Commit Peak: 2.71 GB
Handle Count: 23792
Kernel Total: 121.96 MB
Kernel Paged: 93.36 MB
Kernel Non Paged: 28.60 MB
System Cache: 1.96 GB
Thread Count: 979
--------------------------------------------------------------------------------

Memory Before Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 3.41 GB
Memory Used: 1.27 GB(37.1599%)
Memory Avail.: 2.14 GB
--------------------------------------------------------------------------------

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
--------------------------------------------------------------------------------
Memory Total: 3.41 GB
Memory Used: 1.22 GB(35.8564%)
Memory Avail.: 2.19 GB
--------------------------------------------------------------------------------

Starting Repairs...
   Started at (02/10/2014 12:24:36 PM)

   Done, but failed, at (02/10/2014 12:25:06 PM)
   Total Repair Time: 00:00:31

The current repair has failed to start 8 times.
Something is keeping the repair from running.
Please post in the Tweaking.com forums for support.

[Shane]

siddiquimab, please dont hijack some one elses thread, start a new thread for yourself

Otherwise it gets to confusing on who is doing what when I have multiple people in a thread.

And of course also read what I asked the other user about here (Haven't got a response back yet though.)

The program runs the repair under the system account, which the file tweaking_ras.exe in the files folder is used for that. Check to make sure that your antivirus isnt blocking that exe, you can also check the event viewer to see if there is any errors as well.

But the most common reason is a user didnt disable their AV and it is getting in the way

Shane