And by the same token, not because you experience something means everyone else does, and as a developer you should recognize that because one person experiences/reports an issue does not make it KNOWN.
How do YOU as a developer deal with an issue, if a single user reports it, and you cannot duplicate it - how much time are you going to spend (a) trying to duplicate it, and (b) trying to rectify it after not being able to duplicate it.
At what point do you consider it as a one off quirk and move on?
To approach this from a different angle - I use my DNS-323 as a backup target - I've been doing it for two years. During that period I have had the need to restore my email once - should I report that to my email client vendor, to my server vendor, to my network switch vendor or to my desktop vendor - whose KNOWN issue does it become?
No - a "one" off issue cannot be described as a known issue - and in fact, unless, you can pin point the problem to the DNS-323, it should not be considered a known issue for the DNS-323.
Last but by no means least - have you also reported this to Microsoft, after all you're using beta software, which is expected to have issues?