4.2 fails to import 4.1 curaprofiles

[OldGaf]

This was reported in the beta and was closed as the fix was to go into the stable ver.
It still is broken.

see:
4.2 Beta fails to import 4.1 curaprofiles #6033

Application version
4.2

Platform
Win7

Printer
CR-10s

Reproduction steps
Installed 4.2 and saw no profiles for my CR-10s, but all the Select Mini profiles are fine.

Actual results
No CR-10s profiles loaded on install. Manual import also fails with the following error:
"The machine defined in profile E:/Downloads/CR-10-Mech.curaprofile (fdmprinter) doesn't match with your current machine (creality_base), could not import it."

Expected results
Expected profile to be available on install. Expected manual import of profiles to work.

Additional information

[b4545]

Any known workarounds?

Edit: Easier to just manually create a new profile

[diegopradogesto]

Duplicate of #6083 . We will release a hotfix (Cura 4.2.1) today that fixes this issue (and others).

[mihxew]

Same problem on Cura 4.2.1!!!

[jvcop]

I can confirm this problem on Cura 4.2.1. (Windows 10)

[Ghostkeeper]

The problem here is that Creality printers now have profiles specific to themselves. Cura doesn't know which profiles to put in the "Creality" category and which to put in the "fdmprinter" (profile-less printers) category.

We're looking into finding a way around this. I've heard @nallath had some ideas?

[nallath]

Yeah. The original reason we initially set the filtering of quality_changes there was to prevent people from accidentally importing profiles for the wrong machine. But I'd say that in this case, it's doing more damage than it's trying to prevent.

[Vandrasc]

For our internal reference, devs see CURA-6713.

[polerix]

i eed omputer with workig keys or eterl usb keybord this lptp is the pitts hee retypig the proile is rough

[GregValiant]

I'm cleaning house.
Is this still a problem with current Cura versions (5.8.0 and up)? Can I close this?

[OldGaf]

Feel free to close

[GregValiant]

Thanks.