Exception Occurred During Publishing: CreateDirectory Failed

Version 15



    The purpose of the document is to review a common error when publishing updates.




    Exception occurred during publishing: CreateDirectory Failed



    "System Drive:\WSUS\UpdateServicesPackages" or "System Drive:\WSUS\WsusContent" is not shared for System Center Updates Publisher (SCUP) or System Center Configuration Manager (SCCM)




    Ensure "UpdateServicesPackages" exists in your WSUS content directory. By default, this will be whatever you specified during your SCCM installation. If it doesn't exist, create it and then go through the following steps.


    Microsoft recommends having the WSUSContent on a different drive than the OS. In the following example, the WSUS content is in C:\WSUS, but you can find the location of your content on your WSUS Server at HKLM\Software\Microsoft\Update Services\ServerSetup in the ContentDir key data section:

    WSUS Content Location.PNG


    1. Navigate to "C:\WSUS\UpdateServicesPackages"/"C:\WSUS\WsusContent" then Share the directory and set permissions to:




    If the UpdateServicesPackages location does not exist in the Content Directory you have setup in the registry create it and assign the correct permissions.


    • Admin's Group Full access
    • Network Service Full access
    • Everyone Read access
    • WSUS Administrators Group Full access.


    2. Set NTFS permissions to:


    • Administrators Group Full access
    • Network Service Full access
    • System Full access
    • Users Group Read/List Folder Read & Execute
    • WSUS Admins Group Full access.



    3. The following information is from WSUS: How to change the location where WSUS stores updates locally | SUS Blog :


    This tool will move ALL your existing and future Microsoft and third party content so make sure that your destination location has enough storage space or you could damage your WSUS.


    On your WSUS server open a command prompt with “run as admin”, Navigate to %programfiles%\update services\tools and issue the following command:

    WSUSUtil.exe movecontent <content path> <log path>



    <content path> = Drive letter of WSUS folder location (i.e. E:\WSUS\WSUSContent\UpdateServicesPackages)

    <log path> = Drive letter of log path with log file specified (i.e. C:\Temp\move.log)


    If that doesn’t work, try moving the content to a temporary location and then move it back to the desired path.


    Additional Information


    To find out more about the content and target directory locations use the link below:

    Verifying WSUS Server Settings


    Affected Product(s)


    Shavlik Patch for Microsoft System Center (Formerly SCUPdates)

    When publishing via:

    System Center Update Publisher (SCUP)

    Shavlik Patch Plugin 2.x