Downloads:
2,472,884
Downloads of v 1.3.4686.20160420:
5,248
Last Update:
20 Apr 2016
Package Maintainer(s):
Software Author(s):
- David Carpenter wrote Everything
- IntelliTect created the Chocolatey Package
Tags:
everything file search admin- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Everything (Install)
This is not the latest version of Everything (Install) available.
- 1
- 2
- 3
1.3.4686.20160420 | Updated: 20 Apr 2016
- Software Specific:
- Software Site
- Software License
- Software Docs
- Software Mailing List
- Software Issues
- Package Specific:
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
2,472,884
Downloads of v 1.3.4686.20160420:
5,248
Maintainer(s):
Software Author(s):
- David Carpenter wrote Everything
- IntelliTect created the Chocolatey Package
Everything (Install) 1.3.4686.20160420
This is not the latest version of Everything (Install) available.
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by David Carpenter wrote Everything, IntelliTect created the Chocolatey Package. The inclusion of David Carpenter wrote Everything, IntelliTect created the Chocolatey Package trademark(s), if any, upon this webpage is solely to identify David Carpenter wrote Everything, IntelliTect created the Chocolatey Package goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Everything (Install), run the following command from the command line or from PowerShell:
To upgrade Everything (Install), run the following command from the command line or from PowerShell:
To uninstall Everything (Install), run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
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
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
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 https://community.chocolatey.org/api/v2/. 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
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download everything --internalize --version=1.3.4686.20160420 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade everything -y --source="'INTERNAL REPO URL'" --version="'1.3.4686.20160420'" [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 everything -y --source="'INTERNAL REPO URL'" --version="'1.3.4686.20160420'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install everything
win_chocolatey:
name: everything
version: '1.3.4686.20160420'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'everything' do
action :install
source 'INTERNAL REPO URL'
version '1.3.4686.20160420'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller everything
{
Name = "everything"
Version = "1.3.4686.20160420"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'everything':
ensure => '1.3.4686.20160420',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
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 ferventcoder on 21 Apr 2016.
"Everything" is an administrative tool that locates files and folders by filename instantly for Windows.
Unlike Windows search "Everything" initially displays every file and folder on your computer (hence the name "Everything").
You type in a search filter to limit what files and folders are displayed.
Write-Debug ("Starting " + $MyInvocation.MyCommand.Definition)
$RegQueryCommand = $null
if([System.Environment]::Is64BitOperatingSystem) {
$RegQueryCommand={REG.EXE QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything" -v "UninstallString" }
}
else {
# The registry path for the uninstall command is:
# HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything\UninstallString
# However, this is only visible to a 32 bit PowerShell instance (without using WMI or Remote Registry) :(
# For this reason, we are using the REG.eXE /QUERY
$RegQueryCommand={REG.EXE QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Everything" -v "UninstallString" /reg:32}
}
function GetUninstallCommand()
{
[string]$uninstallCommand=(. $RegQueryCommand)[2].Trim().Split([string[]]@(" "), [StringSplitOptions]::RemoveEmptyEntries)[2]
if($LASTEXITCODE -ne 0)
{
Write-Error "The uninstall registry setting appears to be missing (`$LASTEXITCODE=$LASTEXITCODE)"
}
return $uninstallCommand;
}
function Uninstall()
{
get-process everything -ErrorAction Ignore | Stop-Process #Not required unless the Everything window is open for a search (the default immediately after install
$uninstallCommand = GetUninstallCommand
$(Start-Process $uninstallCommand /S -Wait)
if($LASTEXITCODE -ne 0)
{
Write-Error "The application uninstall command failed."
}
if(Test-Path "$env:ChocolateyInstall\bin\es.exe") {
Remove-Item $env:ChocolateyInstall\bin\es.exe #Remove the item added so es is in the path.
}
}
<#
function VerifyUninstall()
{
#Requery the registry settings to verify they were removed during uninstall.
. $RegQueryCommand 2> out-null
if($LASTEXITCODE -eq 0) {Write-Error "The application was NOT successfully uninstalled as registry settings remain. (`$LASTEXITCODE=$LASTEXITCODE)" }
#Verify the Everything directory was removed.
if(Test-Path ${env:ProgramFiles}\Everything) {Write-Error "The application was NOT successfully uninstalled as the '${env:ProgramFiles}\Everything' still exists." }
}
#>
Uninstall
#VerifyUninstall
Write-Debug ("Finished " + $MyInvocation.MyCommand.Definition)
## Summary
How do I create packages? See https://github.com/chocolatey/choco/wiki/CreatePackages
If you are submitting packages to the community feed (https://chocolatey.org)
always try to ensure you have read, understood and adhere to the create
packages wiki link above.
## Automatic Packages?
Consider making this package an automatic package, for the best
maintainability over time. Read up at https://github.com/chocolatey/choco/wiki/AutomaticPackages
## Shim Generation
Any executables you include in the package or download (but don't call
install against using the built-in functions) will be automatically shimmed.
This means those executables will automatically be included on the path.
Shim generation runs whether the package is self-contained or uses automation
scripts.
By default, these are considered console applications.
If the application is a GUI, you should create an empty file next to the exe
named 'name.exe.gui' e.g. 'bob.exe' would need a file named 'bob.exe.gui'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-set-up-batch-redirects-for-applications-that-have-a-gui
If you want to ignore the executable, create an empty file next to the exe
named 'name.exe.ignore' e.g. 'bob.exe' would need a file named
'bob.exe.ignore'.
See https://github.com/chocolatey/choco/wiki/CreatePackages#how-do-i-exclude-executables-from-getting-batch-redirects
## Self-Contained?
If you have a self-contained package, you can remove the automation scripts
entirely and just include the executables, they will automatically get shimmed,
which puts them on the path. Ensure you have the legal right to distribute
the application though. See https://github.com/chocolatey/choco/wiki/Legal.
You should read up on the Shim Generation section to familiarize yourself
on what to do with GUI applications and/or ignoring shims.
## Automation Scripts
You have a powerful use of Chocolatey, as you are using PowerShell. So you
can do just about anything you need. Choco has some very handy built-in
functions that you can use, these are sometimes called the helpers.
### Built-In Functions
https://github.com/chocolatey/choco/wiki/HelpersReference
A note about a couple:
* Get-BinRoot - this is a horribly named function that doesn't do what new folks think it does. It gets you the 'tools' root, which by default is set to 'c:\tools', not the chocolateyInstall bin folder.
* Install-BinFile - used for non-exe files - executables are automatically shimmed...
* Uninstall-BinFile - used for non-exe files - executables are automatically shimmed
### Getting package specific information
Use the package parameters pattern - see https://github.com/chocolatey/choco/wiki/How-To-Parse-PackageParameters-Argument
### Need to mount an ISO?
https://github.com/chocolatey/choco/wiki/How-To-Mount-An-Iso-In-Chocolatey-Package
### Environment Variables
Chocolatey makes a number of environment variables available (You can access any of these with $env:TheVariableNameBelow):
* TEMP = Overridden to the CacheLocation, but may be the same as the original TEMP folder
* ChocolateyInstall = Top level folder where Chocolatey is installed
* chocolateyPackageName = The name of the package, equivalent to the id in the nuspec (0.9.9+)
* chocolateyPackageVersion = The version of the package, equivalent to the version in the nuspec (0.9.9+)
* chocolateyPackageFolder = The top level location of the package folder
#### Advanced Environment Variables
The following are more advanced settings:
* chocolateyPackageParameters = (0.9.8.22+)
* CHOCOLATEY_VERSION = The version of Choco you normally see. Use if you are 'lighting' things up based on choco version. (0.9.9+)
- Otherwise take a dependency on the specific version you need.
* chocolateyForceX86 = If available and set to 'true', then user has requested 32bit version. (0.9.9+)
- Automatically handled in built in Choco functions.
* OS_PLATFORM = Like Windows, OSX, Linux. (0.9.9+)
* OS_VERSION = The version of OS, like 6.1 something something for Windows. (0.9.9+)
* OS_NAME = The reported name of the OS. (0.9.9+)
* IS_PROCESSELEVATED = Is the process elevated? (0.9.9+)
#### Experimental Environment Variables
The following are experimental or use not recommended:
* OS_IS64BIT = This may not return correctly - it may depend on the process the app is running under (0.9.9+)
* CHOCOLATEY_VERSION_PRODUCT = the version of Choco that may match CHOCOLATEY_VERSION but may be different (0.9.9+)
- it's based on git describe
* IS_ADMIN = Is the user an administrator? But doesn't tell you if the process is elevated. (0.9.9+)
* chocolateyInstallOverride = Not for use in package automation scripts. (0.9.9+)
* chocolateyInstallArguments = the installer arguments meant for the native installer. You should use chocolateyPackageParameters intead. (0.9.9+)
Log in or click on link to see number of positives.
- es.exe (d6e40b993e81) - ## / 67
- Everything-1.3.4.686.x64-Setup.exe (e2f8e15cf6e3) - ## / 56
- Everything-1.3.4.686.x86-Setup.exe (826e76c27f88) - ## / 56
- Everything.1.3.4686.20160420.nupkg (986da796342e) - ## / 57
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 |
---|---|---|---|---|
Everything 1.4.11026 | 202778 | Thursday, August 1, 2024 | Approved | |
Everything 1.4.11025 | 44 | Thursday, August 1, 2024 | Approved | |
Everything 1.4.11024 | 917212 | Friday, May 26, 2023 | Approved | |
Everything 1.4.11023 | 46366 | Wednesday, May 10, 2023 | Approved | |
Everything 1.4.11022 | 293671 | Monday, October 10, 2022 | Approved | |
Everything 1.4.11021 | 17206 | Monday, October 3, 2022 | Approved | |
Everything 1.4.11020 | 44574 | Thursday, September 8, 2022 | Approved | |
Everything 1.4.11018 | 42232 | Wednesday, August 17, 2022 | Approved | |
Everything 1.4.11017.20220621 | 71043 | Tuesday, June 21, 2022 | Approved | |
Everything 1.4.11017 | 42857 | Thursday, May 26, 2022 | Approved | |
Everything 1.4.11015 | 209681 | Friday, December 17, 2021 | Approved | |
Everything 1.4.11014 | 3210 | Thursday, December 16, 2021 | Approved | |
Everything 1.4.11009 | 85708 | Thursday, June 3, 2021 | Approved | |
Everything 1.4.11005 | 63468 | Monday, January 25, 2021 | Approved | |
Everything 1.4.11004 | 7652 | Tuesday, January 19, 2021 | Approved | |
Everything 1.4.11003 | 11158 | Friday, January 8, 2021 | Approved | |
Everything 1.4.11002 | 20534 | Saturday, December 12, 2020 | Approved | |
Everything 1.4.11000 | 12831 | Monday, November 30, 2020 | Approved | |
Everything 1.4.1999 | 4630 | Thursday, November 26, 2020 | Approved | |
Everything 1.4.1992 | 35129 | Saturday, September 19, 2020 | Approved | |
Everything 1.4.1988 | 25193 | Wednesday, August 5, 2020 | Approved | |
Everything 1.4.1987 | 7106 | Thursday, July 30, 2020 | Approved | |
Everything 1.4.1986 | 7181 | Thursday, July 23, 2020 | Approved | |
Everything 1.4.1969 | 79863 | Monday, March 16, 2020 | Approved | |
Everything 1.4.1965 | 8515 | Tuesday, March 3, 2020 | Approved | |
Everything 1.4.1935.20190602 | 63880 | Sunday, June 2, 2019 | Approved | |
Everything 1.4.1935 | 41710 | Monday, February 18, 2019 | Approved | |
Everything 1.4.1932 | 7343 | Thursday, January 31, 2019 | Approved | |
Everything 1.4.1928 | 9402 | Friday, January 11, 2019 | Approved | |
Everything 1.4.1927 | 621 | Friday, January 11, 2019 | Approved | |
Everything 1.4.1924 | 7097 | Friday, December 21, 2018 | Approved | |
Everything 1.4.1922 | 2440 | Saturday, December 15, 2018 | Approved | |
Everything 1.4.1895.20180530 | 16610 | Wednesday, May 30, 2018 | Approved | |
Everything 1.4.1895.20180505 | 3852 | Saturday, May 5, 2018 | Approved | |
Everything 1.4.1895 | 7310 | Friday, February 9, 2018 | Approved | |
Everything 1.4.1877.20170915 | 9110 | Friday, September 15, 2017 | Approved | |
Everything 1.4.1877 | 6250 | Wednesday, June 7, 2017 | Approved | |
Everything 1.4.1873 | 2318 | Tuesday, June 6, 2017 | Approved | |
Everything 1.4.1867.20170417 | 1763 | Saturday, April 29, 2017 | Approved | |
Everything 1.4.1867 | 5586 | Tuesday, April 11, 2017 | Approved | |
Everything 1.4.1809 | 6455 | Friday, December 9, 2016 | Approved | |
Everything (Install) 1.3.4686.20160420 | 5248 | Wednesday, April 20, 2016 | Approved | |
Everything 1.3.4686.20160128 | 2649 | Friday, January 29, 2016 | Approved | |
Everything 1.3.4686.20150529 | 1786 | Saturday, May 30, 2015 | Approved | |
Everything 1.3.4686.20150321 | 4227 | Saturday, March 21, 2015 | Approved | |
Everything 1.3.4686.20140912 | 3906 | Tuesday, September 23, 2014 | Unknown | |
Everything 1.2.1371.20121117 | 2828 | Monday, November 19, 2012 | Unknown | |
Everything 1.2.1371.20121101 | 651 | Tuesday, November 6, 2012 | Unknown |
2014 David Carpenter
Change Log - https://www.voidtools.com/Changes.txt
This package has no dependencies.
Ground Rules:
- This discussion is only about Everything (Install) and the Everything (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 Everything (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.