Kicad changed after Windows update

Layout
1

I recently updated windows and now my Kicad has changed automatically. I was on the verge of finishing a big 4 layer pcb and now Kicad has changed the way it works. Earlier I could move a segment independently but now it has anchor points. Now I can’t add Vias either. Places where the inner layers overlap now show up as white. Earlier this didn’t happen.
I am used to the way it worked earlier and would like it to be that way.

Is there anything that I can do to revert to the old style.

Thanks in advance.

2

What version of KiCad and Windows are you running?
What patches were installed during the windows update? Can you revert these and see if it fixes the issue?

A Windows update will not update KiCad so I can only think a Windows patch has broken something.

3

Sounds like they installed the kicad nightly tbh

1 Like
4

Thanks guys. I tried reverting to an old restore point but that didn’t work. After playing around with it for many hours I think I’ve found the problem. I changed it from ‘Legacy toolset’ to ‘Modern Toolset’ and it seems to have solved the problem. Sadly I don’t know what these Toolsets are.
Anyways, thanks for the replies. It’s appreciated

5

You are using an old, unsupported version of KiCad. In v6 there’s no Legacy option. You should rather learn how to use the new features for your benefit. I know some users miss some of the old functionality, but new features make it possible to do the same things, although in a bit different way. Otherwise you will be stuck with the old version and eventually it will stop working on updated systems.

6

Were you reading too fast? :slight_smile:

7

No. I’m trying to look ahead to the future. Like it or not, continuing with the legacy toolset works as long as the system allows using unsupported v5, but not longer.

8

But Trevor (according to my understanding) was working with Modern Toolset then suddenly something changed. And after some searching he said: “I changed it from ‘Legacy toolset’ to ‘Modern Toolset’ and it seems to have solved the problem”.
So changing back to Modern Toolset solved his problem.
What you said previously (and now) suggest me that you think that he works with Legacy toolset what is not true, I think. I just suggested that may be by reading fast you not noticed the direction of changes he described.

9

Hahaa, it was that way! Now I just have to hope that someone who uses the legacy toolset reads this thread. :smile:

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.