Thanks for the suggestions. I have contacted customer support to see if they will send me replacement screws, otherwise I will source them locally.
Steve7 - is this like what you used to remove the broken screws? https://www.lowes.com/pd/SpeedOut-8-1-8-in-Double-Ended-Screw-Extractor/1000170531
Joscelyne3 - Yes, that happened to the 2017 Imagines. Ours is a very early 2018 and has extra brackets installed on the slide out frames (see TSB 17-001). Unfortunately somebody didn't check the assembly line guys torque settings and the screw heads still got snapped off.![]()
Technical Service Bulletin.
Hi Mike, I had several heads snap off on my Solitude. What I did was step up the size of the screws. If they were #8 I used a#10 . Or #10 up to a#12 . Redrill new hole near old ones snapped, and replaced the others. Seal up the holes from the snapped screws. I also used a cordless drill with a clutch on a low setting so I would not strip out the heads of the new screws.
A while back there was a issue with the Schwintek mechanism, I believe it was mainly with Imagine's . Part of the problem was with the screws being the wrong size. Give customer service a call and ask them if they can send you as many as you need to replace and repair your slides
Hope this may help. Good luck.
Hi John, I have an 2020 Imagine with this screw problem where the screws are coming out along the outside of the slide frame. Did you end up using #12 's? Sorry to be a bonehead on screw size but how long is a #12 ?
Is it wood that the screw goes in too?
Thanks for any help John.
Our 2024 came with some snapped screws too. Upon inspection none of the flange sealant was broke so it's not that the structure is breaking the screws, they were broke from the factory assembly person over tightening.We have a 2024 imagine xls 22mle and are having the same screw head shear issues with the slide out interior attachment clips. So far about half are sheared off, and we’ve owned it less than a month and probably pushed the slide out a half dozen times.
Plan on following the fixes suggested in this thread, but just wanting to let folks know, the issue still seems current