Bootstrapping Boxstarter fails due to Chocolatey directory already existing

[AdmiringWorm]

Checklist

• I have verified this is the correct repository for opening this issue.
• I have verified no other issues exist related to my problem.
• I have verified this is not an issue for a specific package.
• I have verified this issue is not security related.
• I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

This was reported in the community channels, when bootstrapping boxstarter this fails the the installations due to the Chocolatey directory being created manually by Boxstarter, while an update to the Chocolatey installation will throw an exception if it exists, even when empty.

What is Expected?

We should be able to bootstrap and install Boxstarter in the supported scenarios.

How Did You Get This To Happen?

N/A

System Details

• Operating System:
• Windows PowerShell version:
• Chocolatey CLI Version:
• Chocolatey Licensed Extension version:
• Chocolatey License type:
• Terminal/Emulator:

Will be filled out once more information is available.

Installed Packages

N/A

Output Log

N/A

Additional Context

No response

[choco-bot]

🎉 This issue has been resolved in version 3.0.3 🎉

The release is available on:

• GitHub Release
• Chocolatey Packages
  • Boxstarter
  • Boxstarter.Azure
  • Boxstarter.Bootstrapper
  • Boxstarter.Chocolatey
  • Boxstarter.Common
  • Boxstarter.HyperV
  • Boxstarter.TestRunner
  • Boxstarter.WinConfig
• Boxstarter Website

Your GitReleaseManager bot 📦🚀