locked
EventID 513 Capi2 error

    Question

  • I obtain this error situation just after boot-up. I have read and carefully followed the advice and information contained on the 'Technet' information page concerning this. All the required permissions are in place for the Registration folder. vssadmin list writers does not have 'system writer' included in the list. I presume this error will continue if this is not the case and although there seems to be no problem with my system restore and system repair functions, I would prefer to remove this error. What must I do to place 'system writer' back onto the approved list. Any help would be much appreciated.

    Sunday, December 07, 2008 10:44 PM

Answers

  • First make sure you have the same error. CAPI2 513 with the Details Section stating
    Details:
    AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.


    Steps
     1. Take Ownership of FileMaps located at c:\windows\winsxs\Filemaps.
     2. Grant yourself full access permisions to the Filemaps folder... (When you do this you will get an error when it tries to apply this change to the files in the folder... this is ok... just cancel this error message.
     3. Make an empty dir somewhere to hold this files while finding the offending file. Lets say c:\test
     4. Move all of the files from c:\windows\winsxs\Filemaps to c:\test
    (
    If you do a "vssadmin list writers" at this point you will get a CAPI2 513 error with a details that says
    Details:
    AddCoreCsiFiles : BeginFileEnumeration() failed.

    System Error:
    There are no more files.
    )
     5. Start by putting half of the files from c:\test back into c:\windows\winsxs\filemaps.
     6. Test with vssadmin list writers. If you get the original CAPI2 513 error then the bad file was part of the group that you just move in.
         If there is no error then that group was clean.
     Repeat this process until you narrow down which file or files is causing the error. Once found remove it from the filemaps directory. (I would keep a copy of it somehwere for now)
     (I am curious to find out which file was bad for you)

    7. After determing the bad file, make sure you put the permissions back the way they were on the filemaps directory just to be safe. 

    Saturday, May 09, 2009 7:21 PM

All replies

  • Wednesday, December 10, 2008 9:47 AM
    Moderator
  • Same problem for me - I already followed the mentionend TN article but did not succeed in removing this error.

    Wednesday, December 10, 2008 2:47 PM
  • same problem with me - I already followed the mentioned TN article but did not succeed in removing this error

     

    Wednesday, December 10, 2008 2:49 PM
  • Certainly is.  Certainly explains the problem but offers no real help in rectifying it.

     

    Wednesday, December 10, 2008 7:42 PM
  • Still have the problem, even after following the link provided.  There seems to be chatter about this issue but no resolution.
    Sunday, February 08, 2009 6:28 PM
  • Anything new ? No solution up to now...
    Monday, February 16, 2009 10:00 AM
  • bump?
    Tuesday, February 17, 2009 2:40 AM
  • Same issues here. There are many suggestions, but no resolution.

    2008 Ent x64 running SQL Server 2008

    Get the CAPI2 Errors after every backup. Also logs the error when running vssadmin list writers.
    System Writer is not listed.

    Tried rolling back Windows Installer 4.5 Hotfix. Did not resolve the issue.

    Does anyone have any insight as to what is the root cause?




    Did I do that?
    Tuesday, February 17, 2009 5:42 PM
  • Hi,

    Sorry that you are seeing this issue. Can you let me know following information which will help us debug this issue :-

    1) On what machine you are seeing this issue ? Is it SP1 or SP2 ?
    2) If its SP2 then is it that after installing SP2 you started seeing this problem and with SP1 it was working fine ?
    3) Also can you tell me how do I reproduce this error. Is it I need to follow some specific steps and I can get a repro ?

    Thanks,
    Sachin
    Friday, February 20, 2009 10:30 PM
  • Hello,

    I'm on a computer with Vista Home Premium SP1.

    I see the Capi2 error in the application events log whenever a restore point is created, sometimes even 2 times in very short time. The Error is also logged if I use "vvsadmin list writers", the "system writer" is not listed with this command.
    Saturday, February 21, 2009 9:02 AM
  • I'm running Server 2008 x64 enterprise edition. Running Exchange 2007 SP1. This error is preventing me from getting a complete system backup.

    Same thing with me, "System Writer" is not listed with the vssadmin list writers command. Also, my Exchange VSS writer always has "retryable error" listed.
    Monday, February 23, 2009 12:12 AM
  • second computer with Vista Home premium: SP1 installed on January 31st - Capi2 error (which never happened before on this computer) now daily twice occuring. "system writer" also missing in vssadmin
    Wednesday, February 25, 2009 6:44 AM
  • It seems this error is difficult to track down a solution for.  After following the suggested articles on adjusting user permissions, it still wasn't showing the System Writers using vssadmin.  The solution is to adjust the permissions for the winsxs folder.  I made a batch file so I could cookie cutter the solution across my domain and it worked well.

    Hope this helps!

    Takeown /f %windir%\winsxs\filemaps\* /a  
    pause  
    icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"  
    pause  
    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"  
    pause  
    icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users:(RX)  
    pause  
    net stop cryptsvc  
    pause  
    net start cryptsvc  
    pause 


    Rob
    When in doubt defenstrate it
    • Proposed as answer by Rob da Tech Thursday, March 26, 2009 9:29 PM
    Thursday, March 26, 2009 8:52 PM
  • NO - tried it but it didn't help on my system. System Writer is still missing and still the same CAPI2 errors wit ID 512 - Details: AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed. System Error: 0xC0000039 (unresolvable)

    D.

    Friday, March 27, 2009 6:15 PM
  • dsar, the original post was about EventID 513 for CAPI2, not 512.  The 512 looks to be something service related.  Would you verify that your Volume Shadow Copy in Services is set to manual running or Automatic and then start it?  Then try the net stop cryptsvc and then net start cryptsvc from an administrative command prompt and see if it still doesn't list the System Writer?

    Hope this helps,

    Rob
    When in doubt defenstrate it
    Friday, March 27, 2009 7:08 PM
  • Rob, Sorry, that was a typo from my side - I'm getting 513 errors - not 512's
    VSS ist set to manual, and also foolowing your suggestion - start Vss, net stop/start cryptsvc I still do not get the system writer listed.

    Your help i highly appreciated.

    regards,

    D.
    Friday, March 27, 2009 9:05 PM
  • <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-charset:1; mso-generic-font-family:roman; mso-font-format:other; mso-font-pitch:variable; mso-font-signature:0 0 0 0 0 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin-top:0in; margin-right:0in; margin-bottom:10.0pt; margin-left:0in; line-height:115%; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} .MsoPapDefault {mso-style-type:export-only; margin-bottom:10.0pt; line-height:115%;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in; mso-header-margin:.5in; mso-footer-margin:.5in; mso-paper-source:0;} div.Section1 {page:Section1;} -->

    After three days I finally got this fixed.

    I ran process monitor to see what was being access during vssadmin list writers.
    I noticed it was going through all of the files in windows\winsxs\Filemaps. So I setup a test system in virtual pc and in the test system I cleared out the Filemaps directory and copied in all the entries from the production box that was having this problem. Bingo... same error was now on the test system. After a process of elimination I was left with only 1 file that caused the error.

    programdata_microsoft_windows_defender_definition_updates_default_44e57bb5c1e3d0e8

    I then removed this file from the production box's FileMaps directory and the error is now gone.

    Question... Does anyone know if there is going to be any further issues from having to remove this apparently corrupted file from the FileMaps directory? For now all seems to be well as there are no more CAPI2 513 errors and the "System Writer" now shows up under vssadmin list writers.

    Saturday, May 09, 2009 9:41 AM
  • One Last Update....
    I took the file programdata_microsoft_windows_defender_definition_updates_default_44e57bb5c1e3d0e8.cdf-ms from two other systems and compared them with diff and they were both identical. So I placed this known good copy into the FileMaps directory on box that originally had this error and all is still well.

    Looking at the original bad file and the known good copy in a hex editor revealed one notable difference. The bad one had a path including the drive letter "\??\D:\ProgramData\Microsoft\Windows Defender\Definition Updates\Default" while the good copies just had the path with no drive letter "ProgramData\Microsoft\Windows Defender\Definition Updates\Default". There were also several differences in the binary data of the files besides the path string.


    Saturday, May 09, 2009 5:53 PM
  • Great job !!

    unluckily for me it doesn't work on my system, still getting this sh.. CAPi2 error and still the system writer is missing.

    Could you please describe a bit in more detail what you did to identify the corrupt file ? - perhaps there are other files similar corrupted on my systems.

    Did you need to re-boot after you deleted the file ?

    thank you



    Saturday, May 09, 2009 6:43 PM
  • First make sure you have the same error. CAPI2 513 with the Details Section stating
    Details:
    AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed.


    Steps
     1. Take Ownership of FileMaps located at c:\windows\winsxs\Filemaps.
     2. Grant yourself full access permisions to the Filemaps folder... (When you do this you will get an error when it tries to apply this change to the files in the folder... this is ok... just cancel this error message.
     3. Make an empty dir somewhere to hold this files while finding the offending file. Lets say c:\test
     4. Move all of the files from c:\windows\winsxs\Filemaps to c:\test
    (
    If you do a "vssadmin list writers" at this point you will get a CAPI2 513 error with a details that says
    Details:
    AddCoreCsiFiles : BeginFileEnumeration() failed.

    System Error:
    There are no more files.
    )
     5. Start by putting half of the files from c:\test back into c:\windows\winsxs\filemaps.
     6. Test with vssadmin list writers. If you get the original CAPI2 513 error then the bad file was part of the group that you just move in.
         If there is no error then that group was clean.
     Repeat this process until you narrow down which file or files is causing the error. Once found remove it from the filemaps directory. (I would keep a copy of it somehwere for now)
     (I am curious to find out which file was bad for you)

    7. After determing the bad file, make sure you put the permissions back the way they were on the filemaps directory just to be safe. 

    Saturday, May 09, 2009 7:21 PM
  • Almost missed the reboot question...
    No reboot is required. As soon as you move a file in or out of the filemaps directory you can immediately test with vssadmin list writers
    Saturday, May 09, 2009 7:28 PM
  • Hello,

    I did as you described and found 40 (!) files which resulted in the CAPI2 error. All files start with "program_files_*.cdf-ms". A check with a HEX editor showed that all these files had a path including \??\P:\Program....
    By copying thes files from another computer everything seems to be fine now. No more CAPI2 errors and the "System Writer" is present.

    Thank you again for your great work.

    By the way ... the file programdata_microsoft_windows_defender_definition_updates_default_44e57bb5c1e3d0e8.cdf-ms was OK on my computer !!

    dsar
    Sunday, May 10, 2009 9:33 AM
  • Wow, what a strange bug this one is.

    Glad this now appears to be a universal solution to this error condition. In three days I went from not even knowing the system writer existed to knowing way more about it then I really care to know :)

    Paul



     
    Sunday, May 10, 2009 10:24 AM
  • and with the installation of vista sp2 the nice Capi2 error is back ...

    so again the same problem and nearly the same files corrupted (at least 20 out of the original 40)

    copying these files from an other computer with SP2 helped again......

    daniel
    Wednesday, May 27, 2009 5:45 PM
  • http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/bb760434-de80-4cb6-ae9e-bd253e4b037c/

    This is about the same problem. Even thought they opened it with DPM 2007 it excatly the same problem. System Writer missing.

    And another one same problem:
    http://social.technet.microsoft.com/Forums/en-US/windowsbackup/thread/b5236028-4bfe-400c-90e2-b6d40b08e776



    I posted there before and just found a second server having the same error. Still no resolution found.

    EDIT: OK I'm confused. On one server it looks like the security settings get reset. On the other system they seem to stay the way I want them.... need to check that.

    Now the second server also reverted it's security settings inside filebase. Looks like this one set severell updates into status "installed" a few minutes before the error reapeared.
    So there's a chance that the other server had some updates too, which caused him to revert the settings.

    We are opening a case with Microsoft. Hope to get some answers. Coming back as soon as there is more to tell.
    • Edited by Deatheye Wednesday, July 01, 2009 2:11 PM
    • Proposed as answer by Jason Holden Thursday, July 02, 2009 6:13 PM
    Monday, June 29, 2009 1:06 PM
  • I had almost 75,000 files in my \winxs directory.

    Finding the culprit just wasn't feasible.

    Here how i fixed it on my Windows Vista Ultimate x64 SP2 laptop:

    1.  Take ownership of the \winxs directory
    2.  Ensure that the parent folder permissions are applied to all files and subfolders.  Easiest way is to right-click \winxs folder, click properties > Security Tab > Advanced > Edit > Replace all existing inheritable permissions...

    No more CAPI2 errors.

    • Proposed as answer by Jason Holden Thursday, July 02, 2009 6:17 PM
    Thursday, July 02, 2009 6:17 PM
  • For us it looks like the cause was lying in this two foldes and files / subfolders:
    winsxs\filempas
    winsxs\temp

    The wrong NTFS rights inside winsxs\temp seem to somehow overwrite the rights inside winsxs\filemaps. So as long as the error exists inside the temp folder it will reset the right on the filemaps folder.

    Did the following inside command shell

    Takeown /f %windir%\winsxs\filemaps /a
    icacls %windir%\winsxs\filemaps  /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps  /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps  /grant "BUILTIN\Users:(RX)"
    icacls %windir%\winsxs\filemaps  /grant "Administratoren:(RX)"
    Takeown /f %windir%\winsxs\filemaps\* /a
    icacls %windir%\winsxs\filemaps\*.*  /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "BUILTIN\Users:(RX)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "Administrators:(RX)"
    Takeown /f %windir%\winsxs\temp\PendingRenames /a
    icacls %windir%\winsxs\temp\PendingRenames  /grant "Administrators:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "BUILTIN\Users:(RX)"
    Takeown /f %windir%\winsxs\temp\PendingRenames\*.* /a
    icacls %windir%\winsxs\temp\PendingRenames\*.*  /grant "Administrators:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "BUILTIN\Users:(RX)"

    As a side note:
    I think this can also cause severe problems in case you want to upgrade a system with this error.
    winsxs\temp had no NTFS right. There was just no account inside the ntfs rights register. So no access for local system, trusted installer or anything at all.
    Tried to install SP2 on that machine.. totaly fucked it up. Now it even tells me to install SP1! on a windows server 2008.
    Not sure if this really was the cause but it's definitly not a good thing. So for me this means I check for this error before I install any updates...

    • Edited by Deatheye Monday, July 20, 2009 7:44 AM
    • Proposed as answer by AdrianY Wednesday, June 30, 2010 5:54 PM
    Monday, July 20, 2009 7:39 AM
  • Hi,

    this solution most probable helps if you have the CAPI2 error with the message "...AddCoreCsiFiles : BeginFileEnumeration() failed..."

    It did not help on my computer, where I have the CAPI2 errors with the message"...AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed...".

    I still get the error after nearly every Microsoft update and I still have to follow the procedure mentionend in one of the earlier posts - identify the "corrupted" files in filemaps (all of them have a path included like \??\P:\Program....) and copy them to my system from a clean PC.

    Only difference of the affected PC compared to the clean PC is, that the programs are stored on a different drive than c:

    Wednesday, August 05, 2009 7:20 AM
  • Deatheye, your instructions removed the 513 CAPI2 (AddCoreCsiFiles : BeginFileEnumeration() failed.) error from my system (Vista Ultimate x64) and brought back the missing "System writer" to the vssadmin list.

    Thanks a lot!
    Wednesday, November 25, 2009 11:49 PM
  • Thanks Deatheye, your steps resolved the 513 CAPI2 (AddCoreCsiFiles : BeginFileEnumeration() failed.) error on my 2008 Enterprise x64 SP1 box as well.  I also restarted the cryptsvc after applying these changes.  Now I have a handy bat file I can run every time this breaks :/.
    Wednesday, December 16, 2009 4:23 PM
  • For us it looks like the cause was lying in this two foldes and files / subfolders:
    winsxs\filempas
    winsxs\temp

    The wrong NTFS rights inside winsxs\temp seem to somehow overwrite the rights inside winsxs\filemaps. So as long as the error exists inside the temp folder it will reset the right on the filemaps folder.

    Did the following inside command shell

    Takeown /f %windir%\winsxs\filemaps /a
    icacls %windir%\winsxs\filemaps  /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps  /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps  /grant "BUILTIN\Users:(RX)"
    icacls %windir%\winsxs\filemaps  /grant "Administratoren:(RX)"
    Takeown /f %windir%\winsxs\filemaps\* /a
    icacls %windir%\winsxs\filemaps\*.*  /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "BUILTIN\Users:(RX)"
    icacls %windir%\winsxs\filemaps\*.*  /grant "Administrators:(RX)"
    Takeown /f %windir%\winsxs\temp\PendingRenames /a
    icacls %windir%\winsxs\temp\PendingRenames  /grant "Administrators:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\temp\PendingRenames /grant "BUILTIN\Users:(RX)"
    Takeown /f %windir%\winsxs\temp\PendingRenames\*.* /a
    icacls %windir%\winsxs\temp\PendingRenames\*.*  /grant "Administrators:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\temp\PendingRenames\*.* /grant "BUILTIN\Users:(RX)"

    As a side note:
    I think this can also cause severe problems in case you want to upgrade a system with this error.
    winsxs\temp had no NTFS right. There was just no account inside the ntfs rights register. So no access for local system, trusted installer or anything at all.
    Tried to install SP2 on that machine.. totaly ____ it up. Now it even tells me to install SP1! on a windows server 2008.
    Not sure if this really was the cause but it's definitly not a good thing. So for me this means I check for this error before I install any updates...



    Thanks. After much searching, this solution is what worked for me. I'd recommend others give it a go if they are getting these same Event ID 513 errors.
    Monday, May 17, 2010 4:26 AM
  • Hi,

    this solution most probable helps if you have the CAPI2 error with the message "...AddCoreCsiFiles : BeginFileEnumeration() failed..."

    It did not help on my computer, where I have the CAPI2 errors with the message"...AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed...".

    I still get the error after nearly every Microsoft update and I still have to follow the procedure mentionend in one of the earlier posts - identify the "corrupted" files in filemaps (all of them have a path included like \??\P:\Program....) and copy them to my system from a clean PC.

    Only difference of the affected PC compared to the clean PC is, that the programs are stored on a different drive than c:

     

    I have exactly the same problem (RtlConvertNtFilePathToWin32Path() failed) in exactly the same situation (the programs are stored on a different drive than c:). I haven't yet found a solution.

    Tuesday, June 29, 2010 11:00 PM
  • Solution proposed by Deatheye works for me with a Windows Server 2008 STD box.

    I had the error:

    Nombre de registro:Application
    Origen:    Microsoft-Windows-CAPI2
    Fecha:     27/06/2010 10:00:03 p.m.
    Id. del evento:513
    Categoría de la tarea:Ninguno
    Nivel:     Error
    Palabras clave:Clásico
    Usuario:    No disponible
    Equipo:    XXXXXX
    Descripción:
    Error en Servicios de cifrado mientras procesaba el Objeto "System Writer" de la llamada OnIdentity().
    Details:
    AddCoreCsiFiles : BeginFileEnumeration() failed.
    System Error:
    Acceso denegado.
    .

    (OS is in Spanish)

    And vssadmin list writers didn't shows "System Writer". Now it does!

    Thanks!

    Wednesday, June 30, 2010 5:59 PM
  • If the error is 'access denied' then the solutions proposed by Deatheye and Jason Holden seem to work (which are basically doing the same thing, reapplying permissions).

    I did it through the GUI, which found a folder with incorrect permissions. After over-writing these permissions vssadmin brings back system writer and no more errors :)

    Monday, July 05, 2010 11:28 AM
  • Hi,

    this solution most probable helps if you have the CAPI2 error with the message "...AddCoreCsiFiles : BeginFileEnumeration() failed..."

    It did not help on my computer, where I have the CAPI2 errors with the message"...AddCoreCsiFiles : RtlConvertNtFilePathToWin32Path() failed...".

    I still get the error after nearly every Microsoft update and I still have to follow the procedure mentionend in one of the earlier posts - identify the "corrupted" files in filemaps (all of them have a path included like \??\P:\Program....) and copy them to my system from a clean PC.

    Only difference of the affected PC compared to the clean PC is, that the programs are stored on a different drive than c:

     

    I have exactly the same problem (RtlConvertNtFilePathToWin32Path() failed) in exactly the same situation (the programs are stored on a different drive than c:). I haven't yet found a solution.


    This is also occuring in Windows 7 64bit if the "Program Files" and "Program Files (x86)" are located on D: instead of C:

    I also am able to locate 8 or so files that if removed from \winsxs\FileMaps resolve the EventID 513 errors. Furthermore, they all have the \??\X:\ path in the files, so this definitely appears to be a path issue caused by Windows not liking having Program Files anywhere but C:

    If anyone from MS reads this, I have Junctions mapping "C:\Prog...", "C:\Prog...(x86)", and "C:\Users" to drive D:

    msspbm's solution works for me, and all of the corrupted files have file modified dates that are well after installation.

    Monday, September 06, 2010 11:24 PM

  • This is also occuring in Windows 7 64bit if the "Program Files" and "Program Files (x86)" are located on D: instead of C:

    I also am able to locate 8 or so files that if removed from \winsxs\FileMaps resolve the EventID 513 errors. Furthermore, they all have the \??\X:\ path in the files, so this definitely appears to be a path issue caused by Windows not liking having Program Files anywhere but C:

    If anyone from MS reads this, I have Junctions mapping "C:\Prog...", "C:\Prog...(x86)", and "C:\Users" to drive D:

    msspbm's solution works for me, and all of the corrupted files have file modified dates that are well after installation.

    I was seeing the same issue on my Vista system, the difference being my Program Files are on C: but my Windows folder is on J:. So it looks like just the fact that the Windows folder and the Program Files folders are on different drive letters is the trigger.

    msspbm's solution also worked for me. I found 15 files in the FileMaps folder that had the \??\C: in them and needed to be removed.

    Monday, November 01, 2010 1:57 PM
  • Old post but it's always helpful to post a sucesses...

     

    We were getting the same 513 error with Access Denied in the Event Logs and this script worked a charm, no more errors and System Writer is now listed!!

     

    Thanks!

    Thursday, November 11, 2010 9:43 AM
  • For me on two Windows 2008 server from customer

    This worked on an administrator command window:

    Takeown /f %windir%\winsxs\filemaps\* /a
    icacls %windir%\winsxs\filemaps\*.* /grant "NT AUTHORITY\SYSTEM:(RX)"
    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"
    icacls %windir%\winsxs\filemaps\*.* /grant BUILTIN\Users: (RX)

    after this i could do a systemstate backup with:

    wbadmin start systemstatebackup -backuptarget:driveletter:

    Thursday, December 16, 2010 3:36 PM
  • Deatheye's method resolved my issue as well..

    thanks!

    Tuesday, December 21, 2010 8:20 PM
  • Deatheye's post helped me too! great job

    thank you

    Thursday, December 23, 2010 8:26 PM
  • Deatheye's method resolved my issue as well..

    very thanks!

    Tuesday, February 01, 2011 10:50 PM
  • Hi,

    here is another solution that worked for me, i used few CMDlet from difrent solutions :)

    1st i checked that permissions like it says here:
    http://technet.microsoft.com/en-us/library/cc734021(WS.10).aspx

    then i run cmd elevated mode:
    Takeown /f %windir%\winsxs\filemaps\* /a

    and the last command that helped me was:

    icacls %windir%\winsxs\filemaps\*.* /grant "NT Service\trustedinstaller:(F)"

    and all works fine now and i can see system writer.

    thx all


    lipaz@yazamco.co.il, נא לשנן כתובת זו למקרים קשים :)
    Monday, May 23, 2011 10:07 AM
  • msspbm, your solution worked for me.

     

    The files were:

    $$.cdf-ms

    $$_system32_21f9a9c4a2f8b514.cdf-ms

    _0000000000000000.cdf-ms

    Friday, December 23, 2011 12:02 AM