If you go into offline mode, some VST plugins won't work or scanning won't be possible, but FL Studio alone with its plugins will work. Don't go into offline mode, but use a firewall so that FL Studio only accesses the "Local Internet" through the firewall.

 

I blocked FL Studio on Windows Firewall, that is enough?

 

Do not completely block flstudio.exe, but only allow "local internet". <- for vst Scan and so on...

 

How?

 

Unless you have a good reason to say this, I have to disagree with it. Local network only is fine, but easy to screw up for someone. One of the main routes outbound to the internet used by plugins which are trying to call home is by being loaded into your DAW and using that process to do it. (not the only way). If you do not block the DAW, you may as well not bother at all. Disable "send information to help us etc" so that you do not end up with it looping attempts to get by the firewall. There is no reason why FL needs to look anywhere else besides your machine, on your local network unless you are using Audiogridder/VEP, etc.

Does it require constant connection to the internet somehow? If not, block it. Run it until it needs to reconnect again. Open a blank project with no plugins loaded, let it out past your firewall, and then once that little process is done, block it again.

Three different ways to handle it, just to give you an idea of how you could make this very easy and (ai) tailor-made just for FL. Or you could do it manually from your firewall settings.

Spoiler

1. Blocking a Program (Inbound & Outbound)

Run these in Command Prompt (Run as Administrator).
Replace the program path with the actual .exe location.


netsh advfirewall firewall add rule name="Block_App_Out" dir=out action=block program="C:\Path\To\App.exe" enable=yes

netsh advfirewall firewall add rule name="Block_App_In" dir=in action=block program="C:\Path\To\App.exe" enable=yes

This fully prevents the app from sending or receiving data.


2. Unblocking / Removing the Rules


netsh advfirewall firewall delete rule name="Block_App_Out"

netsh advfirewall firewall delete rule name="Block_App_In"


3. PowerShell Versions

Block program

Run in PowerShell as Administrator:


New-NetFirewallRule -DisplayName "Block_App_Out" -Direction Outbound -Program "C:\Path\To\App.exe" -Action Block

New-NetFirewallRule -DisplayName "Block_App_In" -Direction Inbound -Program "C:\Path\To\App.exe" -Action Block

Unblock / remove rules


Remove-NetFirewallRule -DisplayName "Block_App_Out"

Remove-NetFirewallRule -DisplayName "Block_App_In"


4. Optional: One-Click Toggle Batch Files

Block-App.bat


netsh advfirewall firewall add rule name="Block_App_Out" dir=out action=block program="%~1" enable=yes

netsh advfirewall firewall add rule name="Block_App_In" dir=in action=block program="%~1" enable=yes

pause

Run it like:


Block-App.bat "C:\Path\To\App.exe"

Unblock-App.bat


netsh advfirewall firewall delete rule name="Block_App_Out"

netsh advfirewall firewall delete rule name="Block_App_In"

pause

 

Last edited: Dec 15, 2025 at 6:31 AM

Yea, that makes more sense, VSTs are locally stored on machine right? They don't need internet to load on FL Studio i think.

 

there could be some really user specific reasons why you would even need to use the Local Allow rule like you mention; but for the most part you shouldn't even need it. Someone using the witches network block might even add to that subject. But what I am more certain of is that you would definitely want to block the DAW because it is like the barn door.

 

Would it be sufficient to use the normal windows firewall and block all outbound traffic for FL?

 

I don't know, maybe yes?

 

Probably, but I don’t trust the built-in firewall and the third-party ones are more convenient to use.

 

I didn’t know they acquired Melda, I knew about uvi but when did they acquire Melda?

 

I think it was almost a simultaneous purchase in 22, investors simply invested capital and bought all available audio companies at the moment. They all belong to the Waterland investment group now, and I feel a bit sad for the amazing UVI because we all know how investors can deal with a company if they are not satisfied

 

Oh, so they must’ve gotten both at the same time, I know uvi still seems standalone but I hadn’t known that Melda was owned by someone else till recently, maybe there’s just been signs like how you got Falcon libraries with FL Cloud and I missed the clues?

 

April 18, 2023
Image Line (Waterland investment group), the makers of FL Studio,
have acquired the French sample library and plugin developer UVI.

Jean-Bernard Celier, CEO of UVI said

“I am delighted that UVI is joining the Image-Line organisation. They have understood the development and transformation of UVI. We share the same values and have a similar corporate culture. I am confident that Image-Line will provide UVI with the expertise and resources necessary for our future growth. We would like to thank Drake Star for their support and expertise throughout the process.”

Constantin Koehncke, CEO at Image Line

“We are very pleased to welcome UVI, a company we have been following for a long time and whose products are cherished by music producers for their high quality and authenticity. We are excited to bring their instruments, effects and sound products to an even wider audience to further deliver on our mission to help music producers make and share their best music.”

 

No, there were only rumors. The only sign was that the entire catalog of Falcon add-ons started being sold at heavy discounts. They were probably trying to collect the last salaries directly, without going through the head office and the sweaty paws of the financiers.