I don’t usually post on these boards; however I was good to see that I was not the only one that was having this issue. I actually got through to second level support on two separate cases for this issue. The resolution for both of them was that Engineering was aware of the issue and it would likely be fixed in a firmware upgrade. I asked for a timeline and they would not give one to me. It is good to know that at least they have accepted it as a bug. They told me if I could not wait that I should return my box to the retailer for a refund. I did include a link to this and another thread complaining about this issue in the case so that they could see that it was happening to lots of people that were not happy about it.
1 Like
