New Steamapps "corrupt" folder

[Jakey]

There is a new folder in my Steam/Steamapps directory called "corrupt" with about 100 files in it that all look similar to this "380_380_1c3a9310503df53df087a4b9df4d1282bde7cf11_corrupt.chunk".
I've tried deleting all the files in there, verifying all my game files (in case it is game related), but not long after doing so they all come back again. Does anyone know what the "corrupt" folder in steamapps is for, or if there is a way to prevent these files from being created all the time?

[Jakey]

Here is my r/steam post asking the same question: https://www.reddit.com/r/Steam/comments/qz0qzq/new_steamapps_corrupt_folder_what_is_it/

[VicPariah]

Originally posted by jakey1995abc:

Here is my r/steam post asking the same question: https://www.reddit.com/r/Steam/comments/qz0qzq/new_steamapps_corrupt_folder_what_is_it/

Hey, were you ever able to find out what this was?

[Jakey]

Originally posted by V-Pariah:

Originally posted by jakey1995abc:

Here is my r/steam post asking the same question: https://www.reddit.com/r/Steam/comments/qz0qzq/new_steamapps_corrupt_folder_what_is_it/

Hey, were you ever able to find out what this was?

Nope :(

[Keebz]

Why is nobody else talking about this? I can't find anything on the web about what this folder is.

[Jakey]

Originally posted by Keebz:

Why is nobody else talking about this? I can't find anything on the web about what this folder is.

I know right! I don't have a clue how or why it keeps creating these files. It even started occurring on a fresh install of Windows with a fresh install of Steam after not that long, with no unexpected shutdowns, reboots, app crashes, etc... that could have caused it.

[Keebz]

Originally posted by jakey1995abc:

Originally posted by Keebz:

Why is nobody else talking about this? I can't find anything on the web about what this folder is.

I know right! I don't have a clue how or why it keeps creating these files. It even started occurring on a fresh install of Windows with a fresh install of Steam after not that long, with no unexpected shutdowns, reboots, app crashes, etc... that could have caused it.

So this is happening on Windows? For me it's happening on Steam Deck. Interesting. I thought maybe it was a corrupted shader cache, as the numbers at the start of each file coincide with a SteamID. For example, the 380 in your example is Half Life 2 Episode One. But if this happens on Windows too, then I have no idea.

[Balas]

I had the same problem and I solved it this way:

1. I ran the following command at the prompt as an administrator "chkdsk C:/f"
2. After restarting I ran another command at the prompt "sfc /scannow"
If "sfc /scannow" fails to repair corrupted files, try the following command "dism /Online /Cleanup-Image /RestoreHealth", restart your PC and run "sfc /scannow" again
3. After repairing the corrupted files, go to Steam --> settings --> downloads --> clear download data

I managed to solve it this way, if from the 3rd step it does not work, I believe that other methods available on the internet can solve it, the most important thing is to repair the corrupted files in Windows

Hope this helps

[AlfeoZeno]

Originally posted by Balas:

I had the same problem and I solved it this way:

1. I ran the following command at the prompt as an administrator "chkdsk C:/f"
2. After restarting I ran another command at the prompt "sfc /scannow"
If "sfc /scannow" fails to repair corrupted files, try the following command "dism /Online /Cleanup-Image /RestoreHealth", restart your PC and run "sfc /scannow" again
3. After repairing the corrupted files, go to Steam --> settings --> downloads --> clear download data

I managed to solve it this way, if from the 3rd step it does not work, I believe that other methods available on the internet can solve it, the most important thing is to repair the corrupted files in Windows

Hope this helps

That helps!!

[Phénomènes Mystiques]

Originally posted by Balas:

I had the same problem and I solved it this way:

1. I ran the following command at the prompt as an administrator "chkdsk C:/f"
2. After restarting I ran another command at the prompt "sfc /scannow"
If "sfc /scannow" fails to repair corrupted files, try the following command "dism /Online /Cleanup-Image /RestoreHealth", restart your PC and run "sfc /scannow" again
3. After repairing the corrupted files, go to Steam --> settings --> downloads --> clear download data

I managed to solve it this way, if from the 3rd step it does not work, I believe that other methods available on the internet can solve it, the most important thing is to repair the corrupted files in Windows

Hope this helps

This signals a corrupt Windows Update or System File...

[VicPariah]

Originally posted by Wynters:

Originally posted by Balas:

I had the same problem and I solved it this way:

1. I ran the following command at the prompt as an administrator "chkdsk C:/f"
2. After restarting I ran another command at the prompt "sfc /scannow"
If "sfc /scannow" fails to repair corrupted files, try the following command "dism /Online /Cleanup-Image /RestoreHealth", restart your PC and run "sfc /scannow" again
3. After repairing the corrupted files, go to Steam --> settings --> downloads --> clear download data

I managed to solve it this way, if from the 3rd step it does not work, I believe that other methods available on the internet can solve it, the most important thing is to repair the corrupted files in Windows

Hope this helps

This signals a corrupt Windows Update or System File...

I am thinking maybe a corrupted Windows service, perhaps?

[Smokey]

sorry to necro but I have this folder, on my steamdeck so I'm really at a loss with what to do. How do I even run the equivalent of chkdsk on linux 🤣

[Patola [Linux]]

Originally posted by Smokey:

sorry to necro but I have this folder, on my steamdeck so I'm really at a loss with what to do. How do I even run the equivalent of chkdsk on linux 🤣

The equivalent of chkdsk is fsck but it won't fix errors in mounted filesystems.

[Steven]

This thread was quite old before the recent post, so we're locking it to prevent confusion.