JUMP TO SOLUTION Solved

Original topic:

New Samsung fridge with Family Hub keeps restarting, screen freezes after update

(Topic created: 05-02-2022 06:30 PM)
3374 Views
user0fSuOAvMuG
Astronaut
Options
Kitchen and Family Hub

Need help, have reset with switch and unplugged fridge still not changing

1 Solution


Accepted Solutions
Solution
Samsung_Moderator
Community Manager
Community Manager
Options
Kitchen and Family Hub

Hello there! I can definitely understand how frustrating it would be to have your refrigerator resetting frequently. Since you have already tried the troubleshooting steps, the next step we would recommend would be service. If you purchased the refrigerator within the last year, it may still be under the manufacturer warranty. Please send a private message to any of the moderators here for further information about setting up service. 

View solution in context

4 Replies
JCloud
Astronaut
Options
Kitchen and Family Hub
Depending on your model. Press and hold the Power Cool and Power Freeze buttons simultaneously for five seconds. If the reset has worked, you'll hear a chime, and the fridge will start back up with the default settings.
0 Likes
Reply
userBzyB4p9CwZ
Constellation
Options
Kitchen and Family Hub

This is the worst update so far. Everything else was working before this and now the screen on the fridge keeps restarting despite all measures. 

Solution
Samsung_Moderator
Community Manager
Community Manager
Options
Kitchen and Family Hub

Hello there! I can definitely understand how frustrating it would be to have your refrigerator resetting frequently. Since you have already tried the troubleshooting steps, the next step we would recommend would be service. If you purchased the refrigerator within the last year, it may still be under the manufacturer warranty. Please send a private message to any of the moderators here for further information about setting up service. 

userX3wfmPi9Y3
Asteroid
Options
Kitchen and Family Hub

Having the same issue. This is clearly a software issue as the trouble started after a pushed update which has nee noted in another thread as well. Please push out another new update to fix the issue.