[SOLVED] Win2008R2SP1, KB4507449 error 800736B3

D

dwfowler

Member
Joined
Jul 30, 2019
Posts
6
Not freaking out, as this has actually been going on for months, but I do need to get this resolved?

Windows Server 2008 R2 SP1

Since October 2018 (?), any Security Monthly Quality Rollup for Windows Server 2008 R2 for 64-based Systems fails with this error. Attempts to roll back to the last successful installation have failed.

sfc /scannow did not find any integrity violations
Windows6.1-KB947821-v34-x64.msi installed without errors, rebooted.
SFCFix found 106 unfixed errors, but it was still a relief to watch it run. Rebooted afterwards.
Tried to update with KB4507449, but still getting the 800736B3 error.

Zipped up the CBS directory, but it is a whopping 36mb. Hmm.

Yeah, work gives us OneDrive for Business, but getting it to create a direct link for anonymous sharing is like pulling hens' teeth. But Google Drive was much easier to work with.

So, I'm hoping that this link will give you access to the CBS.zip file without a lot of grief? If not, let me know. I'm really easy to work with.

SysNative - Google Drive

I haven't tried sharing Google Drive before, so please be patient? Or at least somewhat kind?
 
OK, please start with the following:

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as the it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


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 provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
I'm sorry that it took so long to get back to you.

I apologize for the size of these files. The LogFile.PML is 4 gb uncompressed, and 315 mb compressed. The CBS log files also grew to 43 mb compressed.

Here is the link from Google Drive. Let me know if this does not work for you?

SysNative - Google Drive
 
No worries:

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

I ran FRST64 as instructed, and here is the Fixlog.txt file.

I did not observe any errors, other than one that a system restore point could not be created (not worried about that).

I have rebooted the server, and refreshed a check for Windows updates, but have not attempted to apply the updates, in case you have concerns.

I do appreciate your assistance.
 

Attachments

I am quite pleased to report that the fix worked, and the server is now current on all Windows Updates. I can't thank you enough.
 
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