Author Topic: Service Permissions - Repair attempt continues to fail systematically  (Read 956 times)

0 Members and 1 Guest are viewing this topic.

Offline woutz

  • Newbie
  • *
  • Join Date: Aug 2020
  • Posts: 4
  • Karma: 0
    • View Profile
Dears,

Posting here for the first time, as adviced by Windows repair program, as the repair attempt  for service permissions continues to fail systematically on my Windows 10 machine, even when having botted in Safe mode.

Would anyone have maybe any idea?

Thanks a lot in advance for your help.

Kind regards,


W.

- - -

Log:
Tweaking.com - Windows Repair 2019 (v4.9.0)
────────────────────────────────────────────────────────────────────────────────

System Variables
────────────────────────────────────────────────────────────────────────────────
Running In Windows Safe Mode: Vrai
OS: Windows 10 Home
OS Architecture: 64-bit
OS Version: (1909) 10.0.18363.815
OS Service Pack:
Computer Name: HP-ENVY
Windows Drive: C:\
Windows Path: C:\WINDOWS
Program Files: C:\Program Files
Program Files (x86): C:\Program Files (x86)
Current Profile: C:\Users\MRO
Current Profile SID: S-1-5-21-4055044429-1540710871-660730752-1001
Current Profile Classes: S-1-5-21-4055044429-1540710871-660730752-1001_Classes
Profiles Location: C:\Users
Profiles Location 2: C:\WINDOWS\ServiceProfiles
Local Settings AppData: C:\Users\MRO\AppData\Local
────────────────────────────────────────────────────────────────────────────────

System Information
────────────────────────────────────────────────────────────────────────────────
System Up Time: 0 Days 00:01:23

Process Count: 50
Commit Total: 1,14 GB
Commit Limit: 31,94 GB
Commit Peak: 1,33 GB
Handle Count: 18336
Kernel Total: 219,14 MB
Kernel Paged: 113,54 MB
Kernel Non Paged: 105,61 MB
System Cache: 1,35 GB
Thread Count: 726
────────────────────────────────────────────────────────────────────────────────

Memory Before Cleaning with CleanMem
────────────────────────────────────────────────────────────────────────────────
Memory Total: 15,94 GB
Memory Used: 1,59 GB(9,9798%)
Memory Avail.: 14,35 GB
────────────────────────────────────────────────────────────────────────────────

Cleaning Memory Before Starting Repairs...

Memory After Cleaning with CleanMem
────────────────────────────────────────────────────────────────────────────────
Memory Total: 15,94 GB
Memory Used: 1,38 GB(8,6692%)
Memory Avail.: 14,56 GB
────────────────────────────────────────────────────────────────────────────────

Starting Repairs...
   Started at (15-08-20 16:37:00)

Setting Any Missing 'InstallDate' From Uninstall Sections Before Running Repair...
Total Missing 'InstallDate' Fixed: 0
 
01 - Reset Registry Permissions
   Restore Windows 7/8/10 Default Registry Permissions
   Start (15-08-20 16:37:02)


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\hku.7z
Done,  0,27 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\hklm.7z
Done,  3,39 seconds.

   Running Repair Under System Account
   Done (15-08-20 16:37:41)

02 - Reset File Permissions
   Restore Windows 7/8/10 Default File Permissions
   Start (15-08-20 16:37:41)


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\default.7z
Done,  0,14 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\profile.7z
Done,  0,17 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\program_files.7z
Done,  0,41 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\program_files_x86.7z
Done,  0,14 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\programdata.7z
Done,  0,14 seconds.


Decompressing & Updating Windows Permission File C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\files\permissions\10\windows.7z
Done,  1,11 seconds.

   Running Repair Under System Account
   Done (15-08-20 16:44:55)

03 - Reset Service Permissions
   Start (15-08-20 16:44:55)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 1)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 2)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 3)

   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (15-08-20 16:46:55)

   Done, but failed, at (15-08-20 16:46:55)
   Total Repair Time: 00:09:56

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.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9934
  • Location: UK
  • Karma: 122
    • View Profile
Apologies for my lateness in replying but I hadn't seen your thread because the Spam filter had held it back.

Can you open a Command Prompt (Admin) and enter these cmds -

chkdsk /r

Enter y when prompted then enter shutdown /r /t 00 to effect an immediate reboot for the chkdsk to execute.

After the chkdsk has completed, right click on the Windows key and select Event Viewer.

When it has read the data, expand Windows Logs then click on Application/Action/Find

Type chkdsk into the Find box and press enter.

Cancel the Find box and read the log in the scrollable pane below.

Primarily you are looking to see if it reports any KBs in bad sectors.

If it does then create a system image immediately onto external media in preparation for a full failure of your HDD.

If that comes back clean then enter -

dism /online /cleanup-image /restorehealth

sfc /scannow

Enter exit to close the command window and try the repair program again, but let me know if sfc /scannow reports anything other no integrity violations.

If the chkdsk does report bad sectors, after you have created the system image you can go back into the Command Prompt (Admin) and enter those other two cmds to see what they report.
Tom.

Offline woutz

  • Newbie
  • *
  • Join Date: Aug 2020
  • Posts: 4
  • Karma: 0
    • View Profile
Thanks a lot for the feedback and for the instructions.

For whatever reason, do not seem to be in a position to open a Command Line anymore on the PC, so opened PowerShell (as admin) instead. Hope that's fine as well?

Below log result are in French, so I translated via DeepL into English. Not sure result is good or bad?


Kind regards,


W.

- - -

General

Vérification du système de fichiers sur C:
Le type du système de fichiers est NTFS.
Le nom de volume est OS.

Une vérification de disque a été planifiée.
Windows va maintenant vérifier le disque.                                 

Étape 1 : Examen de la structure du système de fichiers de base...
Nettoyage en cours des balises dinstance pour le fichier 0x668ba.


---

- System

  - Provider

   [ Name]  Microsoft-Windows-Wininit
   [ Guid]  {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
   [ EventSourceName]  Wininit
 
  - EventID 1001

   [ Qualifiers]  16384
 
   Version 0
 
   Level 4
 
   Task 0
 
   Opcode 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime]  2020-08-18T15:09:53.928691000Z
 
   EventRecordID 31260
 
   Correlation
 
  - Execution

   [ ProcessID]  0
   [ ThreadID]  0
 
   Channel Application
 
   Computer HP-ENVY
 
   Security
 

- EventData

   Vérification du système de fichiers sur C: Le type du système de fichiers est NTFS. Le nom de volume est OS. Une vérification de disque a été planifiée. Windows va maintenant vérifier le disque. Étape 1 : Examen de la structure du système de fichiers de base... Nettoyage en cours des balises dinstance pour le fichier 0x668ba. 1910528 enregistrements de fichier traités. La vérification des fichiers est terminée. 22071 enregistrements de grand fichier traités. 0 enregistrements de fichier incorrect traités. Étape 2 : Examen de la liaison des noms de fichiers... 83333 enregistrements danalyse traités. 2428758 entrées dindex traitées. La vérification des index est terminée. 0 fichiers non indexés analysés. 0 fichiers non indexés récupérés dans le répertoire des fichiers perdus et trouvés. 83333 enregistrements danalyse traités. Étape 3 : Examen des descripteurs de sécurité... Nettoyage en cours de 4578 entrées dindex inutilisées   partir de lindex $SII du fichier 0x9. Nettoyage en cours de 4578 entrées dindex inutilisées   partir de lindex $SDH du fichier 0x9. Nettoyage en cours de 4578 descripteurs de sécurité non utilisés. La vérification des descripteurs de sécurité est terminée. 259116 fichiers de données traités. CHKDSK vérifie le journal USN... Vérification du journal USN terminée. Étape 4 : Recherche de clusters incorrects dans les données des fichiers utilisateur... 1910512 fichiers traités. La vérification des données du fichier est terminée. Étape 5 : Recherche de clusters libres incorrects... 22358055 clusters libres traités. La vérification de lespace libre est terminée. Windows a effectué des corrections sur le système de fichiers. Aucune autre action nest requise. 473990140 Ko despace disque au total. 381770492 Ko dans 1396761 fichiers. 780552 Ko dans 259117 index. 0 Ko dans des secteurs défectueux. 2006872 Ko utilisés par le système. 65536 Ko occupés par le fichier journal. 89432224 Ko disponibles sur le disque. 4096 octets dans chaque unité dallocation. 118497535 unités dallocation au total sur le disque. 22358056 unités dallocation disponibles sur le disque. Informations internes : 00 27 1d 00 91 43 19 00 bc cf 2d 00 00 00 00 00 .'...C....-..... 3c 04 00 00 49 41 01 00 00 00 00 00 00 00 00 00 <...IA.......... Windows a terminé la vérification de votre disque. Veuillez patienter pendant le redémarrage de votre ordinateur. 



----------- Translation - via DeepL.com

General:

File system check on C:
The file system type is NTFS.
The volume name is OS.

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

Step 1: Examine the basic file system structure .
Ongoing cleanup of the dinstance tags for the 0x668ba file.
  1910528 file records processed.                                                 
File verification is complete.
  22071 large file records processed.                       
  0 incorrect file records processed.                   

Step 2: Examination of filename binding .
  83333 analysis records processed.                               
  2428758 turkey records processed.                                                               
Index check completed.
  0 non-indexed files analyzed.                                   
  0 unindexed files recovered from the lost and found directory.                                       
  83333 analysis records processed.                               

Step 3: Security descriptor review .
4578 unused lindex entries are being cleaned up from lindex $SII
of the 0x9 file.
Ongoing cleanup of 4578 unused dindex entries from lindex $SDH
of the 0x9 file.
Cleaning up of 4578 unused security descriptors.
Security descriptor verification is complete.
  259116 data files processed.                                     
CHKDSK checks the USN log .
USN log check complete.

Step 4: Search for incorrect clusters in user file data...
  1910512 files processed.                                                                         
File data check is complete.

Step 5: Search for incorrect free clusters...
  22358055 free clusters processed.                                                               
Checking for free space is complete.

Windows has made corrections to the file system.
No further action is required.

 473990140 KB total disk space.
 381770492 KB in 1396761 files.
    780552 Kb in 259117 indexes.
         0 Kb in bad sectors.
   2006872 Kb used by the system.
     65536 Kb used by the log file.
  89432224 Ko available on the disk.

      4096 bytes in each allocation unit.
 118497535 allocation units in total on the disk.
  22358056 allocation units available on the disk.

Internal information :
00 27 1d 00 91 43 19 00 bc cf 2d 00 00 00 00 00 .'...C...-...
3c 04 00 00 49 41 01 00 00 00 00 00 00 00 ...IA.....

Windows has finished checking your disk.
Please wait while your computer is restarting.


Translated with www.DeepL.com/Translator (free version)

---

Details:

- System

  - Provider

   [ Name] Microsoft-Windows-Wininit
   [ Guid] {206f6dea-d3c5-4d10-bc72-989f03c8b84b}
   [ EventSourceName] Wininit
 
  - EventID 1001

   [ Qualifiers ] 16384
 
   Version 0
 
   Level 4
 
   Task 0
 
   Opcode 0
 
   Keywords 0x80000000000000
 
  - TimeCreated

   [ SystemTime] 2020-08-18T15:09:53.928691000Z
 
   EventRecordID 31260
 
   Correlation
 
  - Execution

   [ ProcessID] 0
   [ ThreadID] 0
 
   Channel Application
 
   Computer HP-ENVY
 
   Security
 

- EventData

   File system check on C: The file system type is NTFS. The volume name is OS. A disk check has been scheduled. Windows will now check the disk. Step 1: Examine the basic file system structure . Ongoing cleanup of the dinstance tags for the 0x668ba file. 1910528 file records processed. File verification is complete. 22071 large file records processed. 0 incorrect file records processed. Step 2: Examination of filename binding . 83333 analysis records processed. 2428758 turkey records processed. Index check completed. 0 unindexed files scanned. 0 unindexed files recovered from lost and found directory. 83333 analysis records processed. Step 3: Security descriptor review . 4578 unused dindex entries are being cleaned up from lindex $SII of file 0x9. 4578 unused turkey entries are being cleaned up from lindex $SDH in the 0x9 file. Cleanup in progress of 4578 unused security descriptors. Security descriptor verification is complete. 259116 data files processed. CHKDSK checks the USN log . USN log check complete. Step 4: Search for incorrect clusters in user file data... 1910512 files processed. File data check is complete. Step 5: Search for incorrect free clusters... 22358055 free clusters processed. Checking for free space is complete. Windows has made corrections to the file system. No further action is required. 473990140 KB total disk space. 381770492 KB in 1396761 files. 780552 Kb in 259117 indexes. 0 Kb in bad sectors. 2006872 Kb used by the system. 65536 Kb occupied by the log file. 89432224 Kb available on the disk. 4096 bytes in each allocation unit. 118497535 allocation units in total on the disk. 22358056 allocation units available on the disk. Internal information : 00 27 1d 00 91 43 19 00 bc cf 2d 00 00 00 00 00 00 00 .'...C...-... 3c 04 00 00 49 41 01 00 00 00 00 00 00 00 ...IA..... Windows has finished checking your disk. Please wait while your computer is restarting. 


Translated with www.DeepL.com/Translator (free version)

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9934
  • Location: UK
  • Karma: 122
    • View Profile
Thanks for that - the chkdsk log looks fine but how did the dism /restorehealth and sfc /scannow commands go ?

One of Win 10's updates changed the default Command Prompt to Powershell but I changed mine back to Command Prompt through Settings/Apps/Default Apps where you can toggle them over.
Tom.

Offline woutz

  • Newbie
  • *
  • Join Date: Aug 2020
  • Posts: 4
  • Karma: 0
    • View Profile
Oh, sure.  Here below are the add. results:


W.

---

PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Outil Gestion et maintenance des images de déploiement
Version : 10.0.18362.1

Version de limage : 10.0.18363.815

[==========================100.0%==========================] La restauration a été effectuée.
Lopération a réussi.
PS C:\WINDOWS\system32> sfc /scannow

Début de lanalyse du système. Cette opération peut nécessiter un certain temps.

Démarrage de la phase de vérification de lanalyse du système.
La vérification est   100% terminée.

Le programme de protection des ressources Windows na trouvé aucune violation dintégrité.
PS C:\WINDOWS\system32>


Translated with DeepL:

PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth

Deployment Image Management and Maintenance Tool
Version: 10.0.18362.1

File Version: 10.0.18363.815

===============================================================================================100.0%=======================================================================================================] The restoration has been completed.
The operation was successful.
PS C:\WINDOWS\system32> sfc /scannow

Beginning system analysis. This may take some time.

Start the system evaluation check phase.
The check is 100% complete.

The Windows resource protection program found no integrity violations.
PS C:\WINDOWS\system32>

Translated with www.DeepL.com/Translator (free version)


---

03 - Reset Service Permissions
   Start (20-08-20 07:39:49)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 1)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 2)

   Running Repair Under Current User Account
The current repair has failed to start for over 30 sec.
Trying Again....(Times Tried: 3)

   Running Repair Under Current User Account
   Running Repair Under System Account
   Done (20-08-20 07:41:50)

   Done, but failed, at (20-08-20 07:41:50)
   Total Repair Time: 00:11:13

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


Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9934
  • Location: UK
  • Karma: 122
    • View Profile
Well they look okay.

Can you see if reinstalling the repair program makes any difference ?

As you are trying this in Safe Mode with Networking then no other 3rd party program will be the cause.
Tom.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9934
  • Location: UK
  • Karma: 122
    • View Profile
If the Windows Repair reinstall doesn't resolve, on rare occasions Window Firewall which is active in that mode can block certain applications.

You can add an exception to Windows Firewall as this article describes - https://www.dummies.com/computers/pcs/computer-security/how-to-allow-firewall-exceptions-on-your-windows-10-laptop/

However, you need to expand the search by clicking on Change Settings and then on Allow another app and Browse to select Desktop where you should see the icon for Tweaking.com Windows Repair.

Click on that and then on Open where it will add it to the Applications list - click Add and try the repair program again.
« Last Edit: August 20, 2020, 02:47:53 AM by Boggin »
Tom.

Offline woutz

  • Newbie
  • *
  • Join Date: Aug 2020
  • Posts: 4
  • Karma: 0
    • View Profile
Thanks a lot for all the tips. Tried all, incl. uninstaling/reinstalling, but nothing worked.

As all this was in context of getting Windows 10 update to work, again, finally decided to reinstall Windows completely, - and now the Tweaking app works! :-)

Thanks, again, for all.

Offline Boggin

  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Jul 2014
  • Posts: 9934
  • Location: UK
  • Karma: 122
    • View Profile
As the dism /restorehealth and sfc /scannow cmds came back clean, I hadn't considered a corrupt system.

For future ref if you need to reinstall Win 10, instead of doing a clean install you can perform a repair install which doesn't affect personal stuff or installed programs.

Open Windows/File Explorer - This PC - insert the install media and double click on its drive which will start the process when using a DVD but will open to its files when using an USB where you would then double click on setup Application.

Anyway, glad you found a fix.
Tom.