Comment 10 for bug 189432

Right, the issue becomes just a packaging issue for the windows packagers to sort out, so it doesn't need to be solved for 0.46.

As well, in order for this bug to remain milestoned at all, we need an assignee for it. We can't block a release on a bug with no one to own it.