Downloads of v


Last Update:

13 Feb 2019

Package Maintainer(s):

Software Author(s):

  • OTC S.A.


winflector remote application execution server rdp

Winflector (Install)

  • 1
  • 2
  • 3 | Updated: 13 Feb 2019



Downloads of v



Software Author(s):

  • OTC S.A.

  • 1
  • 2
  • 3
Winflector (Install)

  • 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

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Winflector (Install), run the following command from the command line or from PowerShell:


To upgrade Winflector (Install), run the following command from the command line or from PowerShell:


To uninstall Winflector (Install), 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 winflector -y --source="'INTERNAL REPO URL'" [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 winflector -y --source="'INTERNAL REPO URL'" 

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

Exit $exitCode

- name: Install winflector
    name: winflector
    version: ''
    state: present

See docs at

chocolatey_package 'winflector' do
  action    :install
  source   'INTERNAL REPO URL'
  version  ''

See docs at

cChocoPackageInstaller winflector
    Name     = "winflector"
    Version  = ""
    Source   = "INTERNAL REPO URL"

Requires cChoco DSC Resource. See docs at

package { 'winflector':
  ensure   => '',
  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 was approved by moderator gep13 on 14 Feb 2019.


To use choco:// protocol URLs, install (unofficial) choco:// Protocol support

Screenshot of Winflector

Winflector is innovative, secure and easy to use software, which allows effective sharing and remote execution of choosen applications through local and wide area networks. Its basic features include:

  • low costs: applications executed remotely over a network
  • works over LAN, Internet, as well as dedicated connection, also at low throughput
  • application is executed on a main server, while a remote user accesses only its windows
  • the application server administrator decides which program(s) to share

Winflector allows sharing of any Windows application, which can be executed by remote users without any modification of the application code, preserving its original appearance and functionality.

Thanks to Winflector server, the applications are executed only on the central machine, while the remote users, using a lightweight client supporting Linux, Windows, Android and HTML5 browser access them the same way they would do locally. Winflector does not use Remote Desktop Services (earlier Windows Terminal Services), RemoteApp or Citrix products (XenApp).

Winflector Console is a special Winflector version designed exclusively for 32-bit text applications executed in the Windows console environment. The Winflector Console is the optimal, simple and low-cost solution for those who plan on using console applications only.

Remote desktop - is it the best solution?

A business application user needs to access applications and their functionality. In this case it is preferable to use a Winflector server, which enables the Windows application to be accessed as if they were locally displayed on the user's desktop. This way, a middle layer of remote desktop is eliminated, along with its increased bandwith usage and heavy interface, which makes it harder to use the actual application and increases the server load. Another advantage of this solution is limiting user access only to application functionality, hence increasing the server security.
Remote desktop is a good solution when one wishes to remotely administrate the computer. In this case, it is efficient to use VNC software or single-user Terminal Services, which is included in the operating system.

This is a fully functional version of Winflector software for two concurrent workstations for free.

Winflector Client


Click here to Patreon-ize the package maintainer.

$ErrorActionPreference = 'Stop'
$packageName    = 'winflector'
$softwareName   = 'Winflector*'
$installerType  = 'EXE'
$toolsDir       = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url            = '' 
$checksum       = 'B1BD04CEE4670BB70948622BDE467DFC1D51FDBFE89D0BA9C5E501870055C293'
$validExitCodes = @(0, 3010, 1641)
$ahkExe         = 'AutoHotKey'
$ahkFile        = "$toolsDir\WinflectorInstall.ahk"

Start-Process $ahkExe $ahkFile

$packageArgs = @{
  packageName   = $packageName
  fileType      = $installerType
  url           = $url
  validExitCodes= $validExitCodes
  silentArgs    = $silentArgs
  softwareName  = $softwareName
  checksum      = $checksum
  checksumType  = 'sha256' 

Install-ChocolateyPackage @packageArgs  
SendMode Input  ; Recommended for new scripts due to its superior speed and reliability.
SetWorkingDir %A_ScriptDir%  ; Ensures a consistent starting directory.
;BlockInput On 
WinWaitActive, Setup,Would you like to enable Winflector server in Windows Firewall?, 60 
Send !y

WinWaitActive,Windows Security,, 30
Send !i
WinWaitActive, Setup,Winflector printer driver has not been installed properly, 10
Send {Enter}
WinWaitActive, Setup - Winflector,, 30
Send !n
Send !a
Send !n
Send !n
Send !n
Send !n
Send !i
;BlockInput Off

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
Winflector (Install) 32174 Friday, July 20, 2018 Approved
Winflector (Install) 1995 Friday, June 1, 2018 Approved
Winflector (Install) 1875 Saturday, April 21, 2018 Approved
Winflector (Install) 4666 Wednesday, June 7, 2017 Approved
Winflector (Install) 1062 Sunday, April 16, 2017 Approved
Winflector (Install) 452 Tuesday, February 14, 2017 Approved
Winflector (Install) 384 Tuesday, January 10, 2017 Approved
Winflector (Install) 377 Saturday, November 19, 2016 Approved
Discussion for the Winflector (Install) Package

Ground Rules:

  • This discussion is only about Winflector (Install) and the Winflector (Install) 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 Winflector (Install), 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