none
November Cumulative Updates - KB3198585 for Windows 10 RTM, KB3198586 for Windows 10 (1511), KB3200970 for Windows 10 (1607)

All replies

  • Hello there! I didn’t have any problems with my new Cumulative Update KB3200970. It took really long time to download and install though.
    I guess, you just need to wait until it finishes itself. Be patient!
    Now i have 14393.447.
    I did install on my desktop pc and laptop, both went well.
    Good luck guys!
    Czecher

    Btw. There is also an update called KB890830 - it says October for me, i did this update last month, it seems to be the same one is it true? Or just the same name + number. 

    Thank you for your answers :)

    Tuesday, November 08, 2016 7:23 PM
  • Hello there! I didn’t have any problems with my new Cumulative Update KB3200970. It took really long time to download and install though.
    I guess, you just need to wait until it finishes itself. Be patient!
    Now i have 14393.447.
    I did install on my desktop pc and laptop, both went well.
    Good luck guys!
    Czecher

    Btw. There is also an update called KB890830 - it says October for me, i did this update last month, it seems to be the same one is it true? Or just the same name + number. 

    Thank you for your answers :)

    Thanks for the info!

    KB890830 is from a long time ago, it would be strange for it to install now unless it failed in the past. It's an update for the Windows Malicious Software Removal Tool.

    Tuesday, November 08, 2016 8:32 PM
  • Several fails, then got KB3198586 to install using method posted by john.b_ in the October thread on Saturday, October 15, 2016 7:55 PM. I'm at 1511 10586.679.
    Wednesday, November 09, 2016 1:37 AM
  • Failed. Machine keeps updating. I was able to download the files but was slow as mention above.

    Wednesday, November 09, 2016 2:57 AM
  • Hello there,
    well the update has been realesed yesterday, as u can see many people have the same update i'm just curious if anyone has the same issue with the name of update KB890830, like everything is okey, but the name is October, i don't know if Microsoft has done a mistake with translation but it says October.
    Original name:
     Nástroj pro odebrání škodlivého softwaru systému Windows pro Windows 8, 8.1, 10 a Windows Server 2012, 2012 R2 x64 Edition – říjen 2016 (KB890830)
    PS: říjen = october
    Thank your for your answers  
    Czecher
    Wednesday, November 09, 2016 11:16 AM
  • Hello there,
    well the update has been realesed yesterday, as u can see many people have the same update i'm just curious if anyone has the same issue with the name of update KB890830, like everything is okey, but the name is October, i don't know if Microsoft has done a mistake with translation but it says October.
    Original name:
     Nástroj pro odebrání škodlivého softwaru systému Windows pro Windows 8, 8.1, 10 a Windows Server 2012, 2012 R2 x64 Edition – říjen 2016 (KB890830)
    PS: říjen = october
    Thank your for your answers  
    Czecher

    It sounds like you are right and I am wrong. The KB number 890830 seems to get re-used for updates to the malicious software removal tool each month, so what you are seeing is correct. Sorry for the confusion. :-/

    John Wink [MSFT]

    Wednesday, November 09, 2016 3:58 PM
  • Failed. Machine keeps updating. I was able to download the files but was slow as mention above.

    Error code 0x8024000b means the operation was canceled, so I'm not sure what happened there. I'd be happy to take a look at your logs though.

    John Wink [MSFT]

    Wednesday, November 09, 2016 4:03 PM
  • I rebooted my machine and tried again and it failed again. I'm trying to patch it again but it takes so much time out of my day. I probably won't have a reply till noon or later

    Wednesday, November 09, 2016 4:10 PM
  • Survey page does not exist.

    https://support.microsoft.com/en-us/common/survey.aspx?scid=sw;en;3763&altstyle=narrow&renderoption=overridedefault&theme=tech&url=http://social.technet.microsoft.com/Forums/windows/en-US/234aee30-e68e-4af7-88e8-9f08114e40ba/november-cumulative-updates-kb3198585-for-windows-10-rtm-kb3198586-for-windows-10-1511?forum=win10itprogeneral&P0=cb98654c-7fa3-4545-9dab-7f08d07761d2

    Wednesday, November 09, 2016 7:43 PM
  • Failed again...

    Thursday, November 10, 2016 12:47 AM
  • It did not apply. Just like all cumulative updates since April, it failed with a c019003f error at operation 8820 of (x). This error is during the restart operation. It proceeds to rollback.

    Found this in the CBS.log

    016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161014000034.cab to WER report.
    2016-11-10 18:37:57, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-11-10 18:37:57, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-11-10 18:37:57, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-11-10 18:37:57, Info                  CBS    Succesfully flushed NtfsLog.etl
    2016-11-10 18:37:57, Info                  CBS    Reporting poqexec status with status: 0xc019003f, failed file: desktop.ini, interfering process: , context: PSRL, first merged sequence: 157
    2016-11-10 18:37:57, Info                  CBS    SQM: poqexec report datapoints not populated because SQM is not initialized or not running online.
    2016-11-10 18:37:57, Error                 CBS    Startup: Primitive operations failed, startupPhase: 0.  The transaction will be cancelled. [HRESULT = 0x800f0921 - CBS_E_PRIMITIVES_FAILED]
    2016-11-10 18:37:57, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagPrimitivesFailed
    2016-11-10 18:37:57, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagPrimitivesFailed, SubStage: 0

    Thursday, November 10, 2016 11:46 PM
  • It did not apply. Just like all cumulative updates since April, it failed with a c019003f error at operation 8820 of (x). This error is during the restart operation. It proceeds to rollback.

    Found this in the CBS.log

    016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161014000034.cab to WER report.
    2016-11-10 18:37:57, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2016-11-10 18:37:57, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-11-10 18:37:57, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2016-11-10 18:37:57, Info                  CBS    Succesfully flushed NtfsLog.etl
    2016-11-10 18:37:57, Info                  CBS    Reporting poqexec status with status: 0xc019003f, failed file: desktop.ini, interfering process: , context: PSRL, first merged sequence: 157
    2016-11-10 18:37:57, Info                  CBS    SQM: poqexec report datapoints not populated because SQM is not initialized or not running online.
    2016-11-10 18:37:57, Error                 CBS    Startup: Primitive operations failed, startupPhase: 0.  The transaction will be cancelled. [HRESULT = 0x800f0921 - CBS_E_PRIMITIVES_FAILED]
    2016-11-10 18:37:57, Info                  CBS    Setting ExecuteState key to: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagPrimitivesFailed
    2016-11-10 18:37:57, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateInitiateRollback | CbsExecuteStateFlagPrimitivesFailed, SubStage: 0


    The pertinent info will be higher up in the CBS log - I believe some advanced installer is failing, but I'd need to know which one and why. Thanks!
    Friday, November 11, 2016 5:15 PM
  • I rebooted my machine and tried again and it failed again. I'm trying to patch it again but it takes so much time out of my day. I probably won't have a reply till noon or later

    Can I get you to run copylogs from my OneDrive and upload the results?

    https://1drv.ms/f/s!AtwXjrnjoGBmmDHUYCOF1rwJZqBc

    Thanks!

    Friday, November 11, 2016 5:17 PM
  • How do I run copy logs? Can you post how to do and I'll have up by Monday.
    Saturday, November 12, 2016 12:25 AM
  • How do I run copy logs? Can you post how to do and I'll have up by Monday.
    Copy copylogs.zip from John Winks OneDrive folder, open copylogs.zip, run copylogs.cmd. You will get two warnings, 1st one -> more info ->run anyway, 2nd one "yes". A Command Window will pop up and run the script. Copy the zip file specified at the end of the window (C:\WULogs...........) to John's OneDrive TechNet sub folder.
    Saturday, November 12, 2016 1:33 AM
  • any issues.

    Surface 2 Pro:  this happened last week while I was away.  Coincidentally I was in such a rush leaving that I had left it running.  Today I noticed that some of the apps which had evidently needed to be restarted were hung (e.g. open unsaved Notepad and Paint windows could not be used.)  Full normal Restart seemed necessary to work around such issues.  I am slightly amazed that we are able to preserve the unsaved files, so making their cloned windows not hang as well would just be a higher level of transparency to aspire to.

    HP Envy (W10 Home, my mother's machine):  I absent-mindedly did nothing special about MalwareBytes before allowing the update.  So far, the update seems to be unaffected.

    BTW how does this work?  Somehow you are applying an update to a hibernated image and then allowing that to (try to)  restart?  Wow.



    Robert Aldwinckle
    ---

    Saturday, November 12, 2016 4:44 PM
  • Here are my log files from running copy files. I did have an error uploading it but I manually put the files here:

    https://1drv.ms/f/s!AjApVpgq6WQ0h-NJDVVdqmbfxCG-YQ

    Saturday, November 12, 2016 6:26 PM
  • The update notification prompting has stopped but the sleep button is gone. I ordered an HP Z Book Studio this weekend because I want off of Dell Hardware after this.  

    Edit: I'm at 70% so maybe another prompting is around the corner

    • Edited by ResidentX10 Monday, November 14, 2016 12:03 PM
    Monday, November 14, 2016 12:01 PM
  • manually put the files here:

    Those are great.  Two things I have noticed so far:

    From  Setup.DevAPI.log

    PS>Get-Clipboard | select-String "Error =" | group
    
    Count Name                      Group
    ----- ----                      -----
        1 !    cpy:           Co... {!    cpy:           Could not delete file 'hidparse.sys'. Error = 0x00000005}
        1 !    sto:      Unable ... {!    sto:      Unable to delete driver package directory 'C:\WINDOWS\System32\DriverStore\FileRepository\input.inf_amd64_b48fb397210cb697'. Error = 0x00000005}
        1 !    cpy:           Co... {!    cpy:           Could not delete file 'bthenum.sys'. Error = 0x00000005}
        1 !    cpy:           Co... {!    cpy:           Could not delete file 'BTHUSB.SYS'. Error = 0x00000005}
        1 !    sto:      Unable ... {!    sto:      Unable to delete driver package directory 'C:\WINDOWS\System32\DriverStore\FileRepository\bth.inf_amd64_0add374da63aea45'. Error = 0x00000005}
    
    

    I don't know if you should try to help it out with those deletions but an alternate tack would be trying to disable or remove those devices using the standard UI before retrying your update.  Do you need those devices?  Could you manage temporarily without them to get past these errors?

    FWIW I had to do something like what I am suggesting above with printer support in order to get a previous update installed.

    However, what I haven't figured out yet is how these correlate with any of your update attempts because the timestamps don't match.   ; ]

    From ReportingEvents.log

    {720B0FF8-C813-4D53-8395-2B94629DB1C4}	2016-11-10 19:14:46:918-0500	1	181 [AGENT_INSTALLING_STARTED]	101	{07A93F97-7EC3-4C75-95E6-283767C4DD84}	200	0	UpdateOrchestrator	Success	Content Install	Installation Started: Windows has started installing the following update: Definition Update for Windows Defender - KB2267602 (Definition 1.231.1677.0)
    {8025941C-C0F7-424E-92C6-ABE18E3B2BE5}	2016-11-10 19:15:44:219-0500	1	183 [AGENT_INSTALLING_SUCCEEDED]	101	{07A93F97-7EC3-4C75-95E6-283767C4DD84}	200	0	UpdateOrchestrator	Success	Content Install	Installation Successful: Windows successfully installed the following update: Definition Update for Windows Defender - KB2267602 (Definition 1.231.1677.0)
    {F100A4F2-BFD2-4825-AED3-F6F04321B351}	2016-11-10 19:33:46:382-0500	1	181 [AGENT_INSTALLING_STARTED]	101	{669E5E1A-9590-4153-BC1B-929BE3652E49}	200	0	UpdateOrchestrator	Success	Content Install	Installation Started: Windows has started installing the following update: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3197954)
    {F2A55514-4858-4F9B-8A86-B086E5095EF2}	2016-11-10 19:37:21:618-0500	1	201 [AGENT_INSTALLING_PENDING]	101	{669E5E1A-9590-4153-BC1B-929BE3652E49}	200	240005	UpdateOrchestrator	Success	Content Install	Installation pending.
    {A9B2862D-97C0-447A-9C5F-21EB6C70B504}	2016-11-10 20:40:05:331-0500	1	181 [AGENT_INSTALLING_STARTED]	101	{93A608A4-1878-456B-8B00-3E74F2FCB8EF}	203	0	UpdateOrchestrator	Success	Content Install	Installation Started: Windows has started installing the following update: Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3202790)
    {01265762-CAA8-4556-B643-7906109ECA79}	2016-11-10 20:40:05:369-0500	1	182 [AGENT_INSTALLING_FAILED]	101	{93A608A4-1878-456B-8B00-3E74F2FCB8EF}	203	80246013	UpdateOrchestrator	Failure	Content Install	Installation Failure: Windows failed to install the following update with error 0x80246013: Security Update for Adobe Flash Player for Windows 10 Version 1607 (for x64-based Systems) (KB3202790).
    {BBAB359C-A5C2-419D-9976-BA83B9F140C7}	2016-11-10 20:40:12:620-0500	1	181 [AGENT_INSTALLING_STARTED]	101	{58111EC9-BB9F-48BE-903C-F2588BFE68EC}	203	0	UpdateOrchestrator	Success	Content Install	Installation Started: Windows has started installing the following update: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3200970)
    {B2B3B6F9-18D3-4741-B73C-F72C90482470}	2016-11-10 20:40:12:838-0500	1	182 [AGENT_INSTALLING_FAILED]	101	{58111EC9-BB9F-48BE-903C-F2588BFE68EC}	203	80246013	UpdateOrchestrator	Failure	Content Install	Installation Failure: Windows failed to install the following update with error 0x80246013: Cumulative Update for Windows 10 Version 1607 for x64-based Systems (KB3200970).
    {513169E9-F7D0-4031-BB18-1F14D8A03DB5}	2016-11-10 20:40:13:250-0500	1	181 [AGENT_INSTALLING_STARTED]	101	{D848EDD0-B379-4D01-8DCE-01F328108A80}	201	0	UpdateOrchestrator	Success	Content Install	Installation Started: Windows has started installing the following update: Security Update for SQL Server 2016 RTM CU (KB3194717)
    {E819BC14-AB8E-4E91-8096-76D55F899FEB}	2016-11-10 20:51:12:313-0500	1	186 [AGENT_INSTALL_CANCEL]	101	{D848EDD0-B379-4D01-8DCE-01F328108A80}	201	8024000b	UpdateOrchestrator	Success	Content Install	User cancelled the installation.
    

    The error code 0x80246013 is another one of the new still undocumented ones.  E.g. we can use the Support list to find that it will be starting with  WU_E_DM  and then fortunately BING helps find this

    http://errco.de/win32/wuerror-h/wu_e_dm_updateremoved/0x80246013/

    <quote>
    An attempt was made to access a downloaded update that has already been removed.
    </quote>

    WTH does that mean?   WindowsUpdate.log  might help clarify that and your .etl files may be enough to generate a clean one.  I may try to do that but I have not had much success myself even with my own, so I would not be very hopeful.  The other event logs might be more reliable supplementary diagnostics to help explain this.

    Meanwhile though I would be more hopeful about creating sufficient conditions to clean up your Setup.DevAPI.log.  E.g. it is possible that these other symptoms occur during recovery processing and therefore would not be an issue, if the first part ran cleanly.

    Also, notice that this time the update that was "cancelled" was one which has something to do with SQL Server; so again, you could change that symptom by uninstalling that product (or component) and seeing if doing that made any other helpful change in your total symptom description.

     

    Good luck



    Robert Aldwinckle
    ---

    Monday, November 14, 2016 5:26 PM
  • WindowsUpdate.log  might help clarify that and your .etl files may be enough to generate a clean one.

    With the standard cmdlet and its parameter overrides the best that I was able to do with those was about 200 out of 4000.   First only a small subset of your .etl files were allowed to be used in order to avoid some obscure resource limitation that I did not bother trying to analyze.  I did however take the time to download and install full symbols for 1607 August for no change.

    I will document some of my procedure because it was obtuse with more pitfalls than I have already alluded to.  I thought I might be able to get at least the full day of the 10th but had to settle for the last 4 hours.

    PS>$fl = (dir WindowsUpdate.20161110.2*.etl).FullName
    PS>Get-WindowsUpdateLog -EtlPath $fl -LogPath $cd\WindowsUpdate.log

    The $cd variable seemed necessary because I could not figure out how to make PowerShell let me use the . for the Current Directory.   So it is simply a pointer to the parent and then back to current directory explicitly by name: 

    PS>$cd
    ..\WU_logs

    So, as expected, it looks like we are going to have to make do without a WindowsUpdate.log.



    Robert Aldwinckle
    ---

    Tuesday, November 15, 2016 5:20 AM
  • An attempt was made to access a downloaded update that has already been removed.

    Your System.evtx shows a  0x800F9022  occurred earlier than that and the CBS.log there shows it represents many  0x800F0826,  which Support does document (in its quirky way):

    0xf0826 CBS_E_PENDING_VICTIM Package failed to install because another pended package failed.

    Have you tried any repairs of WinSxS?  E.g. Windows Update troubleshooter, DISM and scannow.

    http://www.tenforums.com/tutorials/7808-dism-repair-windows-10-image.html

    BTW the same functionality is available from PowerShell  Repair-WindowsImage

     

    Good luck



    Robert Aldwinckle
    ---

    Tuesday, November 15, 2016 6:35 PM
  • Hi Rob,

    I'm nuking my device once my new one gets here(Thursday). The fix is taking too long. I'll see if what happens with Windows Server 2016 running on it.

    I refused to buy Microsoft hardware just in case this was done to drive customers to buy new hardware. Thanks for your help.

    Tuesday, November 15, 2016 7:07 PM
  •  Just like all cumulative updates since April, it failed with a c019003f error at operation 8820 of (x).

    @ Russell

    In April your error code was  0x80071AB0.  A possible meaning of that:

    0x00001AB0  ERROR_TRANSACTIONAL_OPEN_NOT_ALLOWED
        This object is not allowed to be opened in a  transaction.

    Now you see a different code apparently indicating the same thing but maybe in a different state:

    0xC019003F  STATUS_TRANSACTIONAL_OPEN_NOT_ALLOWED
        This object is not allowed to be opened in a  transaction.

    I still think it would be worthwhile to find out what "This object" is.

    Alternatively, as a guess I would say that you have an interferer present, so consider what security packages you have and if you could try disabling or removing them to see if your symptom changes.

     

    Good luck



    Robert Aldwinckle
    ---

    Tuesday, November 15, 2016 7:44 PM
  • 2016-11-10 18:37:55, Info                  CBS    SetProgressMessage: progressMessageStage: -1, ExecuteState: CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback, SubStage: 0
    2016-11-10 18:37:55, Info                  CBS    Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
    2016-11-10 18:37:55, Info                  CBS    Startup: Processing advanced operation queue, startupPhase: 0
    2016-11-10 18:37:55, Info                  CSI    00000003 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0x3a3bdfdc20
    2016-11-10 18:37:55, Info                  CSI    00000004 Creating NT transaction (seq 1), objectname [6]"(null)"
    2016-11-10 18:37:55, Info                  CSI    00000005 Created NT transaction (seq 1) result 0x00000000, handle @0x280
    2016-11-10 18:37:55, Info                  CSI    00000006@2016/11/10:23:37:55.898 Beginning NT transaction commit...
    2016-11-10 18:37:55, Info                  CSI    00000007@2016/11/10:23:37:55.913 CSI perf trace:
    CSIPERF:TXCOMMIT;14250
    2016-11-10 18:37:57, Error                 CSI    00000008 (F) Error: ResolvePendingTransactions called after poqexec failure (call 1)
      Status = c019003f [Error,Facility=FACILITY_TRANSACTION,Code=63 (0x003f)], Operation = MoveFile, DiagString = [l:166]"\??\D:\$$PendingFiles\631a60f9aa3bd20197460000840fc816.desktop.ini, \??\D:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories\desktop.ini"
    [gle=0x80004005]
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161110233637.log to WER report.
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161109042004.log to WER report.
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161105161650.log to WER report.
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161024000920.cab to WER report.
    2016-11-10 18:37:57, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20161014000034.cab to WER report.

    Some lines right before the ones above.  I send the entire file, if there was a place to send it.

    -Russ

    Tuesday, November 15, 2016 11:28 PM
  • 2016-11-10 18:37:57, Error                 CSI    00000008 (F) Error: ResolvePendingTransactions called after poqexec failure (call 1)
      Status = c019003f [Error,Facility=FACILITY_TRANSACTION,Code=63 (0x003f)], Operation = MoveFile, DiagString = [l:166]"\??\D:\$$PendingFiles\631a60f9aa3bd20197460000840fc816.desktop.ini, \??\D:\Users\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Accessories\desktop.ini"
    [gle=0x80004005]

    OK.  That explains the symptom but not the cause.   I imagine the "poqexec failure" could be the cause. 

    AFAIK you are free to upload whatever you think would be useful to John's OneDrive.



    Robert Aldwinckle
    ---

    Tuesday, November 15, 2016 11:58 PM

  • Alternatively, as a guess I would say that you have an interferer present.



    @ Russell

    "interferer" might be a non-Microsoft Service, might be worth a try to:

    1. Download latest Cumulative Update from the Microsoft Update Catalog (http://www.catalog.update.microsoft.com/Search.aspx?q=KB3198586 for example).
    2. Disconnect from the Internet since one of the Services in step 3 is probably virus protection related and to stop other potential interference with update.
    3. Run msconfig, on the services tab Hide all Microsoft Services, uncheck all the non-Microsoft Services, click OK.
    4. Restart your computer.
    5. Run the .msu file downloaded in step 1.
    6. Run winver to verify update succeeded (should be 1511 10586.679 for example).
    7. Run msconfig, on the services tab Hide all Microsoft Services, check all the non-Microsoft Services, click OK.
    8. Restart your computer.

    9. Reconnect to Internet.


    Wednesday, November 16, 2016 12:36 AM
  • any issues.

    Surface 2 Pro:  this happened last week while I was away.  Coincidentally I was in such a rush leaving that I had left it running.  Today I noticed that some of the apps which had evidently needed to be restarted were hung (e.g. open unsaved Notepad and Paint windows could not be used.)  Full normal Restart seemed necessary to work around such issues.  I am slightly amazed that we are able to preserve the unsaved files, so making their cloned windows not hang as well would just be a higher level of transparency to aspire to.

    HP Envy (W10 Home, my mother's machine):  I absent-mindedly did nothing special about MalwareBytes before allowing the update.  So far, the update seems to be unaffected.

    BTW how does this work?  Somehow you are applying an update to a hibernated image and then allowing that to (try to)  restart?  Wow.



    Robert Aldwinckle
    ---


    I'm not sure about hibernate, but I do believe we'll wake a machine from sleep state if we're in the maintenance window.
    Wednesday, November 16, 2016 3:26 PM
  • Hi Rob,

    I'm nuking my device once my new one gets here(Thursday). The fix is taking too long. I'll see if what happens with Windows Server 2016 running on it.

    I refused to buy Microsoft hardware just in case this was done to drive customers to buy new hardware. Thanks for your help.

    The actual problem in your case is this:

    2016-11-10 17:05:06, Error      [0x01805b] CSI    00000299 (F) Failed execution of queue item Installer: Network Drivers ({a111f280-5923-47c0-9a68-d0bafb577901}) with HRESULT 800106d9 [Error,Facility=(0001),Code=1753 (0x06d9)].  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]

    We fixed the vast majority of occurrences of this, but there is some particular edge case that we haven't nailed yet. Ideally I'd love to get a bunch of diagnostic data from your machine so we could knock this edge case down too, please let me know if you'd be willing to help out.

    If not then reinstalling Windows (or, I believe, even an in-place upgrade) should make this go away.

    Let me know if we can get some diagnostic help from you, and thanks!

    John

    Wednesday, November 16, 2016 3:32 PM
  • Let me know if we can get some diagnostic help from you, and thanks!

    @ John

    Thanks for showing us the real problem timestamp.  Notice that the  Setup.DevAPI.log  at that time (or just before) shows the same problem devices that I mentioned as sources of possible workaround?

    BTW were you able to get a clean WindowsUpdate.log from all of the .etl files?   <eg>



    Robert Aldwinckle
    ---

    Wednesday, November 16, 2016 5:34 PM
  • Let me know if we can get some diagnostic help from you, and thanks!

    @ John

    Thanks for showing us the real problem timestamp.  Notice that the  Setup.DevAPI.log  at that time (or just before) shows the same problem devices that I mentioned as sources of possible workaround?

    BTW were you able to get a clean WindowsUpdate.log from all of the .etl files?   <eg>



    Robert Aldwinckle
    ---

    To get to the bottom of this we'll need to get some instrumented binaries onto the machine, so I'm hoping our friend ResidentX10 is willing to help.

    ResidentX10, the first step would be to load up regedit and look for the BuildLavEx key under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows
    NT\CurrentVersion. Based on that we would build specific instrumented binaries and hopefully nail this thing. Please do let me know.

    Thanks!

    Wednesday, November 16, 2016 9:44 PM
  • What's the address of his onedrive?
    Wednesday, November 16, 2016 10:22 PM
  • What's the address of his onedrive?

    ResidentX10 ?

    Above, in his Saturday, November 12, 2016 6:26 PM post.

    Wednesday, November 16, 2016 10:32 PM
  • What's the address of his onedrive?

    For John Wink's do a Find for the first instance of  copylogs  in this thread.


    Robert Aldwinckle
    ---

    Thursday, November 17, 2016 1:47 AM
  • I got your message. I'll try this tomorrow after I get my new hardware...
    Thursday, November 17, 2016 3:06 AM
  • Just want to share that this update has failed about 20 times for me. I've tried every troubleshooting step suggested on MS forums and other articles including Windows Update Troubleshooter, DISM, Scan Now, manually deleting files, etc.

    It's enraging getting a notification asking me to restart every single day when it wont ever actually install the update.

    Mine stops at 99% after rebooting and then says that the update couldnt be installed and it then rolls back.

    Monday, November 21, 2016 5:05 PM
  • Just want to share that this update has failed about 20 times for me. I've tried every troubleshooting step suggested on MS forums and other articles including Windows Update Troubleshooter, DISM, Scan Now, manually deleting files, etc.

    It's enraging getting a notification asking me to restart every single day when it wont ever actually install the update.

    Mine stops at 99% after rebooting and then says that the update couldnt be installed and it then rolls back.

    Did you try the 9 step process I posted Wednesday, November 16, 2016 12:36 AM in this thread above ?

    Monday, November 21, 2016 5:41 PM
  • Hi!

    I try to install the updates KB3200970 and KB3199986 since several weeks, but I still get the error 0x800703f1. Details pls find here: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/cant-install-some-updates-for-win-10-like/ad35d168-95cb-492e-be7f-448aa620600a.

    I've already tried almost everything I could, but without success. 

    Hope, you might have an idea ...

    Thanks and cheers,

    Wladimir

    Wednesday, November 23, 2016 1:28 PM
  • Hi!

    I try to install the updates KB3200970 and KB3199986 since several weeks, but I still get the error 0x800703f1. Details pls find here: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/cant-install-some-updates-for-win-10-like/ad35d168-95cb-492e-be7f-448aa620600a.

    I've already tried almost everything I could, but without success. 

    Hope, you might have an idea ...

    Thanks and cheers,

    Wladimir

    Did you try the 9 step process I posted Wednesday, November 16, 2016 12:36 AM in this thread above ?

    Wednesday, November 23, 2016 5:45 PM
  • I'm still out here and I haven't forgot my commitment. I'll try to work on this on Friday. I'm up to my neck in CPUP classes at the moment. My old Dell is still prompting for updates. My new machine will not even install 1607. HP is preventing it from installing.

    • Edited by ResidentX10 Wednesday, November 23, 2016 6:52 PM
    Wednesday, November 23, 2016 6:49 PM
  • Ok, honestly - not yet, the suggested step with "stop all non-Microsoft services" is the one I didn't try yet. It could be my next try. But first I would wait for a feedback in the thread above (https://answers.microsoft.com/en-us/windows/forum/windows_10-update/cant-install-some-updates-for-win-10-like/ad35d168-95cb-492e-be7f-448aa620600a?page=2) because of 82, too old version in C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.14393.82_none_5be7b69702339d1d\cbscore.dll

    As you can see there, Robert meant: "So, a possibility implied by this idea would be that instead of having a corrupted database all you might have is the wrong modules to use with a newer version of one.  Hopefully things will not have been really corrupted by using that old version for too long."

    Wednesday, November 23, 2016 7:13 PM
  • Not usre it's the update, but I am getting "cannot connect to all drivers" and I've lost the ability to connect to 2 mapped shared drives thru the VPN.

    Wednesday, November 23, 2016 7:30 PM
  • Not sure....sorry
    Wednesday, November 23, 2016 7:31 PM
  • My computer patched today...

    Sunday, November 27, 2016 11:44 PM
  • My computer patched today...

    Congratulations !!!

    Is this with the old Dell or the new HP ? What did you do to get it to install ?

    Monday, November 28, 2016 12:34 AM
  • Hi everyone, I found this thread under the recommendation of Robert in another thread I had opened here

    https://answers.microsoft.com/en-us/windows/forum/windows_10-update/failed-kb3197954-installation-and-dism-permissions/cbfd1c50-b6d5-4a9b-8ae2-0d374761918b

    considering a similar crazy issue I have with another update. As you can see in the above thread, I have tried anything I could think of, and ended up in using the copylogs tools posted here, but it has been quite difficult to find in which log/file exactly I should search for finding a solution to this update installation failure. Also the friend above apparently was quite happy that he made it work and forgot to post an answer to what he did :)

    If you could give any guidance on which logs I should investigate, I would be grateful.


    Wednesday, November 30, 2016 7:11 PM
  • guidance on which logs I should investigate, I would be grateful.

    Currently the only logs available for inspection are a set on the Twitter folder.  I imagine that they are not yours but you could use them to see some frequently seen symptoms.  First, I opened the FilterList.log and noticed the presence of some McAfee software (which for the purposes of looking at possible causes of problem symptoms I class as an "interferer").  So uninstalling that would change that symptom.  Next, the CBS.log itself does not have a "smoking gun" in it but the last CBSPersist log does--an instance of a BFS problem.  Others managed to change that symptom by doing various related things to try to avoid it and in at least one case that resulted in an update being successfully installed that was previously failing.  Next, the SetupAPI.Dev.log indicates a possible problem with a Bluetooth driver from WIDCOMM (as the most frequent example).  Again, disabling and uninstalling that software could possibly change that symptom.  Then if you were lucky it could be enough to change the outcome of the install.  Etc.

    FYI



    Robert Aldwinckle
    ---


    Wednesday, November 30, 2016 8:12 PM