Installing on Windows
- Windows XP or later, up to and including Windows 10
- Java, which is bundled with the Freenet installer
- Free CPU, memory and network resources (Freenet will automatically allocate these depending on the amounts available. You can change these values after installation)
Use the latest installer
We recommend always installing Freenet on Windows by using the latest available Windows installer from the official Freenet website. The Freenet Windows Installer is updated every time a new version of Freenet is released, which might happen as often as several times per week.
The Freenet Windows Installer should be very easy to use. After making sure you have a recent version of Java installed, it will display a single installation screen with various options. After clicking "Install", everything should be handled automatically.
There is also a short video tutorial on how to install Freenet on Windows.
False Kaspersky antivirus detection
Kaspersky falsely detects the installer as a generic P2P virus. We are working on resolving this. It is unfortunately a common false positive of Autohotkey applications.
Download/upload queue database corrupted!
When running Kaspersky on Windows 7, you may receive a warning similar to:
Your node failed to load the database (node.db4o) which we store persistent downloads and uploads in. This is usually caused by data corruption on disk due to e.g. power failure. The files involved are C:\Program Files (x86)\Freenet\persistent-temp-[darknet port]\ and C:\Program Files (x86)\Freenet\node.db4o. Please shutdown your Freenet node, and either restore them from a backup or delete them. Also check whether you are out of disk space. This message can also occasionally happen while Freenet is shutting down.
Kaspersky Anti-Virus 2010 (v9.x) and 2011 (v11.x) on Windows 7 are known to cause issues with the node.db4o file. Adding the Freenet directory to the exclusion zone does not seem to be effective. Temporarily suspending protection during node shutdown/startup seems to allow normal operation, but remember to re-enable it as soon as your node is up and running again. This issue may occur on other versions of windows as well.
Service did not respond to signal
This is a long-standing bug with the Windows installer. We have a new installer that may fix the problem. You can get it here. If it works, please let us know! Note that this is an alpha test, and may be buggy, e.g. it currently has no update script, although the built-in auto-update should work (it can be slow though).
The installer and tray manager might fail to start the service with a
did not respond to signal error message. If you get this error, please try some of the following things:
- Check the
wrapper.logfile. You can find it by right-clicking the tray icon. (You might also have another one located inside the "bin" folder of your installation directory - check that one as well.)
- If it only has a single line (saying that the service has been installed), check whether the LocalService user account has write permissions to the installation folder. You can check this by right-clicking and selecting "Properties" on the installation folder.
- Check the Windows event viewer for any Freenet service errors.
- Try running the node without starting the service. You can do this by opening a command promt and executing
"C:\Program Files (x86)\Freenet\bin\wrapper-windows-x86-32.exe" -c "C:\Program Files (x86)\Freenet\wrapper.conf"(correct the path if Freenet is installed elsewhere)
Freenet has beta support for 64-bit Java on 64-bit Windows, which should be included in new installations soon.
You can opt to update an existing installation using the beta version of the tray application, which is available here.