[SOLVED] Windows Update fails with Error 700736B3

Thanks for the info. Please continue with the following.

Step#1 - 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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - SFC Scan
  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. 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
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.

Items for your next post
1. SFCFix.txt
2. CBS.txt
 

Attachments

SFCFix.txt:
---
Code: 
SFCFix version 3.0.0.0 by niemiro.
Start time: 2016-06-27 10:51:30.720
Microsoft Windows Server 2008 R2 Service Pack 1 - amd64
Using .txt script file at C:\Users\grueger\Desktop\SFCScript(2).txt [0]




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_94c31fb2805ae016\6.1.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_9f17ca04b4bba211\6.1.

Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_94c31fb2805ae016\6.1.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_9f17ca04b4bba211\6.1.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_94c31fb2805ae016\6.1.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\wow64_microsoft-windows-webdavredir-mrxdav_31bf3856ad364e35_none_9f17ca04b4bba211\6.1.
RegistryScript:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2016-06-27 10:51:30.814
Script hash: X6jeBn07T0Wwcuea6V48l8CA5qsp+EdIC41+Zs9xYx4=
----------------------EOF-----------------------

And the attachment... this time really small. I have to restart the server. I can do this the earliest in round about 7 hours from now on.
But your solution looked promising.
 

Attachments

Ok, the installation was successful.
No errors any more on this one.
Can we repair the rest the same way?
And what is this error?
Where does it come from and how do I prevent it from happening again?
 
We need another capture. Please do the following. Note: Please ensure you delete any old logs so you don't send a previous one by mistake.

Step#1 - Capture Process Monitor Trace
 1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt the install of KB3149090 like you did previously.
3. Stop Process Monitor as soon as the update 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.
 
Thanks. This is a much bigger update. I need to gather some more info.

Step#1 - 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.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please
 

Attachments

Just wanted to give you an update. This is a very complex issue so it is taking some extra time to review and come up with a plan. I'll be back with you in the next day.
 
Hehe, thanks. You can read my mind. I wanted to ask if you're sick or too occupied. :)
So, thanks for the update.
 
After looking at this I've determined that the fixes needed to run to possibly get this to work are too dangerous to run on a Server in production.

One option I can offer if your interested, is to have you do a physical to virtual conversion of the machine (unless it's already virtual) and then upload it to me (I can provide info on this separately). I'll do the fixes on this copy to ensure it works and if it does I can provide you step by step what to do.

Another option I have done in the past (but not on a Domain Controller) is to do a repair install. I can provide info on this as well if interested but there is a risk since it's a DC.

Let me know what you would like to do.
 
I've discussed this with my boss and we will take the repair install.
First we have to make sure that the complete serverbackup we use is working (there are errors here too).
After this is confirmed we will make a repair install... is there anything special to a server repair install?
I've only done this with Windows XP and 7 Pro so far.
 
Nothing special. I've done this several times on Server 2008 R2 (sans DC Role) and after the repair and reboot I would get a message about repairing .NET Framework. I would answer OK and it would repair successfully. I just don't know how it would react with it being a DC but worth a shot if you have a good backup. If you do it, please let me know the results.
 
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