Insider Build 14385 won't install on Surface Pro4 - how to trouble shoot?

Hello Mike,

We regret the inconvenience. Let me assist you to resolve the issue.

Follow the below methods and check if it helps to resolve the issue.

Method 1

You cannot rule out the handiwork of a third party software. Perform clean boot to determine if that is the case.

Clean Boot Disclaimer: Please go through the section: How to reset the computer to start as usual after troubleshooting with clean boot of the Kb article to boot the computer in normal startup after fixing the issue.

Also, verify that you have disabled any other third party real-time antimalware products that were installed on your PC, to check if any how incoming/outgoing connections to the PC are affected by the firewall.

Disclaimer: Antivirus software can help protect your computer against viruses and other security threats. In most cases, you shouldn't disable your antivirus software. If you have to temporarily disable it to install other software, you should re-enable it as soon as you're done.

Method 2

Follow these steps to run the Windows in built troubleshooter to identify any potential driver related issues present in your PC.

a)      Write Troubleshooting in the search box and hit enter.

b)      Click on Troubleshooting tab.        

c)      Click on view all option on the upper left corner.

d)      Select the Windows Update option from the list.

e)      Click Next to run the Troubleshooter.

Write to us with the updated status and the required information related to Windows Update, for us to be able to assist you further.

Thank You.

 Is there a  log file I can review to debug the problem?

It's more like there are log files where you can get some clues.   We don't have access to source or support documentation so "debugging" it would just be a wistful dream.  And it is so convoluted and obfuscated that trying to do self-support or reverse engineering with any level of completeness is just too frustrating.

It's really WU's WindowsUpdate.log that you would like to see but we don't have the Symbols for the Insider builds so you are restricted to some other less detailed logs or to the CBS.log.   E.g. see

http://answers.microsoft.com/en-us/windows/forum/windows_10-update/windowsupdatelog-unreadable/2e6b05ed-ac91-4186-a362-c6b5a7e42911

More recently I have found

Messages will be in CBS.log but I suggest using  msinfo32.exe WER and Event log to find the correct context (e.g. timestamps).  There are too many red herrings to chase otherwise.

FWIW I finally got 14385 installed but never got close with 14383 (a multitude of confusing contradictory error codes mostly in the 0x8024xxxx range).  In the CBS.log I noticed some symptoms suggesting that recent changes I had made regarding Printing had come back to bite me (again) so I disabled that.  There were also signs that changes I had made in Language and Region (to try to get Cortana happier) could also have been a problem cause.  I didn't try to do anything more with them so maybe 14385 did something for me about that instead.  The number of full downloads I went through make me glad that my ISP really does allow me "unlimited" broadband.

HTH

Robert Aldwinckle
---

I haven't been able to make this work with troubleshooting or clean boot.

I am loathe to uninstall my AV to install the beta. I am sure most of the general windows population will not be keen to uninstall their AV solution before upgrading to the anniversary release either.

I haven't been able to make this work with troubleshooting or clean boot.

I am loathe to uninstall my AV to install the beta. I am sure most of the general windows population will not be keen to uninstall their AV solution before upgrading to the anniversary release either.

I used to use third party antivirus software and had no problems until I suddenly had problems downloading a build. I uninstalled my third party antivirus and that build installed with no further problems. Since then I use the built in Windows Defender (which kicks in automatically when no third party exists) along with Malwarebytes and encounter no problems. This has been well documented in this forum concerning the use of third party antivirus programs with new beta software as Manufacturers can not keep up with the fast release of beta builds.

Since the Release To Manufacturing is usually a couple of weeks before the release to the general public the 3rd party AV builder may have updates completed before the release.

I also only use Windows Defender and MalwareBytes and have no problems as I am very careful where I browse and what I click on.

WEIRD - before I could uninstall ESET - 14388 dropped and installed without incident.

strange the "preview release" watermark is gone. this must be getting seriously close to release now