Windows server 2008 r2 папка temp

Posted by Mark-Weehooey 2014-05-15T14:58:10Z

• 

  It’s safe to delete them

  A lot of system updates and installs leave these behind

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Brand Representative for Netwrix

  ghost chili

  This files are temporary files created by different Windows operations, like installing updates. You can safely delete them. But don’t forget to make a system backup before.

  You can find more information here: http://answers.microsoft.com/en-us/windows/forum/windows_7-files/cabxxxx-files-found-in-windowstemp-… Opens a new window

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• The only time deleting them can become a problem is if you ever have to uninstall one of those updates. Some cab files are necessary to keep.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Thanks guys I will delete them.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Chad.w

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  habanero

  Just throwing this out for search engine purposes. If you read the article linked by Michael, this is a symptom of a larger problem and not just a byproduct of installing applications. We have systems with 90+GB of these files being generated by a failing windows service that cannot process log files. Deleting the files is a great bandage but is far from the solution to the root cause. 

  
  3 found this helpful
  thumb_up
  thumb_down
  

• 

  Thanks for mentioning that Chad. I had the same issue: c:windowslogscbs had an old large log file that couldn’t get zipped, on a 2008r2 server. +1.

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  I wrote a powershell script that fixes this issue on a remote computer.  Email techaz@gmail.com and I’d be more than happy to share the script.  It does the following:

  ·       
  Stops the update service on the machine

  ·       
  Removes the temp files from c:windowstemp

  ·       
  Renames the softwaredistribution folder

  ·       
  Restarts the update service on the machine

  ·       
  Removes the old softwaredistribution
  folder

  ·       
  Stops the trustedinstaller service on the
  machine

  ·       
  Removes the cab files from c:windowslogsCBS

  ·       
  Restarts the trustedinstaller service

  ·       
  Reconnects with WSUS and rebuilds cab files

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Strangeronfire wrote:

  I wrote a powershell script that fixes this issue on a remote computer.  Email techaz@gmail.com and I’d be more than happy to share the script.  It does the following:

  ·       
  Stops the update service on the machine

  ·       
  Removes the temp files from c:windowstemp

  ·       
  Renames the softwaredistribution folder

  ·       
  Restarts the update service on the machine

  ·       
  Removes the old softwaredistribution
  folder

  ·       
  Stops the trustedinstaller service on the
  machine

  ·       
  Removes the cab files from c:windowslogsCBS

  ·       
  Restarts the trustedinstaller service

  ·       
  Reconnects with WSUS and rebuilds cab files

  Would you mind sharing this script on the SpiceWorks script section?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  #variables

  $Machine = read-host «Type in the Computer Name»
  $service1 = ‘wuauserv’
  $service2 = ‘trustedinstaller’

  #stops update service

  [string]$WaitForIt = «»
  [string]$Verb = «»
  [string]$Result = «FAILED»
  $svc = (get-service -computername $Machine -name $service1)
  Write-host «$service1 on $machine is $($svc.status)»
  Switch ($svc.status) {
      ‘Stopped’ {
          Write-host «Starting $service1…»
          $Verb = «start»
          $WaitForIt = ‘Running’
          $svc.Start()}
      ‘Running’ {
          Write-host «Stopping $service1…»
          $Verb = «stop»
          $WaitForIt = ‘Stopped’
          $svc.Stop()}
      Default {
          Write-host «$service1 is $($svc.status). Taking no action.»}
  }
  if ($WaitForIt -ne «») {
      Try { # For some reason, we cannot use -ErrorAction after the next statement:
          $svc.WaitForStatus($WaitForIt,’00:02:00′)
      } Catch {
          Write-host «After waiting for 2 minutes, $service1 failed to $Verb.»
      }
      $svc = (get-service -computername $Machine -name $service1)
      if ($svc.status -eq $WaitForIt) {$Result = ‘SUCCESS’}
      Write-host «$Result`: $service1 on $Machine is $($svc.status)»
  }

  #removes temp files and renames software distribution folder

  Remove-Item \$Machinec$windowstemp* -recurse
  Rename-Item \$Machinec$windowsSoftwareDistribution SoftwareDistribution.old

  #restarts update service

  [string]$WaitForIt = «»
  [string]$Verb = «»
  [string]$Result = «FAILED»
  $svc = (get-service -computername $Machine -name $service1)
  Write-host «$service1 on $machine is $($svc.status)»
  Switch ($svc.status) {
      ‘Stopped’ {
          Write-host «Starting $service1…»
          $Verb = «start»
          $WaitForIt = ‘Running’
          $svc.Start()}
      ‘Running’ {
          Write-host «Stopping $service1…»
          $Verb = «stop»
          $WaitForIt = ‘Stopped’
          $svc.Stop()}
      Default {
          Write-host «$service1 is $($svc.status). Taking no action.»}
  }
  if ($WaitForIt -ne «») {
      Try { # For some reason, we cannot use -ErrorAction after the next statement:
          $svc.WaitForStatus($WaitForIt,’00:02:00′)
      } Catch {
          Write-host «After waiting for 2 minutes, $service1 failed to $Verb.»
      }
      $svc = (get-service -computername $Machine -name $service1)
      if ($svc.status -eq $WaitForIt) {$Result = ‘SUCCESS’}
      Write-host «$Result`: $service1 on $Machine is $($svc.status)»
  }

  #removes software distribution.old

  Remove-Item \$Machinec$windowsSoftwareDistribution.old -recurse

  #stops trustedinstaller service

  [string]$WaitForIt = «»
  [string]$Verb = «»
  [string]$Result = «FAILED»
  $svc = (get-service -computername $Machine -name $service2)
  Write-host «$service2 on $machine is $($svc.status)»
  Switch ($svc.status) {
      ‘Stopped’ {
          Write-host «Starting $service2…»
          $Verb = «start»
          $WaitForIt = ‘Running’
          $svc.Start()}
      ‘Running’ {
          Write-host «Stopping $service2…»
          $Verb = «stop»
          $WaitForIt = ‘Stopped’
          $svc.Stop()}
      Default {
          Write-host «$service2 is $($svc.status). Taking no action.»}
  }
  if ($WaitForIt -ne «») {
      Try { # For some reason, we cannot use -ErrorAction after the next statement:
          $svc.WaitForStatus($WaitForIt,’00:02:00′)
      } Catch {
          Write-host «After waiting for 2 minutes, $service2 failed to $Verb.»
      }
      $svc = (get-service -computername $Machine -name $service2)
      if ($svc.status -eq $WaitForIt) {$Result = ‘SUCCESS’}
      Write-host «$Result`: $service2 on $Machine is $($svc.status)»
  }

  #removes cab files from trustedinstaller

  remove-item \$Machinec$windowsLogsCBS* -recurse

  #restarts trustedinstaller service

  [string]$WaitForIt = «»
  [string]$Verb = «»
  [string]$Result = «FAILED»
  $svc = (get-service -computername $Machine -name $service2)
  Write-host «$service2 on $machine is $($svc.status)»
  Switch ($svc.status) {
      ‘Stopped’ {
          Write-host «Starting $service2…»
          $Verb = «start»
          $WaitForIt = ‘Running’
          $svc.Start()}
      ‘Running’ {
          Write-host «Stopping $service2…»
          $Verb = «stop»
          $WaitForIt = ‘Stopped’
          $svc.Stop()}
      Default {
          Write-host «$service2 is $($svc.status). Taking no action.»}
  }
  if ($WaitForIt -ne «») {
      Try { # For some reason, we cannot use -ErrorAction after the next statement:
          $svc.WaitForStatus($WaitForIt,’00:02:00′)
      } Catch {
          Write-host «After waiting for 2 minutes, $service2 failed to $Verb.»
      }
      $svc = (get-service -computername $Machine -name $service2)
      if ($svc.status -eq $WaitForIt) {$Result = ‘SUCCESS’}
      Write-host «$Result`: $service2 on $Machine is $($svc.status)»
  }

  #rebuilds cab files from WSUS

  invoke-command -ComputerName $Machine -ScriptBlock { & cmd.exe «c:windowssystem32wuauclt.exe /detectnow» }

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I have windows 7 PC, onto which around 370 GB is utilized by cab log files Out of 450 GB, I see the system does not have SCCM in it.I have windows 7 64 bit.

  However once a cab file is deleted it re-occurs in  few minutes 

  Can any one help? 

  Regards,

  Rohit

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  M Boyle

  
  

  This person is a verified professional.

  Verify your account
  to enable IT peers to see that you are a professional.

  ghost chili

  @Daniel, you can use functions to simplify your code.

  Powershell

  $Machine = read-host "Type in the Computer Name"
  
  $windowsUpdateService = 'wuauserv'
  $trustedInstallerService = 'trustedinstaller'
  
  function Set-ServiceState 
  {
      [CmdletBinding()]
      param(
          [string]$ComputerName,
          [string]$ServiceName
      )
  
      Write-Verbose "Evaluating $ServiceName on $ComputerName."
  
      [string]$WaitForIt = ""
      [string]$Verb = ""
      [string]$Result = "FAILED"
  
      $svc = Get-Service -computername $ComputerName -name $ServiceName)
      Switch ($svc.status) {
          'Stopped' {
              Write-Verbose "[$ServiceName] is currently Stopped. Starting."
              $Verb = "start"
              $WaitForIt = 'Running'
              $svc.Start()
          }
          'Running' {
              Write-Verbose "[$ServiceName] is Running. Stopping."
              $Verb = "stop"
              $WaitForIt = 'Stopped'
              $svc.Stop()
          }
          default {
              Write-Verbose "$ServiceName is $($svc.status). Taking no action."
          }
      }
  
      if ($WaitForIt -ne "") {
          Try { # For some reason, we cannot use -ErrorAction after the next statement:
              $svc.WaitForStatus($WaitForIt,'00:02:00')
          } Catch {
              Write-Warning "After waiting for 2 minutes, $ServiceName failed to $Verb."
          }
  
          $svc = (get-service -computername $ComputerName -name $ServiceName)
          if ($svc.status -eq $WaitForIt) {
              $Result = 'SUCCESS'
          }
  
          Write-Verbose "$Result - $ServiceName on $ComputerName is $($svc.status)"
          Write-Verbose ("{0} - {1} on {2} is {4}" -f $Result, $ServiceName, $ComputerName, $svc.status)
      }
  
  }
  
  # stop update service
  Set-ServiceState -ComputerName $Machine -ServiceName $windowsUpdateService -Verbose
  
  #removes temp files and renames software distribution folder
  Remove-Item \$Machinec$windowstemp* -recurse
  Rename-Item \$Machinec$windowsSoftwareDistribution SoftwareDistribution.old
  
  #restarts update service
  Set-ServiceState -ComputerName $Machine -ServiceName $windowsUpdateService
  
  
  #removes software distribution.old
  Remove-Item \$Machinec$windowsSoftwareDistribution.old -recurse
  
  #stops trustedinstaller service
  Set-ServiceState -ComputerName $Machine -ServiceName $trustedInstallerService
  
  
  #removes cab files from trustedinstaller
  remove-item \$Machinec$windowsLogsCBS* -recurse
  
  #restarts trustedinstaller service
  Set-ServiceState -ComputerName $Machine -ServiceName $trustedInstallerService
  
  
  #rebuilds cab files from WSUS
  invoke-command -ComputerName $Machine -ScriptBlock { & cmd.exe "c:windowssystem32wuauclt.exe /detectnow" }
  

  much less code duplication though I have not tested it

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  Do we know why this even happens? It’s randomly happening on machines around the office (350+ users) and is an easy fix now, but how to resolve the real problem going forward?

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Also have the problem here — random machines too, not all of them — maybe 25% ?

  125GB of CAB files in the temp directory.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Has anyone tested that script that M Boyle provided?  It looks good but I am no Powershell Pro

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• same here.  VM that just stopped responding because disk was full.  Turned out to be 140GB of cabs.

  We don’t use WSUS, but I wonder if its supposed to clear them out automatically?

  Perhaps I should set a weekly task to run and empty the TEMP folder.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I follow this directions and fix my issue: 

  I wrote a powershell script that fixes this issue on a remote computer. Email techaz@gmail.comand I’d be more than happy to share the script. It does the following:

  ·       Stops the update service on the machine

  ·       Removes the temp files from c:windowstemp

  ·       Renames the softwaredistribution folder

  ·       Restarts the update service on the machine

  ·       Removes the old softwaredistribution folder

  ·       Stops the trustedinstaller service on the machine

  ·       Removes the cab files from c:windowslogsCBS

  ·       Restarts the trustedinstaller service

  ·       Reconnects with WSUS and rebuilds cab files

  If you want the script is a few post above. 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• appreciate the offer, but we don’t use WSUS.

  However, I did go here and follow directions to create a scheduled daily task to empty the folder. 

  https://social.technet.microsoft.com/wiki/contents/articles/36429.schedule-task-to-empty-windows-tem… Opens a new window.

  And ran this command to set the execution policy for powershell.

  Set-ExecutionPolicy RemoteSigned

  Works perfectly.

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Ups sorry forgot to tell you we dont use WSUS either but we follow the steps until the step »

  Reconnects with WSUS and rebuilds cab files» and that stop the cab’s file creation. 

  just my 2 cents 

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• Have had this cause big problems w a retail customer whose QB POS crashed due to a few hundred GB of these cabs. Also cropped up on a few other machines. A few of these just sit there doing nothing for the most part and drives are becoming full. My feeling is something changed in the last 6mos to 1year that is causing this. Can only imagine a Win update as like I said a few of these are more or less static (used primarily for RDC to access networked devices programming GUIs). 

  In any event if anyone gets info on the root cause and solution please post here. Thanks

  Clifford

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  The script provided in this thread doesn’t require WSUS to be used. It simply performs a «check for updates» in Windows Update, which will recreate the SoftwareDistribution folder. If WSUS is in use it’ll check the WSUS server. If WU is in use it’ll check the normal Windows Update.

  That said, the core issue behind the infinite cab problem is often the CBS logs, which have exceeded the storage limits of the MakeCab program. MakeCab suffers from a 2gb file limitation, so once any single file in the c:windowslogsCBS folder grows beyond 2gb it chokes and fails, consuming memory until the process is killed every hour by the task scheduler when it attempts to do it again. If the machine is left on 24/7 it’ll continue to consume a huge chunk of space every hour with new, broken cabs until it eats up all the disk space and has to be manually attended to. The fix is to purge the CBS folder so that this will stop. This step is already in the script provided above, so it should be a fine solution. You could also manually remove just the contents of the CBS folder and the cabs themselves, which will have the same effect:
  

  del c:windowslogscbscbs*
  del c:windowstempcab*

  I know, it’s not glamorous like the powershell script above, but it works.

  
  6 found this helpful
  thumb_up
  thumb_down
  

• 

  This worked for me on a Server 2008 R2 box — cleared up 110GB on a 130GB C: drive. 2 simple commands as shawnkhall stated

  del c:windowslogscbscbs*
  del c:windowstempcab*

  
  2 found this helpful
  thumb_up
  thumb_down
  

• shawnkhall solutions appear to be the most elegant / streamlined for addressing this problem that I have seen….a problem which I have been dealing with on many different clients’ Windows 7 computers now for over one year, so thanks for that.  My question is, do shawnkhall’s solutions *keep* this problem from happening in the future, or not?  I ask because I’ve read some things about this (amazing that it even exists) problem that only deleting the files simply frees up the hard drive space for the problem to start filling up the hard drive (slowly but surely) again.

  Another really surprising thing about this year long + problem is that *none* of my other local IT colleagues have seen this problem at all on their clients Windows 7 computers.  As much as I have seen this problem on my clients’ computers, I simply can not understand why none of my local IT colleagues haven’t seen it!  That makes me start to think this problem is caused by (or exacerbated by) software I typically use (like Webroot antivirus, etc. etc.), and or configurations that I utilize, that my IT colleagues don’t.  If I am right about that, I wonder what the common denominator is for all of us across the Internet that have seen this problem?

  Thanks!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  Hi, +bripchris. Yes and no. Removing the source CBS logs (the ones responsible for exceeding the 2gb limit) will resolve the current CBS log issue and prevent it from happening again on the current machine…until there’s another hiccup with the Windows Update service that causes a log to be generated that would otherwise exceed the 2gb makecab limitation.

  It’s a real fix for the current instance of the current issue, but it’s only as permanent as whatever other problems the machine has that will recreate logs that exceed the makecab limit. 

  Regularly reviewing the WU logs for potential issues (likely a result of intermittent connectivity problems that force fractional downloads of updates and attempts to re-download) will minimize the risk of recurrence.

  
  1 found this helpful
  thumb_up
  thumb_down
  

• 

  You ROCK!!!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  I’ve disable windows update service and all warning popups.
  Since the win7 refused to get its update repaired. I’ve chosen to not use it
  and hide the warnings. Not a fix but quick remedy!

  
  Was this post helpful?
  thumb_up
  thumb_down
  

• 

  shawnkhall wrote:

  The script provided in this thread doesn’t require WSUS to be used. It simply performs a «check for updates» in Windows Update, which will recreate the SoftwareDistribution folder. If WSUS is in use it’ll check the WSUS server. If WU is in use it’ll check the normal Windows Update.

  That said, the core issue behind the infinite cab problem is often the CBS logs, which have exceeded the storage limits of the MakeCab program. MakeCab suffers from a 2gb file limitation, so once any single file in the c:windowslogsCBS folder grows beyond 2gb it chokes and fails, consuming memory until the process is killed every hour by the task scheduler when it attempts to do it again. If the machine is left on 24/7 it’ll continue to consume a huge chunk of space every hour with new, broken cabs until it eats up all the disk space and has to be manually attended to. The fix is to purge the CBS folder so that this will stop. This step is already in the script provided above, so it should be a fine solution. You could also manually remove just the contents of the CBS folder and the cabs themselves, which will have the same effect:
  

  del c:windowslogscbscbs*
  del c:windowstempcab*

  I know, it’s not glamorous like the powershell script above, but it works.

  This worked for me. It was a CBS log over 20 gb in size and hundreds of gbs of cabs in the temp folder. Those two lines wiped it all. Thanks Shawn!

  
  Was this post helpful?
  thumb_up
  thumb_down