Is it Cura or Windows?

[sillywan 0]

I am trying to get the truth so I can possibly save myself hours of re-installation of windows and etc... Can a windows update make cura no longer slice properly? Any of them? At least from 4.6.2 up to 4.13.1 . I was using 4.6 with no issues for months and then I updated and it has been failure after failure since then. There are so many folks having no problem at all it cant be Cura.  I am at a loss. I have asked on groups and we have checked our OS data and they were the same. Their Cura worked flawlessly and mine is slicing see through prints if it prints any thing at all. It will stop responding when you press slice. Like the algorythym is messed up. Weird because it is doing the same thing on my win 10 machine. I have already got the win 7 machine ready for a clean install of 7 pro I am just shooting a last flare in an effort to resolve this issue without the pain of an OS rebuild. Thank you for your help.

[ahoeben 1,968]

On 2/17/2022 at 6:30 PM, sillywan said:

Can a windows update make cura no longer slice properly?

Please clarify what you mean by "no longer slice properly". What can happen is that Cura no longer starts or slices at all (eg because of changes in graphics drivers or changes in firewall policies). But a Windows Update can not change the actual gcode that is created.

 

If you think that something changed between Cura 4.6.2 and 4.13.1, you could try reinstalling Cura 4.6.2:

https://github.com/Ultimaker/Cura/releases/tag/4.6.2

Most previous releases can be found here:

https://github.com/Ultimaker/Cura/releases