SFC - System File Checker bleibt bei 23 24% stehen - Windows Resource Protection konnte die angeforderte Operation nicht ausführen

1151
Alex S

Ausführen von SFC nach 2 Stromausfällen auf Desktop Windows 8.1 Pro.

Details hier:
Opera-Fehler „Benutzerprofilverzeichnis kann nicht geöffnet werden, da Ihnen keine ausreichenden Berechtigungen zur Verfügung stehen.“ Nach Stromausfall

Zusätzliche Information:

Da sich dies herausstellte, dachte ich, ich sollte eine typische Systemprüfung durchführen, die ich mithilfe von Image-Health durchführte. Dazu gehören DISM- und SFC-Befehlsoptionen über ein einfach zu bedienendes Menüsystem.

DISM lief einwandfrei, aber SFC stoppte bei 23% und wurde beim Bericht erstellt (die meisten der vielen Hex / Binary-Stilinformationen, die keine Datei- / Ordnernamen des Problems enthalten).

Nun, für diejenigen, die sagen, dass SFC nicht von Bedeutung ist, lassen Sie mich das noch einmal wiederholen. - Alle genannten Checks, die ich schon oft verwendet habe, haben zuvor gut funktioniert.

Ich glaube also, dass Opera & SFC, die beide Probleme mit Berechtigungen haben, irgendwie miteinander verbunden ist.

Die einzige weitere Ergänzung war die Installation von Windows 8.1 Security Rollup vor diesen beiden Stromausfällen. 

=============================================================================== System File Checker is scanning the online image for corruption. Please Wait.. This will take 10-15 minutes or more.. ===============================================================================  Beginning system scan. This process will take some time.  Beginning verification phase of system scan. Verification 24% complete.  Windows Resource Protection could not perform the requested operation. =============================================================================== A SFC Details Report was Created on your Desktop =============================================================================== Press any key to continue . . .

SFC Details.txt

2017-05-28 19:35:08, Info CSI 0000000a [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:08, Info CSI 0000000b [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:10, Info CSI 0000000c [SR] Verify complete 2017-05-28 19:35:10, Info CSI 0000000d [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:10, Info CSI 0000000e [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:12, Info CSI 0000000f [SR] Verify complete 2017-05-28 19:35:12, Info CSI 00000010 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:12, Info CSI 00000011 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:14, Info CSI 00000012 [SR] Verify complete 2017-05-28 19:35:14, Info CSI 00000013 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:14, Info CSI 00000014 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:16, Info CSI 00000015 [SR] Verify complete 2017-05-28 19:35:16, Info CSI 00000016 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:16, Info CSI 00000017 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:18, Info CSI 00000018 [SR] Verify complete 2017-05-28 19:35:18, Info CSI 00000019 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:18, Info CSI 0000001a [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:20, Info CSI 0000001b [SR] Verify complete 2017-05-28 19:35:20, Info CSI 0000001c [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:20, Info CSI 0000001d [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:22, Info CSI 0000001e [SR] Verify complete 2017-05-28 19:35:22, Info CSI 0000001f [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:22, Info CSI 00000020 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:24, Info CSI 00000021 [SR] Verify complete 2017-05-28 19:35:24, Info CSI 00000022 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:24, Info CSI 00000023 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:26, Info CSI 00000024 [SR] Verify complete 2017-05-28 19:35:26, Info CSI 00000025 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:26, Info CSI 00000026 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:28, Info CSI 00000027 [SR] Verify complete 2017-05-28 19:35:28, Info CSI 00000028 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:28, Info CSI 00000029 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:30, Info CSI 0000002a [SR] Verify complete 2017-05-28 19:35:30, Info CSI 0000002b [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:30, Info CSI 0000002c [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:31, Info CSI 0000002d [SR] Verify complete 2017-05-28 19:35:32, Info CSI 0000002e [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:32, Info CSI 0000002f [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:33, Info CSI 00000030 [SR] Verify complete 2017-05-28 19:35:33, Info CSI 00000031 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:33, Info CSI 00000032 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:35, Info CSI 00000033 [SR] Verify complete 2017-05-28 19:35:35, Info CSI 00000034 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:35, Info CSI 00000035 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:37, Info CSI 00000036 [SR] Verify complete 2017-05-28 19:35:37, Info CSI 00000037 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:37, Info CSI 00000038 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:39, Info CSI 00000039 [SR] Verify complete 2017-05-28 19:35:39, Info CSI 0000003a [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:39, Info CSI 0000003b [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:41, Info CSI 0000003c [SR] Verify complete 2017-05-28 19:35:41, Info CSI 0000003d [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:41, Info CSI 0000003e [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:42, Info CSI 0000003f [SR] Verify complete 2017-05-28 19:35:42, Info CSI 00000040 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:42, Info CSI 00000041 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:44, Info CSI 00000042 [SR] Verify complete 2017-05-28 19:35:44, Info CSI 00000043 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:44, Info CSI 00000044 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:46, Info CSI 00000045 [SR] Verify complete 2017-05-28 19:35:46, Info CSI 00000046 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:46, Info CSI 00000047 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:48, Info CSI 00000048 [SR] Verify complete 2017-05-28 19:35:48, Info CSI 00000049 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:48, Info CSI 0000004a [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:50, Info CSI 0000004b [SR] Verify complete 2017-05-28 19:35:50, Info CSI 0000004c [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:50, Info CSI 0000004d [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:52, Info CSI 0000004e [SR] Verify complete 2017-05-28 19:35:52, Info CSI 0000004f [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:52, Info CSI 00000050 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:53, Info CSI 00000051 [SR] Verify complete 2017-05-28 19:35:53, Info CSI 00000052 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:53, Info CSI 00000053 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:55, Info CSI 00000054 [SR] Verify complete 2017-05-28 19:35:55, Info CSI 00000055 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:55, Info CSI 00000056 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:57, Info CSI 00000057 [SR] Verify complete 2017-05-28 19:35:57, Info CSI 00000058 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:57, Info CSI 00000059 [SR] Beginning Verify and Repair transaction 2017-05-28 19:35:59, Info CSI 0000005a [SR] Verify complete 2017-05-28 19:35:59, Info CSI 0000005b [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:35:59, Info CSI 0000005c [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:01, Info CSI 0000005d [SR] Verify complete 2017-05-28 19:36:01, Info CSI 0000005e [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:01, Info CSI 0000005f [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:03, Info CSI 00000060 [SR] Verify complete 2017-05-28 19:36:03, Info CSI 00000061 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:03, Info CSI 00000062 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:04, Info CSI 00000063 [SR] Verify complete 2017-05-28 19:36:04, Info CSI 00000064 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:04, Info CSI 00000065 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:06, Info CSI 00000066 [SR] Verify complete 2017-05-28 19:36:06, Info CSI 00000067 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:06, Info CSI 00000068 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:08, Info CSI 00000069 [SR] Verify complete 2017-05-28 19:36:08, Info CSI 0000006a [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:08, Info CSI 0000006b [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:10, Info CSI 0000006c [SR] Verify complete 2017-05-28 19:36:10, Info CSI 0000006d [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:10, Info CSI 0000006e [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:12, Info CSI 0000006f [SR] Verify complete 2017-05-28 19:36:12, Info CSI 00000070 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:12, Info CSI 00000071 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:14, Info CSI 00000072 [SR] Verify complete 2017-05-28 19:36:14, Info CSI 00000073 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:14, Info CSI 00000074 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:15, Info CSI 00000075 [SR] Verify complete 2017-05-28 19:36:15, Info CSI 00000076 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:15, Info CSI 00000077 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:17, Info CSI 00000078 [SR] Verify complete 2017-05-28 19:36:17, Info CSI 00000079 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:17, Info CSI 0000007a [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:20, Info CSI 0000007b [SR] Verify complete 2017-05-28 19:36:20, Info CSI 0000007c [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:20, Info CSI 0000007d [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:22, Info CSI 0000007f [SR] Verify complete 2017-05-28 19:36:22, Info CSI 00000080 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:22, Info CSI 00000081 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:25, Info CSI 0000009c [SR] Verify complete 2017-05-28 19:36:25, Info CSI 0000009d [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:25, Info CSI 0000009e [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:27, Info CSI 000000a7 [SR] Verify complete 2017-05-28 19:36:27, Info CSI 000000a8 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:27, Info CSI 000000a9 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:30, Info CSI 000000b0 [SR] Verify complete 2017-05-28 19:36:30, Info CSI 000000b1 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:30, Info CSI 000000b2 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:32, Info CSI 000000b4 [SR] Verify complete 2017-05-28 19:36:32, Info CSI 000000b5 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:32, Info CSI 000000b6 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:35, Info CSI 000000bf [SR] Verify complete 2017-05-28 19:36:35, Info CSI 000000c0 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:35, Info CSI 000000c1 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:38, Info CSI 000000c4 [SR] Verify complete 2017-05-28 19:36:38, Info CSI 000000c5 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:38, Info CSI 000000c6 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:40, Info CSI 000000c7 [SR] Verify complete 2017-05-28 19:36:40, Info CSI 000000c8 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:40, Info CSI 000000c9 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:43, Info CSI 000000cb [SR] Verify complete 2017-05-28 19:36:43, Info CSI 000000cc [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:43, Info CSI 000000cd [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:47, Info CSI 000000e6 [SR] Verify complete 2017-05-28 19:36:47, Info CSI 000000e7 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:47, Info CSI 000000e8 [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:50, Info CSI 000000f8 [SR] Verify complete 2017-05-28 19:36:50, Info CSI 000000f9 [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:50, Info CSI 000000fa [SR] Beginning Verify and Repair transaction 2017-05-28 19:36:54, Info CSI 0000011e [SR] Verify complete 2017-05-28 19:36:54, Info CSI 0000011f [SR] Verifying 100 (0x0000000000000064) components 2017-05-28 19:36:54, Info CSI 00000120 [SR] Beginning Verify and Repair transaction
0
Warum glauben Sie, dass Sie SFC ausführen müssen? Darüber hinaus sollten Sie DISM und nicht SFC ausführen, seit Sie Windows 8 oder höher verwenden Ramhound vor 6 Jahren 0
Ran dism. War in Ordnung. Ran sfc, der noch nie Probleme hatte. Etwas wurde gepatzt Alex S vor 6 Jahren 0
Siehe meine vorhergehende, aber zusammenhängende Frage zur Oper. Kann nicht per Handy verbunden werden Alex S vor 6 Jahren 0
Wenn bei DISM angegeben wurde, dass keine Reparatur erforderlich ist, besteht kein Grund zur Beeinträchtigung des SFC-Ausfalls. Ich bin zu faul, eine andere Frage zu lesen. Bitte machen Sie diese Frage klar Ramhound vor 6 Jahren 0
Wird auf dem Handy mehr posten, sobald chkdsk abgeschlossen ist Alex S vor 6 Jahren 0
Stellen Sie sicher, dass Sie sfc von 64bit cmd.exe ausführen, wenn Sie 64bit Windows 8.1 verwenden magicandre1981 vor 6 Jahren 0
@ magicandre1981 - Ja, es ist 64 Bit CMD - Wie gesagt, ich habe das schon viele Male gemacht, aber zum ersten Mal habe ich ein solches Problem Alex S vor 6 Jahren 0
@Ramhound - Aktualisierte und hinzugefügte Informationen zu der anderen, aber VERBUNDENTE Frage - https://superuser.com/questions/1213677/opera-error-can-t-open-user-profile-directory-ecache-you-ausreichend -priv Alex S vor 6 Jahren 0

0 Antworten auf die Frage

Verwandte Probleme