Patches dumping to root?

Comments

3 comments

  • SelfMan

    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: https://www.800error.com/KB4566116-Windows-Updates-Update-nicht-werden#!

    -1
    Comment actions Permalink
  • Brian Green

    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.   

    0
    Comment actions Permalink
  • SelfMan

    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.

    0
    Comment actions Permalink

Please sign in to leave a comment.