C costinz Member Joined Jan 20, 2019 Posts 9 Jan 20, 2019 #1 I have tried various methods found on threads on your forum, with no luck. Attachments FRST.txt 25.4 KB · Views: 3 Addition.txt 31.6 KB · Views: 5
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Jan 22, 2019 #2 Hello! Please remove the manual proxies you have set. Afterwards, retry updates.
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 14, 2019 #3 Hello, Same issues - by the way the proxy was disabled. Still happens with 2019-03 Security Monthly Quality Rollup
Hello, Same issues - by the way the proxy was disabled. Still happens with 2019-03 Security Monthly Quality Rollup
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 14, 2019 #4 Hi! Can I get fresh CBS logs?
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #5 Hello - attached. Attachments CBS.log 113.9 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #6 Have you tried removing ESET?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #8 SURT and SFC did not report problems of any kind? Can you provide more information about the error?
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #9 SURT and SFC do not report any error. The error code is 80070020
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #10 Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar. 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
Step#1 - Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try installing the update just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar. 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
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #11 Hello - I'm afraid this won't help. The updates fail as soon as the server is rebooting - after 15% complete it reverts changes.
Hello - I'm afraid this won't help. The updates fail as soon as the server is rebooting - after 15% complete it reverts changes.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #12 I see. Can you upload a log where the error is clearly visible (after the failure) + setupapi.dev.log from C:\Windows\Inf.
I see. Can you upload a log where the error is clearly visible (after the failure) + setupapi.dev.log from C:\Windows\Inf.
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #13 Attached both Attachments CBS.zip 1.2 MB · Views: 1 setupapi.dev.zip 615.4 KB · Views: 1
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #14 Thank you. Could you please temporarily remove your backup software as there have bee several reports of it causing this issues.
Thank you. Could you please temporarily remove your backup software as there have bee several reports of it causing this issues.
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #15 Hello, unfortunately still reverting changes after Veritas Agent uninstall.
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Mar 15, 2019 #16 Okay, why do you have both ESET and Symantec present on the Server?
C costinz Member Joined Jan 20, 2019 Posts 9 Mar 15, 2019 #17 ESET replaced Symantec - Symantec has only the cloud agent - not the client installed.