Wait what? never heard of such an issue.
It's exclusively to borders? All types?

I'm here with the same issue, and it does look like it's all the furniture not just the arches. The debug log mentions there is an issue with setting the item's faction. "Tried to SetFaction on LTS_ThickDoor289671 which cannot have a faction. "

Modern walls do not have built in power conduits. Not sure why since before 1.4, those were there. I am going to try and change mod order around

Mod settings @Cloud, LTS Systems mod settings

Any way the futuristic doors could get a "reconnect" button? One of my tantrum-ing colonists destroyed an upstream power line and the door lost power, but it refuses to turn back on even once I restored power to it :(

That sounds so weird, it should have a power toggle automatically

Okay I am having the same issue as Loodon and Blaze, which would probably be why the arches and doors won't deconstruct. I'll check the error logs in a moment and get back to you on my end.

Okay, so, I cannot even select the frame, but I can select the door, this being the log for trying to claim it

Tried to SetFaction on LTS_SimpleDoorOne80698 which cannot have a faction.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.Thing:SetFaction (RimWorld.Faction,Verse.Pawn)
Verse.Building:SetFaction (RimWorld.Faction,Verse.Pawn)
RimWorld.Building_Door:SetFaction (RimWorld.Faction,Verse.Pawn)
RimWorld.Designator_Claim:DesignateThing (Verse.Thing)
RimWorld.Designator_Claim:DesignateSingleCell (Verse.IntVec3)
Verse.Designator:DesignateMultiCell (System.Collections.Generic.IEnumerable`1<Verse.IntVec3>)
Verse.DesignatorManager:ProcessInputEvents ()
RimWorld.MapInterface:HandleMapClicks ()
(wrapper dynamic-method) RimWorld.UIRoot_Play:RimWorld.UIRoot_Play.UIRootOnGUI_Patch1 (RimWorld.UIRoot_Play)
(wrapper dynamic-method) Verse.Root:Verse.Root.OnGUI_Patch2 (Verse.Root)

The frame does produce a log too if I try claiming it with a zone.

Full logs, if that would help: https://gist.github.com/HugsLibRecordKeeper/4640707fe00d320d02c14450ae25ae20

Destroy tool through dev mode did work to remove the offenders. I did not try manually destroying them with colonists, which probably would have worked.

shall checkj it out

Alrighty boss, thank you for your time and sorry for the trouble.

Hmmm, could I ask you to redownload LTS Systems and this mod possibly? Could be a conflict cause I cannot replicate issue.

Do so by deleting the files for both mods, sorry for the inconvenience but sometimes Steam messes with the downloads of mods during updates.

Un-subbed and re-subbed without going straight into the files, and upon trying to place a doorframe with godmode, it actually fails immediately due to the faction issue. I'll try going in there and wiping them and trying again, it is more than likely either a load order or mod conflict issue.

Okay so, I didn't get to deleting the files outright yet, but I relaunched it and the opening log had something to yell at me for, and it isn't the normal yelling from Vanilla Expanded content.

Config error in LTS_HyllisS: Beauty stat base is defined, but Things of category None cannot have beauty.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.DefDatabase`1<Verse.BuildableDef>:ErrorCheckAllDefs ()
System.Reflection.MonoMethod:Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
System.Reflection.MethodBase:Invoke (object,object[])

Config error in LTS_FuturisticReinforcedWall: does not add to map mesh but has a link drawer. Link drawers can only work on the map mesh.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.DefDatabase`1<Verse.ThingDef>:ErrorCheckAllDefs ()
System.Reflection.MonoMethod:Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object[],System.Globalization.CultureInfo)
System.Reflection.MethodBase:Invoke (object,object[])

It's those two kinds of errors for just about everything. If it isn't recognizable, I am dead certain it has to do with a mod conflict.

Sadly, the issue still persists, including the new list of errors. Since it is probably just a mod conflict, I don't think I'll try messing around to figure it out just yet. Sorry for the time spent over mostly nothing, thank you for trying to help as well.