none
Windows update KB3000850 fails with error: 0x800700a1 RRS feed

  • Question

  • Windows update KB3000850 fails with the following error: 0x800700a1

    In WindowsUpdate.log there is the following:
    FATAL: CBS called Error with 0x800700a1


    In CBS.log there is the following error:

    2014-11-25 11:17:54, Error                 CSI    00000ea8 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #11395486# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_WRITE_ATTRIBUTES), oa = @0xa81c89d2f0->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[9]"MSDTC.LOG"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa81c89d398, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)[gle=0xd000003b]

    2014-11-25 11:17:54, Error                 CSI    00000ea9@2014/11/25:11:17:54.259 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2155): Error STATUS_OBJECT_PATH_SYNTAX_BAD originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)[gle=0x80004005]



    Tuesday, November 25, 2014 3:49 PM

Answers

  • Resolved with help from the people on the sysnative forum:

    http://www.sysnative.com/forums/windows-update/12060-windows-update-kb3000850-fails-with-error-0x800700a1.html

     

    For whatever reason system restore after this update causes the following file to either become corrupt or otherwise un-decompressable:

    C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG

    To fix that file needs to be replaced with a working copy from elsewhere.

     

    Microsoft support have confirmed it is a bug with the update and will be refunding whatever I paid for the support ticket.

    • Marked as answer by pbellchambers Wednesday, December 3, 2014 12:06 PM
    Wednesday, December 3, 2014 12:05 PM

All replies

  • I'm seeing the same issue on my x64 8.1 machine.
    Tuesday, November 25, 2014 9:17 PM
  • I wonder if there's anything common between our systems:

    Lenovo w540 - Windows 8.1 Pro 64-bit

    Eset anti-virus (v8.0.304.0)

    I don't even know where to begin debugging this error, it doesn't give anything particularly helpful to an end user.

    STATUS_OBJECT_PATH_SYNTAX_BAD

    Wednesday, November 26, 2014 2:24 PM
  • Windows update KB3000850 fails with the following error: 0x800700a1

    C:\>set /a c = 0xa1
    161
    C:\>net helpmsg %c%
    
    The specified path is invalid.
    

    I suspect you are overlooking something in the vicinity of what you have snipped.  Others have found that they have some customization which needs to be undone before the update can be applied...

    http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-with-windows-update-kb3000850/b0e3fa91-5f31-4258-998a-1d0dff88a37e?page=2

    FYI



    Robert Aldwinckle
    ---


    Wednesday, November 26, 2014 3:18 PM
  • Tried all the suggestions in that thread, including running the DSIM tool.

     

    Still getting the same error: 800700a1

     

    I've uploaded the complete logs here: https://mega.co.nz/#F!wpZCHQRB!1GI7_PRJ3_S2nwITYVxDsg

     

    This is a bigger snip from CBS.log around the errors:

    2014-11-26 16:28:39, Info                  CSI    00000458 'From' Namespace [wcm://Microsoft-Windows-IPMIProvider?version=6.3.9600.16384&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers] not found, servicing aborted, reverting to Install of 'To'

    2014-11-26 16:28:39, Info                  CSI    00000459 Processing Namespace [wcm://Microsoft-Windows-IPMIProvider?version=6.3.9600.17415&language=neutral&processorArchitecture=x86&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers]

    2014-11-26 16:28:39, Info                  CSI    0000045a done

    2014-11-26 16:28:39, Info                  CSI    00000e98 Regenerating payload files from delta files on component: [ml:280{140},l:186{93}]"amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6"
    2014-11-26 16:28:39, Info                  CSI    00000e99 Creating NT transaction (seq 2), objectname [6]"(null)"
    2014-11-26 16:28:39, Info                  CSI    00000e9a Created NT transaction (seq 2) result 0x00000000, handle @0xf7c
    2014-11-26 16:28:39, Error                 CSI    00000e9b (F) STATUS_OBJECT_PATH_SYNTAX_BAD #8867646# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_WRITE_ATTRIBUTES), oa = @0xa2a758d410->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[9]"MSDTC.LOG"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xa2a758d4b8, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
    [gle=0xd000003b]
    2014-11-26 16:28:39, Error                 CSI    00000e9c@2014/11/26:16:28:39.304 (F) base\wcp\sil\merged\ntu\ntsystem.cpp(2155): Error STATUS_OBJECT_PATH_SYNTAX_BAD originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
    [gle=0x80004005]
    2014-11-26 16:28:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
    2014-11-26 16:28:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20141126162432.log to WER report.
    2014-11-26 16:28:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20141120100026.cab to WER report.
    2014-11-26 16:28:39, Info                  CBS    Added C:\WINDOWS\Logs\CBS\CbsPersist_20141028123021.cab to WER report.
    2014-11-26 16:28:39, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-11-26 16:28:39, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-11-26 16:28:39, Info                  CBS    Not able to add SCM.EVM to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2014-11-26 16:28:39, Error                 CSI    00000e9d (F) STATUS_OBJECT_PATH_SYNTAX_BAD #8867645# from Windows::Rtl::SystemImplementation::CSystemIsolationLayer_IRtlSystemIsolationLayerTearoff::TransferFile(flags = (ReplaceIfExists|OpenForBackupIntent), op = [8]"HardLink", odir = NULL, oname = [l:18{9}]"MSDTC.LOG", ndir = @0xa29be2af38, nname = [l:18{9}]"MSDTC.LOG", disp = (null))
    [gle=0xd000003b]
    2014-11-26 16:28:39, Error                 CSI    00000e9e (F) STATUS_OBJECT_PATH_SYNTAX_BAD #8867523# from CFileInstaller::DoComponentOperation(...)[gle=0xd000003b]
    2014-11-26 16:28:39, Error                 CSI    00000e9f (F) STATUS_OBJECT_PATH_SYNTAX_BAD #8867522# from CFileInstaller::ProcessComponentChange(...)[gle=0xd000003b]
    2014-11-26 16:28:39, Error                 CSI    00000ea0 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #8867521# from PrimitiveInstaller::CCoordinator::ProcessChange(Change 6.3.9600.16384 -> 6.3.9600.17415 for Microsoft-Windows-COM-DTC-Runtime, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral)[gle=0xd000003b]
    2014-11-26 16:28:39, Info                  CSI    0000045b SMI Primitive Installer [done]

    2014-11-26 16:28:40, Error                 CSI    00000ea1 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #4347192# from CCSDirectTransaction::PerformChangeAnalysis(...)[gle=0xd000003b]
    2014-11-26 16:28:40, Error                 CSI    00000ea2 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #4347191# from CCSDirectTransaction::PrepareForCommit(...)[gle=0xd000003b]
    2014-11-26 16:28:40, Error                 CSI    00000ea3 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #4347190# from CCSDirectTransaction::ExamineTransaction(...)[gle=0xd000003b]
    2014-11-26 16:28:40, Error                 CSI    00000ea4 (F) STATUS_OBJECT_PATH_SYNTAX_BAD #4347189# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0xd000003b]
    2014-11-26 16:28:40, Info                  CSI    0000045c SMI Primitive Installer [started]

    2014-11-26 16:28:40, Info                  CSI    0000045d 'From' Namespace [wcm://Microsoft-Windows-Installer-Engine?version=6.3.9600.17399&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers] not found, servicing aborted, reverting to Install of 'To'

    2014-11-26 16:28:40, Info                  CSI    0000045e Processing Namespace [wcm://Microsoft-Windows-Installer-Engine?version=6.3.9600.17415&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers]

    2014-11-26 16:28:40, Info                  CSI    0000045f done

    2014-11-26 16:28:40, Info                  CSI    00000460 'From' Namespace [wcm://Microsoft.Windows.WinHTTP?version=5.1.9600.16384&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers] not found, servicing aborted, reverting to Install of 'To'

    2014-11-26 16:28:40, Info                  CSI    00000461 Processing Namespace [wcm://Microsoft.Windows.WinHTTP?version=5.1.9600.17415&language=neutral&processorArchitecture=wow64&publicKeyToken=31bf3856ad364e35&versionScope=nonSxS&scope=allUsers]

    2014-11-26 16:28:40, Info                  CSI    00000462 done

     

    Is this the root cause?

    2014-11-26 16:28:39, Info                  CSI    00000e99 Creating NT transaction (seq 2), objectname [6]"(null)"

    Is there supposed to be a "null" going into whatever that is?


    Wednesday, November 26, 2014 4:44 PM
  • Originally the update did install on my system. It got to the point of rebooting and applying. The screen was black and I could not do anything to the system. So I rebooted the system (after letting it sit for a few hours at the black screen) and was able to log in. Then the real problem started. The system was extremely slow. Anything I selected or modified would apply after 30-60 seconds. It kept doing that so I restored Windows to a good state that was about 7-14 days old. After I did that, the update will no longer install.

    Which logs do I need to view and what do I look for?

    Wednesday, November 26, 2014 5:33 PM
  • Is this the root cause?

    2014-11-26 16:28:39, Info                  CSI    00000e99 Creating NT transaction (seq 2), objectname [6]"(null)"

    Is there supposed to be a "null" going into whatever that is?


    My guess is the download is corrupt.  Do you have an AV running?

    2014-11-26 16:24:53, Info                  DPX    Extraction of file: update.ses failed because it is not present in the container.
    2014-11-26 16:24:53, Info                  DPX    DpxException hr=0x80070002 code=0x020109
    2014-11-26 16:24:53, Info                  CBS    Not able to add file to extract: update.ses [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    

    This was the first error in your larger extract.  What does it mean?  FWIW I suspect you could have something in a DPX log about this.  Maybe that will clarify its significance.  Because I don't have access to either source or support documentation I have no way to read between the lines of these diagnostics.  That's why I would be running ProcMon to try to capture all diagnostic writes and help correlate them.  You could do that much just by capturing  Operation Is WriteFile.  If you allow more to be captured (default is all) you can also supplement each record that you find interesting.

    Otherwise perhaps it would help to download the update manually, do a checksum on it and install it manually?

     
    Good luck



    Robert Aldwinckle
    ---

    Thursday, November 27, 2014 3:07 AM
  • There were no errors in the DPX logs. The above logs were actually from a manually downloaded copy of the update, it doesn't work manually or in windows update.

     

    I had a look at ProcMon, however admittedly I don't really know what I am looking for amongst the vast amount of logging. When it was set to only show "Operation Is WriteFile" while running the update in the background everything was "SUCCESS", there were no failures, even when the update failed. I tried expanding the filters a bit, but as mentioned, I don't really know what I'm looking for, there wasn't anything obvious that stood out to me at least.

     

    Not sure where to go from here, is paying £190 for a microsoft support ticket actually worth it? Do they generally resolve issues like these well or is it just the same as talking to their online chat support guys (who suggested clearing the internet explorer cache to resolve this particular issue, lol).


    Thursday, November 27, 2014 11:55 AM
  • I restored Windows to a good state that was about 7-14 days old. After I did that, the update will no longer install.

    For what it's worth this is the same that happened to me. Installed the update successfully once, I didn't have any problems with it, but then for an unrelated reason (new nvidia driver that I installed broke my machine a few days later) I restored windows to before applying the update, and now the update won't install.

     

    Other windows updates installed fine after the system restore. It's just this one that's broken.

    Thursday, November 27, 2014 11:57 AM
  • I had a look at ProcMon, however admittedly I don't really know what I am looking for amongst the vast amount of logging. When it was set to only show "Operation Is WriteFile" while running the update in the background everything was "SUCCESS",


    The intention of that filter is to get an inventory of the diagnostics.  You can use the Tools, Count... with it to summarize them on the Path field.  They don't even show message content, just timestamp and length.  But using those details you can infer which message a particular write is related.  Then once you have a match you can remove the filter there and try guessing that the preceding Registry and File access events can supplement that one.  Etc.


    Robert Aldwinckle
    ---

    Thursday, November 27, 2014 1:15 PM
  • (new nvidia driver that I installed broke my machine a few days later)

    That sounds like a clue.   ; }


    Robert Aldwinckle
    ---

    Thursday, November 27, 2014 1:17 PM
  • I restored Windows to a good state that was about 7-14 days old. After I did that, the update will no longer install.

    For what it's worth this is the same that happened to me. Installed the update successfully once, I didn't have any problems with it, but then for an unrelated reason (new nvidia driver that I installed broke my machine a few days later) I restored windows to before applying the update, and now the update won't install.

     

    Other windows updates installed fine after the system restore. It's just this one that's broken.

    Same thing here.

    Installed successfully, had to do a restore - reinstalling the update fails. Error 0x800700a1.
    I tried the Update provided by Microsoft Update and i tried the manual downloaded files. Same error. I think while the first succesfull update installed any path was changed. After the restore the updatefiles themself where gone, but the changed pathname still exists. So a reinstallation fails.

    BR
    Jochen

    Friday, November 28, 2014 9:20 AM
  • Well I've raised a support request with Microsoft, lets hope the £250 is worth it.

     

    Steps to reproduce are easy:

     

    1. Install KB3000850 successfully

    2. Perform system restore to before installing the update

    3. Install KB3000850 again - update fails with error 800700a1

    Monday, December 1, 2014 11:12 AM
  • Same here (Windows 8.1, installed KB3000850 without problems, system restore to previous point in time, tried to re-install KB3000850 with error 800700A1).

    Would be very interested to hear if Microsoft (or any other) has a solution for this nasty situation.

    Regards, Erik

    Monday, December 1, 2014 8:22 PM
  • system restore to previous point in time, tried to re-install KB3000850 with error 800700A1).

    Get some details.  E.g. trace with ProcMon.  Otherwise, I would wonder about things like the version of dism.exe.  When the last rollup (KB2919355) went on it changed things so much that trying to go back meant that the new DISM wouldn't work with the old data (and vice versa).  Then instead of a System Restore perhaps you should go back to a previous full image for maximal consistency for both the data and the programs?  Of course everyone has been doing a full image backup before they try the rollup, right?   <eg>



    Robert Aldwinckle
    ---

    Monday, December 1, 2014 10:13 PM
  • Of course everyone has been doing a full image backup before they try the rollup, right?

    Oh of course we all have.

     

    God forbid we actually have an expectation of things we have paid for just you know... working.

    Tuesday, December 2, 2014 10:40 AM
  • Resolved with help from the people on the sysnative forum:

    http://www.sysnative.com/forums/windows-update/12060-windows-update-kb3000850-fails-with-error-0x800700a1.html

     

    For whatever reason system restore after this update causes the following file to either become corrupt or otherwise un-decompressable:

    C:\Windows\WinSxS\amd64_microsoft-windows-com-dtc-runtime_31bf3856ad364e35_6.3.9600.16384_none_0a1162f033fa01f6\MSDTC.LOG

    To fix that file needs to be replaced with a working copy from elsewhere.

     

    Microsoft support have confirmed it is a bug with the update and will be refunding whatever I paid for the support ticket.

    • Marked as answer by pbellchambers Wednesday, December 3, 2014 12:06 PM
    Wednesday, December 3, 2014 12:05 PM