Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

8,991

Downloads of v 2.4.0.237:

127

Last Update:

12 Sep 2019

Package Maintainer(s):

Software Author(s):

  • NeoSmart Technologies

Tags:

operating-system boot bootloader boot-manager mbr boot-menu bcd grub

EasyBCD

Downloads:

8,991

Downloads of v 2.4.0.237:

127

Maintainer(s):

Software Author(s):

  • NeoSmart Technologies

EasyBCD

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.

Details
WARNING

This package was rejected on 30 Sep 2019. The reviewer Pauby has listed the following reason(s):

boubou (maintainer) on 22 Aug 2019 20:01:10 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 22 Aug 2019 20:34:42 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Write-ChocolateySuccess/Write-ChocolateyFailure have been deprecated, but have been found in the package's automation scripts. Remove the usage of those two functions. If there is an error, throw the error. More... This can also give a false positive for commented code with the words:
    • Write-ChocolateySuccess
    • Write-ChocolateyFailure
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 22 Aug 2019 22:41:49 +00:00:

easybcd has failed automated testing.
This is not the only check that is performed so check the package page to ensure a 'Ready' status.
Please visit https://gist.github.com/d432ad75631e8263486777380fdc0c58 for details.
The package status will be changed and will be waiting on your next actions.

  • NEW! We have a test environment for you to replicate the testing we do. This can be used at any time to test packages! See https://github.com/chocolatey/chocolatey-test-environment
  • Please log in and leave a review comment if you have questions and/or comments.
  • If you see the verifier needs to rerun testing against the package without resubmitting (a issue in the test results), you can do that on the package page in the review section.
  • If the verifier is incompatible with the package, please log in and leave a review comment if the package needs to bypass testing (e.g. package installs specific drivers).
  • Automated testing can also fail when a package is not completely silent or has pop ups (AutoHotKey can assist - a great example is the VeraCrypt package).
  • A package that cannot be made completely unattended should have the notSilent tag. Note that this must be approved by moderators.

boubou (maintainer) on 23 Aug 2019 15:09:08 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 23 Aug 2019 15:42:40 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Write-ChocolateySuccess/Write-ChocolateyFailure have been deprecated, but have been found in the package's automation scripts. Remove the usage of those two functions. If there is an error, throw the error. More... This can also give a false positive for commented code with the words:
    • Write-ChocolateySuccess
    • Write-ChocolateyFailure
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 23 Aug 2019 16:32:07 +00:00:

easybcd 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 https://gist.github.com/b0575a6e817bf6818900dfef7d30d0e1 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 27 Aug 2019 07:24:12 +00:00:

The Package Source URL is going to a 404. Can you please update that to go to the actual package source, which will now be your GitHub Repository, assuming you have one?

While you are making that change, it would be great to get the other Guidelines reported above implemented in the package as well.

It would be great if you could use PowerShell splatting in the installation script, as this makes it much easier to moderate.

The uninstall script is using a much older template, that is using deprecated functions, can you please correct this? It is likely that the uninstall script is actually not needed, since Chocolatey's auto uninstaller will likely be able to uninstall it. Did you test with this?

If you can fix up those things, we can get this approved.

boubou (maintainer) on 29 Aug 2019 16:04:07 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 29 Aug 2019 16:39:42 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The licenseUrl should not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • The nuspec has been enhanced to allow packageSourceUrl, pointing to the url where the package source resides. This is a strong guideline because it simplifies collaboration. Please add it to the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 29 Aug 2019 19:37:50 +00:00:

easybcd 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 https://gist.github.com/6d1d630e785adf57630c1a6db10cbbc1 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 30 Aug 2019 06:43:39 +00:00:

I have to ask about your GitHub Repository here:

https://github.com/sboulianne/chocolatey

Normally, we would ask that this URL be used as the packageSourceUrl in the nuspec file, but it doesn't look like you have the package source files in that repository. Normally, we would expect that the nuspec, the chocolateyInstall.ps1, and other files are contained within that repository. You seem to only have the icons and the nupkg files.

Can I ask why that is?

Since you have an icon, it would be good to update the nuspec to include the iconUrl.

The install script has a $toolDir variable which isn't being used, as the Install-ChocolateyPackage function doesn't have an unzipLocation argument. Can you please remove this?

boubou (maintainer) on 30 Aug 2019 23:40:34 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 31 Aug 2019 00:14:38 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 iconUrl should be added if there is one. Please correct this in the nuspec, if applicable. More...
  • The licenseUrl should not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 31 Aug 2019 01:45:03 +00:00:

easybcd 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 https://gist.github.com/4407dc5ed5432b8707e8681df3f85199 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 02 Sep 2019 06:51:42 +00:00:

As per your other package, can you please remove the unziplocation variable, as this is not being used in this package.

Also, can you provide instructions on how I can validate the URL that is being used to download the exe? i.e. where on this site:

https://neosmart.net/EasyBCD/

Can I find that URL?

boubou (maintainer) on 02 Sep 2019 23:17:27 +00:00:

User 'boubou' (maintainer) submitted package.

boubou (maintainer) on 02 Sep 2019 23:24:36 +00:00:

  1. There is no unzplocation into my nuspec file.
  2. If you want to validate the URL, go to https://neosmart.net/EasyBCD/, download the EasyBCD then check the checksum...
    You will see that the checksum is the same. ;)

Thanks for all Gary! I really appreciate it!

chocolatey-ops (reviewer) on 02 Sep 2019 23:50:00 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 03 Sep 2019 01:53:39 +00:00:

easybcd 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 https://gist.github.com/1d23e52b5f5d9005287dfbde3772ad88 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 03 Sep 2019 06:16:56 +00:00:

No, there is not, but there is in the chocolateyInstall.ps1 file, which is what I was referring to.

Please provide full steps on how to download the installer. There are various options that can be selected, some of which require purchasing of a license, others which require registration on the site. I don't really want to waste my time picking the wrong one, and given that you have already gone through this process, it would be easier if you could just tell me.

boubou (maintainer) on 04 Sep 2019 16:40:03 +00:00:

Sure.
Near of the bottom of the page, there are 2 options if you want get EasyBCD.

  1. Buy the product.
    Commercial $29.95
    Priority technical support
    Works with enterprise and professional editions of Windows
    Detailed PDF instruction manual
    Automatic upgrades to new releases
  2. Register
    Non-commercial Free
    Limited, community support
    No early access to new features
    Only for personal, non-commercial use
    Once you entered your name+email, you will be redirected to a download page and a link will be email to you if you want to share the package with someone else.
    The link will expire after some times.

boubou (maintainer) on 04 Sep 2019 20:07:45 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 04 Sep 2019 20:41:06 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 04 Sep 2019 23:36:06 +00:00:

easybcd 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 https://gist.github.com/4683cabc60d85949a7c7be7922b09405 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 05 Sep 2019 07:01:15 +00:00:

Thank you for the information!

Can you confirm exactly what you mean by:

> The link will expire after some times.

What does that mean for this package version going forward? Does that mean that the package will stop working after a period of time? Is there not a stable download URL that can be used?

boubou (maintainer) on 05 Sep 2019 13:57:48 +00:00:

When you want to download the installer from the Neosmart Technologies website, I cant get a permanent link to download the installer.
Its why I used another site to get the file.

gep13 (reviewer) on 10 Sep 2019 06:23:07 +00:00:

Where did you find this other site? Is it linked from the main Neosmart Website? We can't simply use any random site, otherwise, how do we know that the installer isn't malicious?

boubou (maintainer) on 10 Sep 2019 13:31:54 +00:00:

The other site isnt linked to Neosmart site but I compared the checksum and it was the same!

gep13 (reviewer) on 10 Sep 2019 18:53:10 +00:00:

Simply put, that isn't good enough. If the download URL isn't from the original application site, or the license allows the embedding of the application into the package, you can't use a random download site to install from.

boubou (maintainer) on 12 Sep 2019 16:09:46 +00:00:

User 'boubou' (maintainer) submitted package.

chocolatey-ops (reviewer) on 12 Sep 2019 16:40:52 +00:00:

easybcd has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.

Guidelines

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 not usually be an exact match to softwareUrl. Please correct this in the nuspec, if applicable. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
  • Summary (summary) is a short explanation of the software. Please include summary in the nuspec. More...
Suggestions

Suggestions are either newly introduced items that will later become Guidelines or items that are don't carry enough weight to become a Guideline. Either way they should be considered. A package version can be approved without addressing Suggestion comments.

  • The nuspec has been enhanced to allow more information related to the software. More... Please consider adding one or more of the following to the nuspec, if available:
    • docsUrl - points to the location of the wiki or docs of the software
    • mailingListUrl - points to the forum or email list group for the software
    • bugTrackerUrl - points to the location where issues and tickets can be accessed
    • projectSourceUrl - points to the location of the underlying software source

chocolatey-ops (reviewer) on 12 Sep 2019 18:26:18 +00:00:

easybcd 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 https://gist.github.com/70afdbe8b05a71bcf8be692291ed1423 for details.
This is an FYI only. There is no action you need to take.

gep13 (reviewer) on 13 Sep 2019 06:35:17 +00:00:

Can you please provide information about where this URL was found on the website? Is it a time limited URL that will stop working after a period of time?

boubou (maintainer) on 27 Sep 2019 14:56:14 +00:00:

I agree, its a time limited link.
I wrote a post on the forum.

boubou (maintainer) on 27 Sep 2019 15:03:56 +00:00:

I just look on the forum and I saw this is NO permanent link.
https://neosmart.net/forums/threads/permanent-download-link-for-easybcd.17494/#post-92955
If you cant accept an trustable external link (from my VPS server), reject this package, remove me as a maintainer.
Thanks.

Pauby (reviewer) on 30 Sep 2019 13:26:36 +00:00:

Package rejected as per maintainers request - If you cant accept an trustable external link (from my VPS server), reject this package, remove me as a maintainer.
Status Change - Changed status of package from 'submitted' to 'rejected'.

Description

EasyBCD is the answer to tweaking the Windows bootloader. With EasyBCD, almost anything is possible, e.g. to boot a Win7-VHD-image.
Setting up and configuring Windows boot entries is simple, and there is no easier way to quickly boot right into Linux, Mac OS X, or BSD straight from the Windows bootloader - on the fly, no expert knowledge needed!
EasyBCD is geared for users of all kinds. Whether you just want to add an entry to your old XP partition or want to create a duplicate for testing purposes; if youre interested in debugging the Windows Kernel or septuple-booting your seven test operating systems, EasyBCD is the key.


easybcd.png
 
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop';
$toolsDir   = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
$url        = 'http://newsletter.neosmart.net/wf/click?upn=oADKZsSomiiZr72Q1doXUM-2FEL4SkvpA6hcaiQOBcVlBm1zALWy1HPBhnRXVuiTzl8AnqID6YZLKytbZd-2FgN6s2oukQX4NIQnICYy4fqMoTaTwl9O92pGrgjjBLNth5CRpWT4iDwByDQNIs9LIWR4oAyo-2Bo8ZNO-2B-2FdK4WXLKFCzg9VvcbfJjhVzhGmr6m81pgytT8qMpWPdHEQfuwVesMKDufLUW79y9MlV3kfvS-2FfRVIG4gP1Z7uHqmbvO6hr23n06zG-2F85mElWJUOG2nEIEzIC8XSToh6Mjl-2BeN2LT0xbdq5S7I9meud9v3xOH6Z8dvvMs3qfFKnajxhyH8Ad-2Fl5gMS4e8EErp1jEV4U2QbbXAOg4ShkQ-2FSV0PUnnpMQYdW_gujZenN5kIwq3KCCCq9ISJuJFa1b0jWoxi-2FhbtGHe4cSM6a6AG0liMuKL96XLG-2B7Ig5IcMOqc-2B4FKvrh0NM4BFmEqUclcR3j81dfCgPH1DGODoa4N5-2FHJcXk0LLUwF3YsRk2yO6vLJLbFjMuaa9n-2F4RQC4P-2BPBpFftUJHusmYY8KnO3xl6fBAYGMk4LDCJaRuxBDGrjVnxuS2YCdNJ3d8pb9pYU8OnYP8DmAVw2YySkav56oV9e-2FYHx2tWjx5U1FdQ3oNRfa3I4zYYiBOe3L-2FdnvPbARz1mQ9G7b371uDhUTdOCVzNKLyzT-2BOByzF4bF1hPF3Dv3VlVYIcaZRTnbMd0V2lQsR5sa5kUn-2BboByJg-3D'
$packageArgs = @{
  packageName   = $env:ChocolateyPackageName
  fileType      = 'EXE'
  url           = $url
  softwareName  = 'easybcd'
  checksum = '0A94A43AF2DB7BDBADA87B34BF03D3B221110D1CA21BBEBEC55B08767C1281CC'
  checksumType  = 'sha256'
  silentArgs    = "/S"
  validExitCodes= @(0)
  
}

Install-ChocolateyPackage @packageArgs

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

This package has no dependencies.

Discussion for the EasyBCD Package

Ground Rules:

  • This discussion is only about EasyBCD and the EasyBCD 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 EasyBCD, 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