Bug: Updating firmware resets to factory default

I am writing because this is now the second time in a row that my router RUTC50 reset to factory default after updating firmware from the interface.

this happened with RUTC_R_00.07.17.5 and RUTC_R_00.07.17.4

after both updates the router reverts to original factory settings and I have to re-apply all my setting manually and login with default factory password.

luckily the second time I had a settings backup BUT I could NOT apply it because I had to enable storage memory expansion before.

I am thinking this has to do with the bug and RUTOS fails to apply the settings because I have the storage memory expansion enabled before update.

re-enabling storage I had to reformat the drive (odd ?)

if that is not it there is a bug somewhere and I am happy to provide any information needed.

the only other thing is that I have the netbird package installed ( could this be the cause ? )

Greetings,

Could you please confirm which firmware version the device was running prior to the update? Specifically, did you upgrade from version 7.17.4 to 7.17.5, after which the router lost its configuration?

If the update was performed from a significantly older firmware version, there is a possibility of software migration issues, which can result in the configuration being reset to factory defaults.

I will investigate this further and run tests on my end.

Furthermore, for troubleshooting purposes, we will require more sensitive information from your end, such as the troubleshoot file, which may contain passwords, public IP addresses, serial numbers, and such. I will need the troubleshooting file to be able to recreate your current configuration. To avoid leaking this information, we have sent you a form to fill out, which you will receive in your e-mail inbox that you have registered your account with in the forums. In the Ticket ID field of the form, please enter the ID of this thread, which is 15889.

Best Regards,
Justinas

Hi Justinas

I did upgrade from 7.17.4 to 7.17.5 the second time
the first time this happened was from the last full release (the one before 7.17.5) to 7.17.4. I don’t remember the exact build number but I am sure because 7.17.4 is the only firmware I ever tried outside of the secure channel.

Not sure how to get this troubleshoot file but I guess it will tell me when submitting the form ?

update: I submitted the form but it did not ask me for the file or tell me how to get the file for you

Just adding a data point to this thread: this happened to me recently as well, when updating from 7.17.4 to 7.18 (which I know has now been pulled).

This topic was automatically closed after 60 days. New replies are no longer allowed.