Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #182569 > unrolled thread

Windows %TEMP% folder & files

Back to article view | Back to alt.comp.os.windows-10

Contents

  Windows %TEMP% folder & files Jim Dell <Jim.Dell@gmail.com> - 2025-02-26 09:12 -0500
    Re: Windows %TEMP% folder & files "R.Wieser" <address@is.invalid> - 2025-02-26 16:51 +0100
    Re: Windows %TEMP% folder & files Paul <nospam@needed.invalid> - 2025-02-26 12:53 -0500
      Re: Windows %TEMP% folder & files "Carlos E.R." <robin_listas@es.invalid> - 2025-02-26 19:29 +0100
        Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-02-26 20:46 +0000
          Re: Windows %TEMP% folder & files Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-26 21:15 +0000
            Re: Windows %TEMP% folder & files Newyana2 <newyana@invalid.nospam> - 2025-02-26 20:06 -0500
              Re: Windows %TEMP% folder & files Paul <nospam@needed.invalid> - 2025-02-26 21:09 -0500
              Re: Windows %TEMP% folder & files Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-27 11:15 +0000
                Re: Windows %TEMP% folder & files Newyana2 <newyana@invalid.nospam> - 2025-02-27 07:34 -0500
                  Re: Windows %TEMP% folder & files Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-27 19:00 +0000
                    Re: Windows %TEMP% folder & files Newyana2 <newyana@invalid.nospam> - 2025-02-27 16:54 -0500
                      Re: Windows %TEMP% folder & files Ed Cryer <ed@somewhere.in.the.uk> - 2025-02-27 22:54 +0000
                      Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-03-01 15:29 +0000
          Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-02-26 16:06 -0600
            Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-02-27 13:29 +0000
          Re: Windows %TEMP% folder & files Anssi Saari <anssi.saari@usenet.mail.kapsi.fi> - 2025-02-27 12:37 +0200
        Re: Windows %TEMP% folder & files Char Jackson <none@none.invalid> - 2025-02-26 17:57 -0600
          Re: Windows %TEMP% folder & files John <Man@the.keyboard> - 2025-02-27 12:01 +0000
        Re: Windows %TEMP% folder & files Zaidy036 <Zaidy036@air.isp.spam> - 2025-02-26 19:20 -0500
    Re: Windows %TEMP% folder & files Newyana2 <newyana@invalid.nospam> - 2025-02-26 13:42 -0500
    Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-02-26 13:55 -0600
      Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-02-26 14:23 -0600
    Re: Windows %TEMP% folder & files John <Man@the.keyboard> - 2025-02-27 11:47 +0000
      Re: Windows %TEMP% folder & files Jim Dell <Jim.Dell@gmail.com> - 2025-02-27 08:49 -0500
        Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-02-27 15:00 +0000
      Re: Windows %TEMP% folder & files Jim Dell <Jim.Dell@gmail.com> - 2025-02-27 08:49 -0500
    Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-02-27 06:43 -0800
      Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-02-27 15:31 +0000
        Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-02-28 05:29 -0800
          Re: Windows %TEMP% folder & files Paul <nospam@needed.invalid> - 2025-02-28 12:32 -0500
            Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-03-02 06:11 -0800
          Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-02-28 11:39 -0600
            Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-03-02 06:14 -0800
              Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-03-02 15:20 +0000
                Re: Windows %TEMP% folder & files Paul <nospam@needed.invalid> - 2025-03-02 14:57 -0500
                  Re: Windows %TEMP% folder & files Frank Slootweg <this@ddress.is.invalid> - 2025-03-02 20:28 +0000
                Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-03-03 06:15 -0800
              Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-03-02 14:44 -0600
          Re: Windows %TEMP% folder & files Mr Xi Ji Ping <ping@china.cn> - 2025-02-28 17:39 +0000
            Re: Windows %TEMP% folder & files VanguardLH <V@nguard.LH> - 2025-02-28 12:10 -0600
            Re: Windows %TEMP% folder & files "John C." <r9jmg0@yahoo.com> - 2025-03-02 06:18 -0800
          Re: Windows %TEMP% folder & files Jim Dell <Jim.Dell@gmail.com> - 2025-03-01 19:11 -0500
      Re: Windows %TEMP% folder & files John <Man@the.keyboard> - 2025-02-28 23:40 +0000
    Re: Windows %TEMP% folder & files Zaidy036 <Zaidy036@air.isp.spam> - 2025-02-27 10:03 -0500

Page 1 of 3  [1] 2 3  Next page →

#182569 — Windows %TEMP% folder & files

Got a question about the files in %TEMP%

There are thousands of them on my system

If you run “dir %TEMP%” from a command prompt you’ll see them.

Mostly mine are
HeadlessChrome304648710500
scoped_dir304_1457881672
folders

The only thing that changes is the numbers after the text.

Yes, a run a Chrome Headless job. Is there a parameter to set to I 
should set to prevent the HeadlessChrome folders?

I don’t know what is causing the scoped_dir folders from being created.

Any help would be appreciated.

Jim

[toc] | [next] | [standalone]

#182572

Jim,

> Is there a parameter to set to I should set to prevent the HeadlessChrome 
> folders?
>
> I don't know what is causing the scoped_dir folders from being created.

That %TEMP% folder is used what its for : for temporary foders and files 
generated by whatever programs you are running.  Though it customary that 
programs clean up behind themselves, it not always done or possible.

Bottom line : you can (should be able to) delete all of that folders 
contents.   Perhap s even add it to the "startup" folder.

Regards,
Rudy Wieser

[toc] | [prev] | [next] | [standalone]

#182573

On Wed, 2/26/2025 9:12 AM, Jim Dell wrote:
> Got a question about the files in %TEMP%
> 
> There are thousands of them on my system
> 
> If you run “dir %TEMP%” from a command prompt you’ll see them.
> 
> Mostly mine are
> HeadlessChrome304648710500
> scoped_dir304_1457881672
> folders
> 
> The only thing that changes is the numbers after the text.
> 
> Yes, a run a Chrome Headless job. Is there a parameter to set to I should set to prevent the HeadlessChrome folders?
> 
> I don’t know what is causing the scoped_dir folders from being created.
> 
> Any help would be appreciated.
> 
> Jim

scoped_dir304_1457881672

https://answers.microsoft.com/en-us/windows/forum/all/where-are-they-coming-from/6b703805-45e5-4e54-b9ce-3b07212ff18b

   "It appears these temp files are created from the Opera web browser...

    Normally when you close Opera it will delete these temp files upon closing.
    If you're you're leaving the browser open, and then shutting down without
    closing the browser first it does not have a chance to delete the temp files on close"

The tools provided with the system, may not do all that good of a job.

Cleanmgr.exe  should have something for %temp% .
I find though, that %temp% sometimes appears untouched.
You clean it, go look, and things that are delete-able are still there.

There is also some sort of Storage Spaces, that switches itself on
when disk space is low. And I don't want *any* automation to have
unfettered delete capability, because such tools don't really know
a valuable asset from junk. I remember when Cleanmgr had a tick
box to delete the *entire* contents of Downloads -- which for me
would be a disaster.

Cleaning it manually will work. Some of the files and folders in
there are "hot" and have a handle to them. A lot of the others will
easily delete when you attempt to throw them away. You can "skip"
the ones that refuse to go, rather than resorting to (infected)
UnLocker to do it. Things that have a handle, generally have a good
reason. There have been exceptions.

If you have thousands of folders, a cleanup attempt should get most of
them. The rest may be ready to harvest on the next "look", like
after a reboot. You can try "classes" of objects, like sort
the list, highlight all the scoped_dir and just delete those
(when Opera is not running).

   Paul

[toc] | [prev] | [next] | [standalone]

#182574

On 2025-02-26 18:53, Paul wrote:
> The tools provided with the system, may not do all that good of a job.

Somebody may have written a script to delete any file in that directory 
that is older than the current boot date. Run that on every boot. 
Alternatively, delete any thing older than 6 months, for instance.

-- 
Cheers, Carlos.

[toc] | [prev] | [next] | [standalone]

#182579

Carlos E.R. <robin_listas@es.invalid> wrote:
> On 2025-02-26 18:53, Paul wrote:
> > The tools provided with the system, may not do all that good of a job.
> 
> Somebody may have written a script to delete any file in that directory 
> that is older than the current boot date. Run that on every boot. 
> Alternatively, delete any thing older than 6 months, for instance.

  One thing I noted in my %TEMP% folder [1], is that, while there are
quite a lot of files and folders which use quite some space (210 Files,
105 Folders, Size 312MB), they are not very old! The oldest (both files
and folders) are of December 17, so a bit over two months old.

  So it seems the %TEMP% folder *is* being cleaned by some mechanism.

  Anybody having any insight on what is doing that cleaning?

[1[ C:\Users\<user>\AppData\Local\Temp

[toc] | [prev] | [next] | [standalone]

#182580

Frank Slootweg wrote:
> Carlos E.R. <robin_listas@es.invalid> wrote:
>> On 2025-02-26 18:53, Paul wrote:
>>> The tools provided with the system, may not do all that good of a job.
>>
>> Somebody may have written a script to delete any file in that directory
>> that is older than the current boot date. Run that on every boot.
>> Alternatively, delete any thing older than 6 months, for instance.
> 
>    One thing I noted in my %TEMP% folder [1], is that, while there are
> quite a lot of files and folders which use quite some space (210 Files,
> 105 Folders, Size 312MB), they are not very old! The oldest (both files
> and folders) are of December 17, so a bit over two months old.
> 
>    So it seems the %TEMP% folder *is* being cleaned by some mechanism.
> 
>    Anybody having any insight on what is doing that cleaning?
> 
> [1[ C:\Users\<user>\AppData\Local\Temp

It's probably done by the Windows Disk-cleanup utility; and that is only 
run as and when needed by users, and requires a tick for Temporary files.

Ed

[toc] | [prev] | [next] | [standalone]

#182585

On 2/26/2025 4:15 PM, Ed Cryer wrote:

>>
>>    Anybody having any insight on what is doing that cleaning?
>>
>> [1[ C:\Users\<user>\AppData\Local\Temp
> 
> It's probably done by the Windows Disk-cleanup utility; and that is only 
> run as and when needed by users, and requires a tick for Temporary files.
> 

   Not likely. I cleaned up a Win10 laptop just today with several GB
of TEMP and other junk. It's a good idea to run disk cleanup
manually.

  On XP/7 I use a script that just deletes all TEMP files from multiple
folders and ignores errors, which are generated if a file is in use.
There can be an app data user folder as well as c:\Windows\TEMP.

   The winsxs temp files never get cleaned as far as I know. That's
why I invlcuded the command line for that above. It supposedly
deletes things like outdated file versions where a newer version
exists.

   Windows since Vista has been incredibly bloated and sloppy about
these things, with winsxs, especially, growing out of control. People
need to take charge themselves or they'll end up with 40, 60, 80 or
more GB of junk. I see people on Reddit trying to figure out how
to get a few GBs space out of a full disk. It's nuts.

[toc] | [prev] | [next] | [standalone]

#182587

On Wed, 2/26/2025 8:06 PM, Newyana2 wrote:
> On 2/26/2025 4:15 PM, Ed Cryer wrote:
> 
>>>
>>>    Anybody having any insight on what is doing that cleaning?
>>>
>>> [1[ C:\Users\<user>\AppData\Local\Temp
>>
>> It's probably done by the Windows Disk-cleanup utility; and that is only run as and when needed by users, and requires a tick for Temporary files.
>>
> 
>   Not likely. I cleaned up a Win10 laptop just today with several GB
> of TEMP and other junk. It's a good idea to run disk cleanup
> manually.
> 
>  On XP/7 I use a script that just deletes all TEMP files from multiple
> folders and ignores errors, which are generated if a file is in use.
> There can be an app data user folder as well as c:\Windows\TEMP.
> 
>   The winsxs temp files never get cleaned as far as I know. That's
> why I invlcuded the command line for that above. It supposedly
> deletes things like outdated file versions where a newer version
> exists.
> 
>   Windows since Vista has been incredibly bloated and sloppy about
> these things, with winsxs, especially, growing out of control. People
> need to take charge themselves or they'll end up with 40, 60, 80 or
> more GB of junk. I see people on Reddit trying to figure out how
> to get a few GBs space out of a full disk. It's nuts.

I think you can still find small drives for sale.

I use Lexar NS100 256GB drives for scratch here, and I might have
four of those. If used for a single Windows OS, there's not much chance
of "overrunning" one of those.

At the 128GB size, you might be a bit more pressed for space. The thing is,
the SSDs can be relatively linear on price, so if the 256GB drive is $40 CDN,
the 128GB drive would be $20 CDN. I don't think they stock those.

My C: is set to 118GB, and I can see a 10GB backup that could be
removed right now. But I'm not sure going after the nickels and dimes
is going to make a dent in the content. I have a ChromeOS Flex installer
to remove from it. There would be on the order of 8GB of bloat that
is unexplained, but it could be coming from my Downloads folder.

My Downloads is 24.9GB and that will shrink when the 10GB of backups
are removed. My %temp% is 15MB :-) WinSxS is 12GB, but some of that
would be hardlinked to System32, and even if you deleted portions
of the WinSxS, the directory savings would be no more than 500MB or so,
on 12GB. Of course, at 12GB, that is 4GB of content which likely
does not belong there (older versions, used or not used ?).

I don't want to poke at that, or it could spend three hours
doing unnecessary compression of those materials. Which is the last
thing I want done.

   Paul

[toc] | [prev] | [next] | [standalone]

#182589

Newyana2 wrote:
> On 2/26/2025 4:15 PM, Ed Cryer wrote:
> 
>>>
>>>    Anybody having any insight on what is doing that cleaning?
>>>
>>> [1[ C:\Users\<user>\AppData\Local\Temp
>>
>> It's probably done by the Windows Disk-cleanup utility; and that is 
>> only run as and when needed by users, and requires a tick for 
>> Temporary files.
>>
> 
>    Not likely. I cleaned up a Win10 laptop just today with several GB
> of TEMP and other junk. It's a good idea to run disk cleanup
> manually.
> 
>   On XP/7 I use a script that just deletes all TEMP files from multiple
> folders and ignores errors, which are generated if a file is in use.
> There can be an app data user folder as well as c:\Windows\TEMP.
> 
>    The winsxs temp files never get cleaned as far as I know. That's
> why I invlcuded the command line for that above. It supposedly
> deletes things like outdated file versions where a newer version
> exists.
> 
>    Windows since Vista has been incredibly bloated and sloppy about
> these things, with winsxs, especially, growing out of control. People
> need to take charge themselves or they'll end up with 40, 60, 80 or
> more GB of junk. I see people on Reddit trying to figure out how
> to get a few GBs space out of a full disk. It's nuts.

I regularly empty my Temp file in users/ Appdata/ Local. I just go 
there, select all, and delete. One file won't delete; 
FXSAP|DebugLogFile, associated with Windows Fax.
I don't use Chrome, but Edge puts lots of rubbish in there, and even 
after a couple of days from empty it will build to 100MB. Why can't 
computer programmers clean up their mess? They're as bad as builders. I 
once complained to a builder about that, and he said "Oh, you mean the 
bits?"
(:-  Bits to him; a clean-up job for me!

You mention a script. Others have mentioned other scripts. I'd be 
interested in the best available.
To all; If you think you have the best, post here and I'll try them.

Ed

[toc] | [prev] | [next] | [standalone]

#182592

On 2/27/2025 6:15 AM, Ed Cryer wrote:

> I regularly empty my Temp file in users/ Appdata/ Local. I just go 
> there, select all, and delete. One file won't delete; 
> FXSAP|DebugLogFile, associated with Windows Fax.
> I don't use Chrome, but Edge puts lots of rubbish in there, and even 
> after a couple of days from empty it will build to 100MB. Why can't 
> computer programmers clean up their mess? They're as bad as builders. I 
> once complained to a builder about that, and he said "Oh, you mean the 
> bits?"
> (:-  Bits to him; a clean-up job for me!
> 

  He probably has a wife who picks up after him.
> You mention a script. Others have mentioned other scripts. I'd be 
> interested in the best available.
> To all; If you think you have the best, post here and I'll try them.
> 

  I wrote a script on XP because deleting by hand would often
get stopped when one file wouldn't delete. So it was easier to
write a VBScript that would keep going when it hit a file it
couldn't delete. There were also 3 TEMP folders. C:\,
C:\Windows and the appdata TEMP. On Win10 there's still
C:\Windows\TEMP. My Intel graphics is using it now.

   My script is nothing special. It just goes through deleting
what it can, gives me a report, then shows a message to run
Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
in order to clean anything unnecessary out of winsxs.

[toc] | [prev] | [next] | [standalone]

#182612

Newyana2 wrote:
> On 2/27/2025 6:15 AM, Ed Cryer wrote:
> 
>> I regularly empty my Temp file in users/ Appdata/ Local. I just go 
>> there, select all, and delete. One file won't delete; FXSAP| 
>> DebugLogFile, associated with Windows Fax.
>> I don't use Chrome, but Edge puts lots of rubbish in there, and even 
>> after a couple of days from empty it will build to 100MB. Why can't 
>> computer programmers clean up their mess? They're as bad as builders. 
>> I once complained to a builder about that, and he said "Oh, you mean 
>> the bits?"
>> (:-  Bits to him; a clean-up job for me!
>>
> 
>   He probably has a wife who picks up after him.
>> You mention a script. Others have mentioned other scripts. I'd be 
>> interested in the best available.
>> To all; If you think you have the best, post here and I'll try them.
>>
> 
>   I wrote a script on XP because deleting by hand would often
> get stopped when one file wouldn't delete. So it was easier to
> write a VBScript that would keep going when it hit a file it
> couldn't delete. There were also 3 TEMP folders. C:\,
> C:\Windows and the appdata TEMP. On Win10 there's still
> C:\Windows\TEMP. My Intel graphics is using it now.
> 
>    My script is nothing special. It just goes through deleting
> what it can, gives me a report, then shows a message to run
> Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
> in order to clean anything unnecessary out of winsxs.
> 
> 

That one folder is always the only one that is system-locked and 
undeletable. But it provides little hold-up, since WinExplorer tells me 
it can't delete it, gives me highlight, and when I hit ok it's the only 
one left; job finished.

I never get much debris in the other two folders. The C:\Windows Temp 
gets some, but something other than me deletes it occasionally.

Ed

[toc] | [prev] | [next] | [standalone]

#182616

On 2/27/2025 2:00 PM, Ed Cryer wrote:
> Newyana2 wrote:
>> On 2/27/2025 6:15 AM, Ed Cryer wrote:
>>
>>> I regularly empty my Temp file in users/ Appdata/ Local. I just go 
>>> there, select all, and delete. One file won't delete; FXSAP| 
>>> DebugLogFile, associated with Windows Fax.
>>> I don't use Chrome, but Edge puts lots of rubbish in there, and even 
>>> after a couple of days from empty it will build to 100MB. Why can't 
>>> computer programmers clean up their mess? They're as bad as builders. 
>>> I once complained to a builder about that, and he said "Oh, you mean 
>>> the bits?"
>>> (:-  Bits to him; a clean-up job for me!
>>>
>>
>>   He probably has a wife who picks up after him.
>>> You mention a script. Others have mentioned other scripts. I'd be 
>>> interested in the best available.
>>> To all; If you think you have the best, post here and I'll try them.
>>>
>>
>>   I wrote a script on XP because deleting by hand would often
>> get stopped when one file wouldn't delete. So it was easier to
>> write a VBScript that would keep going when it hit a file it
>> couldn't delete. There were also 3 TEMP folders. C:\,
>> C:\Windows and the appdata TEMP. On Win10 there's still
>> C:\Windows\TEMP. My Intel graphics is using it now.
>>
>>    My script is nothing special. It just goes through deleting
>> what it can, gives me a report, then shows a message to run
>> Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
>> in order to clean anything unnecessary out of winsxs.
>>
>>
> 
> That one folder is always the only one that is system-locked and 
> undeletable. But it provides little hold-up, since WinExplorer tells me 
> it can't delete it, gives me highlight, and when I hit ok it's the only 
> one left; job finished.
> 
> I never get much debris in the other two folders. The C:\Windows Temp 
> gets some, but something other than me deletes it occasionally.
> 

    I just had an interesting experience. My system somehow grew to
22.6 GB -- about 2 GB too big. I looked around and found that the
TEMP folder in winsxs is not emptied by any means. I thought
my DISM line cleaned it, but it turns out what that does is to delete
unneeded old versions of updates and components. In some cases
it can clean up a great deal, especially if you allow Windows Update.

   But nothing cleans TEMP. I looked online. How to delete
winsxs\temp\InFlight, which had grown to nearly 4 GB, and all the
files seemed to be dated 2/10. What did I do on 2/10? Beats me.
Is it safe to delete those files? I couldn't find any definitive answer.

   Finally I made a current disk image, rebooted, used my handy
utility to remove restrictions from all 12K files(!), and deleted InFlight.
No problems that I can see. Apparently there are some things that
get stuck there. What really strikes me is that so much documentation
is missing for Win10. It's 10 years old. I used to know prety much
everything on 98 and XP. On 10 I find endless folders with mysterious
names, containing files that are equally mysterious. And no one seems
to know what they are. So much crap.

[toc] | [prev] | [next] | [standalone]

#182618

Newyana2 wrote:
> On 2/27/2025 2:00 PM, Ed Cryer wrote:
>> Newyana2 wrote:
>>> On 2/27/2025 6:15 AM, Ed Cryer wrote:
>>>
>>>> I regularly empty my Temp file in users/ Appdata/ Local. I just go 
>>>> there, select all, and delete. One file won't delete; FXSAP| 
>>>> DebugLogFile, associated with Windows Fax.
>>>> I don't use Chrome, but Edge puts lots of rubbish in there, and even 
>>>> after a couple of days from empty it will build to 100MB. Why can't 
>>>> computer programmers clean up their mess? They're as bad as 
>>>> builders. I once complained to a builder about that, and he said 
>>>> "Oh, you mean the bits?"
>>>> (:-  Bits to him; a clean-up job for me!
>>>>
>>>
>>>   He probably has a wife who picks up after him.
>>>> You mention a script. Others have mentioned other scripts. I'd be 
>>>> interested in the best available.
>>>> To all; If you think you have the best, post here and I'll try them.
>>>>
>>>
>>>   I wrote a script on XP because deleting by hand would often
>>> get stopped when one file wouldn't delete. So it was easier to
>>> write a VBScript that would keep going when it hit a file it
>>> couldn't delete. There were also 3 TEMP folders. C:\,
>>> C:\Windows and the appdata TEMP. On Win10 there's still
>>> C:\Windows\TEMP. My Intel graphics is using it now.
>>>
>>>    My script is nothing special. It just goes through deleting
>>> what it can, gives me a report, then shows a message to run
>>> Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
>>> in order to clean anything unnecessary out of winsxs.
>>>
>>>
>>
>> That one folder is always the only one that is system-locked and 
>> undeletable. But it provides little hold-up, since WinExplorer tells 
>> me it can't delete it, gives me highlight, and when I hit ok it's the 
>> only one left; job finished.
>>
>> I never get much debris in the other two folders. The C:\Windows Temp 
>> gets some, but something other than me deletes it occasionally.
>>
> 
>     I just had an interesting experience. My system somehow grew to
> 22.6 GB -- about 2 GB too big. I looked around and found that the
> TEMP folder in winsxs is not emptied by any means. I thought
> my DISM line cleaned it, but it turns out what that does is to delete
> unneeded old versions of updates and components. In some cases
> it can clean up a great deal, especially if you allow Windows Update.
> 
>    But nothing cleans TEMP. I looked online. How to delete
> winsxs\temp\InFlight, which had grown to nearly 4 GB, and all the
> files seemed to be dated 2/10. What did I do on 2/10? Beats me.
> Is it safe to delete those files? I couldn't find any definitive answer.
> 
>    Finally I made a current disk image, rebooted, used my handy
> utility to remove restrictions from all 12K files(!), and deleted InFlight.
> No problems that I can see. Apparently there are some things that
> get stuck there. What really strikes me is that so much documentation
> is missing for Win10. It's 10 years old. I used to know prety much
> everything on 98 and XP. On 10 I find endless folders with mysterious
> names, containing files that are equally mysterious. And no one seems
> to know what they are. So much crap.
> 

My Win10 box of tricks is over 10 years old, but I stick with it. It has 
a 500GB SSD, 8GB RAM, CPU as old as Noah, and it still functions quickly 
enough and well enough for my moderate computing needs.
The SSD is littered with files of every description; many empty folders, 
lots of uninstall left-overs, and God knows what else. Just simply 
listing through the file types installed is sufficient proof of all the 
litter. Most of the ones listed ring no bell at all.

I don't know why I even bother emptying Appdata\ Temp occasionally. That 
holds just a fraction of all the gumph and gagga to be found.
The thing is, though, that the SSD is less than half full.
It's mere habit with the TEMP folder.
I hope I don't get some itch to tidy up properly. I'd probably be able 
to clear out several hundred GBs. But, while doing that, I might disturb 
something that might cost me hours of time to restore.
So then, quod non fractum est, noli tangere.

Ed

Ed

[toc] | [prev] | [next] | [standalone]

#182672

Newyana2 <newyana@invalid.nospam> wrote:
[...]

> 		   What really strikes me is that so much documentation
> is missing for Win10. It's 10 years old. I used to know prety much
> everything on 98 and XP. On 10 I find endless folders with mysterious
> names, containing files that are equally mysterious. And no one seems
> to know what they are. So much crap.

  FWIW, when I (re)search some Windows related issue in Google, quite
often useful answers are found in https://learn.microsoft.com/en-us/...
pages. So that seems to be the kind of Windows documentation you're
missing.

  I use Google to find the pages on Microsoft Learn site. I have not
tried (no need sofar) to browse/search the site itself.

  Hope this helps.

[toc] | [prev] | [next] | [standalone]

#182581

Frank Slootweg <this@ddress.is.invalid> wrote:

>   One thing I noted in my %TEMP% folder [1], is that, while there are
> quite a lot of files and folders which use quite some space (210 Files,
> 105 Folders, Size 312MB), they are not very old! The oldest (both files
> and folders) are of December 17, so a bit over two months old.
> 
>   So it seems the %TEMP% folder *is* being cleaned by some mechanism.
> 
>   Anybody having any insight on what is doing that cleaning?
> 
> [1[ C:\Users\<user>\AppData\Local\Temp

Windows has its own cleanup schedule.  Look in Task Scheduler under
Microsoft -> Windows for DiskCleanup.  That cleans when space is low.  I
thought there was another cleanup event, but don't remember it now.  Of
course, it's possible cleanmgr.exe was scheduled to run, but you had to
add that.

In the Start Menu, search on "storage sense".  Or, go to Settings ->
System -> Storage.  If that is enabled, it cleans up the drive(s).
There is a "Configure Storage Sense or run it now" link there.  Click on
it to see, if enabled, at what intervals it runs.

https://support.microsoft.com/en-us/windows/manage-drive-space-with-storage-sense-654f6ada-7bfc-45e5-966b-e24aded96ad5

[toc] | [prev] | [next] | [standalone]

#182593

VanguardLH <V@nguard.lh> wrote:
> Frank Slootweg <this@ddress.is.invalid> wrote:
> 
> >   One thing I noted in my %TEMP% folder [1], is that, while there are
> > quite a lot of files and folders which use quite some space (210 Files,
> > 105 Folders, Size 312MB), they are not very old! The oldest (both files
> > and folders) are of December 17, so a bit over two months old.
> > 
> >   So it seems the %TEMP% folder *is* being cleaned by some mechanism.
> > 
> >   Anybody having any insight on what is doing that cleaning?
> > 
> > [1[ C:\Users\<user>\AppData\Local\Temp
> 
> Windows has its own cleanup schedule.  Look in Task Scheduler under
> Microsoft -> Windows for DiskCleanup.  That cleans when space is low.  I
> thought there was another cleanup event, but don't remember it now.  Of
> course, it's possible cleanmgr.exe was scheduled to run, but you had to
> add that.
> 
> In the Start Menu, search on "storage sense".  Or, go to Settings ->
> System -> Storage.  If that is enabled, it cleans up the drive(s).
> There is a "Configure Storage Sense or run it now" link there.  Click on
> it to see, if enabled, at what intervals it runs.
> 
> https://support.microsoft.com/en-us/windows/manage-drive-space-with-storage-sense-654f6ada-7bfc-45e5-966b-e24aded96ad5

  Thanks for that! You hit the nail on the head!

[BTW, my system is Windows 11, but probably most, if not all, of this
also goes for Windows 10.]

  There's indeed a 'SilentCleanup' task in the DiskCleanup Task
Scheduler folder which runs 'cleanmgr.exe /autocleanstoragesense' and it
has run today at 09:03.

  The task is indeed triggered from outside the Task Scheduler, because
the 'Next Run Time' field is empty and there are no triggers on the
'Triggers' tab of the task.

  'Storage Sense' is Off, but on the Storage Sense page (in Settings),
there is this section:

"Cleanup of temporary files

 [V] Keep Windows running smootly by automatically cleaning up temporary
     system and app files"

  So 'Disk Clean-up' (cleanmgr.exe) only cleans temporary files, not any
of its other possible tasks, and it does this anyway, not just "when
disk space is running low" (I have 760GB free), so the 'Description:' of
the Task Scheduler task is a bit misleading.

  The 'Storage Sense' part (in Settings) says it "runs when disk space
is low", but, as mentioned, Storage Sense is off on my system and indeed
says "We have cleaned up 0 bytes in the past month.".

  Summary: This setting causes the %TEMP% folder to be cleaned
automatically:

Settings -> System -> Storage -> Storage Sense ->

"Cleanup of temporary files

 [V] Keep Windows running smootly by automatically cleaning up temporary
     system and app files"

  Thanks again, VanguardLH!

[toc] | [prev] | [next] | [standalone]

#182588

Frank Slootweg <this@ddress.is.invalid> writes:

>   So it seems the %TEMP% folder *is* being cleaned by some mechanism.
>
>   Anybody having any insight on what is doing that cleaning?

I think Windows comes with some cleanup scripts since Windows 7-ish and
they're executed periodically by the task scheduler. I remember some
journo whined about that, the scripts like to clean up stuff like
shortcuts to network drives on the desktop if said network drive doesn't
happen to be available when the script runs. Which isn't that uncommon
for a journalist's laptop or anyone else's for that matter.

Can't find anything with web search though, just a lot of stuff on how
to schedule your own tasks with it.

[toc] | [prev] | [next] | [standalone]

#182582

On Wed, 26 Feb 2025 19:29:02 +0100, "Carlos E.R."
<robin_listas@es.invalid> wrote:

>On 2025-02-26 18:53, Paul wrote:
>> The tools provided with the system, may not do all that good of a job.
>
>Somebody may have written a script to delete any file in that directory 
>that is older than the current boot date. Run that on every boot. 
>Alternatively, delete any thing older than 6 months, for instance.

I added a startup script about 3-4 years ago that I probably found here.
On Windows startup, it deletes the entire %temp% directory, then it
immediately creates it anew, now empty of course.

rd %temp% /s /q
md %temp%

I've never encountered any issues, so I'm thinking there's nothing in
there that needs to survive a reboot/restart.

[toc] | [prev] | [next] | [standalone]

#182591

On Wed, 26 Feb 2025 17:57:48 -0600, Char Jackson <none@none.invalid>
wrote:

>On Wed, 26 Feb 2025 19:29:02 +0100, "Carlos E.R."
><robin_listas@es.invalid> wrote:
>
>>On 2025-02-26 18:53, Paul wrote:
>>> The tools provided with the system, may not do all that good of a job.
>>
>>Somebody may have written a script to delete any file in that directory 
>>that is older than the current boot date. Run that on every boot. 
>>Alternatively, delete any thing older than 6 months, for instance.
>
>I added a startup script about 3-4 years ago that I probably found here.

 That sounds vaguely like a Mayana thing. 

>On Windows startup, it deletes the entire %temp% directory, then it
>immediately creates it anew, now empty of course.
>
>rd %temp% /s /q
>md %temp%

 Oooooohhhh, dangerous? Also shiny. Thank you. 

>
>I've never encountered any issues, 

 So, *not* dangerous? 

 It's not likely that deleting the %TEMP% would do much if any harm.
Windows would just remake it were you not to. 

>so I'm thinking there's nothing in
>there that needs to survive a reboot/restart.

 There's "KBnnnnnnn" things in there that are left over from "updates"
being installed. I had lots from 2013 onwards. I binned them all. I'm
no longer doing updates of my Win-7 OS so my WIndows won't miss them
overly much. 

 There were, in my %TEMP% *hundreds* of AppInstal* files from Opera's
browser installations. I binned those, too. Also dead VLC copies.
Damn, but Widows can be untidy. :) 

 There was a file called "~~PDTemp" that keeps appearing when I kill
it. I'm using "PowerDesk" as my replacement for "Windows Explorer" so
I think that's never going to vanish. :) 

                                                            J. 

[toc] | [prev] | [next] | [standalone]

#182583

On 2/26/2025 1:29 PM, Carlos E.R. wrote:
> On 2025-02-26 18:53, Paul wrote:
>> The tools provided with the system, may not do all that good of a job.
> 
> Somebody may have written a script to delete any file in that directory 
> that is older than the current boot date. Run that on every boot. 
> Alternatively, delete any thing older than 6 months, for instance.
> 
:: Limit C:\Users\Eric\AppData\Local\Temp Files and Folders
:: 
---------------------------------------------------------------------------------------------------------------------------------------- 

:: Remove files LAST ACCESSed OLDER than 30 Days
SET _SRC=C:\Users\xxxx\AppData\Local\Temp
FORFILES /P %_SRC% /S /C "CMD /C DEL /Q @path" /D -30  > NUL 2>&1
:: Remove empty folders
FOR /f "delims=" %%i in ('DIR %_SRC% /AD /S /B ^| SORT /R') DO RD "%%i" 
 > NUL 2>&1

:: Limit C:\Windows\Temp Files and Folders
:: 
---------------------------------------------------------------------------------------------------------------------------------------- 

:: Remove files LAST ACCESSed OLDER than 30 Days
SET _SRC=C:\Windows\Temp
FORFILES /P %_SRC% /S /C "CMD /C DEL /Q @path" /D -30  > NUL 2>&1
:: Remove empty folders
FOR /f "delims=" %%i in ('DIR %_SRC% /AD /S /B ^| SORT /R') DO RD "%%i" 
 > NUL 2>&1

[toc] | [prev] | [next] | [standalone]

Page 1 of 3  [1] 2 3  Next page →

Back to top | Article view | alt.comp.os.windows-10

csiph-web