Skip to main content
You can configure WinFsp-MemFs-Extended to automatically create your RAM disk when you log into your Windows account. This is accomplished using the Windows Task Scheduler and the WinFsp launcher control utility.

​
Prerequisites

Before setting up autostart, ensure:
  • WinFsp is installed on your system
  • WinFsp-MemFs-Extended is properly installed
  • You have the WinFsp Launcher Service component installed (available during installation)

​
Using Task Scheduler

The recommended method for autostart is to create a scheduled task that launches the RAM disk on logon.
1

Open Task Scheduler

Press Win + R, type taskschd.msc, and press Enter to open the Windows Task Scheduler.
2

Create a new scheduled task

In Task Scheduler, click “Create Task” (not “Create Basic Task”) in the Actions pane on the right.
3

Configure general settings

In the “General” tab:
  • Enter a name for your task (e.g., “Launch RAM Disk”)
  • Select “Run whether user is logged on or not” (optional)
  • Check “Run with highest privileges”
  • Ensure “Configure for” matches your Windows version
  • Set the user account to your account
4

Add a logon trigger

Switch to the “Triggers” tab:
  • Click “New”
  • Set “Begin the task” to “At log on”
  • Select “Specific user” and choose your user account
  • Click “OK”
5

Configure the action

Switch to the “Actions” tab and click “New”:Program/Script:
"C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe"
Add arguments:
start Memefs ramdisk "" \\.\R:
Replace R: with your desired drive letter. The arguments are:
  • start - Command to start a service
  • Memefs - The WinFsp service name (from installer)
  • ramdisk - Instance name (can be customized)
  • "" - Empty UNC prefix (for disk mode)
  • \\.\R: - Mount point (drive letter)
Click “OK”.
6

Adjust power settings (optional)

Switch to the “Conditions” tab:
  • Uncheck “Start the task only if the computer is on AC power” if you want the RAM disk on battery-powered devices
  • Adjust other power-related settings as needed
7

Save and test

  • Click “OK” to save the scheduled task
  • Right-click the task and select “Run” to test it immediately
  • Check if the RAM disk appears in File Explorer
  • Log out and log back in to verify automatic startup

​
WinFsp launcher integration

During installation, you can enable the “WinFsp Launcher Service” component. This registers WinFsp-MemFs-Extended with the WinFsp launcher control system.

​
Registry configuration

The installer creates the following registry entries: Location: HKLM\SOFTWARE\WOW6432Node\WinFsp\Services\Memefs Keys:
  • Executable: Path to memefs-x64.exe
  • CommandLine: -i -F NTFS -l Ram -u %1 -m %2
  • Security: D:P(A;;RPWPLC;;;WD)
  • JobControl: 1
These settings allow the launcher to:
  • Use case-insensitive mode (-i)
  • Report as NTFS filesystem (-F NTFS)
  • Set volume label to “Ram” (-l Ram)
  • Accept UNC prefix and mount point parameters (%1 and %2)

​
Customizing launcher settings

You can modify the CommandLine value in the registry to change default behavior: 
-i -F NTFS -l "My RAM Disk" -s 2147483648 -u %1 -m %2
This would:
  • Add a custom volume label
  • Set a default size of 2GB
  • Maintain compatibility with launcher parameters

​
Launcher command syntax

The launchctl-x64.exe utility syntax: 
launchctl-x64.exe start <ServiceName> <InstanceName> <UNCPrefix> <MountPoint>

​
Examples

Mount to R: drive: 
launchctl-x64.exe start Memefs ramdisk "" \\.\R:
Mount to auto-selected drive letter: 
launchctl-x64.exe start Memefs ramdisk "" \\.\*
Network share mode: 
launchctl-x64.exe start Memefs ramdisk \\Server\\Share ""

​
Stopping the service

To stop a running RAM disk launched via launcher: 
launchctl-x64.exe stop Memefs ramdisk
Warning: Stopping the service will unmount the RAM disk and all data will be lost.

​
Troubleshooting

​
Task doesn’t run on logon

  • Verify the task is enabled in Task Scheduler
  • Check that “Run with highest privileges” is enabled
  • Review the task history for error messages
  • Ensure the WinFsp service is running

​
Drive letter already in use

  • Change the mount point in the task arguments
  • Use * to auto-select an available drive letter
  • Check for conflicting mapped network drives

​
Permission errors

  • Ensure the task runs with your user account
  • Verify “Run with highest privileges” is checked
  • Check that WinFsp is properly installed

​
Service fails to start

  • Verify the WinFsp Launcher Service component was installed
  • Check registry entries at HKLM\SOFTWARE\WOW6432Node\WinFsp\Services\Memefs
  • Review Windows Event Viewer for error details

Build docs developers (and LLMs) love

Get started for freeTalk to us