Downloads of v 4.73:


Last Update:

02 Jun 2018

Package Maintainer(s):

Software Author(s):

  • Flux Software LLC


f.lux flux lighting monitor color admin notsilent

f.lux (Portable)

This is not the latest version of f.lux (Portable) available.

  • 1
  • 2
  • 3

4.73 | Updated: 02 Jun 2018



Downloads of v 4.73:



Software Author(s):

  • Flux Software LLC

  • 1
  • 2
  • 3
f.lux (Portable) 4.73

This is not the latest version of f.lux (Portable) available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


Deployment Method: Individual Install, Upgrade, & Uninstall

To install f.lux (Portable), run the following command from the command line or from PowerShell:


To upgrade f.lux (Portable), run the following command from the command line or from PowerShell:


To uninstall f.lux (Portable), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade f.lux.portable -y --source="'INTERNAL REPO URL'" --version="'4.73'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade f.lux.portable -y --source="'INTERNAL REPO URL'" --version="'4.73'" 

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install f.lux.portable
    name: f.lux.portable
    version: '4.73'
    state: present

See docs at

chocolatey_package 'f.lux.portable' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '4.73'

See docs at

cChocoPackageInstaller f.lux.portable
    Name     = "f.lux.portable"
    Version  = "4.73"
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'f.lux.portable':
  ensure   => '4.73',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package was approved as a trusted package on 02 Jun 2018.


Ever notice how people texting at night have that eerie blue glow?

Or wake up ready to write down the Next Great Idea, and get blinded by your computer screen?

During the day, computer screens look good—they're designed to look like the sun. But, at 9PM, 10PM, or 3AM, you probably shouldn't be looking at the sun.

f.lux fixes this: it makes the color of your computer's display adapt to the time of day, warm at night and like sunlight during the day.

It's even possible that you're staying up too late because of your computer. You could use f.lux because it makes you sleep better, or you could just use it just because it makes your computer look better.

f.lux makes your computer screen look like the room you're in, all the time. When the sun sets, it makes your computer look like your indoor lights. In the morning, it makes things look like sunlight again.

Tell f.lux what kind of lighting you have, and where you live. Then forget about it. f.lux will do the rest, automatically.

You can pass the following parameters:

  • /noautostart - By default a shortcut to f.lux will be created in your Startup folder so that it starts with Windows. Use this parameter to stop this behaviour.


-params '"/noautostart"'

NOTE: This is the portable version of f.lux and installs in the Chocolatey tools folder - use this version if you want f.lux to be available to everybody on your system.

NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.

$ErrorActionPreference = 'Stop'

Write-Verbose "Stopping the 'flux' process if it is running."
Get-Process -Name 'flux' -ErrorAction SilentlyContinue | Stop-Process

Start-Sleep -Milliseconds 500
$ErrorActionPreference = 'Stop'

$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
    packageName    = $env:ChocolateyPackageName
    url            = ''
    checksum       = 'D8115FDC53BD65B451E067BB90F156801AA97F82153F3A4FC6BF6F23602EC023'
    checksumType   = 'SHA256'
    unzipLocation  = $toolsdir

# Some of this was taken from
Install-ChocolateyZipPackage @packageArgs

# Start menu shortcuts
$progsFolder = [Environment]::GetFolderPath('Programs')
If ( Test-ProcessAdminRights ) {
    $progsFolder = [Environment]::GetFolderPath('CommonPrograms') 

Install-ChocolateyShortcut -shortcutFilePath (Join-Path -Path $progsFolder -ChildPath 'f.lux.lnk') `
    -targetPath "$($env:ChocolateyInstall)\lib\$packageName\tools\flux.exe" `
    -WorkingDirectory "$($env:ChocolateyInstall)\lib\$packageName\tools\runtime"

# only create the shortcut in startup if the /noautostart parameter has not been passed
$arguments = Get-PackageParameters -Parameter $env:ChocolateyPackageParameters
if (-not $arguments.ContainsKey("noautostart")) {
    Write-Verbose "Setting to autostart with Windows."
    $params = @{
        ShortcutFilePath = Join-Path -Path $progsFolder -ChildPath 'Startup\f.lux.lnk'
        TargetPath       = "$($env:ChocolateyInstall)\lib\$packageName\tools\flux.exe"
        WorkingDirectory = "$($env:ChocolateyInstall)\lib\$packageName\tools\runtime"
        Arguments        = '/noshow'

    Install-ChocolateyShortcut @params
$ErrorActionPreference = 'Stop'

[Environment]::GetFolderPath('Programs'), [Environment]::GetFolderPath('CommonPrograms') | ForEach-Object {
    Remove-Item -Path (Join-Path -Path $_ -ChildPath 'f.lux.lnk') -ErrorAction SilentlyContinue
    Remove-Item -Path (Join-Path -Path $_ -ChildPath '\Startup\f.lux.lnk') -ErrorAction SilentlyContinue

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
f.lux (Portable) 4.119 211 Monday, February 8, 2021 Approved
f.lux (Portable) 4.118 310 Wednesday, June 24, 2020 Approved
f.lux (Portable) 4.111 519 Friday, August 30, 2019 Approved
f.lux (Portable) 4.110 112 Friday, August 30, 2019 Approved
f.lux (Portable) 4.108 122 Saturday, August 17, 2019 Approved
f.lux (Portable) 4.104 249 Wednesday, May 8, 2019 Approved
f.lux (Portable) 4.103 126 Friday, May 3, 2019 Approved
f.lux (Portable) 4.100 188 Thursday, April 4, 2019 Approved
f.lux (Portable) 4.99 127 Thursday, March 28, 2019 Approved

Discussion for the f.lux (Portable) Package

Ground Rules:

  • This discussion is only about f.lux (Portable) and the f.lux (Portable) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or f.lux (Portable), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus