mkpasswd (434): [31] A device attached to the system is not functioning.

Linda Walsh
Mon Aug 2 23:19:00 GMT 2010

On 7/30/2010 6:33 AM, Larry Hall (Cygwin) wrote:
> On 7/30/2010 3:14 AM, Linda Walsh wrote:
>> This is still a problem.
>> /bin>  mkpasswd
>> SYSTEM:*:18:544:,S-1-5-18::
>> LocalService:*:19:544:U-NT AUTHORITY\LocalService,S-1-5-19::
>> NetworkService:*:20:544:U-NT AUTHORITY\NetworkService,S-1-5-20::
>> Administrators:*:544:544:,S-1-5-32-544::
>> mkpasswd (434): [31] A device attached to the system is not functioning.
>> /bin>
> Looking at the code (which you can find here 
> <>), 
> it appears either NetUserGetInfo() or NetUserEnum()
> is failing.  Seems like a strange error message but perhaps it makes more
> sense in context.  Since I cannot reproduce it, I cannot be of more help.
>> Note:
>> mkgroup doesn't give an error message.  Why mkpasswd does and mkgroup does
>> not might be pertinent -- don't they use similar mechanisms?  What do they do
>> different?
> Because they are looking for different information.  See 
> <>

There's lots of places where error results are printed out without saying what call they are referring to.  Since I'm not the only one with this problem, is it possible to have error messages also mention what call returned the error?  - maybe print out any useful (human interpretable) parameters?  

Or are there other programs in windows that would try to print out the same information?

I.e. say some variant of the "net" or "netsh" commands"?  On linux, I can try debugging with the 'net' command and it's various outputs, but I don't know what I'd use here to do the same.  

I've tried building things from cygwin before and never had any luck just satisfying the dependencies, so that's been a non-starter for me.

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list