Kaseya Community

Patch File Failed to Download

This question is not answered


I'm working with a client and they have some machines that are getting 'Patch File Failed to Download' under the test in Patch Status.  The strange thing is I can run the test again and different machines will now get the error while machines that once had the error are now successful and so forth.  They are set up to receive downloads directly from the Internet and the credentials are good.  They have good Internet speed.  I didn't know if this is somewhat cosmetic and if I should be concerned that the patches won't download.  I'm not in a position to test the patching yet so I'm just getting prepared.  I've had this error before with other clients but they usually had a valid reason like web filtering or a DNS issue and once the machine failed it always failed until fixed.

Thank you,


All Replies
  • David,

    I recommend you open a ticket on this.  There can be some variables at play that are difficult to advise via forums.  Behavior may be slightly different in 6.2 than in 6.3 just because there are some minor variations in the way credentials are used for some patch functions.  I could provide some very generalized information, but a ticket will be the best route to figuring out what's occurring, why, and how to prevent the same issue from reoccurring.

    From a general perspective, test whether the behavior is different when there is a user logged onto the machine v. when you run the test when no user is logged in.  It's possible that the network is able to authenticate/allow the tasks when the logged on user is present but not when no user is present.  This could be due to proxy, firewall rules, webfilter, or local security policies.  

    The patch test status is static - if failed, the notification of failure will remain until the next time the test runs.  Therefore, it's quite possible that the test will fail due to some environmental issue (whether that's internet or access rights or anything else) but then pass next time because the underlying condition of the failure is no longer present.  

    In any case, with a ticket, we can access your system and investigate the root cause for your particular environment.