If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
KB4497934 update fails
Past couple of days have had an update fail:
2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
Ads |
#2
|
|||
|
|||
KB4497934 update fails
Jonathan N. Little wrote:
Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? This is a comment I could find. "Thank you for your time. Error 0x800f0986 is for incompatibility of update with ecosystem. We will offer the October Update to users via Windows Update when data shows your device is ready and you will have a great experience. If we detect that your device may have an issue, such as an application incompatibility, we will not install the update until that issue is resolved As Microsoft said in their blog post. Thanks again. " So that probably explains why running a hoover over the carpets, isn't helping. Now, the question would be, where is the damn log with the details. Is this a "cbs" thing? Where does windows Update keep logs ? cbs.log ? What if you were to "grep all the .log files on the system for 0x800f0986" ? Maybe Agent Ransack could do that for you, as it has content search and regex for filenames. filename: log$ content: 800f0986 (or maybe a decimal equivalent?) Paul |
#3
|
|||
|
|||
KB4497934 update fails
Paul wrote:
Jonathan N. Little wrote: Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? This is a comment I could find. Â*Â* "Thank you for your time. Â*Â*Â* Error 0x800f0986 is for incompatibility of update with ecosystem. Â*Â*Â*Â*Â*Â*Â* We will offer the October Update to users via Windows Update Â*Â*Â*Â*Â*Â*Â* when data shows your device is ready and you will have a Â*Â*Â*Â*Â*Â*Â* great experience. If we detect that your device may have Â*Â*Â*Â*Â*Â*Â* an issue, such as an application incompatibility, we will not Â*Â*Â*Â*Â*Â*Â* install the update until that issue is resolved Â*Â*Â* As Microsoft said in their blog post. Thanks again. Â*Â* " So that probably explains why running a hoover over the carpets, isn't helping. Now, the question would be, where is the damn log with the details. Is this a "cbs" thing? Where does windows Update keep logs ? cbs.log ? What if you were to "grep all the .log files on the system for 0x800f0986" ? Maybe Agent Ransack could do that for you, as it has content search and regex for filenames. Â*Â* filename:Â*Â*Â*Â* log$ Â*Â* content:Â*Â*Â*Â*Â* 800f0986Â* (or maybe a decimal equivalent?) Â* Paul Windows is such a PITA, whereas Linux grep 0x800f0986 /var/log/* or journalctl | grep 0x800f0986 so much simpler (* except Linux would not use some meaningless octal error code, but some human-descriptive error message) -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#4
|
|||
|
|||
KB4497934 update fails
Jonathan N. Little wrote:
Paul wrote: Jonathan N. Little wrote: Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? This is a comment I could find. "Thank you for your time. Error 0x800f0986 is for incompatibility of update with ecosystem. We will offer the October Update to users via Windows Update when data shows your device is ready and you will have a great experience. If we detect that your device may have an issue, such as an application incompatibility, we will not install the update until that issue is resolved As Microsoft said in their blog post. Thanks again. " So that probably explains why running a hoover over the carpets, isn't helping. Now, the question would be, where is the damn log with the details. Is this a "cbs" thing? Where does windows Update keep logs ? cbs.log ? What if you were to "grep all the .log files on the system for 0x800f0986" ? Maybe Agent Ransack could do that for you, as it has content search and regex for filenames. filename: log$ content: 800f0986 (or maybe a decimal equivalent?) Paul Windows is such a PITA, whereas Linux grep 0x800f0986 /var/log/* or journalctl | grep 0x800f0986 so much simpler (* except Linux would not use some meaningless octal error code, but some human-descriptive error message) There might be a WindowsUpdate.log, if memory serves. The thing is, Agent Ransack is like Linux "find" and "grep" at the same time. And the same could be done natively in WinXP. The problem with using Federated Search in Windows 10, is it's "never going to be set up properly" to get the desired result. I would promote Federated Search and try and teach people to use the Search Language, but ensuring the disk is indexed is "too hard". I have a lot of trouble here, getting C: even remotely close to fully indexed, so the built in inverted index can do the job for us. Agent Ransack, at least I know it'll do its best to examine the whole drive. It's not plotting and scheming to miss stuff. And on content searches, it's multithreaded, and will examine one file on each CPU core while running. It doesn't index anything in advance, but it does put the effort into the brute force search its got. https://www.mythicsoft.com/agentransack/?page=download Paul |
#5
|
|||
|
|||
KB4497934 update fails
Paul wrote:
Jonathan N. Little wrote: Paul wrote: Jonathan N. Little wrote: Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? This is a comment I could find. Â*Â* "Thank you for your time. Â*Â*Â* Error 0x800f0986 is for incompatibility of update with ecosystem. Â*Â*Â*Â*Â*Â*Â* We will offer the October Update to users via Windows Update Â*Â*Â*Â*Â*Â*Â* when data shows your device is ready and you will have a Â*Â*Â*Â*Â*Â*Â* great experience. If we detect that your device may have Â*Â*Â*Â*Â*Â*Â* an issue, such as an application incompatibility, we will not Â*Â*Â*Â*Â*Â*Â* install the update until that issue is resolved Â*Â*Â* As Microsoft said in their blog post. Thanks again. Â*Â* " So that probably explains why running a hoover over the carpets, isn't helping. Now, the question would be, where is the damn log with the details. Is this a "cbs" thing? Where does windows Update keep logs ? cbs.log ? What if you were to "grep all the .log files on the system for 0x800f0986" ? Maybe Agent Ransack could do that for you, as it has content search and regex for filenames. Â*Â* filename:Â*Â*Â*Â* log$ Â*Â* content:Â*Â*Â*Â*Â* 800f0986Â* (or maybe a decimal equivalent?) Â* Paul Windows is such a PITA, whereas Linux grep 0x800f0986 /var/log/* or journalctl | grep 0x800f0986 so much simpler (* except Linux would not use some meaningless octal error code, but some human-descriptive error message) There might be a WindowsUpdate.log, if memory serves. The thing is, Agent Ransack is like Linux "find" and "grep" at the same time. And the same could be done natively in WinXP. I have grep installed, perl, grep, sed, awk, are the first things I install on a Windows system. C:\Windows\WindowsUpdate.log: "Windows Update logs are now generated using ETW (Event Tracing for Windows). Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log. For more information, please visit https://go.microsoft.com/fwlink/?LinkId=518345" Another friggin' hoop to jump through. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#6
|
|||
|
|||
KB4497934 update fails
Jonathan N. Little wrote:
Paul wrote: Jonathan N. Little wrote: Paul wrote: Jonathan N. Little wrote: Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? This is a comment I could find. Â*Â* "Thank you for your time. Â*Â*Â* Error 0x800f0986 is for incompatibility of update with ecosystem. Â*Â*Â*Â*Â*Â*Â* We will offer the October Update to users via Windows Update Â*Â*Â*Â*Â*Â*Â* when data shows your device is ready and you will have a Â*Â*Â*Â*Â*Â*Â* great experience. If we detect that your device may have Â*Â*Â*Â*Â*Â*Â* an issue, such as an application incompatibility, we will not Â*Â*Â*Â*Â*Â*Â* install the update until that issue is resolved Â*Â*Â* As Microsoft said in their blog post. Thanks again. Â*Â* " So that probably explains why running a hoover over the carpets, isn't helping. Now, the question would be, where is the damn log with the details. Is this a "cbs" thing? Where does windows Update keep logs ? cbs.log ? What if you were to "grep all the .log files on the system for 0x800f0986" ? Maybe Agent Ransack could do that for you, as it has content search and regex for filenames. Â*Â* filename:Â*Â*Â*Â* log$ Â*Â* content:Â*Â*Â*Â*Â* 800f0986Â* (or maybe a decimal equivalent?) Â* Paul Windows is such a PITA, whereas Linux grep 0x800f0986 /var/log/* or journalctl | grep 0x800f0986 so much simpler (* except Linux would not use some meaningless octal error code, but some human-descriptive error message) There might be a WindowsUpdate.log, if memory serves. The thing is, Agent Ransack is like Linux "find" and "grep" at the same time. And the same could be done natively in WinXP. I have grep installed, perl, grep, sed, awk, are the first things I install on a Windows system. C:\Windows\WindowsUpdate.log: "Windows Update logs are now generated using ETW (Event Tracing for Windows). Please run the Get-WindowsUpdateLog PowerShell command to convert ETW traces into a readable WindowsUpdate.log. For more information, please visit https://go.microsoft.com/fwlink/?LinkId=518345" Another friggin' hoop to jump through. Latest attempt to install displayed after using PS comment to generate "readable" log C:\Users\Jonathan\Desktopgrep 12:35 WindowsUpdate.log 2019/05/30 12:35:55.8588521 9648 13860 Shared InitializeSus 2019/05/30 12:35:55.8593003 9648 13860 IdleTimer Non-AoAc machine. Aoac operations will be ignored. 2019/05/30 12:35:55.8593843 9648 13860 Agent WU client version 10.0.17763.292 2019/05/30 12:35:55.8597513 9648 13860 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled. 2019/05/30 12:35:55.8598250 9648 13860 Agent Base directory: C:\WINDOWS\SoftwareDistribution 2019/05/30 12:35:55.8603172 9648 13860 Agent Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore\DataStor e.edb 2019/05/30 12:35:55.8633731 9648 13860 DataStore JetEnableMultiInstance succeeded - applicable param count: 5, applied param count: 5 2019/05/30 12:35:56.0363532 9648 13860 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2019/05/30 12:35:56.0370192 9648 13860 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 2. 2019/05/30 12:35:56.0399757 9648 13860 Shared Network state: Connected 2019/05/30 12:35:56.5517988 9648 13860 Misc *FAILED* [8024000C] LoadHistoryEventFromRegistry completed 2019/05/30 12:35:56.5519844 9648 13860 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2019/05/30 12:35:56.5519949 9648 13860 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 2. 2019/05/30 12:35:56.5520026 9648 13860 Shared Power status changed 2019/05/30 12:35:56.5557256 9648 12380 Agent *FAILED* [80240013] m_services.Add() 2019/05/30 12:35:56.5557299 9648 12380 Agent *FAILED* [80240013] Method failed [CAgentServiceManager::CreateServiceObjectAndAddInt oMap:2034] -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#7
|
|||
|
|||
KB4497934 update fails
Jonathan N. Little wrote:
Latest attempt to install displayed after using PS comment to generate "readable" log C:\Users\Jonathan\Desktopgrep 12:35 WindowsUpdate.log 2019/05/30 12:35:55.8588521 9648 13860 Shared InitializeSus 2019/05/30 12:35:55.8593003 9648 13860 IdleTimer Non-AoAc machine. Aoac operations will be ignored. 2019/05/30 12:35:55.8593843 9648 13860 Agent WU client version 10.0.17763.292 2019/05/30 12:35:55.8597513 9648 13860 Agent SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled. 2019/05/30 12:35:55.8598250 9648 13860 Agent Base directory: C:\WINDOWS\SoftwareDistribution 2019/05/30 12:35:55.8603172 9648 13860 Agent Datastore directory: C:\WINDOWS\SoftwareDistribution\DataStore\DataStor e.edb 2019/05/30 12:35:55.8633731 9648 13860 DataStore JetEnableMultiInstance succeeded - applicable param count: 5, applied param count: 5 2019/05/30 12:35:56.0363532 9648 13860 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2019/05/30 12:35:56.0370192 9648 13860 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 2. 2019/05/30 12:35:56.0399757 9648 13860 Shared Network state: Connected 2019/05/30 12:35:56.5517988 9648 13860 Misc *FAILED* [8024000C] LoadHistoryEventFromRegistry completed 2019/05/30 12:35:56.5519844 9648 13860 Shared UpdateNetworkState Ipv6, cNetworkInterfaces = 0. 2019/05/30 12:35:56.5519949 9648 13860 Shared UpdateNetworkState Ipv4, cNetworkInterfaces = 2. 2019/05/30 12:35:56.5520026 9648 13860 Shared Power status changed 2019/05/30 12:35:56.5557256 9648 12380 Agent *FAILED* [80240013] m_services.Add() 2019/05/30 12:35:56.5557299 9648 12380 Agent *FAILED* [80240013] Method failed [CAgentServiceManager::CreateServiceObjectAndAddInt oMap:2034] Well 15th time is the charm! And in Windows fashion no real indication wtf was the issue in the first place...just keep repeating until it "magically" works. So glad this is my only Winbox left. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#8
|
|||
|
|||
KB4497934 update fails
Jonathan N. Little wrote:
Past couple of days have had an update fail: 2019-05 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4497934) - Error 0x800f0986 Current Windows 10 Pro OS Build 17763.316 Repeated retries fail. Stopping WU service and clearing SoftwareDistribution dirs still fails Downloaded file: windows10.0-kb4497934-x64_2a3224347811199634033c289ee046f71639611e.msu and manual install also fails! Cannot find specific info in error code 0x800f0986. I am sure this update is the prelude to the biannual crapshoot "feature-update-fun", just wondering if a) anyone else getting similar error? b) if so, any fixes? https://www.askwoody.com/tag/kb-4497934/ "The changes to v1803 and v1809 will be available in the June Patch Tuesday updates. These Cumulative Updates are Previews. You don¢t need to install them." |
Thread Tools | |
Display Modes | Rate This Thread |
|
|