Windows не удается подключиться к принтеру ошибка 0x00000057

Вопрос решил путём описанным
тут

Выгрузил ветку реестра и в безопасном режиме перезаписал файлы

• Помечено в качестве ответа
  Anton Sashev Ivanov
  16 августа 2016 г. 5:46

I figured out my situation.  Maybe it’s yours. 

It’s actually the print driver failing to install, not the connection to the print server.  An initial attempt to install the driver failed, so the driver directory is present on the workstation, but missing the files. 

1)  On a machine with the same driver installed (and working properly), open Regedit, and browse to:
     HKLMSystemCurrentControlSetControlPrintEnvironmentsWindows NT x86DriversVersion-3
2)  Locate the subkey for the printer driver you are dealing with and click the key for the printer driver.

3)  Look for the “InfPath” on the right.  Note the path.
5)  Now browse to C:WindowsSystem32DriverStoreFileRepository and locate the folder indicated in the InfPath reg value. 

6)  Go to the users computer exhibiting this behavior, and browse to C:WindowsSystem32DriverStoreFileRepository and see if the folder is present.  In my case, the folder was present, but empty.  If it is here and it is empty, you will
have to modify security on the folder, first taking over ownership, then granting yourself full control. 

7)  Once security is granted, copy the contents of this folder from a good machine to the machine presenting the 0x00000057.

Now try connecting to the print queue on the print server.  The driver should now download and install properly.

Good luck.  This isn’t the first time I’ve seen this happen, but this is the first time I decided a reimage was more than I wanted to take on, and I wanted to solve this so that I can correct it the next time it happens.  And I have yet to find
a real solution to the 0x00000057 error code.

Joel

• Proposed as answer by

  Monday, June 13, 2011 6:28 PM

• Marked as answer by
  Kevin Remde
  Monday, November 14, 2011 11:50 AM

Wow… I know it’s an old thread but well worth adding to, as this was a highly ambiguous issue.

I had the 0x00000057 error with a Xerox Workcentre 7535 Copier that I was installing in a domain Server 2008 R2/Win7Pro client setup. The printer drivers were installed on the server and worked for several other individuals. However, one individual was having
problems installing the Xerox on his relatively new Windows 7 Pro 32-bit. We had an HP 1312 nfi Multifunction as well, which was shared on the 2008 R2 server. He had no problems installing the HP with the Universal PCL5 and PS drivers HP had on their site. So,
when I tried installing the Xerox 7535 using the latest WHQL drivers offered by the Xerox site I got that 0x00000057 error.

At first I thought it had something to do with the share being messed up so I reinstalled the x64 drivers and added x86 drivers to the server and that didn’t work (Reboots of both the server and the client didn’t help either). I then tried installing the
driver locally and got the same error, which led me to believe it was a workstation issue.

Ultimately the registry suggestion by Joe IT proved fruitless, in my case. However, I did check the ..DriverStoreFileRepository folder and tried to look for some folders starting with X. There were only two and they did not look like xerox driver names.
I asked a co-worker with Win7Pro that successfully installed the drivers to let me know if there were additional folders listed, and there were two xerox type driver folders that were missing off the problematic windows 7 system.

I ended up putting the administrators group with full rights on the FileRepository folder (had to accept each subfolder as a failure due to no access permissions to change sub folder’s permissions). Then I copied the 2 missing folders over to the «broken»
system. I removed the admin group (and left the default Everyone and System accounts) permissions.

• Proposed as answer by
  sniperdoc
  Tuesday, October 23, 2012 1:08 PM
• Marked as answer by
  Guowen Su
  Thursday, October 3, 2013 6:06 AM

if you have access to another machine with the same OS; try installing the driver on the second computer then take ownership of it like in the steps above. copy the desired driver folder from C:WindowsSystem32DriverStoreFileRepository then paste it
on your computer in the same location making sure to overwrite the old files. then in the registry make sure the infPath key is pointing to the correct .inf file. i had to do this because i had an older version of a print driver installed than the one used
on our print server. i could not get the driver uninstalled by normal means so i just copied the files for the new driver and put them where the old ones were. worked like a charm.

• Proposed as answer by
  thai land
  Monday, October 1, 2012 5:53 PM
• Marked as answer by
  Kevin Remde
  Thursday, July 16, 2015 9:27 AM

This case have already close. :0)

Guowen Su
Cisco Certified Network Associate
Cisco Certified Internetwork professional — MPLS
Certified Information Systems Security Professional
Microsoft Partner Network 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Certified Ethical Hacker
Computer Hacking Forensics Investigator
Certified Sonicwall Security Administrator
Microsoft Geeks

• Marked as answer by
  Guowen Su
  Thursday, October 3, 2013 3:25 AM

I figured out my situation.  Maybe it’s yours. 

It’s actually the print driver failing to install, not the connection to the print server.  An initial attempt to install the driver failed, so the driver directory is present on the workstation, but missing the files. 

1)  On a machine with the same driver installed (and working properly), open Regedit, and browse to:
     HKLMSystemCurrentControlSetControlPrintEnvironmentsWindows NT x86DriversVersion-3
2)  Locate the subkey for the printer driver you are dealing with and click the key for the printer driver.

3)  Look for the “InfPath” on the right.  Note the path.
5)  Now browse to C:WindowsSystem32DriverStoreFileRepository and locate the folder indicated in the InfPath reg value. 

6)  Go to the users computer exhibiting this behavior, and browse to C:WindowsSystem32DriverStoreFileRepository and see if the folder is present.  In my case, the folder was present, but empty.  If it is here and it is empty, you will
have to modify security on the folder, first taking over ownership, then granting yourself full control. 

7)  Once security is granted, copy the contents of this folder from a good machine to the machine presenting the 0x00000057.

Now try connecting to the print queue on the print server.  The driver should now download and install properly.

Good luck.  This isn’t the first time I’ve seen this happen, but this is the first time I decided a reimage was more than I wanted to take on, and I wanted to solve this so that I can correct it the next time it happens.  And I have yet to find
a real solution to the 0x00000057 error code.

Joel

• Proposed as answer by

  Monday, June 13, 2011 6:28 PM

• Marked as answer by
  Kevin Remde
  Monday, November 14, 2011 11:50 AM

Wow… I know it’s an old thread but well worth adding to, as this was a highly ambiguous issue.

I had the 0x00000057 error with a Xerox Workcentre 7535 Copier that I was installing in a domain Server 2008 R2/Win7Pro client setup. The printer drivers were installed on the server and worked for several other individuals. However, one individual was having
problems installing the Xerox on his relatively new Windows 7 Pro 32-bit. We had an HP 1312 nfi Multifunction as well, which was shared on the 2008 R2 server. He had no problems installing the HP with the Universal PCL5 and PS drivers HP had on their site. So,
when I tried installing the Xerox 7535 using the latest WHQL drivers offered by the Xerox site I got that 0x00000057 error.

At first I thought it had something to do with the share being messed up so I reinstalled the x64 drivers and added x86 drivers to the server and that didn’t work (Reboots of both the server and the client didn’t help either). I then tried installing the
driver locally and got the same error, which led me to believe it was a workstation issue.

Ultimately the registry suggestion by Joe IT proved fruitless, in my case. However, I did check the ..DriverStoreFileRepository folder and tried to look for some folders starting with X. There were only two and they did not look like xerox driver names.
I asked a co-worker with Win7Pro that successfully installed the drivers to let me know if there were additional folders listed, and there were two xerox type driver folders that were missing off the problematic windows 7 system.

I ended up putting the administrators group with full rights on the FileRepository folder (had to accept each subfolder as a failure due to no access permissions to change sub folder’s permissions). Then I copied the 2 missing folders over to the «broken»
system. I removed the admin group (and left the default Everyone and System accounts) permissions.

• Proposed as answer by
  sniperdoc
  Tuesday, October 23, 2012 1:08 PM
• Marked as answer by
  Guowen Su
  Thursday, October 3, 2013 6:06 AM

if you have access to another machine with the same OS; try installing the driver on the second computer then take ownership of it like in the steps above. copy the desired driver folder from C:WindowsSystem32DriverStoreFileRepository then paste it
on your computer in the same location making sure to overwrite the old files. then in the registry make sure the infPath key is pointing to the correct .inf file. i had to do this because i had an older version of a print driver installed than the one used
on our print server. i could not get the driver uninstalled by normal means so i just copied the files for the new driver and put them where the old ones were. worked like a charm.

• Proposed as answer by
  thai land
  Monday, October 1, 2012 5:53 PM
• Marked as answer by
  Kevin Remde
  Thursday, July 16, 2015 9:27 AM

This case have already close. :0)

Guowen Su
Cisco Certified Network Associate
Cisco Certified Internetwork professional — MPLS
Certified Information Systems Security Professional
Microsoft Partner Network 2011
Microsoft Certified Professional
Microsoft Certified Systems Administrator:Security
Microsoft Certified Systems Engineer: Security
Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration
Microsoft Certified Technology Specialist: Windows 7, Configuring
Microsoft Certified IT Professional: Enterprise Administrator
Microsoft Certified IT Professional: Server Administrator
Certified Ethical Hacker
Computer Hacking Forensics Investigator
Certified Sonicwall Security Administrator
Microsoft Geeks

• Marked as answer by
  Guowen Su
  Thursday, October 3, 2013 3:25 AM