{"id":2482,"date":"2020-11-03T03:00:19","date_gmt":"2020-11-03T03:00:19","guid":{"rendered":"http:\/\/leinss.com\/blog\/?p=2482"},"modified":"2022-07-08T17:18:40","modified_gmt":"2022-07-08T17:18:40","slug":"failed-to-apply-cumulative-update-on-server-2016","status":"publish","type":"post","link":"https:\/\/leinss.com\/blog\/?p=2482","title":{"rendered":"Failed to Apply Cumulative Update on Server 2016"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">These errors are always fun to track down.  Last month, I had a Windows Server 2016 VM that would always roll back the latest cumulative update for the OS.  I tried the usual tricks of running sfc \/scannow, dism, safe mode, etc. and nothing worked.  I gave up and moved on to something else.  Now again this month I had even more servers doing the exact same thing.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After some Googling, I did a deep dive into the logs under C:\\windows\\logs\\cbs\\ and looked for &#8220;, error&#8221; (<em>comma, then a space, then the word erro<\/em>r) around the time I tried applying the update and then found this:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Error [0x01803e] CSI 000000f5 (F) Failed execution of queue item Installer: HTTP Installer ({86fee01a-954a-11df-bc0c-cea7dfd72085}) with HRESULT HRESULT_FROM_WIN32(1058). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This did ring a bell as months earlier I had found a dev box that would not patch and it ended up that http.sys was disabled on that VM as well (<em>but it was enabled on the prod box???<\/em>).  The common thread between all 3 VMs was that they were all running Apache Tomcat.  The web developer had disabled the http.sys driver as this can &#8220;hijack&#8221; programs from listening on port 80, so to prevent this they just disable it, which also causes PowerShell remote management, printer spooler and branchcache services not to run (because they all rely on the http.sys driver running).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The fix is simple: enable the http.sys driver, run the patches, then disable http.sys:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sc qc http\nsc config http start= auto\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">After patching we can run these commands to set it back to disabled and restart again:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>net stop http \/y\nsc config http start= disabled\nsc qc http<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Soli Deo Gloria<\/li><\/ul>\n","protected":false},"excerpt":{"rendered":"<p>These errors are always fun to track down. Last month, I had a Windows Server 2016 VM that would always roll back the latest cumulative update for the OS. I tried the usual tricks of running sfc \/scannow, dism, safe mode, etc. and nothing worked. I gave up and moved on to something else. Now &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/leinss.com\/blog\/?p=2482\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Failed to Apply Cumulative Update on Server 2016&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[4,7],"tags":[],"class_list":["post-2482","post","type-post","status-publish","format-standard","hentry","category-operating-system","category-tech-tips"],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_shortlink":"https:\/\/wp.me\/p7wiG8-E2","jetpack-related-posts":[],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2482","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2482"}],"version-history":[{"count":13,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2482\/revisions"}],"predecessor-version":[{"id":3116,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/2482\/revisions\/3116"}],"wp:attachment":[{"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2482"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2482"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/leinss.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2482"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}