Maybe it's an OS issue. I checked the data directory for WCG and the only files that aren't current seem to be applications and graphics. This machine is running W7 from several years ago.

Newer clients are supposed to do a better 'clean-up' job. When there is no more work of an application on the client, it removes the 'sticky' stuff such as the app [and then when intermittent it re-fetches everything if there's work again... most irritating if pertaining to CEP2, so a fix had to be put in place for that not to happen, to include for dddt2].

There's a persistency flag that's set and that needs flipping, so yes, WCG has to keep that set current [uplinger knows all about the subject]. When a new version of app arrives, the old is removed automatically [it is], which with beta is kind of like never to happen.

Deleting is pointless unless you edit the control files. Do project detach/add. The client will otherwise try refetching them again. It would though be wondrous if cfsw, dddt2, dsfl, hpf2 is still on the server [maybe they are to not get clients to constantly ask to re-supply?]. Stopped bothering me. Allocated a 20GB partition to BOINC. The whole of 1.34 is used.

Thanks for all the replies. It seems to be a function of the length of time the client has been running. Admittedly, it isn't a lot of space (1.2GB currently) but I see posts of people defragging disks which means they are constantly moving this stuff. This client used to run on Windows XP for many years, was stopped, data structure was copied to flash drive, XP upgraded to Win7, Boinc re-installed and data structure copied back. So, this client is about 8 years old. What this tells me is the project doesn't cleanup as sciences end and their "old" exe, image, beta files all remain. I looked at a newer installed client an those older files don't exist so they are currently not being sent by the server. I guess those of us with older, active (run lots of sciences) clients will accumulate this plaque until we clean it out. Since sciences don't come and go all that often, it isn't so much a problem with the production stuff but it's the beta stuff that is disconcerting to me. Every time a new beta is run, stuff will accumulate. Probably wouldn't hurt to reset this client anyway.

Removing the "sticky" tag results in the files being deleted at client startup. No scheduler request involved. The "exe" files for the old projects don't have the "sticky" tag so those will stay regardless. Anyone know what the values mean for the "status" tag?

I'm not deleting any files. The client is doing the deleting. I'm just editing the client_state.xml file (after making a copy of course) but to clean this mess up is a lot of editing. So far about 200 files have been deleted but underneath 1GB in size. I just remove the "sticky" tag and the client removes the rest of the XML that describes that file... I'm just experimenting while waiting for the final few WUs to complete. I just hate to think the only solution is to detach/add as that doesn't fix anything it only masks the real problem but I've been here long enough to know very few things really get fixed.....