Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Try to install KB4049411 and attach CBS.log if it fails.
[SOLVED] [10v1607b14393 x64] WU no longer working
- Thread starter bastianr
- Start date
can you specify how I can install a specific KB? the only way I know is to click the "Check for updates" button, but then it installs whatever it finds necessary first and that's not necessarily that one..
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Download an offline package for that update and run it.
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Is KB4053579 installed?
no, I had tried to install that one earlier by downloading a cumulative file. Strangely, it tells me this update is not suitable for my PC?? Although it is definitely the x64 version I have downloaded, checked it a couple of times.
I just ran it again, attached the updated CBS.log
View attachment CBS.zip
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Can you completely remove Avira using its removal tool and then try to upgrade again?
I've tried this, but no success. Have reinstalled it now as I didn't feel comfortable without AntiVirus.. I spend the last couple of days again trying to analyze a few other things and I realized that I have a device in the device manager which is shown as unknown. It shows "device descriptor request failed". Hence, I am unable to identify which device this is supposed to be.
I realized a while ago that my camera is not working. To be honest, I am not 100% sure if it was ever working as I never use it. I have researched everywhere, but there doesn't seem to be a dedicated driver for it. Actually, it would also wonder me because typically these kind of devices just work with windows standard drivers...
I have used the HP Recovery Manager to reinstall the chipset drivers, but that didn't help.
I fear that even a reinstall would not help with that particular issue as it would probably still not detect this device properly..
Any ideas?
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Please attach: C:\Windows\inf\setupapi.dev.log
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Can you take a screenshot of this device's HWID in Device Manager?
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Can you uninstall the device from the Device Manager?
I can, tried this as well. Update doesn't work anyway. Right now, I have disabled the device as you can see in the screenshot, but update doesn't work like that either..
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Have you tried to upgrade to v1703 first?
sorry for the late response, i was travelling.
I tried to go to 1709 directly via an ISO, but that didn't work either..
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Please read my question again.
sorry i didn't believe it makes a difference to go to 1709 vs. 1703 first so i thought you just meant going straight to the newest version.
Anyway, i downloaded an ISO for 1703, tried it, again same problem
CBS.log attached:
View attachment CBS.zipView attachment CBS.zip
Strange is that it doesn't show any errors in the log this time, but it stopped with a popup "Failed to install"...
Sysnative Windows Update
Inactive
- Oct 9, 2014
- 741
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run Dism /Online /Get-Drivers just like you have in the past.
3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
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.
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and run Dism /Online /Get-Drivers just like you have in the past.
3. Stop Process Monitor as soon as DISM fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
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.
Has Sysnative Forums helped you? Please consider donating to help us support the site!