“Falha ao configurar” loop de reinicialização com as atualizações do Windows 7

3

Em uma tentativa de reparar um laptop antigo do Dell Inspiron que foi reparado anteriormente (enviado para um reparador e limpo instalado), estou preso a esse problema. Desde esse último reparo, o laptop ainda tem problemas e as atualizações do Windows falharam.

Quando ele tentar aplicar as alterações, o Windows Update falhará em um loop de reinicialização "Falha ao configurar ... reverter alterações". Parece também que todos os que falharam são atualizações de segurança.

Ao tentar executar chkdsk /f /r , ele me dirá:

The type of the file system is NTFS.

Cannot lock current drive.

Chkdsk cannot run because the volume is in use by another process.

Ao tentar fazer sfc /scannow , ele me dirá:

There is a system repair pending which requires reboot to complete.

Restart Windows and run sfc again.

Estou apenas assumindo que não posso usar esses comandos porque o Windows Update está no caminho? Eu fiz a varredura com o Malwarebytes (o VIPRE também está instalado) para que o problema não seja um vírus ou malware.

Usar o WindowsUpdateDiagnostic corrigirá alguns problemas, mas não conseguirá corrigir "O registro do serviço está ausente ou corrompido".

Estou perdido para onde ir, pois parece que nada está funcionando.

Visão geral do sistema

  • Dell Inspiron (2009)
  • Windows 7 Home Premium SP1 de 64 bits
  • 4 GB de RAM
por Matthew Wright 29.10.2015 / 02:10

2 respostas

7

Windows Failure - Recovery Console (Steps and Commands)

Leave a comment below with the error, or anything else you think may be helpful to others, which these steps helped you resolve.

(Links at bottom for step-by-step instruction still for getting to Recovery Console and Safe Mode)

Run the below #1 command (steps) first to find out which drive letter is assigned to the Windows OS partition from the Recovery Console as it may not be the standard "C" drive as it is otherwise.

  1. From the Recovery Console type in bcdedit| find "osdevice" press Enter and then look at the command output result.

Where you see osdevice partition=D: (output result of the command per #1) whatever drive letter is after parition= is the drive letter you'll use in place of C:\ in the below command so if it's ~D= then the below command will use ~image:D:\ /cle~ in that part of the command.

Warning: Ensure spaces are in the command and the forward and back slashes are just as typed.

  1. From the Recovery Console type in dism /image:C:\ /cleanup-image /revertpendingactions, and press Enter

    • If you get the error. . .
      • The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior. then. . .
      • type in (assuming OS is on "D" drive here) MD D:\Scratch press Enter then type in DISM /Image:D:\ /ScratchDir:D:\Scratch /Cleanup-Image /RevertPendingActions press Enter to rerun the command.)

If you still have trouble getting #2 to run from the Recovery Console, then try running the below command when logged onto Windows normally from the command prompt (run as administrator). If you're able to get #2 to run without error, then just skip the #3 step entirely.

  1. Type in DISM /Online /Cleanup-Image /RevertPendingActions from the command line run as administrator, and then press Enter.

If you cannot get #2 or #3 to work above, then you may need to boot to a Linux OS or perhaps you can do from Recovery Console and rename the below file on the "C" drive location (or whatever drive letter Windows is on per #1 above still) which is the file that keeps records of where the OS is on pending Windows Updates, etc.

Once this file is renamed, then a new file will be created on the next Windows Update attempt but if you have to run this option to fix the issue, it may be best to do #5 before applying any new Windows Updates.

  1. This is the file that you'll rename ->C:\Windows\winsxs\pending.xml

    Ensure you replace C:\Windows\~ with the drive letter determined in #1 above here too

    • From the Recovery Console type in CD /D "C:\Windows\winsxs" press Enter

    • Type in REN "pending.xml" "bak_pending.xml.bak" press Enter, reboot machine and complete #5 below

  2. Once that completes, boot to Safe Mode and then run the below command (optional):

    • Type in sfc /scannow from the command line run as administrator, and press Enter.

NONE OF THIS IS WORKING!!!

A few last resort items to try in order and from the Recovery Console. . .

Anywhere a drive letter is anywhere on any of the commands, ensure the drive letter is what's determined per step #1 above.

  1. CHKDSK D: /F /R < Let this complete regardless of how long it takes to complete; kick it off, and just check in on it periodically.

  2. SFC /SCANNOW /OFFBOOTDIR=D:\ /OFFWINDIR=D:\Windows

Important Note Installing Service Pack 1

Once you get this fixed, please download the Windows 7 Service Pack 1 manually (below download link), install it, and then reboot.

Be sure to not apply any Windows Updates via the Windows Update process until this is complete. Once Service Pack 1 is downloaded and installed, then move forward with the Windows Updates.

Download

Mais recursos

por 29.10.2015 / 02:50
2

Do log , vejo que você recebe um erro ERROR_RM_NOT_ACTIVE . Abra o Explorer, exclua todos os arquivos de C:\Windows\System32\config\TxR (verifique se os arquivos ocultos são mostrados no Explorer), agora abra um cmd.exe como Admin e execute este comando:

fsutil resource setautoreset true C:\

Agora reinicie o Windows e, após a reinicialização, tente instalar as atualizações novamente.

    
por 30.10.2015 / 06:38