os error 32 when trying to check in files revision control

Summary

edit: fixed it by right click on project name file and save/resave all. am getting this error in uefn when i try to check in files for revision control, can anyone help? tried verifying files for uefn, deleting some verse i added recently and some other stuff nothing seems to fix

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Unreal Revision Control

Steps to Reproduce

check in changes and and it just crashes it while loading and shows error

Expected Result

its supposed to check in changes for rev control

Observed Result

i get error in message log when i check in changes

Platform(s)

uefn windows 11

Upload an image

image1241241.png

It means revision control cannot write to those files because some other process is using them.

Do you have multiple editors open?

Did you try restarting your machine?

1 Like

hi @vex407 .

Please check your PC disk for errors as this is a known problem

open the Windows Command Line as ā€œRun as Administratorā€

C:> CHKDSK C: /SCAN REM Online check disk

C:> CHKDSK C: /F REM RESTART PC FOR FULL DISK CHECK/FIX

I got that error message (32) for the first time last week and also today (more details below) after I wanted to delete HLODs in one of my projects:

LogWorldPartitionEditor: Error: #### COMMANDLET OUTPUT >> [2026.02.25-07.45.05:271][ 0]LogIas: Error: Failed to open ā€˜C:/Users/Gamer/AppData/Local/UnrealEditorFortnite/Saved/PersistentDownloadDir/iaseditor/ias.cache.0.jrn’ for FDiskJournal (Failed to open file ā€˜C:/Users/Gamer/AppData/Local/UnrealEditorFortnite/Saved/PersistentDownloadDir/iaseditor/ias.cache.0.jrn’ for writing [The process cannot access the file because it is being used by another process. (32)])

Since I got it for the first time, it was impossible to delete or generate HLODs in that project, because every time it ended with that error (with more error lines after it).

The only solution that I figured out was to delete all files for that project from my local storage, delete all files from the folder ā€œUnrealEditorFortniteā€ (this might not have been necessary) and then sync the latest version from the server that I checked in via URC. Then I generated new HLODs, which worked, but I was not able to delete them or generate new HLODs in that project anymore again. So I hunted down what specific actor could be causing this and I found it – it was 1 prop that was only in 1 location without any other instances, so I deleted it after I synced last version from the server again and it started to work (generate + delete HLODs). It was weird, because I had that prop in the map in the same location for a very long time and I generated and deleted HLODs many times, always without issues (and I haven’t touched that actor in a long time either).

And today after I checked in few newer versions via URC with many changes I tried to generate HLODs again to see if it will be still OK. I did it once, it was OK (generate + delete afterwards), but when I tried to do it for the second time, that error ā€œ32ā€ appeared again, so I was in the same situation as before.

So this time I went further and I did following:
– deleted all local files of that specific project
– deleted everything in \AppData\Local\UnrealEditorFortnite
– reinstalled UEFN
– reinstalled Fortnite
– disconnected my PC from OneDrive, so it can’t sync anything anymore

But I have installation of UEFN + all UEFN projects on another drive that was never synced via OneDrive, I also always disabled syncing to OneDrive before I opened UEFN just to be sure, and that file ias.cache.0.jrn is in a folder that was never synced via OneDrive, so it shouldn’t interfere with anything regarding UEFN. This started happening last week while I started working in UEFN 2 years ago on this PC (without changes to HW or SW, but who knows what Windows 11 does over time).

I just finished these newest changes last hour and I tried to generate and delete HLODs in that project (after deleting local files with HLODs and syncing from server without HLODs again) two times and it worked without issues (so 4 processes in total that could fail). Which means - so far so good.

BTW: I just did CHKDSK /Scan for both drives (where I have OS and where I have UEFN project files) and for both drives it ended with no problems and with 0 KB in bad sectors.

resave all files it worked for me

1 Like

I didn’t think of that :-). I’ll try it next time it happens again, thanks for the tip.

1 Like