“Just purchased this wash machine and the spin cycle doesn't seem like it goes to 700rpms. Has anyone else noticed this? On a couple of loads of laundry, we have had to run the spin/drain cycle only after the normal cycle had ended.”
Answer This Question
1-6 of 6 Answers
Hi! We just purchased this particular model after a HORRID experience with a Maytag (coincidentally that one was only 93 days old and apparently had a bad motor, I couldn't believe it - after 93 days, it just stopped spinning ANY water out. The Warranty process was even worse, that's actually what led us to Samsung) and have only had it about 2-3 weeks, but so far its worked like a DREAM! It spins the clothes so well that its cut my drying time down almost in half! From everything I researched, experienced first-hand, and read up on this particular model (and after the Maytag fiasco, there was a LOT of reviews research, in particular) that is not normal and should be brought to the attention of Warranty immediately! Either via Samsung or the company you purchased it through. I'm so sorry you're having that trouble, it can be terribly frustrating! I hope you get a satisfactory resolution soon!
Sorry, there was a problem. Please try again later.I’ve had my machine for two weeks and have used the normal, quick, and delicate wash cycles and have never had to run an additional spin cycle when the wash stops. I’m not sure how fast the spin cycle goes but it appears it’s going very fast and the clothes come out very dry and rung out.
Sorry, there was a problem. Please try again later.I have to drain and spin again.
Sorry, there was a problem. Please try again later.I have never had to rerun the spin cycle.
Sorry, there was a problem. Please try again later.I haven't had that problem check with best buy
Sorry, there was a problem. Please try again later.Hi there Pickleball73! I'd like to offer this link (https://bit.ly/3v0MAY1) to help with this. It has detailed information on what steps to take if the washer is not spinning properly. ^Jecca
Sorry, there was a problem. Please try again later.