Semiconducted

+1 on gr5's suggestion. It's an annoying workaround, but I also just use the CPE profile for PETG on an UM2+. If your brand of filament calls for slightly higher temps, try the Nylon profile. @gr5 - thanks for tips on raising the bed temp & slowing the print speed. PETG likes to string and / or accumulate nozzle boogers, so any tips on reducing those is welcome! 😀

+1 I had also been experiencing this behavior in 4.6.0 and 4.6.1 (don't recall if also in 4.5.0).

I was using an Ultimaker S5, though I usually use an Ultimaker 2+ Extended. PETG is not shown for either printer before or immediately after the marketplace install nor after restarting Cura (as the 'success (?)' message requests). Re: material not visible My professional UX design advice is to handle this use case differently. Hiding incompatible materials creates a mismatch between the perceived system state and the actual system state. It also sets the user up to experience repeated "silent errors" wherein they install the material, get a "success" confirmation, but then see no system change, leaving them baffled as to what went wrong, even though nothing did. I suggest indicating that the material is installed but just not available for this machine. It could be as simple as showing the unavailable materials as greyed out / not selectable. Or these materials could all be put in a separate 'incompatible with this printer' group. Or... (I could go on and on)

The set of Generic profiles in my installation of Cura 4.6.1 (and 4.6.0, 4.5.0) is missing profiles like PETG that do appear in the marketplace Generic profiles. This is why I chose to install them from the marketplace. However, once installed, they still do not appear in Cura, as if they are not properly being overwritten (good ol' permissions issues?). Hope this helps!

Explicitly created a whitelist on my router for all the domains listed on the support page but still the same repeating sync loop. Logs attached. Thanks for your help! cura.log

Same here. Happens in both Ultimaker Cura 4.5.0 and 4.6.0 on macOS 10.15.4. - tried complete uninstall, restarted computer, reinstall - added "Full Disk Access" in security preferences - explicitly added "allow incoming connections" in firewall rules to both 4.5.0 and 4.6.0 - happens on 2 different wifi networks and also via Verizon mobile tether