- This topic has 1 reply, 2 voices, and was last updated 5 years, 11 months ago by .
-
Posts
-
I’m running a remote Windows Update task on about 100 computers. All using the same account (with administrative privileges).
On a few computers, I’m receiving the following error:
Windows Update: Error 1614: Failed to create remote working directory. Please check permissions on the target computer and verify your working directory path in Tools > Settings. HRESULT -2147024843: Path not found.
The account used has administrative privileges in those machines (confirmed).
I run a procmon on remote in a remote computer with this behavior, and try to run a “Check for Windows Update” task on BatchPatch (x91)
I see a lot of errors for process name ‘w3wp.exe’ (IIS) trying to access the folder “C:INETPUBWWWROOTC$PROGRAM FILESBATCHPATCH”, resulting in “PATH NOT FOUND ERROR”.
Anyone can help me?
-2147024843 == ‘The network path was not found’
Since you are only seeing this on a few machines, I can think of a couple things that might cause this…
1. If the target computer does not have a C drive, then there will be no \targetComputerC$ , and so BatchPatch will not be able to create the directory. Check to see if the target computer has Windows installed on a different drive letter such as D or E etc.
2. A firewall issue could cause this. From the BatchPatch computer make sure you can access \targetComputerC$
BatchPatch ‘Getting Started’ page, which includes Windows Firewall Configuration
- You must be logged in to reply to this topic.