[SOLVED] Windows Server 2008 R2 Update Failure

blkdrac

blkdrac

Member
Joined
Aug 2, 2019
Posts
16
Morning,

Found your forum after a bit of searching on my own to find fixes for this problem.

Have gone down through your checklist of things to do.

#2: Ran SFC and no problems
#3: Ran SURT and lots of problems (lol)
#4: Ran and it found problems but could not fix (also on the first step of the scan it failed to do anything and just an error)
#5: Link to the CSB folder (DropBox): DropBox Link

Any form of help would be most appreciated. Been working on getting this fixed for over 2 weeks now.

Thank you,
Jeremy
 
Forgot the SFCFix report:

SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-02 10:51:36.844
Microsoft Windows Server 2008 R2 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423.
CORRUPT: Failed to repair orphaned component "value name not identified" (amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423) on component watchlist.





SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 45
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
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-08-02 10:58:59.072
----------------------EOF-----------------------
 
This is a Hyper-V VM. Have 4 other VM's running and no problems with any of the rest of them.

I haven's updated any ram on that machine. And no, haven't tested it for memory problems.
 
I see. Please do the following:


Step#1 - Export CBS hive
  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to Dropbox or OneDrive or SendSpace and just provide the link here.
 
Okie, not a problem. :-) Figured you have lots on your plate, helping lots of people.

Thank you very much.
 
Thank you for your patience!

SFCFixScript.txt

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.

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

Attachments

Ok, done.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2019-08-07 12:43:07.046
Microsoft Windows Server 2008 R2  - amd64
Using .txt script file at C:\Users\admJeremy\Desktop\SFCFixScript.txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_6_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_7_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_9_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017_RTM~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_6_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_6_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_7_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_7_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_9_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_9_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017_RTM~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017_RTM~31bf3856ad364e35~amd64~~6.1.1.1.
WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_6_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_7_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_8_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_9_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017_RTM~31bf3856ad364e35~amd64~~6.1.1.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2482017~31bf3856ad364e35~amd64~~6.1.1.1.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 6 datablocks.
Finish time: 2019-08-07 12:43:07.499
Script hash: 4qeWY2kDKihUjvX6f2SEJqn8brjpH5OHf5r7pT81I0k=
----------------------EOF-----------------------
 
Thanks!

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.
6. Run SURT again and attach CheckSUR.log.
 

Attachments

I am redacting the profiles from the Farbar scan just for security reasons, if you need them I can send them to you by PM.

Code: 
Fix result of Farbar Recovery Scan Tool (x64) Version: 07-08-2019 02
Ran by Redacted (08-08-2019 07:46:33) Run:1
Running from C:\Users\Redacted\Desktop
Loaded Profiles: Redacted
Boot Mode: Normal
==============================================

fixlist content:
*****************
CreateRestorePoint:
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423|Package_1_for_KB2508429~31bf3856ad364e35~amd64~~6.1.1.0.2508429-5_neutral_LDR
DeleteValue: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423|Package_1_for_KB2508429~31bf3856ad364e35~amd64~~6.1.1.0.2508429-6_neutral_GDR
*****************

Error: (0) Failed to create a restore point.
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423\\Package_1_for_KB2508429~31bf3856ad364e35~amd64~~6.1.1.0.2508429-5_neutral_LDR" => removed successfully
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-smbserver-common_31bf3856ad364e35_0.0.0.0_none_83cebf6510aec423\\Package_1_for_KB2508429~31bf3856ad364e35~amd64~~6.1.1.0.2508429-6_neutral_GDR" => removed successfully

==== End of Fixlog 07:46:33 ====
 

Attachments

Tried running update on it for the Service Pack and it gets about 3/4 of the way through and fails.
Capture3.PNG

I am including the Windows application error logs for this install, there were 4 of them (don't know if this helps any)
 

Attachments

Last edited:
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