D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 10, 2022 #1 Hi Guys, I have this machine that won't update due to a pending.xml flag that won't clear no matter how many times I try to reboot it. Please see the below and attached. Appreciate your help as always! Derrick Step #2 - Run SFC Scan Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again. Step #3 – SURT/DISM Scan Skipped per instructions Step #4 - Run SFCFix See attached report Step #5 – Export/Upload CBS folder Uploaded Attachments CBS.zip 29.8 KB · Views: 4 SFCFix.txt 942 bytes · Views: 2
Hi Guys, I have this machine that won't update due to a pending.xml flag that won't clear no matter how many times I try to reboot it. Please see the below and attached. Appreciate your help as always! Derrick Step #2 - Run SFC Scan Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again. Step #3 – SURT/DISM Scan Skipped per instructions Step #4 - Run SFCFix See attached report Step #5 – Export/Upload CBS folder Uploaded
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 11, 2022 #2 Could you please open an elevated command prompt and enter the following command: Rich (BB code): fsutil resource setautoreset true %systemdrive%\ If you get a operation success message then please reboot your computer.
Could you please open an elevated command prompt and enter the following command: Rich (BB code): fsutil resource setautoreset true %systemdrive%\ If you get a operation success message then please reboot your computer.
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 11, 2022 #3 I ran the command and got the operation success message then rebooted. The pending windows updates failed. I then ran sfc /scannow to see what it would do but got this same message: There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again. Please see the attached for where I've been stuck on the updates. Thx! Attachments Capture.PNG 114.7 KB · Views: 4
I ran the command and got the operation success message then rebooted. The pending windows updates failed. I then ran sfc /scannow to see what it would do but got this same message: There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again. Please see the attached for where I've been stuck on the updates. Thx!
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 11, 2022 #4 Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply. Attachments fixlist.txt 1.4 KB · Views: 8
Step#1 - FRST Fix NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system 1. Please download Farbar Recovery Scan Tool and save it to your Desktop. Note: You need to run the 64-bit Version so please ensure you download that one. 2. Download the attached fixlist.txt and save it to the Desktop. Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop). 3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator. 4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run. 5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 12, 2022 #5 Please see the attached. Thx! Attachments Fixlog.txt 6.3 KB · Views: 3
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 14, 2022 #6 Hmm, looks like those files weren't deleted. Could you please try the following from Windows RE: Rich (BB code): attrib -r -s -h C:\Windows\System32\Config\TxR\* del C:\Windows\System32\Config\TxR\* attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* del C:\Windows\System32\SMI\Store\Machine\*.tm* del C:\Windows\System32\SMI\Store\Machine\*.blf del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms Please note you'll need to change C:\ to the drive letter where Windows is installed if it is different.
Hmm, looks like those files weren't deleted. Could you please try the following from Windows RE: Rich (BB code): attrib -r -s -h C:\Windows\System32\Config\TxR\* del C:\Windows\System32\Config\TxR\* attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* del C:\Windows\System32\SMI\Store\Machine\*.tm* del C:\Windows\System32\SMI\Store\Machine\*.blf del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms Please note you'll need to change C:\ to the drive letter where Windows is installed if it is different.
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 14, 2022 #7 This is what I got: Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. C:\Users\Derrick>attrib -r -s -h C:\Windows\System32\Config\TxR\* C:\Users\Derrick>del C:\Windows\System32\Config\TxR\* C:\Windows\System32\Config\TxR\*, Are you sure (Y/N)? Y C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.0.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.1.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.2.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TMContaine r00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TMContaine r00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process. C:\Users\Derrick>attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.tm* C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process. C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.blf C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process.
This is what I got: Microsoft Windows [Version 6.2.9200] (c) 2012 Microsoft Corporation. All rights reserved. C:\Users\Derrick>attrib -r -s -h C:\Windows\System32\Config\TxR\* C:\Users\Derrick>del C:\Windows\System32\Config\TxR\* C:\Windows\System32\Config\TxR\*, Are you sure (Y/N)? Y C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.0.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.1.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.2.regt rans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce3-d672-11e1-bc42-842b2b432f94}.TxR.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TMContaine r00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\Config\TxR\{b517bce4-d672-11e1-bc42-842b2b432f94}.TMContaine r00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process. C:\Users\Derrick>attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.tm* C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process. C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.blf C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TM.blf The process cannot access the file because it is being used by another process. C:\Users\Derrick>del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000001.regtrans-ms The process cannot access the file because it is being used by another process. C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT{b517bd07-d672-11e1-bc42-842b2b4 32f94}.TMContainer00000000000000000002.regtrans-ms The process cannot access the file because it is being used by another process.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 14, 2022 #8 Was that from the Windows Recovery Environment?
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 14, 2022 #9 Oops. I missed the "RE" in your last message. What's the best way that you suggest to boot into the RE?
Oops. I missed the "RE" in your last message. What's the best way that you suggest to boot into the RE?
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 15, 2022 #10 If you have a recovery partition then you can use that otherwise you'll need to boot from a Windows ISO. There's a few options listed here - Windows Recovery Environment (Windows RE)
If you have a recovery partition then you can use that otherwise you'll need to boot from a Windows ISO. There's a few options listed here - Windows Recovery Environment (Windows RE)
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 15, 2022 #11 All executed except the last two - "Could Not Find" What should I do next? The Windows Update history looks the same. I didn't try to check for new updates yet. attrib -r -s -h C:\Windows\System32\Config\TxR\* del C:\Windows\System32\Config\TxR\* attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* del C:\Windows\System32\SMI\Store\Machine\*.tm* del C:\Windows\System32\SMI\Store\Machine\*.blf COULD NOT FIND del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms COULD NOT FIND
All executed except the last two - "Could Not Find" What should I do next? The Windows Update history looks the same. I didn't try to check for new updates yet. attrib -r -s -h C:\Windows\System32\Config\TxR\* del C:\Windows\System32\Config\TxR\* attrib -r -s -h C:\Windows\System32\SMI\Store\Machine\* del C:\Windows\System32\SMI\Store\Machine\*.tm* del C:\Windows\System32\SMI\Store\Machine\*.blf COULD NOT FIND del C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms COULD NOT FIND
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 15, 2022 #12 That's fine, could you please try and install one of the problematic updates? If it fails (it probably will), then please attach the latest CBS log.
That's fine, could you please try and install one of the problematic updates? If it fails (it probably will), then please attach the latest CBS log.
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 15, 2022 #13 Checked for updates and got this error code: 80070BC9. Clicked try again and it said to restart. Restarted and had it check again. Same error code. Clicked Try again. Said to restart again. I didn't. Please see attached CBS. Thx. Attachments CBS.zip 91 KB · Views: 1
Checked for updates and got this error code: 80070BC9. Clicked try again and it said to restart. Restarted and had it check again. Same error code. Clicked Try again. Said to restart again. I didn't. Please see attached CBS. Thx.
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 17, 2022 #14 It seems to be the same error as before, let's try a different approach and try and revert the pending changes. Please create a suitable backup beforehand and then enter the Windows RE as you did before, however, you'll need to run the following command instead: Rich (BB code): DISM /Image:C:\ /Cleanup-Image /RevertPendingActions Please change the partition letter C:\ if is different for your system. If successful, then you should see something similar to the following: Rich (BB code): Reverting pending actions from the image... The operation completed. Any revert of pending actions will be attempted after reboot. The operation completed successfully.
It seems to be the same error as before, let's try a different approach and try and revert the pending changes. Please create a suitable backup beforehand and then enter the Windows RE as you did before, however, you'll need to run the following command instead: Rich (BB code): DISM /Image:C:\ /Cleanup-Image /RevertPendingActions Please change the partition letter C:\ if is different for your system. If successful, then you should see something similar to the following: Rich (BB code): Reverting pending actions from the image... The operation completed. Any revert of pending actions will be attempted after reboot. The operation completed successfully.
D DerrickH Contributor Joined Oct 14, 2017 Posts 43 Feb 25, 2022 #15 I'm sorry but I was out of town. I did the procedure (3 attempts total) and they appeared to fail. I decided to check for updates anyway and it found (3) new ones instead of it asking me to reboot! I installed them one by one and the first 2 installed fine: Windows Malicious Software Removal Tool x64 - v5.98 (KB890830) 2022-02 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012 for x64 (KB5010582) This one failed and reverted but after installing again and rebooting it finally took: 2022-02 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5010392) Looks like you guys pulled through again for me. Thank you!
I'm sorry but I was out of town. I did the procedure (3 attempts total) and they appeared to fail. I decided to check for updates anyway and it found (3) new ones instead of it asking me to reboot! I installed them one by one and the first 2 installed fine: Windows Malicious Software Removal Tool x64 - v5.98 (KB890830) 2022-02 Security and Quality Rollup for .NET Framework 3.5, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows Server 2012 for x64 (KB5010582) This one failed and reverted but after installing again and rebooting it finally took: 2022-02 Security Monthly Quality Rollup for Windows Server 2012 for x64-based Systems (KB5010392) Looks like you guys pulled through again for me. Thank you!
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,245 Location %systemroot% Feb 25, 2022 #16 No problem, glad you were able to install updates normally again