Downloads of v 4.7.0:


Last Update:

12 Nov 2019

Package Maintainer(s):

Software Author(s):

  • MehediH


tweeten twitter tweetdeck social facebook

Tweeten (Install)



Downloads of v 4.7.0:



Software Author(s):

  • MehediH

Tweeten (Install)

Some Checks Have Failed or Are Not Yet Complete

1 Test Failing and 1 Passing Test

Validation Testing Failed

Verification Testing Passed


This package was rejected on 17 Dec 2019. The reviewer chocolatey-ops has listed the following reason(s):

bc3tech (maintainer) on 12 Nov 2019 20:37:55 +00:00:

User 'bc3tech' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Nov 2019 21:11:20 +00:00:

tweeten has failed automated validation.


Requirements represent the minimum quality of a package that is acceptable. When a package version has failed requirements, the package version requires fixing and/or response by the maintainer. Provided a Requirement has flagged correctly, it must be fixed before the package version can be approved. The exact same version should be uploaded during moderation review.

  • Nuspec file contains templated values which should be removed. More...

Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.

  • The licenseUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...

chocolatey-ops (reviewer) on 12 Nov 2019 21:37:56 +00:00:

tweeten has passed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 02 Dec 2019 21:41:23 +00:00:

We've found tweeten v4.7.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.

Take action:

  • Log in to the site and respond to the review comments.
  • Resubmit fixes for this version.
  • If the package version is failing automated checks, you can self-reject the package.

If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.

Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.

chocolatey-ops (reviewer) on 17 Dec 2019 21:45:33 +00:00:

Unfortunately there has not been progress to move tweeten v4.7.0 towards an approved status within 15 days after the last review message, so we need to close (reject) the package version at this time. If you want to pick this version up and move it towards approval in the future, use the contact site admins link on the package page and we can move it back into a submitted status so you can submit updates.

Status Change - Changed status of package from 'submitted' to 'rejected'.


Tweeten is a TweetDeck client built for those who get real work done. For those who are on Twitter 24/7. For those who simply want more. For those who live for the dank memes. For those who want a better TweetDeck.

$ErrorActionPreference = 'Stop';

$packageName= 'tweeten'
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = ''

$packageArgs = @{
  packageName   = $packageName
  unzipLocation = $toolsDir
  fileType      = 'EXE'
  url           = $url

  silentArgs    = '/S'
  validExitCodes= @(0, 3010, 1641)

  softwareName  = 'Tweeten*'
  checksum      = 'FCABF2ACBF5F306CE49AB91D130B6219E28E1C858A899C2C01073D8DB43B87D4'
  checksumType  = 'sha256'

New-Item "$($toolsDir)\TweetenSetup.exe.ignore" -type file -force | Out-Null

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName   = 'tweeten'
$softwareName  = 'Tweeten*'
$installerType = 'EXE'

$silentArgs = '/currentuser /S'
$validExitCodes = @(0)

$uninstalled = $false
$local_key     = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key   = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

[array]$key = Get-ItemProperty -Path @($machine_key6432,$machine_key, $local_key) `
                        -ErrorAction SilentlyContinue `
         | ? { $_.DisplayName -like "$softwareName" }

if ($key.Count -eq 1) {
  $key | % { 
    $uninstallString = "$($_.UninstallString)" 
    $file = $uninstallString.Substring(0, $uninstallString.indexOf('/current')).Replace('"', '')

    if ($installerType -eq 'MSI') {
      $silentArgs = "$($_.PSChildName) $silentArgs"

      $file = ''

    Uninstall-ChocolateyPackage -PackageName $packageName `
                                -FileType $installerType `
                                -SilentArgs "$silentArgs" `
                                -ValidExitCodes $validExitCodes `
                                -File $file
} elseif ($key.Count -eq 0) {
  Write-Warning "$packageName has already been uninstalled by other means."
} elseif ($key.Count -gt 1) {
  Write-Warning "$key.Count matches found!"
  Write-Warning "To prevent accidental data loss, no programs will be uninstalled."
  Write-Warning "Please alert package maintainer the following keys were matched:"
  $key | % {Write-Warning "- $_.DisplayName"}

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.

Version Downloads Last Updated Status
Tweeten (Install) 3.0.1-beta 291 Saturday, June 18, 2016 Exempted
Tweeten (Install) 2.0.3-beta 222 Tuesday, May 24, 2016 Exempted
Tweeten (Install) 2.0.1-beta 263 Monday, May 23, 2016 Exempted
Tweeten (Install) 2.0-beta 191 Monday, May 9, 2016 Exempted
Tweeten (Install) 1.9.1-beta 198 Tuesday, April 26, 2016 Exempted
Tweeten (Install) 1.8-beta2 248 Thursday, April 14, 2016 Exempted
Tweeten (Install) 1.8-beta 238 Thursday, April 14, 2016 Exempted

This package has no dependencies.

Discussion for the Tweeten (Install) Package

Ground Rules:

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