ChocoGUI Crash on Startup -- Windows 10

[drfrpjr]

I have been using Choco and ChocoGUI -- the latest versions -- with Windows 10 on a Surface. Works fine. Powershell version=5.0.10240.17443

However, I just got a new desktop PC and while Choco is fine, ChocoGUI viciously crashes with the error below. This is running as administrator, etc. I think I have tried everything else above as well. Powershell version=5.1.14393.953

I included the Powershell versions because that seems to be the only differences between the two systems in terms of dependencies.

Any advice?

Thanks.

[LawrenceIRL]

I'll add that this also occurs over here too.
It seems to only crash when selecting an internal source. My source is running Chocolatey Server.
Issue does not occur in the pre-release version from MyGet.

[wjk]

@drfrpjr @TheVakman This actually isn't what you think it is. The problem (as evidenced in that TLDR error dialog) is that the Choco GUI client is trying to use the MD5 crypto algorithm on a system with Windows' FIPS mode feature enabled. When FIPS mode is enabled, the .NET Framework will refuse to load certain crypto algorithms, instead throwing an exception. This has nothing to do with one's package source, and entirely with an incompatibility between ChocoGUI and the security policies of your organization.

This problem can be corrected by placing the following code in the App.config file for ChocolateyGUI, and then rebuilding the project from source. I got this code from the App.config file for the choco checksum tool. You can see it here (click the "Show" link next to the file called checksum.exe.config).

<configuration>
    <runtime>
        <enforceFIPSPolicy enabled="false"/>
    </runtime>
</configuration>

I am not certain as to ChocolateyGUI's policies regarding FIPS mode compatibility. If anyone wants me to submit a PR with this change, please let me know. Hope this helps!

[drfrpjr]

William, Thanks for the information. I actually did not build ChocolateyGUI, but installed it using Choco. Any chance of making this the default in the ChocolateyGUI build? That said, what compiler tools are needed to compile from source?

…

----Fred From: William Kent [mailto:notifications@github.com] Sent: Monday, August 14, 2017 12:17 PM To: chocolatey/ChocolateyGUI <ChocolateyGUI@noreply.github.com> Cc: Phelan Jr., Frederick R. Dr. (Fed) <frederick.phelan@nist.gov>; Mention <mention@noreply.github.com> Subject: Re: [chocolatey/ChocolateyGUI] ChocoGUI Crash on Startup -- Windows 10 (#458) @drfrpjr<https://github.com/drfrpjr> @TheVakman<https://github.com/thevakman> This actually isn't what you think it is. The problem (as evidenced in that TLDR error dialog) is that the Choco GUI client is trying to use the MD5 crypto algorithm on a system with Windows' FIPS mode feature enabled. When FIPS mode is enabled, the .NET Framework will refuse to load certain crypto algorithms, instead throwing an exception. This has nothing to do with one's package source, and entirely with an incompatibility between ChocoGUI and the security policies of your organization. This problem can be corrected by placing the following code in the App.config file for ChocolateyGUI<https://github.com/chocolatey/ChocolateyGUI/blob/develop/Source/ChocolateyGui/app.config>, and then rebuilding the project from source. I got this code from the App.config file for the choco checksum tool. You can see it here<https://www.chocolatey.org/packages/chocolatey/0.10.7> (click the "Show" link next to the file called checksum.exe.config). <configuration> <runtime> <enforceFIPSPolicy enabled="false"/> </runtime> </configuration> I am not certain as to ChocolateyGUI's policies regarding FIPS mode compatibility. If anyone wants me to submit a PR with this change, please let me know. Hope this helps! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#458 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOIqbBAb8qFbFShajuJqGx6i5ihPlZuuks5sYHLxgaJpZM4OcC_6>.

[wjk]

@drfrpjr You'll need Visual Studio 2017 (the free Community edition is OK to use here, as this is an open-source project, and the Community edition's license terms specifically allow use for open-source development, but of course a higher edition will do if you have a license).

What you'll want to do is install VS2017 (you'll need to select at least the .NET Desktop Development workflow during the installation process, or else the project won't load). Once that is done, clone the ChocolateyGUI repository and run the build.ps1 script in the repository root. Once that has finished running, you can open Source\ChocolateyGUI.sln and edit away. You will need to add the <enforceFIPSPolicy /> tag from my above post into the Source\ChocolateyGUI\app.config file (try inserting it directly after line 3), and then build the entire solution.

[drfrpjr]

I have VS2015 … will that work?

…

-----Fred From: William Kent [mailto:notifications@github.com] Sent: Monday, August 14, 2017 9:29 PM To: chocolatey/ChocolateyGUI <ChocolateyGUI@noreply.github.com> Cc: Phelan Jr., Frederick R. Dr. (Fed) <frederick.phelan@nist.gov>; Mention <mention@noreply.github.com> Subject: Re: [chocolatey/ChocolateyGUI] ChocoGUI Crash on Startup -- Windows 10 (#458) @drfrpjr<https://github.com/drfrpjr> You'll need Visual Studio 2017 (the free Community edition is OK to use here, as this is an open-source project, and the Community edition's license terms specifically allow use for open-source development, but of course a higher edition will do if you have a license). What you'll want to do is install VS2017 (you'll need to select at least the .NET Desktop Development workflow during the installation process, or else the project won't load). Once that is done, clone the ChocolateyGUI repository and run the build.ps1 script in the repository root. Once that has finished running, you can open Source\ChocolateyGUI.sln and edit away. You will need to add the <enforceFIPSPolicy /> tag from my above post into the Source\ChocolateyGUI\app.config file (try inserting it directly after line 3<https://github.com/chocolatey/ChocolateyGUI/blob/develop/Source/ChocolateyGui/app.config#L3>), and then build the entire solution. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#458 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOIqbDehvhuRGiWWvRoVcN9uUBDQs1Jtks5sYPRlgaJpZM4OcC_6>.

[wjk]

It should, but I haven't been able to test it. The main reason I recommended VS2017 was because the solution file had a VS2017 header in it. However, a cursory search reveals no VS2017-specific project features. Try it and let me know how it goes. Thanks!

[drfrpjr]

Thanks, I’ll give it a try on a personal device with VS17 … and let you know what happens!

…

----Fred From: William Kent [mailto:notifications@github.com] Sent: Tuesday, August 15, 2017 7:30 AM To: chocolatey/ChocolateyGUI <ChocolateyGUI@noreply.github.com> Cc: Phelan Jr., Frederick R. Dr. (Fed) <frederick.phelan@nist.gov>; Mention <mention@noreply.github.com> Subject: Re: [chocolatey/ChocolateyGUI] ChocoGUI Crash on Startup -- Windows 10 (#458) It should, but I haven't been able to test it. The main reason I recommended VS2017 was because the solution file had a VS2017 header in it. However, a cursory search reveals no VS2017-specific project features. Try it and let me know how it goes. Thanks! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#458 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOIqbHV1aUxsJstQjRE0cyE4ad8nQqr1ks5sYYE1gaJpZM4OcC_6>.

[LawrenceIRL]

@wjk Thanks. I'm okay with using the pre-release version as that's the default in that version. I just wanted to note that it didn't happen on the pre-release version and now we know why. I'm very curious when that one will replace the older version.

[RichiCoder1]

I took @wjk's suggestion and simply disabled the check in d365ec3. It doesn't make any sense to respect this policy for ChocolateyGUI and even microsoft recommends against it.

[drfrpjr]

Is that fix reflected in a ChocolateyGUI update with Choco?

…

----Fred

Sent from my iPad On Sep 26, 2017, at 12:39 PM, Richard Simpson <notifications@github.com<mailto:notifications@github.com>> wrote: I took @wjk<https://github.com/wjk> and simply disabled the check in d365ec3<d365ec3>. It doesn't make any sense to respect this policy for ChocolateyGUI and even microsoft recommends against it. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#458 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOIqbKyUuvSlyLNA9FKK7AJeyjcg8An3ks5smSitgaJpZM4OcC_6>.

[RichiCoder1]

It should be in the latest prerelease.

[hltdev8642]

@drfrpjr @TheVakman This actually isn't what you think it is. The problem (as evidenced in that TLDR error dialog) is that the Choco GUI client is trying to use the MD5 crypto algorithm on a system with Windows' FIPS mode feature enabled. When FIPS mode is enabled, the .NET Framework will refuse to load certain crypto algorithms, instead throwing an exception. This has nothing to do with one's package source, and entirely with an incompatibility between ChocoGUI and the security policies of your organization.

This problem can be corrected by placing the following code in the App.config file for ChocolateyGUI, and then rebuilding the project from source. I got this code from the App.config file for the choco checksum tool. You can see it here (click the "Show" link next to the file called checksum.exe.config).

<configuration>
    <runtime>
        <enforceFIPSPolicy enabled="false"/>
    </runtime>
</configuration>

I am not certain as to ChocolateyGUI's policies regarding FIPS mode compatibility. If anyone wants me to submit a PR with this change, please let me know. Hope this helps!

Thank you!! this works perfectly. I just edited the ChocolateyGUI.exe.config file and added that and it works now.

[drfrpjr]

Hi, Thanks for the update. Actually, Chocolatey GUI has been fixed for some time now. I am not sure what changed it, but it has been working for at least a year now. Thanks,

…

--Fred

________________________________ Frederick R. Phelan Jr., Ph.D.

________________________________ NIST 100 Bureau Dr., STOP 8542 Gaithersburg, MD 20899-8542 301.975.6761 301.975.4924 (FAX) frederick.phelan@nist.gov<mailto:frederick.phelan@nist.gov> My WebEx<https://nist-secure.webex.com/meet/frederick.phelan> My NIST Home Page<https://www.nist.gov/people/phelan-jr-frederick-r> WebFF Project Page<https://mgi.nist.gov/webff-force-field-repository-organic-and-soft-materials> [mml] -Omnia in mensura et numero et pondere disposuisti. (Sapientiae 11:21)- From: hltdev8642 <notifications@github.com> Sent: Sunday, August 23, 2020 1:23 PM To: chocolatey/ChocolateyGUI <ChocolateyGUI@noreply.github.com> Cc: Phelan Jr., Frederick R. Dr. (Fed) <frederick.phelan@nist.gov>; Mention <mention@noreply.github.com> Subject: Re: [chocolatey/ChocolateyGUI] ChocoGUI Crash on Startup -- Windows 10 (#458) @drfrpjr<https://github.com/drfrpjr> @TheVakman<https://github.com/TheVakman> This actually isn't what you think it is. The problem (as evidenced in that TLDR error dialog) is that the Choco GUI client is trying to use the MD5 crypto algorithm on a system with Windows' FIPS mode feature enabled. When FIPS mode is enabled, the .NET Framework will refuse to load certain crypto algorithms, instead throwing an exception. This has nothing to do with one's package source, and entirely with an incompatibility between ChocoGUI and the security policies of your organization. This problem can be corrected by placing the following code in the App.config file for ChocolateyGUI<https://github.com/chocolatey/ChocolateyGUI/blob/develop/Source/ChocolateyGui/app.config>, and then rebuilding the project from source. I got this code from the App.config file for the choco checksum tool. You can see it here<https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.chocolatey.org%2Fpackages%2Fchocolatey%2F0.10.7&data=02%7C01%7Cfrederick.phelan%40nist.gov%7C2f2b809e5fd447d8d3c708d847892104%7C2ab5d82fd8fa4797a93e054655c61dec%7C1%7C0%7C637338001580092684&sdata=IBh%2BIXdXl1sc75YvaosMZS9ntMnMpBG%2B3XaupQFJMH4%3D&reserved=0> (click the "Show" link next to th e file called checksum.exe.config). <configuration> <runtime> <enforceFIPSPolicy enabled="false"/> </runtime> </configuration> I am not certain as to ChocolateyGUI's policies regarding FIPS mode compatibility. If anyone wants me to submit a PR with this change, please let me know. Hope this helps! Thank you!! this works perfectly. I just edited the ChocolateyGUI.exe.config file and added that and it works now. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#458 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADRCU3HE5OYUJDTNCH3CE4LSCFF5PANCNFSM4DTQF75A>.