Replies: 1 comment
-
Can you ensure you're running Chocolatey CLI 2.1.0? Can you uninstall Chocolatey GUI and install 2.1.0? Note, don't do a forced install, uninstall it. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have chocolatey installed on 2 computers, my laptop on my desktop.
both run Windows 10 x64 the latest version (3155)
Today I noticed that the chocolatey GUI looks different on my desktop 10 on my laptop. the desktop version also had a different menu structure and some features like the light/dark appearance switch missing.
Odd, since both of them displayed the last versions of the GUI installed listed as as 2.1.0.
Then I noticed that the desktop machine despite the version 2.1 installed identify/displays version 1.7
I try to update it but it said it is already updated and current 2.1.
So I thought perhaps I need to install the chocolatey GUI and reinstall it.
I did that and the result is now it does not work anymore and crashes upon start up with the following error message:
"Failed to start application.\nCould not load file or assembly
'System.Reactive,Linq, Version =3.0.3000.0, Culture—neutral,
PublicKeyToken—94bc3704cddfc263' or one of its dependencies. The
located assembly's manifest definition does not match the assembly
reference. (Exception from HRESIJLT: 0x80131040)\n\nMore details
available in application logs."
What is this and what do I do to get it to work again and also be the correct version?
The GUI log shows the following:
2023-07-08 17:57:24.418 -07:00 [Fatal] Failed to start application.
System.IO.FileLoadException: Could not load file or assembly 'System.Reactive.Linq, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'System.Reactive.Linq, Version=3.0.3000.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263'
at ChocolateyGui.Common.Windows.ViewModels.SourcesViewModel.OnViewReady(Object view)
at System.Windows.ContextLayoutManager.fireLayoutUpdateEvent()
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.Interop.HwndSource.SetLayoutSize()
at System.Windows.Interop.HwndSource.set_RootVisualInternal(Visual value)
at System.Windows.Window.SetRootVisual()
at System.Windows.Window.SetRootVisualAndUpdateSTC()
at System.Windows.Window.SetupInitialState(Double requestedTop, Double requestedLeft, Double requestedWidth, Double requestedHeight)
at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
at System.Windows.Window.ShowHelper(Object booleanBox)
at ChocolateyGui.Common.Windows.Bootstrapper.d__43.MoveNext() in C:\buildAgent\work\774e9aed9020e028\Source\ChocolateyGui.Common.Windows\Bootstrapper.cs:line 138
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Beta Was this translation helpful? Give feedback.
All reactions