Important Notice: On February 29th, this community was put into read-only mode. All existing posts will remain but customers are unable to add new posts or comment on existing. Please feel to join our Community Discord for any questions and discussions.

Patches dumping to root?

Over the last year or so, I've noticed that PDQ-delivered patches are extracting and installing from the root of the hard drive which is both making a mess and causing issues on our limited-drive tablets.  I thought maybe it was the account it ran under, so I tried changed from the deployment user to system, but it seems to still happen.  Ideas?




Date Votes
  • Hi Brian,
    this is not a PDQ problem. All the Windows and office updates are created by Microsoft it self.
    When a patch is installed, it cleans up these temporary folders. Some patches require a restart and clean the folders afterwards. These folders remain only in case where the patch installation has failed or was forcibly interrupted. You can safely delete them if they remain after 2-3 reboots. (at least I haven't had the problem doing so)

    PDQ is not to blame here. You better check the event logs for installation errors anddo some:
    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
    You might want to check:!

  • Sorry, that's not true.   Patches that come down through WSUS drop into the .\softwaredownload folder for installation, not in the root of the C: drive.   As you can see, we have up to a year's worth of patches sitting in the root on 100s of boxes.  I'm not about to manually hit every box to find a randomly named directory to remove them, that rather defeats the purpose of automation.   

    DISM'ing a box isn't going to help in this case.  There isn't system corruption on these boxes.  But if it matters, this runs weekly on an automated task.

    This is absolutely an issue with PDQ's method of deployment.  We have no such issue with patches coming down through WSUS.   

  • Sorry, these folders are not created by PDQ Deploy itself. Its the patches them self/patch engine who create them. When they are installed, they extract to these random folders. I assume that some patch is failing to install an those folders are remnants of failed installations. Check the event logs at Application and Services Logs\Microsoft\Windows\WindowsUpdateClient

    Also start powershell and enter: Get-WindowsUpdateLog

    It will create a WindowsUpdate.log file on your desktop. Check for most recent fails.