1

volunteer IT dept for a church. Server 2012 R2, Update was not working, got it to run and now after installing many updates, it appears the July 9 2019 rollop KB4507448 is the cause of failure.

After installing, system restarts, then reports could not complete and removes changes, restarts, repeats one more, then finally boots up with over 100 updates to be installed.

Tried a second time and got same results.

Suggestions?

12 Spice ups
2

Have you tried clearing the Update file location and then pulling the KB directly from MS?

EDIT: Location of Update directory

C:\Windows\SoftwareDistribution

3

Monday night, installed many (maybe nearly 200) updates and thought I was done, but update still not working, renamed the softwaredistribution folder as suggested Wednesday, Thursday the system started installing the updates AGAIN completely disrupting business for hours. when complete it restarted and began the could not complete, removing, restarting previously described.

No I have not tried a direct download and install (did download earlier) but waiting till after business day to try it. This has been an UPDATE HELL week.

4

Typically if it doesn’t go through Auto Download and install through Windows Update, chances are there’s either a Missing KB that you need (or it’s corrupted), but there are those times where a direct download will bypass that requirement and magic happens.

/shrug. It’s MS. What’d you expect?

5

Same problem here. But only KB4507448 doesn’t install (removes changes, restarts but no effect on other updates). Any suggestion how to diagnose cause of a problem?

6

Welcome to Spiceworks and thanks for your 1st post. The post is not appropriate to Spiceworks so I’m moving this to the General Windows Forum.

7

Hey OP,
Have you check Event logs in the Event Viewer?
Try “sfc /scannow” and restart the system at last.
Try chkdsk /f /r on your C drive.
Let me know if it did or didn’t help you. Thank you

8

I’m having issues with KB4507460 “Cumulative Update for Windows Server 2016 for x64-based Systems” Getting Error 0x8e5e03fa. This is a new Windows 2016 Server which has been receiving updates with no problem until last week.

@EminentX, your suggestions were helpful. Event viewer showed errors that indicate a “hardware problem”. I did an 'sfc /VERIFYONLY, and it apparently logged some errors, so I now know I need to run the utility with /SCANNOW to fix stuff. I also notice that there are other logs in there that seem to coincide with the date that this update failed.

9

In my case, the issue was resolved by disconnecting the attached storage prior to running the updates.

10

Thanks, will try removing external drive.

since my original post, I have tried all the following (muttiple times)

  1. stop BITS/Wsusa and removed Software Distribution folder
  2. sfc
    3 dism /online /restore health
  3. installing in small batches and have reduced the over 200 to just over 40.

Not sure what has happened, but now about half the time, restarting fails well into into loading Windows (logo up, busy stars rotate)d and hangs with a BSOD "your pc ran into a problem and needs to restart. We’re collecting some error info and then you can restart 0% complete’. the system is actually hung and my only action is to press the power button, power the server back on and it mostly starts and reboots the first time (have has to do it twice couple of times). Implication is inaccessible boot device.

Dell has replaced the MB and got same results. I seems to be some form of software bug/corruption when the reload of the OS determines it needs to complete and update and goes into the ‘getting ready’ sequence (my guess is it can’t find the info or data for the completion).

Maybe the external drive (an expansion Seagate USB hard drive) is being looked at instead of the Dell Virtual Raid c drive) and hence 'inaccessible boot device"

Any suggestions are welcome and this is driving me crazy as when I am doing remote maintenance (Remote Desktop) it is a real issue when I restart and cannot get backl in, cannot tell what happened, but when I travel on site, I walk in to the BSOD.