[Server2012R2Upd3 x64] Windows Update failure

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 attached file 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

Last edited:
Slowly moving forward.
Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 02.01.2018
Ran by administrator (11-01-2018 17:39:31) Run:1
Running from C:\Users\administrator.Q\Desktop
Loaded Profiles: administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER (Available Profiles: wg_service & prtgdata & administrator & Administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER & Classic .NET AppPool & .NET v4.5 & .NET v2.0 & .NET v4.5 Classic & .NET v2.0 Classic)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_cfscommonuifx.resources_31bf3856ad364e35_6.3.9600.16384_en-us_b8e784add9b78244|identity
StartRegedit:
"identity"=hex:43,66,73,43,6f,6d,6d,6f,6e,55,49,46,78,2e,52,65,73,6f,75,72,63,\
  65,73,2c,20,43,75,6c,74,75,72,65,3d,65,6e,2d,55,53,2c,20,56,65,72,73,69,6f,\
  6e,3d,36,2e,33,2e,39,36,30,30,2e,31,36,33,38,34,2c,20,50,75,62,6c,69,63,4b,\
  65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,\
  20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,6d,73,\
  69,6c,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"c!cfscommonui..anguagepack_31bf3856ad364e35_6.3.9600.16384_40ac03822614c8d4"=hex:
"c!sharemgmt-r..anguagepack_31bf3856ad364e35_6.3.9600.16384_ed9c5f2b21765200"=hex:
"c!microsoft-w..anguagepack_31bf3856ad364e35_6.3.9600.16384_19f3ba13d2461e3c"=hex:
"f!cfscommonuifx.resources.d_056cfbf11562afac"=dword:00000021
EndRegedit:
*****************

Error: (0) Failed to create a restore point.

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.


========= End of CMD: =========

"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_cfscommonuifx.resources_31bf3856ad364e35_6.3.9600.16384_en-us_b8e784add9b78244\\identity" => removed successfully

====> Registry

==== End of Fixlog 17:39:32 ====
dism now fails with a source error:
Code: 
C:\Windows\Logs\CBS>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required t
o restore the feature. For more information on specifying a source location, see
 http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
 
Downloaded and ran fixlist.txt again
Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 02.01.2018
Ran by administrator (11-01-2018 17:54:34) Run:2
Running from C:\Users\administrator.Q\Desktop
Loaded Profiles: administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER (Available Profiles: wg_service & prtgdata & administrator & Administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER & Classic .NET AppPool & .NET v4.5 & .NET v2.0 & .NET v4.5 Classic & .NET v2.0 Classic)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
cmd: reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS
DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_cfscommonuifx.resources_31bf3856ad364e35_6.3.9600.16384_en-us_b8e784add9b78244|identity
StartRegedit:
"identity"=hex:43,66,73,43,6f,6d,6d,6f,6e,55,49,46,78,2e,52,65,73,6f,75,72,63,\
  65,73,2c,20,43,75,6c,74,75,72,65,3d,65,6e,2d,55,53,2c,20,56,65,72,73,69,6f,\
  6e,3d,36,2e,33,2e,39,36,30,30,2e,31,36,33,38,34,2c,20,50,75,62,6c,69,63,4b,\
  65,79,54,6f,6b,65,6e,3d,33,31,62,66,33,38,35,36,61,64,33,36,34,65,33,35,2c,\
  20,50,72,6f,63,65,73,73,6f,72,41,72,63,68,69,74,65,63,74,75,72,65,3d,6d,73,\
  69,6c,2c,20,76,65,72,73,69,6f,6e,53,63,6f,70,65,3d,4e,6f,6e,53,78,53
"c!cfscommonui..anguagepack_31bf3856ad364e35_6.3.9600.16384_40ac03822614c8d4"=hex:
"c!sharemgmt-r..anguagepack_31bf3856ad364e35_6.3.9600.16384_ed9c5f2b21765200"=hex:
"c!microsoft-w..anguagepack_31bf3856ad364e35_6.3.9600.16384_19f3ba13d2461e3c"=hex:
"f!cfscommonuifx.resources.d_056cfbf11562afac"=dword:00000021
EndRegedit:
*****************

Error: (0) Failed to create a restore point.

========= reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS =========

The operation completed successfully.


========= End of CMD: =========

"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_cfscommonuifx.resources_31bf3856ad364e35_6.3.9600.16384_en-us_b8e784add9b78244\\identity" => not found

====> Registry

==== End of Fixlog 17:54:34 ====
 
Had to reboot to release a lock on components, and ran dism after the reboot with a different result:
Code: 
C:\Windows\Logs\CBS>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 582

An illegal character was encountered. For a multi-byte character set this includ
es a lead byte without a succeeding trail byte. For the Unicode character set th
is includes the characters 0xFFFF and 0xFFFE.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Package containing cbs.log, dism.log, and components here: Download package2.zip from Sendspace.com - send big files the easy way
 
I'm going to need another thing:

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run DISM just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
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 attached file 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

Same result unfortunately.
Code: 
C:\Windows\Logs\CBS>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]

Error: 582

An illegal character was encountered. For a multi-byte character set this includ
es a lead byte without a succeeding trail byte. For the Unicode character set th
is includes the characters 0xFFFF and 0xFFFE.

The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 02.01.2018
Ran by administrator (15-01-2018 08:44:12) Run:3
Running from C:\Users\administrator.Q\Desktop
Loaded Profiles: administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER (Available Profiles: wg_service & prtgdata & administrator & Administrator & ReportServer & SQLSERVERAGENT & MSSQLSERVER & Classic .NET AppPool & .NET v4.5 & .NET v2.0 & .NET v4.5 Classic & .NET v2.0 Classic)
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
cmd: reg load hklm\components c:\windows\system32\config\components
DeleteValue:HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_jsc_b03f5f7f11d50a3a_6.3.9600.20708_none_ac0b2c3fb531ff52|S256H
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_jsc_b03f5f7f11d50a3a_6.3.9600.20708_none_ac0b2c3fb531ff52]
"S256H"=hex:16,0d,52,37,d4,a3,79,75,85,a5,4b,7c,41,87,ff,ab,34,62,cd,1c,70,2c,\
b3,0d,5a,f6,85,ad,1a,17,06,ef
EndRegedit:
*****************

Error: (0) Failed to create a restore point.

========= reg load hklm\components c:\windows\system32\config\components =========

The operation completed successfully.


========= End of CMD: =========

"HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\msil_jsc_b03f5f7f11d50a3a_6.3.9600.20708_none_ac0b2c3fb531ff52\\S256H" => removed successfully

====> Registry

==== End of Fixlog 08:44:13 ====

I'll PM you with another package of the procmon etl during a dism and a copy of the cbs.log.
 
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 attached file 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

Apologies for the delay, was out for a few days.

Made some progress in the meanwhile, the integration tools have managed to update and a few Windows updates installed successfully. Last hanging update is a .NET update KB4033369 that will always fail to install. I've cleared out SoftwareDistribution and run sfc and dism with no positive result.

dism will always finished saying it repaired the corruption successfully, but the update will never apply.

Code: 
C:\Windows\Logs\CBS>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 6.3.9600.17031

Image Version: 6.3.9600.17031

[==========================100.0%==========================]
The restore operation completed successfully. The component store corruption was
 repaired.
The operation completed successfully.

cbs.log at Download CBS.log from Sendspace.com - send big files the easy way
 
Hello, I apologize for the delay!

Please attempt to install again and when it fails do the following:

Using the .NET Collect Utility


  1. Download collect.exe and save to your desktop.
  2. Go ahead and run the tool
  3. The utility creates a compressed cabinet of all the needed logs to %TEMP%\vslogs.cab.
  4. Please zip/attach to this post or if too large, send using a service such as SendSpace.
 
Before we do anything further, I would like to inform you that we are dealing with a .NET Framework issue here, namely the 4.7 version. Framework errors are considered to be the hardest of them all, so there is a chance we will not be able to resolve this without repair install. Also, please ensure that you have backed up everything prior to fixing.

Questions:

1. Which version of .NET Framework is currently present on the system?
2. If you go to Programs and Features, which version is listed there?
3. Have you tried running the offline installer for the Framework?
4. Have you tried uninstalling framework and installing the latest version afterwards?

Don't do anything but answer the questions until you have taken all the precautionary measures.

Thank you.
 
1. Add Roles and Features shows 3.5 and 4.5 are installed. In the registry Software\Microsoft\NET Framework Setup\NDP\v4\Full\Release is 460805, which is ".NET Framework 4.7 installed on all other Windows OS versions" according to MS.
2. See above
3. Just tried -- failed with "Component store is corrupted"
4. That scares me, I'll take a few more solid backups and give that a shot later this week.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top