Can't modify or delete walls and sweeps

[design]

Suddenly in the last week or so, I have noticed some walls in my drawings that don't let me modify, stretch, delete, paint with a different material or make any form of change to it's parameters. I have searched online but have found nothing similar. I have tried repairing and even re-installing revit from scratch but no change. I am running Revit 2020.1 on Windows 10, version 1903. I did a quick screencast of the issue. You will notice that when I delete the right hand wall, I can then go backwards and delete the original wall but not before. This issue has occurred in multiple of my files recently.. I would really like to find a way to fix this without having to resort to deleting a large part of my model without know what is causing this in the first place and why all of a sudden.

Any help would be appreciated.

[Luiscko]

I not pretty sure, I have never happened this thing maybe you need to try in other file and check if you can do it, if not probably your update does not install pretty well, that means that you need to reinstall your update and maybe with that it could be work.

[Anonymous]

Are the elements not pinned?  There is a small button on the bottom right that allows you to select pinned elements (or not).

Are you not using design options?  These elements could be on an option that is not editable.

[design · Accepted solution]

I think I have solved the problem.  It turns out I was no longer getting warnings. The warning dialog box was no longer popping up when a conflict was occurring. I found this article that explains the problem. It is was the Autodesk Revit Infraworks Updater 2020 add-in that is the problem and uninstalling it fixed my issue.

https://knowledge.autodesk.com/support/revit-products/learn-explore/caas/sfdcarticles/sfdcarticles/W...

[jbrin]

I just ran into this issue where I could not delete a wall after creating it. I couldn't even select it! I went to 3D view and was able to select/delete it there. I'm not sure what the issue is, but I figured this might help someone in a pinch to at least resolve the issue in the immediate instance.