chocolatey / ChocolateyGUI

A delicious GUI for Chocolatey
https://docs.chocolatey.org/en-us/chocolatey-gui/
Apache License 2.0
1.66k stars 253 forks source link

Problems running Chocolatey GUI on Windows 10 Technical Preview #183

Closed sevenday4 closed 9 years ago

sevenday4 commented 10 years ago

Sorry Gary I tried earlier to put the snapshot here, but the attach image selections is greyed out. Try looking at this snapshot using this URL: https://onedrive.live.com/redir?page=view&resid=7D6A6736229274CE!43783&authkey=!ADN9ipJin7HqOf8 And yes, that was me, I am sevenday4.

gep13 commented 10 years ago

As per this:

image

You can drag and drop, or copy/paste directly into the comment box. This is what I have just done.

image

You should be able to get a bit further with this, if you do the following:

This will then fail, for other reasons, when you try to actually install something.

But it should get you slightly further.

sevenday4 commented 10 years ago

Either its too early in the morning (been awake since 2 a.m. and gallons of coffee) or I am making this way more complicated then it needs to be. Thank goodness my keyboard is lit! I'm looking at things through slits!

sevenday4 commented 10 years ago

I couldn't find ChocolateyGUI in start menu. I have added a lot new things and they show up on my desk top but missing in my start menu. I'm going to do a restart of my machine and see if that will cause things to show up on the start menu even though it should happen instantaneous.

sevenday4 commented 10 years ago

Okay, I did a right click 'Run as administer' and so far things are working fine. Let me see if I can make it fail and under what conditions.

sevenday4 commented 10 years ago

Ok, so far chocolateyGUI is working pretty well. I can look for just about any file that is in any repository, I can visit the sites of the projects and so on. But, I'm having problems downloading files in Chocolatey mode. I don't know if update works since all of my software is up to date. What I plan to do is purposely find a file that I know is still being maintained but outdated. Then we'll see if Chocolatey can update that file.

sevenday4 commented 10 years ago

okay, I suggest putting in a refresh button. I put on my machine a project and ChocolateyGUI did not see it. Well, I got the program to fail then I restarted again, this time it is more stable but Chocolatey doesn't see all the files on my computer nor can it update the file that it couldn't see.

gep13 commented 10 years ago

Okay, I did a right click 'Run as administer' and so far things are working fine.

That's good

okay, I suggest putting in a refresh button. I put on my machine a project and ChocolateyGUI did not see it. Well, I got the program to fail then I restarted again, this time it is more stable but Chocolatey doesn't see all the files on my computer nor can it update the file that it couldn't see.

I am really not sure that I follow what you are suggesting here. Can you provide some step by step instructions for what you are doing, what is happening, and what you expect to be happening?

Thanks!

sevenday4 commented 10 years ago

What I understand what ChocolateyGUI is suppose to be is an package manager in the windows environment. When I installed a new file unto my machine, ChocolateyGUI did not refresh to acknowledge that in fact a new file has indeed been installed on the PC. My guess is that you have the Chocolatey page to show what's in the Chocolatey repository versus the PC? Now I cannot get ChocolateGUI to fire up. I went to my administrative events viewer to see what is going on, and I am getting an error indicator.Log Name: Application Source: Application Error Date: 10/30/2014 7:49:46 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: GuyEPipili-HP Description: Faulting application name: ChocolateyGUI.exe, version: 0.12.0.0, time stamp: 0x544fe258 Faulting module name: clr.dll, version: 4.5.21.0, time stamp: 0x5418f79c Exception code: 0xc00000fd Fault offset: 0x00000000001521d8 Faulting process id: 0x8bac Faulting application start time: 0x01cff450bf18541d Faulting application path: C:\Program Files (x86)\ChocolateyGUI\ChocolateyGUI.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: fd49c15f-6043-11e4-95da-e06995bff930 Faulting package full name: Faulting package-relative application ID: Event Xml:

1000 2 100 0x80000000000000 3636 Application GuyEPipili-HP ChocolateyGUI.exe 0.12.0.0 544fe258 clr.dll 4.5.21.0 5418f79c c00000fd 00000000001521d8 8bac 01cff450bf18541d C:\Program Files (x86)\ChocolateyGUI\ChocolateyGUI.exe C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll fd49c15f-6043-11e4-95da-e06995bff930 Hopefully this will give more insight as to why ChocolateyGUI is crashing. Anyway, I thought since this is a package manager, that it it would scan a PC every so often to see if there are any changes (whether something was installed or deleted). If you do not want ChocolateGUI to do scans then add a refresh button where the PC user can manually refresh the display of ChocolateyGUI.
sevenday4 commented 10 years ago

This URL from Microsoft can explain the error meaning a little bit better: file:///C:/Users/Guy/Downloads/Source%20%20Application%20Error%20ID%20%201000%20%28Windows%20Operating%20System%206.4.9860.0%29%20-%20Events%20And%20Errors%20Message%20Center%20%20Message%20Details.htm

gep13 commented 10 years ago

Anyway, I thought since this is a package manager, that it it would scan a PC every so often to see if there are any changes (whether something was installed or deleted). If you do not want ChocolateGUI to do scans then add a refresh button where the PC user can manually refresh the display of ChocolateyGUI.

At present, ChocolateyGUI is only aware of packages that it has installed. It has no way to know about applications that you have installed outwith the Chocolatey eco-system. Having said that, there are new features coming in Chocolatey that might allow this type of scenario to occur, but right now, this is not the case.

ChocolateyGUI will only report back about the currently installed packages that it is aware of, i.e. packages that have been downloaded/installed through either Chocolatey on the command line, or ChocolateyGUI.

sevenday4 commented 10 years ago

Okay so whatever went through ChocolateGUI is ChocolateGUI is concerned about, correct? I am trying home in as to where the aim of the project at present is concerned with.

gep13 commented 10 years ago

ChocolateyGUI is a wrapper around Chocolatey. And Chocolatey is a package manager for Windows. ChocolateyGUI calls into Chocolatey to install packages on your machine. Chocolatey doesn't know anything about applications that are installed in the traditional manner, i.e. double clicking an EXE or an MSI. Rather, it only knows about applications that are installed via one of the many packages that exist on the Chocolatey.org feed. As a result, ChocolateyGUI only knows about the packages that Chocolatey knows about.

sevenday4 commented 10 years ago

Hmmm, I got it now. You have to forgive me, it takes several pots of coffee and several trips to the restroom before the cobwebs finally disappear. Been up since 2 a.m.

gep13 commented 10 years ago

You have to forgive me,

Not a problem at all.

sevenday4 commented 10 years ago

Are you guys using any of the Boxstarter modules and not having them installed have an effect on Chocolatey in any way though Boxstarter is installed through PS?

gep13 commented 10 years ago

In the same way that ChocolateyGUI is built on top of Chocoately, Boxstarter is also built on top of Chocolatey. Chocolatey doesn't rely on anything in Boxstarter, but Boxstarter relies on Chocolatey.

sevenday4 commented 10 years ago

So in essence Chocolatey is a standalone tool that acts like a foundation.

gep13 commented 10 years ago

So in essence Chocolatey is a standalone tool that acts like a foundation.

Yes, you can think of it like that. Chocolatey is the basis, that many other tools are built on. Just like Chocolatey relies on NuGet, which is the underlying technology that is being used.

sevenday4 commented 10 years ago

With Windows 10 continuously changing, into what nobody knows, are you going to use commands that are backwards compatible even though Microsoft is trying to get everyone on Windows 8 and above (Lol). In other words, keep as simple as possible.

gep13 commented 10 years ago

Yes, I believe the plan is to remain as backwards compatible as possible.

DavidBurela commented 9 years ago

I had issues with running the Chocolatey GUI on Windows 10. Installing the pre release with
choco install ChocolateyGUI -source https://www.myget.org/F/chocolateygui/ -pre and then running the GUI as an administrator did fix this. I have been able to successfully install packages with this version

gep13 commented 9 years ago

@DavidBurela thanks for the information!

I haven't yet played with Windows 10 myself. I have downloaded the iso, and I have been meaning to set it up, but not had a chance yet.

sevenday4 commented 9 years ago

Hi Gary, I would suggest very strongly that you use the spare machine with this build. If you only have one machine, either VM or wait for the next build. Each build is done from scratch, and this build is hinky to say it kindly. Many issues with loading it on machines then there are issues with FTP client and other little nuances.

RichiCoder1 commented 9 years ago

I have a machine that is running win10. I'll see if I can run some tests on my own.

gep13 commented 9 years ago

I have a machine that is running win10. I'll see if I can run some tests on my own.

Woot!

RichiCoder1 commented 9 years ago

I did end up running ChocoGUI with no issues, but I'm going to say we say we don't start work on official support until post 0.12.

gep13 commented 9 years ago

Can I get anyone who is following this thread to try out a new version of ChocolateyGUI using the following command:

choco install chocolateygui -version 0.13.0-PullRequest0243 -source https://ci.appveyor.com/nuget/chocolateygui-36tajo4x9yei -pre

This is a new release of ChocolateyGUI which includes the ability to use the latest Chocolatey, i.e. 0.9.9.x, and it should hopefully solve a lot of the problems that have been reported lately.

Please give it a try, and let me know if you are still running into issues.

johnnyramos commented 9 years ago

Is that version the same code as the one on the develop branch?

gep13 commented 9 years ago

@johnnyramos no, that build is from a Pull Request, that hasn't yet been merged into develop

johnnyramos commented 9 years ago

Also, you have a space between the 0.13 and .0.

Chocolatey v0.9.9.2 Installing the following packages: chocolateygui By installing you accept licenses for the packages. chocolateygui not installed. An error occurred during installation: Unable to resolve dependency 'PowerShell'. chocolateygui install not successful. chocolateygui not installed. An error occurred during installation: Unable to resolve dependency 'PowerShell'.

Chocolatey installed 0/1 package(s). 1 package(s) failed. See the log for details. Failures:

gep13 commented 9 years ago

yeah, if you don't already have PowerShell installed, you will need a slightly different command to pull in the pre-requistes, as the AppVeyor feed doesn't know about upstream source.

Try:

choco install chocolateygui -version 0.13.0-PullRequest0243 -source https://ci.appveyor.com/nuget/chocolateygui-36tajo4x9yei;http://chocolatey.org/api/v2/ -pre

johnnyramos commented 9 years ago

Weird, I mean - I'm on Windows 8.1 and work off powershell alot. Is there anyway to skip the req?

Name Value


PSVersion 4.0 WSManStackVersion 3.0 SerializationVersion 1.1.0.1 CLRVersion 4.0.30319.0 BuildVersion 6.3.9600.17400 PSCompatibleVersions {1.0, 2.0, 3.0, 4.0} PSRemotingProtocolVersion 2.2

gep13 commented 9 years ago

Yes, but I have just stepped away from computer. Check the choco wiki install command for argument to ignore dependencies. The installation of the dep in this case wouldn't change anything, as it would see the PS v4 is already installed, and it would do nothing but tell Chocolatey that it is already installed.

Sent from my Windows Phone


From: Johnny Ramosmailto:notifications@github.com Sent: ‎23/‎03/‎2015 22:07 To: chocolatey/ChocolateyGUImailto:ChocolateyGUI@noreply.github.com Cc: Gary Ewan Parkmailto:gep13@gep13.co.uk Subject: Re: [ChocolateyGUI] Problems running ChocolateyGUI on Windows 10 Technical Preview (#183)

Weird, I mean - I'm on Windows 8.1 and work off powershell alot. Is there anyway to skip the req?

Name Value


PSVersion 4.0 WSManStackVersion 3.0 SerializationVersion 1.1.0.1 CLRVersion 4.0.30319.0 BuildVersion 6.3.9600.17400 PSCompatibleVersions {1.0, 2.0, 3.0, 4.0} PSRemotingProtocolVersion 2.2


Reply to this email directly or view it on GitHub: https://github.com/chocolatey/ChocolateyGUI/issues/183#issuecomment-85224860

johnnyramos commented 9 years ago

Looks to be running well in Windows 8.1 and sees the packages for 0.9.9.2. :+1:

Would test on Windows 10, but that has it's own OS bugs and won't allow me to run a cmd window.

RichiCoder1 commented 9 years ago

It breaks league of legends for me.

priorities

gep13 commented 9 years ago

Breaks how?

Sent from my Windows Phone


From: Richard Simpsonmailto:notifications@github.com Sent: ‎24/‎03/‎2015 03:21 To: chocolatey/ChocolateyGUImailto:ChocolateyGUI@noreply.github.com Cc: Gary Ewan Parkmailto:gep13@gep13.co.uk Subject: Re: [ChocolateyGUI] Problems running ChocolateyGUI on Windows 10 Technical Preview (#183)

It breaks league of legends for me.

priorities


Reply to this email directly or view it on GitHub: https://github.com/chocolatey/ChocolateyGUI/issues/183#issuecomment-85323454

RichiCoder1 commented 9 years ago

Windows 10 does, I should clarify, and it cause LoL to crash anytime I start a game. Unrelated issue, but it's the reason why I reverted my home machine to 8.1

gep13 commented 9 years ago

ha ha, gotcha :+1:

gep13 commented 9 years ago

I have just proved that on a Windows 7 VM, with Chocolatey 0.9.8.33, ChocolateyGUI functions as expected :-) Boom!

ScottIsAFool commented 9 years ago

I'm having an issue on 10041 of Win10. I have ChocolateyGUI installed, and it runs just fine, I can search, look at packages etc, however, when I click on install, the UI fades out (overlay), then waits a few seconds, then goes back to normal. Nothing further happens. No package is installed. Nothing. I've tried running it as administrator, with no joy either. Shame, I hate CLI :)

gep13 commented 9 years ago

I have just set up a new VM with Windows 10 (10041), installed Chocolatey 0.9.9.2 and ChocolateyGUI 0.13.0 and I can confirm that it is all working as expected. I am able to install and uninstall packages through ChocolateyGUI.

As per our Twitter discussion, it looks like you still had Chocolatey 0.9.8.33 installed (this is currently the default version that you will get when installing from the command on the website). To get the latest version of Chocolatey installed, run:

choco update chocolatey

and once that is installed, run:

choco --version

to confirm that it is installed

image

With this test completed, I am happy to close this issue, as ChocolateyGUI now has been tested on Windows 10. If anyone runs into any other issues, please raise a separate issue.

drfrpjr commented 7 years ago

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

Any advice?

Thanks.

image

mwallner commented 7 years ago

crash of @drfrpjr already documented in #458 - this issue was closed a while ago and won't be reopened.