Target PC Windows Update Error Message

BatchPatch Forums Home Forums BatchPatch Support Forum Target PC Windows Update Error Message

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #14495
    jason.l
    Participant

    Error 1800: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147022976: The file cannot be accessed by the system.
    – 08:37:52

    I have a BatchPatch system deployed, and I consistently receive the error message below whenever I try to find new Windows updates on the target PCs.

    The target PC is reachable via ping, and the \\hostname\c$ share is accessible from the machine (or Server) where BatchPatch is installed. I have the required privileges, and the same process is working successfully on other target PCs within the environment. I am using cached-mode and offline-mode. Target PC’s firewall and AV are turned off. Target PC’s file and printer sharing service is turned on.

    #14497
    doug
    Moderator

    We’ve never seen this error before, but I think the most likely reason for it in your situation is that the WsusScn2.cab file is corrupt. Either it was corrupted during download to the BatchPatch computer, or it was corrupted during copy from the BatchPatch computer to the target computer. The location of the file on the BatchPatch computer is your local update cache directory, as defined under ‘Tools > Settings > Windows Update > Local update cache directory’. The location on the target computer would be the remote working directory, as defined under ‘Tools > Settings > Remote Execution > Remote Working Directory.’ One way to verify if the file is corrupt is to manually check it by right clicking on it and selecting Properties, and then select the Digital Signatures tab. If there is no Digital Signatures tab or the tab exists without a Digital Signature appearing there, then it’s surely corrupt. If the signature is intact, then I don’t think the file is likely to be corrupt, as a corrupt file would, I think, necessarily break the signature. If it’s not corruption, then it would seemingly have to be a permissions issue.

Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.