-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.4.1] Recent files in Windows Jump list cannot locate files correctly #6919
Comments
I can confirm this happens in 4.4, and that 4.3 works correctly. This is going to be a difficult one, since this happens before Cura starts and the right file is clearly known to windows.Yet it's still probably somehow related to something we did, since 4.3 still works. I've found where windows saves this information, but those file don't seem to do anything different between the versions at first glance at least. |
Maybe something to do with quotes and spaces in the file path? |
Developers: https://jira.ultimaker.com/browse/CURA-7102 |
I have been having this exact problem ever since I uninstalled all old versions of Cura prior to installing 4.5. I still have this problem with 4.6.1. |
It's still on the bug backlog I'm afraid :-/ We'll pick it up at some point, though that might be a while (we've got a lot on our plates). |
Ok. I just thought it might be helpful to know that it stared when I removed old versions of Cura. |
During the installation or afterwards? |
I uninstalled old versions (3.6 to 4.4) before installation. Then noticed the problem after installing the new version (4.5 at the time). I believe I also checked the box to remove all configurations, because I had a corrupt configuration. I even tried installing all old versions back to 4.2.1 and the problem persists on all versions 4.4 and newer. |
Hi @goscicki, I think I've found the reason behind your issue. Since, indeed we had not changed anything in that part of the code, I did a little test of my own because the earliest version I had installed was Cura v4.3.0.
That happens because in the registry the stl file opening is associated with all Cura versions you've installed, but it will open only with the earliest one (in your case 4.3.0). So, if you want to remove this registry associations completely you should open regedit as an administrator and then remove the following:
Now you'll need to right click on an .stl file and choose 'Open with' and then select the latest Cura you're using. After that's done, the recent files will be opening with the version you desire. |
@evtrados Great! This one really stimied me. Can you add it to the change control board? I think we might need to discuss if we can solve problems like this in a version upgrade then. |
Yes, I will add it to the board. As far as I investigated these entries are not deleted upon uninstall. The only one that gets deleted is the "actual" 'Open with..' association in HKEY_CLASSES_ROOT.stl\OpenWithProgids, so we might need to add the aforementioned ones as well. |
@evtrados Thank you! I haven't installed 4.7 yet because I'm almost done with a big important project. If I'm done tonight, I'll install 4.7 and delete those keys. I'll be sure to let you know how it goes. Thanks again! |
@evtrados Unfortunately the problem persists after following those steps. I should clarify. The problem doesn't seem to be with file associations, since Cura opens with clicking directly on a file. The problem is in the recent jump list on the windows task bar. |
Thanks for trying it out @goscicki and I'm sorry it still doesn't work for you. |
That opens with 4.7 as expected. |
I should also note that I deleted the following keys and rebooted: HKEY_LOCAL_MACHINE\SOFTWARE\Classes\UltimakerCura.stl* folders |
Got it! It took one last step. I deleted TPI_v9.3mf from the jump list, then reopened the file. That re-added it to the list correctly and it works now. @evtrados thank you so much for your help! |
Glad that I could help @goscicki!! |
Have the same problem after installing 4.8. I noticed that HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf was still missing, so I added the following: [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf\OpenWithProgids] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf.4.8] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf.4.8\DefaultIcon] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf.4.8\shell] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf.4.8\shell\open] [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf.4.8\shell\open\command] I also found HKEY_CLASSES_ROOT\3mf_auto_file\shell\open\command was still set to "C:\Program Files\Ultimaker Cura 4.7\Cura.exe" "%1" and changed it to 4.8 Now files open with 4.8 however the jump list for 4.8 still does not work. But 4.7 still works fine. I am so confused. I even deleted the broken items from the jump list and rebooted like last time, but no success. I wish I knew where the jump lists are handled in the registry. |
Well, I found a solution for now by making this change: [HKEY_LOCAL_MACHINE\SOFTWARE\Classes.3mf] Now the jump list works on 4.8 but not on 4.7, which is ok for now. This is a somewhat confusing issue that I have never experienced with any other program. |
Hmmm, it is a bit confusing indeed. I'll try to investigate why it happens. It's probably because there's something going wrong with assigning the latest version as default for all the file types. |
I'm cleaning house. |
I do not know. I have stopped using Cura, so I am unable to assist with testing. |
I'll close it. |
Application version
4.4.1
Platform
Windows 10
Printer
Irrelevant
Reproduction steps
Screenshot(s)
![Screenshot (40)](https://user-images.githubusercontent.com/59352/71776649-997d9c00-2f95-11ea-80fd-6fb39ea3bbe0.png)
Actual results
Error message pops up asking user if file perhaps was moved
Expected results
Cura opens, loading file clicked in recent list.
Project file
Irrelevant
Log file
Did not find anything relevant in log file.
Additional information
I did make sure I hadn't changed the files or moved/deleted them.
In the cura application the "File->Open recent" entries function correctly.
The text was updated successfully, but these errors were encountered: