S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 3, 2018 #41 Try to install KB4049411 and attach CBS.log if it fails.
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 4, 2018 #42 softwaremaniac said: Try to install KB4049411 and attach CBS.log if it fails. Click to expand... 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..
softwaremaniac said: Try to install KB4049411 and attach CBS.log if it fails. Click to expand... 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..
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 4, 2018 #43 Download an offline package for that update and run it.
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 4, 2018 #44 I have tried that, but the weird thing is that catalog.update.microsoft.com states this KB does not exist?? Maybe I am too stupid for this..
I have tried that, but the weird thing is that catalog.update.microsoft.com states this KB does not exist?? Maybe I am too stupid for this..
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 4, 2018 #45 Is KB4053579 installed?
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 5, 2018 #46 softwaremaniac said: Is KB4053579 installed? Click to expand... 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
softwaremaniac said: Is KB4053579 installed? Click to expand... 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
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 5, 2018 #47 Can you completely remove Avira using its removal tool and then try to upgrade again?
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 14, 2018 #48 softwaremaniac said: Can you completely remove Avira using its removal tool and then try to upgrade again? Click to expand... 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?
softwaremaniac said: Can you completely remove Avira using its removal tool and then try to upgrade again? Click to expand... 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?
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 14, 2018 #49 Please attach: C:\Windows\inf\setupapi.dev.log
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 15, 2018 #50 softwaremaniac said: Please attach: C:\Windows\inf\setupapi.dev.log Click to expand... pls. see attached: View attachment setupapi.dev.log
softwaremaniac said: Please attach: C:\Windows\inf\setupapi.dev.log Click to expand... pls. see attached: View attachment setupapi.dev.log
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 15, 2018 #51 Can you take a screenshot of this device's HWID in Device Manager?
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 15, 2018 #52 softwaremaniac said: Can you take a screenshot of this device's HWID in Device Manager? Click to expand... the problem is that it's not showing any, see attached View attachment screenshots.pdf
softwaremaniac said: Can you take a screenshot of this device's HWID in Device Manager? Click to expand... the problem is that it's not showing any, see attached View attachment screenshots.pdf
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 16, 2018 #53 Can you uninstall the device from the Device Manager?
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 17, 2018 #54 softwaremaniac said: Can you uninstall the device from the Device Manager? Click to expand... 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..
softwaremaniac said: Can you uninstall the device from the Device Manager? Click to expand... 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..
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 17, 2018 #55 Have you tried to upgrade to v1703 first?
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 26, 2018 #56 softwaremaniac said: Have you tried to upgrade to v1703 first? Click to expand... sorry for the late response, i was travelling. I tried to go to 1709 directly via an ISO, but that didn't work either..
softwaremaniac said: Have you tried to upgrade to v1703 first? Click to expand... sorry for the late response, i was travelling. I tried to go to 1709 directly via an ISO, but that didn't work either..
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 26, 2018 #57 Please read my question again.
B bastianr Active member Joined Jan 4, 2018 Posts 36 Feb 28, 2018 #58 softwaremaniac said: Please read my question again. Click to expand... 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"...
softwaremaniac said: Please read my question again. Click to expand... 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"...
S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Feb 28, 2018 #59 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.
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.
B bastianr Active member Joined Jan 4, 2018 Posts 36 Mar 1, 2018 #60 Hi, Output as below: Read More: C:\WINDOWS\system32>dism /online /get-drivers Tool zur Imageverwaltung für die Bereitstellung Version: 10.0.14393.0 Abbildversion: 10.0.14393.0 Liste der Treiber von Drittanbietern wird aus dem Treiberspeicher abgerufen... Fehler: 126 Fehler: Der Treiberspeicher für das Abbild konnte nicht geöffnet werden. Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log". Logfiles attached. View attachment logfiles.zip
Hi, Output as below: Read More: C:\WINDOWS\system32>dism /online /get-drivers Tool zur Imageverwaltung für die Bereitstellung Version: 10.0.14393.0 Abbildversion: 10.0.14393.0 Liste der Treiber von Drittanbietern wird aus dem Treiberspeicher abgerufen... Fehler: 126 Fehler: Der Treiberspeicher für das Abbild konnte nicht geöffnet werden. Die DISM-Protokolldatei befindet sich unter "C:\WINDOWS\Logs\DISM\dism.log". Logfiles attached. View attachment logfiles.zip