Couldn't set the secure storage master key

Any correct answer about this issue??

What we know is "something" that partners/customers are doing during between the box coming from the factory and the box being live in production is breaking the encryption system on a very small number of boxes.  But we have never gotten enough details about what the the "something" is.  But the something is really early in the processes, because it appears broken in the first boot in the logs.

At best I get told "we installed version x".

The detail level I need is:
Box arrived from the factory.
Box was powered on with no ethernet connection.  Observed that version was 18.5 GA.
Box was powered off.  USB key with 19.0 MR1 was plugged in.
19.0 MR1 was installed from USB while there was no ethernet connection.
ethernet was plugged in.  Box was booted.

If you are a partner or a customer with support, please raise a ticket with support and give them as much detail as possible, getting them to write it in the ticket.  Ask them to escalate to GES, who can escalate to Dev.  You can point them to this thread.  We want to use this process because we get most accurate count of how many customers are affected.

If you are someone with SUPER DETAILED steps of the history of the box, you can message me privately in the forum.  Even though the solution might still come through a support ticket, I am more likely to be able to get the detail I need if I can talk more directly with the people involved.

If you are a home user or someone who cannot raise a support ticket, then open a support tunnel and message me privately with the access id.

Repairing a box takes 2 min if I have a support tunnel, assuming it is a fairly new box that you haven't done a lot of things on.

What we know is "something" that partners/customers are doing during between the box coming from the factory and the box being live in production is breaking the encryption system on a very small number of boxes.  But we have never gotten enough details about what the the "something" is.  But the something is really early in the processes, because it appears broken in the first boot in the logs.

At best I get told "we installed version x".

The detail level I need is:
Box arrived from the factory.
Box was powered on with no ethernet connection.  Observed that version was 18.5 GA.
Box was powered off.  USB key with 19.0 MR1 was plugged in.
19.0 MR1 was installed from USB while there was no ethernet connection.
ethernet was plugged in.  Box was booted.

If you are a partner or a customer with support, please raise a ticket with support and give them as much detail as possible, getting them to write it in the ticket.  Ask them to escalate to GES, who can escalate to Dev.  You can point them to this thread.  We want to use this process because we get most accurate count of how many customers are affected.

If you are someone with SUPER DETAILED steps of the history of the box, you can message me privately in the forum.  Even though the solution might still come through a support ticket, I am more likely to be able to get the detail I need if I can talk more directly with the people involved.

If you are a home user or someone who cannot raise a support ticket, then open a support tunnel and message me privately with the access id.

Repairing a box takes 2 min if I have a support tunnel, assuming it is a fairly new box that you haven't done a lot of things on.