Error 0x801F0005 when using source folder option

5 posts

Mkn
14 Oct

I was trying to reduce the impact of the heavy writing of the classic Outlook logging files from "%appdata%\Local\Temp\Outlook Logging" to RAM FS using the source folder option; however, I received this error:

could not mount the volume
transport error (error 2149515269)

A quick check for my own interest shows this 0x801F0005 to be ERROR_FLT_INVALID_NAME_REQUEST. I've checked using Proc Explorer that no processes were using the folder. I can delete the folder and re-create it, but still get the error. I then tried other folders on my C: drive with the same result, but all my other drive letters work fine with the source folder option.

Any thoughts?

Andrew SoftPerfect
14 Oct

That error comes from a file system filter on C: (antivirus, backup, security software) refusing the operation, not from RAM FS itself. We can't reproduce it on a stock Windows system: your exact Outlook Logging path and a folder in the root of C: both mount fine with Defender running.

If you'd like us to look into it, please run this in an administrator Command Prompt and post the output:

fltmc instances

Otherwise, a simpler way is to redirect TEMP and TMP to a RAM FS volume in Tools → Set Windows Temporary Folder. Outlook Logging lives in your Temp folder, so it moves along with every other application's temporary files, not just Outlook's. Add Temp to the volume's Create Folders list so it exists from boot, then sign out and back in.

Mkn
14 Oct

Sadly I cannot use RAM FS for the whole Temp folder as some of the (poorly written) software I use creates many GB of temp files there (50GB+) on every run.

Output of fltmc instances attached.

The C, D, E, F and H partitions are all physical SSDs, S is RAM Disk, and T is RAM FS.

Andrew SoftPerfect
15 Oct

Thanks for the fltmc output, it was exactly what we needed. It pointed straight at the OneDrive cloud files filter (CldFlt) on C:, so we could reproduce the error quickly and trace it to how RAM FS renamed the source folder, which that filter refuses. It affects any PC with OneDrive, so your report helped a lot of people.

The fix is in this snapshot build. Please install it over, reboot and let me know how it goes.

Alternatively, there are two other options:

1. Move your whole TEMP/TMP to RAM FS except for those poorly written apps. Set TEMP and TMP to RAM FS in Tools → Set Windows Temporary Folder, and start each of those apps from a batch file that points it back to the original folder:

@echo off
set TEMP=%LOCALAPPDATA%\Temp
set TMP=%LOCALAPPDATA%\Temp
start "" "C:\Path\To\Program.exe"

2. Link just the Outlook folder to RAM FS. Close Outlook, delete the Outlook Logging folder, and run this in a normal Command Prompt:

mklink /J "%LOCALAPPDATA%\Temp\Outlook Logging" "T:\Outlook Logging"

Then add Outlook Logging to T:'s Create Folders list so it exists after every restart.

Mkn
15 Oct

Thanks for the fast turnaround, it does indeed work now!

Regarding the other options, I do already do the opposite of pointing a couple of those apps with excessive TEMP/TMP use to another hardly used SSD using a similar technique to your first option but all done in the shortcut. It just gets messy either with the inclusion or exclusion TEMP approach and updates for new versions as it's a dev PC with lots installed. I was mainly experimenting with RAM FS and tried the Outlook logging folder (same issue with classic and new sadly) as etl log files compress well.

Thanks again.

Reply
Shown with your post. Sign in to keep the same name every time.
(optional, never shown)
Only needed if you want notifications about replies.
Drag files here, paste a screenshot, or . Images up to 10 MB. Text, log and zip files up to 2 MB. Up to 5 files per post.
You can edit your post until someone replies.