Forum Discussion
[Insider] Cant update from 17763.107 to 18290.1000 on HP probook 450 G3
Window update install fail and it re-download the package build so many times. I tried many solutions to solve it but nothing work.
Do anyone have same problem and had solved it?
8 Replies
Hello, I may be able to help, I just need a little more info. do you have an error log or output that shows how it failed. There are a couple things you can do to get that information. https://www.onthewinside.com/blog/how-to-troubleshoot-a-bad-upgrade-part-2-lets-dig-deeper . What I am looking for is the actual failure code that caused the bad upgrade. Was it due to a bad download, drive etc. If you could get me something I can possibly help you out more.
Murray
And there are logs when run SetupDiag.
Well the SetupDiag logs give us a big fat zero
SetupDiag was unable to match to any known failure signatures. found with the results log. The initial error leads that you produced out of the eventlog leads me to believe that it is an incomplete download or something that is missing. Lets start with the following to get your system on the right track:
Do a DiskCleanup and choose system files and cleanup anything you don't need and ensure you have enough free drive space (you may not choose to remove older versions if you wish to downgrade)
From an Admin CMD prompt run
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
Download the following script
https://gallery.technet.microsoft.com/scriptcenter/Reset-WindowsUpdateps1-e0c5eb78
extract the file and save it to a temp directory
do a reboot then before you try anything else login and spawn a powershell prompt with bypass
powershell –ExecutionPolicy Bypass
go to the directory where the file is saved and run it with
./Reset-WindowsUpdate.ps1
This will reset your windows update completely, restart as it will ask you to do this and it should finally do a re download of the 18290 within windowsupdates. Let it go through its routine and see the results. This may not always work but it has a good chance of getting thing working. Because the setupdiag produced no know errors and the EventVwr error points to a really generic error by reseting everything and then seeing what errors appear my get us in a better spot. Let me know how things turn out.
Murray
Sorry for late reply. I found this in event log:
<Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" /><EventID>20</EventID><Version>1</Version><Level>2</Level><Task>1</Task><Opcode>13</Opcode><Keywords>0x8000000000000028</Keywords><TimeCreated SystemTime="2018-10-10T05:11:27.718591500Z" /><EventRecordID>15199</EventRecordID><Correlation /><Execution ProcessID="1512" ThreadID="9360" /><Channel>System</Channel><Computer>HN-PVANH-NB</Computer><Security UserID="S-1-5-18" /></System><Data Name="errorCode">0x80070103</Data><Data Name="updateTitle">Conexant - MEDIA - 7/3/2018 12:00:00 AM - 8.65.262.0</Data><Data Name="updateGuid">{298e7794-324f-4dfd-9529-7eba09145516}</Data><Data Name="updateRevisionNumber">1</Data><Data Name="serviceGuid">{8b24b027-1dee-babb-9a95-3517dfb9c552}</Data></EventData></Event>
