System Error 66 (0x42): ERROR_BAD_DEV_TYPE [Solved]

Make sure the command and listed path are correct

3 min. read

Published onSeptember 13, 2024

published onSeptember 13, 2024

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

TheERROR_BAD_DEV_TYPEsystem error, with code66 (0x42), is often encountered when using a DOS application to run a print command or adding/mapping a PSDrive. The error message reads,System Error 66: The network resource type is not correct.

The problem usually appears when you run an incorrect command, the connections are not in order, the firewall or security software conflicts with the operation, or you have set an incorrect path.

Before you start troubleshooting things, install all pending Windows updates, reconnect the printer, or reboot the device and try adding the PSDrive again.

How do I fix ERROR_BAD_DEV_TYPE?

1. Check the command for mistakes

If you are getting the66 (0x42) The network resource type is not correcterror while running thenet usecommand from a DOS window with administrative privileges, it could be mistakes within the command to blame.

First, make sure that you are using this command while replacingPrinterServerandPrinterNamewith the ones in your case:net use lpt1 \PrinterServer\PrinterName /persistent:yes

Also, for some users, replacing127.0.0.1asPrinterServerwith the actual printer server name did the trick!

2. Run the network troubleshooter

3. Check the path (if adding a new PSDrive)

If you are adding a newPSDrivefrom within an elevated Windows PowerShell, make sure the path listed in the command is correct.

For one user, adding a backslash () to the drive’s path triggeredERROR_BAD_DEV_TYPE The network resource type is not correcterror. This is because the target host was unreachable. So, check for such inaccuracies!

4. Temporarily disable the firewall

If the error message doesn’t appear again, check whetherPort 445is blocked in Windows Defender Firewall and open it. It’s not recommended to keep the firewall disabled for extended periods since this puts your PC at risk. So, this approach should only be used as a workaround!

5. Perform a system restore

When nothing else works, asystem restorewill fixSystem Error 66: ERROR_BAD_DEV_TYPE. You just have to pick the right restore point.

Before you leave, discover expert tips toeffectively manage printers and devicesand get the best performance!

For any queries or to share which fix worked for you, drop a comment below.

System Error 66 (0x42): ERROR_BAD_DEV_TYPE [Solved]#

How do I fix ERROR_BAD_DEV_TYPE?#

1. Check the command for mistakes#

2. Run the network troubleshooter#

3. Check the path (if adding a new PSDrive)#

4. Temporarily disable the firewall#

5. Perform a system restore#