[SOLVED] [WinServer2008R2SP1 x64] Persistent Error Code 8007000D.

[gjz]

Step #1
Space between start= and delayed-auto?


sc config wuauserv start= delayed-auto && sc start wuauserv
[SC] ChangeServiceConfig SUCCESS


SERVICE_NAME: wuauserv
TYPE : 20 WIN32_SHARE_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x7d0
PID : 428
FLAGS :


Step#2
Access Denied
System Update Readiness Tool (SUR)


Attach
C:\Windows\Logs\CBS\CheckSUR.log

 

[Sysnative Windows Update]

FRST Fix
Please download the 64bit version from here.
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. 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[gjz]

Please find the log results attached:

 

[Sysnative Windows Update]

Thank you. Please run System Update Readiness Tool again and provide CheckSUR.log

 

[gjz]

Running System Update Readiness Tool (SUR)

Attached
C:\Windows\Logs\CBS\CheckSUR.log

 

[Sysnative Windows Update]

Please attempt to install one of the updates and provide CBS.log if it fails. Please also tell me which exact update you have attempted.

 

[gjz]

I attempted to install the Knowledge Base with the lowest number first: KB3068708.

Install results:

But still in the list to be installed:

CBS.log compressed as ZIP file (use 7-zip to unpack):

 

[Sysnative Windows Update]

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Attempt to install KB3068708 again just like you did previously.
3. Stop Process Monitor as soon as the update is complete. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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.

 

[gjz]

Run it twice because it appeared to be installed again but upon searching for updates it resurfaced that it was not installed. Ran the PM again and captured again the log, a bit more compact because I may have ran it too long first time. CBS.log is included and may contain more events as I ran it twice and searched for updates. Hopefully it doesn't add overhead otherwise I have to clear the logs and re-run it. Attachments are too large and will send PM to you with link for download. KB is not installed according to the system updates even if it reports that it has.

 

[Sysnative Windows Update]

FRST Fix
Please download the 64bit version from here.
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. 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.

 

[gjz]

Script run without problems. Attached the Fixlog.txt file:

 

[Sysnative Windows Update]

Please try installing updates and provide CBS.log if any fail.

 

[gjz]

Install all high priority updates as instructed.

System reported one failed install but has to reboot system.

After reboot KB3068708 failed to install.

To assure no others failed ran a Check for Updates which resulted in only KB3068708 need installation.

Rerun installation of KB3068708, which failed and attach log files marked when they where captured. From my experience it is smarter to re-run the updater as sometimes the failed update will get fixed when doing so.

End result is that all updates have been installed and system appears to be working normal. But to avoid surprises I have send the several logs marked with descriptive text when they where captures. Please see PM for logfiles. The logfiles are so big that I cannot open them with Notepad++. Not sure why that is but they are very large. Is there a way to disable and enable this horrific type of logging? I noticed that other servers also suffer from slow and lengthy update process and probably they too create enourmous log files each time you run the updates.

 

[Sysnative Windows Update]

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. 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).
2. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
3. 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.
4. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
5. Try the offending update and if it fails, attach CBS.log

 

[gjz]

Ran the FRST64 utility with Administrator rights which first resulted in an error and second time it passed. It appears faster and log file is now smaller.

Attached both CBS.log files in PM for review if it has run as expected, they are too large to post here.

Used also DISM command to clean-up a little bit the winsxs folder as it remained large which did help but I cannot get it to be smaller than 17.7GB. Which may be a bad limitation for existing Windows 2008 servers as they age. For other trying to fix size problems with your winsxs folder on Windows 2008 R2 you can use these one of these DISM commands:
dism /online /cleanup-image /spsuperseded
dism /online /cleanup-image /spsuperseded /hidesp
It will take a long time bu should end with ...successfully. Do not use these commands on a newer server like Windows 2012 as this command changed and you have more options. A little bit of system defragmentation may help as well, just search for defrag and you will find it. It will run 3-10 steps (increases with fragmentation level). Don't forget to run analyse first. On AD without other roles just run both manually once a year and it will help. Using this command it reduced the size from 21.9G to 17.8GB. Which is ofter the difference between running smoothly or running out of space.

 

[Sysnative Windows Update]

Are you experiencing any more issues with Windows Update? If so, what are they?

 

[gjz]

No, I am very happy and believe it works. Let me close the ticket.

And of course remind others that the solution in the Thread is custom for my problem and if experience the same issue that this thread can be read but a new one should be opened as the fixed really target my unique problems. And ... if you are happy, don't forget to donate something.