[SOLVED] Windows Server 2012 Standard: same updates again and again..

Offspring · Oct 15, 2019

Hi all!

I have this problem of updates always coming back on a Server 2012, even though it seems to install correctly, after reboot it shows the same updates as available for installation again..

SFC found issues it couldn't resolve, so here are the next troubleshooting steps below..

What could I do to solve this annoying issue?

Thank you very much for the support!

JM

___________

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-10-15 19:22:24.003
Microsoft Windows Server 2012 - amd64
Not using a script file.

AutoAnalysis::
FIXED: Performed DISM repair on file Amd64\CNBJ2530.DPB of version 6.2.9200.16430.

SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.

Failed to generate a complete zip file. Upload aborted.

SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2019-10-16 02:29:51.557
----------------------EOF-----------------------

Link on CBS Logs: CBS.zip

Sysnative Windows Update · Oct 15, 2019

Hello and welcome!

Please start with SFC Scan:

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Offspring · Oct 16, 2019

Here is the CBS.log

Sysnative Windows Update · Oct 16, 2019

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

Download SFCFix.exe (by niemiro) and save this to your Desktop.
Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
Save any open documents and close all open windows.
On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
SFCFix will now process the script.
Upon completion, a file should be created on your Desktop: SFCFix.txt.
Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

SFC Scan

Click on the Start button and in the search box, type Command Prompt
When you see Command Prompt on the list, right-click on it and select Run as administrator
When command prompt opens, copy and paste the following commands into it, press enter after each

sfc /scannow

Wait for this to finish before you continue

copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Offspring · Oct 16, 2019

Hi again,

Please find below the result of SFCFix, and attached the log file from SFC that didn't find any issue this time!

Should I try updates again now or is there any other step I should go through before?

Thank you for your support!

Code:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-10-16 11:04:15.902
Microsoft Windows Server 2012  - amd64
Using .zip script file at C:\Users\Administrateur\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\amd64\cnbj2530.dpb

Successfully copied file C:\Users\Administrateur\AppData\Local\niemiro\Archive\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\amd64\cnbj2530.dpb to C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\amd64\cnbj2530.dpb.

Successfully restored ownership for C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\amd64\cnbj2530.dpb
Successfully restored permissions on C:\Windows\winsxs\amd64_prncacla.inf_31bf3856ad364e35_6.2.9200.16430_none_fdce12188b615b12\amd64\cnbj2530.dpb
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2019-10-16 11:04:16.782
Script hash: IVpRFbNXl/Z9+LrRJnrYu6EUy07Y6EZvkN3AZzSKiRM=
----------------------EOF-----------------------

Sysnative Windows Update · Oct 16, 2019

Yes, please try the update.

Offspring · Oct 16, 2019

Hmm I had a short moment of hope when I saw success after installing the pending updates and then seeing the green "Your system is up-to-date" thing...
But I searched for updates again and they came back

Same state than before, with some updates with status "waiting for a restart" although I restarted several times.

Do you have any idea where I should look next?

Thank you for your time!

JM

Sysnative Windows Update · Oct 16, 2019

Hi!

Please do the following:

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.

Offspring · Oct 16, 2019

Ouch! I ran the Farbar 64bits with the fixlist.txt, it finished and wanted to reboot.
Now it's still restarting and always finishing update 3/3 during restart, hits 100% and restart again, forever!

The bad thing is that this server is in production again tomorrow morning (like in 7 hours from now

)

Sysnative Windows Update · Oct 16, 2019

So it does not boot into Windows or it does, but it keeps asking for a restart?

Offspring · Oct 16, 2019

It's in a restart loop, doing update 3/3 up to 100%, then restarting, update 3/3 again, forever.
That happened after Farbar notified me that it would need to reboot, and rebooted by itself.

Sysnative Windows Update · Oct 16, 2019

I see, thank you.

Do you have a USB drive we could use to access the command prompt from recovery mode and delete a certain file?

Offspring · Oct 16, 2019

Well, I could organize this and use my Win10 bootable USB key, but I'm actually 15 minutes drive away from the server, connecting through Chrome Remote Desktop.. I'd have to go there early I think the first worker starts at 5:30 am

Sysnative Windows Update · Oct 16, 2019

Okay, let me explain what I think happened here, the CLFS Log files got corrupt: Using Common Log File System - Windows drivers

I've cleared them out and that has likely resolved the issue. However, it looks like there is still a remnant from an old update in the database giving us grief, so I'd like you to find and rename or delete the following file: C:\Windows\WinSXS\Pending.xml and then reboot the Server.

Bear in mind that since this will likely have to be done from recovery mode, the drive letter will likely be changed.

In order to see what the letter is do the following:

Boot to the Command Prompt.
Type in Notepad.
Press Ctrl+O
Navigate to This PC and check what the drive letter is
Find the file I spoke of (pending.xml) and rename it or delete it.
Reboot and let me know.

And please accept my apologies for not anticipating this in advance.

Offspring · Oct 16, 2019

Woow, after at least 20 reboots it finally booted!
I'm feeling better now :)

Here is the result:

Code:

Résultats de correction de Farbar Recovery Scan Tool (x64) Version: 12-10-2019 02
Exécuté par Administrateur (16-10-2019 21:37:14) Run:1
Exécuté depuis C:\Users\Administrateur\Desktop
Profils chargés: Administrateur & MSSQL$SQLEXPRESS (Profils disponibles: GHP & MEL & KOW & HEP & Administrateur & MSSQL$SQLEXPRESS)
Mode d'amorçage: Normal
==============================================

fixlist contenu:
*****************
cmd: sc config trustedinstaller start= auto
cmd: net start trustedinstaller
cmd: fsutil resource setautoreset true %SystemDrive%\
cmd: attrib -r -s -h %SystemRoot%\System32\Config\TxR\*
StartPowershell:
function Move-LockedFile
{
    param($path, $destination)
    $path = (Resolve-Path $path).Path
    $destination = $executionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($destination)
  
    $MOVEFILE_DELAY_UNTIL_REBOOT = 0x00000004
    $MOVEFILE_REPLACE_EXISTING = 1
    $memberDefinition = @'
    [DllImport("kernel32.dll", SetLastError=true, CharSet=CharSet.Auto)]
    public static extern bool MoveFileEx(string lpExistingFileName, string lpNewFileName,
       int dwFlags);
'@
    $type = Add-Type -Name MoveFileUtils -MemberDefinition $memberDefinition -PassThru  
    $type::MoveFileEx($path, $destination, $MOVEFILE_DELAY_UNTIL_REBOOT + $MOVEFILE_REPLACE_EXISTING)
}
Get-ChildItem -path "$env:SystemRoot\system32\Config\TxR\." |
Foreach-Object {
  write-output $_.fullname
  Move-LockedFile -path $_.fullname "$env:SystemRoot\Temp\junk"
}
EndPowershell:
cmd: attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\*
cmd: del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.tm*
cmd: del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.blf
cmd: del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms
EmptyTemp:

*****************


========= sc config trustedinstaller start= auto =========

[SC] ChangeServiceConfig r‚ussite(s)

========= Fin de CMD: =========


========= net start trustedinstaller =========

Le service Programme d'installation pour les modules Windows d‚marre.
Le service Programme d'installation pour les modules Windows a d‚marr‚.


========= Fin de CMD: =========


========= fsutil resource setautoreset true %SystemDrive%\ =========

Op‚ration r‚ussie.

========= Fin de CMD: =========


========= attrib -r -s -h %SystemRoot%\System32\Config\TxR\* =========


========= Fin de CMD: =========


========= Powershell: =========

C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.0.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.1.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.2.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.3.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.4.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.5.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.6.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1b-d701-11e1-b7c4-0026b9545789}.TxR.blf
True
C:\Windows\system32\Config\TxR\{16943b1c-d701-11e1-b7c4-0026b9545789}.TM.blf
True
C:\Windows\system32\Config\TxR\{16943b1c-d701-11e1-b7c4-0026b9545789}.TMContainer00000000000000000001.regtrans-ms
True
C:\Windows\system32\Config\TxR\{16943b1c-d701-11e1-b7c4-0026b9545789}.TMContainer00000000000000000002.regtrans-ms
True

========= Fin de Powershell: =========


========= attrib -r -s -h %SystemRoot%\System32\SMI\Store\Machine\* =========


========= Fin de CMD: =========


========= del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.tm* =========


========= Fin de CMD: =========


========= del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.blf =========

Impossible de trouver C:\Windows\System32\SMI\Store\Machine\*.blf

========= Fin de CMD: =========


========= del /f /q %SystemRoot%\System32\SMI\Store\Machine\*.regtrans-ms =========

Impossible de trouver C:\Windows\System32\SMI\Store\Machine\*.regtrans-ms

========= Fin de CMD: =========


=========== EmptyTemp: ==========

BITS transfer queue => 8388608 B
DOMStore, IE Recovery, AppCache, Feeds Cache, Thumbcache, IconCache => 16100235 B
Java, Flash, Steam htmlcache => 343 B
Windows/system/drivers => 152942300 B
Edge => 0 B
Chrome => 156162537 B
Firefox => 0 B
Opera => 0 B

Temp, IE cache, history, cookies, recent:
Default => 0 B
Users => 0 B
ProgramData => 0 B
Public => 0 B
systemprofile => 128 B
systemprofile32 => 256 B
LocalService => 256 B
NetworkService => 256 B
GHP.ALMEC => 58507 B
MEL => 205771 B
KOW => 230464 B
HEP => 272009 B
Acronis Agent User => 272009 B
Administrateur => 1662813 B
MSSQL$SQLEXPRESS => 1662813 B

RecycleBin => 13159930415 B
EmptyTemp: => 12.6 GB données temporaires supprimées.

================================


Le système a dû redémarrer.

==== Fin de Fixlog 21:37:59 ====

Sysnative Windows Update · Oct 16, 2019

Ah, okay! Awesome!

Please check for updates.

Offspring · Oct 16, 2019

I think it's fine, no updates found! :)
And the update history shows all the latest updates have succeeded! No more "restart pending"!

THANK YOU VERY MUCH!!! You were of a great help!

Sysnative Windows Update · Oct 16, 2019

That is amazing news indeed!

Thank you for placing your trust into Sysnative Forums.

[SOLVED] Windows Server 2012 Standard: same updates again and again..

Member

Inactive

Member

Attachments

Inactive

Attachments

Member

Attachments

Inactive

Member

Inactive

Attachments

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive

Member

Inactive