> > Have you been able to determine *why* Microsoft made this
> braindead
> > decision? Or where it's documented? Their own knowledgebase is
> filled
> > with examples of using the device, so I imagine they'll have to
> post a
> > workaround somewhere...
>
> AFAIK, nobody has posted any links to information that shows that
> Microsoft actually *did* change this. I've searched their KB some
> (including the partner-only one for people with the paid
> agreements, which contains information about bugs that they don't
> want to be public), and find nothing about it.
>
> Unless you can reproduce this on a clean system, I'm definitely
> inclined to say this is caused by some other piece of software on
> the machine - firewall, antivirus, antispyware or virus/spyware
> itself.
Actually, I've been able to find some more information about this, which
confirms that the problem is access rights on the NUL device, but it's
*NOT* set by a MS security patch.
I'd be interested in seeing the output from the command:
Subinacl /service NULL
On a system where this does not work.
(If you get an empty update, make sure you have a version of subinacl
that corresponds to your windows version)
(There are known apps that mess this up, but my NDA prevents me from
telling you which one(s)...)
//Magnus
