unable to repair even in safe mode : access refused

[labbyjoel]

I'm unable to run the repair.

The windows event viewer show this error :  ( sorry it's french )

Nom du journal :System
Source :       Service Control Manager
Date :         21/10/2016 10:58:09
ID de l’événement :7000
Catégorie de la tâche :Aucun
Niveau :       Erreur
Mots clés :    Classique
Utilisateur :  N/A
Ordinateur :   JOEL4
Description :
Le service Tweaking Run As System 0001 n’a pas pu démarrer en raison de l’erreur :
Accès refusé.
XML de l’événement :
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2016-10-21T08:58:09.575046300Z" />
    <EventRecordID>182579</EventRecordID>
    <Correlation />
    <Execution ProcessID="532" ThreadID="1244" />
    <Channel>System</Channel>
    <Computer>JOEL4</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">Tweaking Run As System 0001</Data>
    <Data Name="param2">%%5</Data>
  </EventData>
</Event>

any idea  ?

thanks !

joel

[Boggin]

That's okay - I copied and pasted into Google Translate.

See if the program will open when you right click on the icon and select Run as administrator and I'll pass this onto Shane.

[labbyjoel]

I think my explanation is wrong

I can run the repair program, every optionnal steps runs well ( unless one reparse point unable to repair )

when I launch the "repair" option, I get this log :

Code: [Select]

Tweaking.com - Windows Repair v3.9.13
────────────────────────────────────────────────────────────────────────────────

System Variables
────────────────────────────────────────────────────────────────────────────────
OS: Windows 7 Professional
OS Architecture: 64-bit
OS Version: 6.1.7601
OS Service Pack: Service Pack 1
Computer Name: JOEL4
Windows Drive: C:\
Windows Path: C:\Windows
Program Files: C:\Program Files
Program Files (x86): C:\Program Files (x86)
Current Profile: C:\Users\joell
Current Profile SID: S-1-5-21-3295233227-2378846417-109446503-1018
Current Profile Classes: S-1-5-21-3295233227-2378846417-109446503-1018_Classes
Profiles Location: C:\Users
Profiles Location 2: C:\Windows\ServiceProfiles
Local Settings AppData: C:\Users\joell\AppData\Local
────────────────────────────────────────────────────────────────────────────────

System Information
────────────────────────────────────────────────────────────────────────────────
System Up Time: 03 Days 00:21:19

Process Count: 103
Commit Total: 9,99 GB
Commit Limit: 31,92 GB
Commit Peak: 10,49 GB
Handle Count: 44005
Kernel Total: 4,80 GB
Kernel Paged: 3,04 GB
Kernel Non Paged: 1,76 GB
System Cache: 7,33 GB
Thread Count: 1514
────────────────────────────────────────────────────────────────────────────────

Memory Before Cleaning with CleanMem
────────────────────────────────────────────────────────────────────────────────
Memory Total: 15,96 GB
Memory Used: 9,50 GB(59,5057%)
Memory Avail.: 6,46 GB
────────────────────────────────────────────────────────────────────────────────

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
────────────────────────────────────────────────────────────────────────────────
Memory Total: 15,96 GB
Memory Used: 7,70 GB(48,2491%)
Memory Avail.: 8,26 GB
────────────────────────────────────────────────────────────────────────────────

Starting Repairs...
   Started at (24/10/2016 11:25:49)


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


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


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

   Done, but failed, at (24/10/2016 11:27:49)
   Total Repair Time: 00:02:02

The current repair has failed to start 4 times.
Something is keeping the repair from running.

Try running the repairs in Windows Safe Mode. (This will keep 3rd party programs from getting in the way of the repairs)
If the repairs still fail then please post in the Tweaking.com forums for support.
And when I check the windows event viewer I see the "access refused" error

Hope clearer this time    sorry !

[Boggin]

I think I've already passed this onto Shane to have a look at but he's had quite a lot of work come in for his computer repair business, that he's been unable to catch up with his emails.

I'll ask Jim to have a look at it.

[jpm]

are you booting into safe mode when this happens?

[labbyjoel]

Yes, i've tried both way .

[Shane]

The program runs a lot of the repairs under the system account. To do that it installs a service that runs as system and launches the repair from there.

For some reason your system isnt letting the program have access to installing the service. The user account you are running under has to have admin rights, can you double check that the user account isnt limited?

Shane

[labbyjoel]

Thanks for your reply.

My account is a domain administrator, I've got all te rights on this computer.

May be can I try to run the service manually ?

[Boggin]

Either create another admin account or invoke the hidden admin account by going Start - type cmd then right click on cmd and select Run as administrator - accept the UAC and enter -

net user administrator /active:yes

shutdown /r /t 00

After the reboot log in through the Admin icon and try the program again.

When done, the hidden admin account should be turned off and can be done by changing yes to no

[Shane]

I wonder if while it is safe mode the user account is a domain admin but is it a local admin for the computer itself? Perhaps that is where the problem is.

So if you add the account to the system locally and make it an admin that would do the trick as well.

If that isnt an option then you may have to run the repairs in normal mode, but you need to make sure your AV is off and anything else, a clean boot would be a good idea to do if safe mode wont let you have the access you need.

Shane

[labbyjoel]

You are right, there is a problem with my domain admin user, When logging with local admin account, I've been able to repair without any problem ! Thanks for your help !