Steam - Error : Manifest_DebugFiles_Win64.txt

[Lukapaka]

An error occurred while updating PLAYERUNKNOWN'S BATTLEGROUNDS (disk write error) :
Z:\SteamLibrary\steamapps\downloading\578080\Manifest_DebugFiles_Win64.txt

I first got the error when I attempted to install the previous patch for PUBG on September 21st. At the time, I had the game installed on my Z: (a HDD) while Steam itself is stored on my C: (a SDD). I located the file found myself entirely unable to delete, open, or otherwise do anything at all with this file, and would be alerted that "The process cannot access the file because it is being used by another process." In the end, I uninstalled the game and reinstalled PUBG to my C:. Lucky for me, that fixed the issue... until last night, when the game required a new update to be installed.

Now, the same issue is happening, exactly the same. I attempt to update the game (which is now on my C:) and receive the error exactly as before, file path and all.

I have followed all the steps in the "See the Steam support site for more information" page, and am at a complete loss. Searching for this on google and Steam forums had absolutely no results, and I'm really hoping someone out there has an answer for me.


I should mention, I did install Reshade and applied it to PUBG on August 12th, while it was still installed on my Z:

Help please!! I'd really like to not reinstall for every patch that comes out...

[Lukapaka]

D: I'm very sad this is happening, and not a single other soul on the collective internet seems to have had this happen to them, or have any idea what is going on...

[Lukapaka]

This file is absolutely the most stubborn file on the face of the earth. I've tried multiple Unlocker tools to delete it, I've tried booting in Safe Mode to delete it. I've tried locating what process is using it with some pretty cool software and ending that process before deleting it... all of it no luck. Overall, I think my drive is partially corrupt.

In any case, I was able to figure out a workaround to my problem and thought I'd share it here.
I cut and pasted the entire steamapps folder to the main drive and into a folder call Steam Backup. This successfully moved the suspect file out of the directory my Steam Library is located on that drive. For good measure, I completely deleted the Steam Library and recreated it via Steam Browser and am now installing a new game to it to rebuild all the folder structures. As far as data files go, I didn't have much saved on that drive anyway, so I went ahead and deleted everything in the backup file (except for the suspect file, which refused to be deleted). I renamed Steam Backup to "Locked File" and plan to just ignore it until I get a new HDD or second SDD to replace the drive with entirely.

Next PUBG update, I will see if this work around is successful and let you all know.

[$cary]

thanks

[Lukapaka]

Well PUBG had a ~1GB update, and it just completed without a hitch! To reiterate, the fix for me was to move the parent folder of the evil file and rename it. I removed the folder as a Content Library with Steam and created a new one on the drive.

I still have the file on my computer, buried in a folder name "Locked File" and I suspect it will remain there until I replace the drive.

I hope this helps somebody else someday, because it was very frustrating for me not finding any info out there on this issue.