I couldn't agree more - you buy Cisco because you need something that works. People who buy Cisco are not worrying about the price tag. They really dropped the ball letting this bug out and then ignoring it for so long, still now without any official fix or update.
It makes me think it is a rebranded or white-labelled 3rd party product and not produced by Cisco's own team (this is a common thing these days). Though perhaps that gives Cisco too much credit, as it assumes they wouldn't have done this badly themselves.
Bugs happen. Unavoidable. But they should be caught in pre-release update tests, and if not then at least fixed quickly. None of that happened here and it remains a problem for many.
I have this same bug. I've read all the responses and I don't see a clear solution.
I would expect a clear reply from Cisco. I also purchased Cisco trying to avoid this type bug I would expect from a non Cisco hardware company. Very sad to unbox a new router at this price, then have this bug out of the box. It's costing me a major delay and consulting time.
I had the same problem and opened a support case. As a workaround, installing the signatures from the PC or through an USB stick worked. Finally, I got the response that this an already known bug and can be tracked here: https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvs01386.
So hopefully this will be fixed in the next firmware release...