Deployment Failed: Error - Failed To Create Remote Directory - %SystemRoot%\ProPatches

Version 3


    When deploying to a machine it fails with the error: Error - Failed to create remote directory - %SystemRoot%\ProPatches


    You can also see this error in the ST.Protect.managed log


    2015-04-08T12:55:19.6125618Z 0022 E PatchDeploymentTaskView.cs:305|Deployment id 10217: Error on machine 'Server1': Failed - Error - Failed to create remote directory - %SystemRoot%\ProPatches


    You are able to scan the machine but you are not able to access the UNC path via Windows Explorer; ie \\Machine\C$




    A Windows server is missing the Administrative Share (e.g. C$, D$)


    Additional Information:

    By default, Windows creates hidden or Administrative Shares for root partitions or volumes on the server.
    These shares are known by the drive letter followed by the dollar sign ($). Sometimes the Administrative
    will disappear for some or all of the drives




    Open the registry and examine the AutoShareServer and\or AutoShareWks registry values to ensure that they are not set to 0:

       a.  Windows Server 2008 R2 and earlier- At the domain controller (DC) desktop click the Start menu, select Run, type regedit and click OK.


       Windows Server 2012 and later- Press the Windows key + Q, and type regedit in the search box.  Double-click on the regedit.exe icon when displayed.


       b.  Locate and then click the following registry sub-key:



       c.  If the AutoShareServer and AutoShareWks DWORD values in the LanmanServer\Parameters sub-key are configured with a value data of 0,

            change that value to 1.


      Back up the registry before you modify it, this is done at your own risk. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base


    Affected Product(s)

    Shavlik Protect 9.x