[SOLVED] Cumulative updates failing since June - Server 2016 1607

Well I didn't say anything but it's actually now happening to all four of our Server 2016 servers. That is the biggest commonality. Three of those servers were built from the same VM template, but the fourth was an in place upgrade.

I've checked several of the other servers with older OS's and the updates have continued to install.

I'm at a loss as to what it is that happened to cause this, especially because it was not all in the same month. I also understand that you are under no obligation, so if you want to shelve this case that's fine.
 
I ran netsh winhttp show proxy and was told there was no proxy. I also checked IE Internet Settings and there was no proxy there.
 
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 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).
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. Try updates and if any fail, attach CBS.log.
 

Attachments

I think a cleanup was a good idea. I ran through it and started a Windows Update. But it's frozen on 45% of a download. I'm going to try a stand alone update again once this process ends. I zipped up the current CBS.log and am attaching it now because currently it cycles through the CBS logs in an hour and I may miss when the current Windows Update attempt ends.

After I try an in place upgrade again I'll be sure to upload a current CBS.log if necessary.
 

Attachments

This CBS.zip of the CBS directory covers about 1.5 hours. I'm not sure if the 45% download progress freeze ended in this time. Soon I will try a stand alone update and provide another copy.
 

Attachments

Hey softwaremaniac,

I'm assuming by your message that my logs did not help. I haven't had a chance yet to do a stand alone install attempt. Hopefully tomorrow. When I do, do you want a CBS log at the time it asks to reboot or after it reverts and boots up again?

Also, if it would help I could try a regular Window Update attempt again and set an alarm for every hour throughout the day so I can catch the download halt when it's still in the logs. Let me know.
 
That is correct. If you don't wait until the error code, I cannot see anything as the log will capture only normal WU operation.

Since this is a reverting case, we may not even get that in CBS.log, but in setupapi.dev.log.
 
Ok. I will try a standard Windows Update process again first. Note that the Windows Update screen does not currently display an error code on failure. It just quits after hanging for a few hours. Regardless I will set an alarm for every hour today to try to catch it when it stop and while the CBS directory has not yet overwritten.

After I post that I will try a standalone installation again. If it fails I'll post the CBS directory and setupapi.dev.log after the reversion.
 
I was able to grab the CBS directory and the setupapi.dev.log within an hour after the Update Status reset. Like before, no error message was displayed, just an option to start downloading again.

I will try a stand alone update today or tomorrow and give you more logs then.
 

Attachments

Yes, I finally have an error to work with!

Code: 
2019-03-05 16:48:46, Error                 CSI    00000307@2019/3/5:21:48:46.727 (F) CMIADAPTER: Inner Error Message from AI HRESULT = c004f01f [Error,Facility=FACILITY_ITF,Code=61471 (0xf01f)]
 [
(null)
]
[gle=0x80004005]
2019-03-05 16:48:46, Error                 CSI    00000308@2019/3/5:21:48:46.727 (F) CMIADAPTER: AI failed. HRESULT = c004f01f [Error,Facility=FACILITY_ITF,Code=61471 (0xf01f)]
    Element:
    '<sppInstaller xmlns="urn:schemas-microsoft-com:spp:installer" />'
[gle=0x80004005]
2019-03-05 16:48:46, Error                 CSI    00000309@2019/3/5:21:48:46.727 (F) CMIADAPTER: Exiting with HRESULT code = c004f01f [Error,Facility=FACILITY_ITF,Code=61471 (0xf01f)].

Can you tell me if either of these two folders exist:


C:\Windows\system32\spp\tokens\skus\serverweb


C:\Windows\System32\spp\tokens\skus\ServerDatacenter

Can you tell me what edition of the Server is installed?

Thank you :)
 
Excellent!

C:\Windows\system32\spp\tokens\skus\serverweb exists.

C:\Windows\System32\spp\tokens\skus\ServerDatacenter does not exist.

The Standard edition is installed.

The directory C:\Windows\System32\spp\tokens\skus\ServerStandard exists.
 
Fantastic! That worked! Thank you so much!

44753

I checked the other 3 Server 2016 servers and each one has a C:\Windows\system32\spp\tokens\skus\serverweb directory with a time stamp that corresponds to when updates stopped working. Each of these servers are edition Standard. Shall I attempt the same fix on these servers?
 
Ok. I'm more limited as to when I can reboot the other 3 servers. I'll update you soon.
 
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