Download Pentax USB Devices Driver

 

With our USB PC Driver for the SCUF Vantage and Vantage 2, PC games that support PlayStation® 4 controllers are now playable on Windows 7 and Windows 10. Step 1 – Installing the Driver For your Windows 7 or Windows 10 computer to recognize your SCUF Vantage or Vantage 2 as a PlayStation® 4 controller, you will first need to install our USB. Obtaining USB Drivers for your Wireless Device. Connect with us on Messenger. Visit Community. 24/7 automated phone system: call.611 from your mobile.

Download pentax usb devices driver win 7Download

Search this Thread
05-13-2011, 11:03 AM #1
Veteran Member

Location: NY
Device not recognized.
I am having major problems connecting my k5 and Kx to a computer. I have tried on three laptops 2 running windows 7 and one running XP.
I am continually getting the device not recognized message, sometimes it will connect only to fail after a few minutes at that point I get a rapid flashing of the top display on the K5. I really need to get this working as I want to use pktether for astro work.
Anyone else had this issue and if so how did you cure it.
Terry
05-13-2011, 11:12 AM #2
Junior Member


Location: Lat. N35°19'87' Long. W97°27'27'
Cable?
Originally posted by telfish
I am having major problems connecting my k5 and Kx to a computer. I have tried on three laptops 2 running windows 7 and one running XP.
I am continually getting the device not recognized message, sometimes it will connect only to fail after a few minutes at that point I get a rapid flashing of the top display on the K5. I really need to get this working as I want to use pktether for astro work.
Anyone else had this issue and if so how did you cure it.
Terry
Since it is two different cameras, have you tried a different cable?
05-13-2011, 11:28 AM #3
Veteran Member

Location: NY
Originally posted by jessecad
Since it is two different cameras, have you tried a different cable?
Yep, I have 3 cables, all are intermittent. I find if I restart the laptop then sometimes I can get things to work for a while.
05-13-2011, 12:46 PM #4
Senior Member

Location: Hilversum
Posts: 215
Do you have similar issues with other USB devices? Is your laptop old?
Check power saving options. Try pulling the battery (while shutdown), and boot up with just socket power.
05-13-2011, 01:25 PM #5
Veteran Member

Location: NY
Originally posted by Francis
Do you have similar issues with other USB devices? Is your laptop old?
Check power saving options. Try pulling the battery (while shutdown), and boot up with just socket power.
One is six months old win7 64 bit, one is two years old win 7 64 bit and the last is 5 years old XP 32 bit.
It's a bit of a mystery, If I re boot sometimes I can get them to recognize the cameras but mainly it's a device not recognized message
05-13-2011, 04:21 PM #6
Site Supporter


Location: Perth Western Australia
Posts: 35,571
It may pay to see if there are updated drivers for your USB ports and if so download and install them. I use Driver Detective which finds all the new drivers for my PC and believe me when I say updated drivers do make a difference.
Is there some major reason that you connect your cameras to the PC instead of using a Card Reader which is much faster?
05-13-2011, 09:08 PM #7
Veteran Member

Location: Fife, Scotland
Are you using a port on thr PC? If you are using a hub try without.
Also try cleaning up all your USB devices - there are 'ghost' ones around and this article is about how to show them in XP, I believe it works with W7 as well.
Device Manager does not display devices that are not connected to the Windows XP-based computer
Unplug as many USB devices as you can, then delete all the ones not in use in Device Manager.
It is, however, very strange that you have the same problem with multiple cameras and multiple PCs.
Also - do you have the same problem with any other kind of device?
And why is using a card reader faster than plugging the camera in? I've done both and not noticed a difference. I've also heard that a few folks who use a card reader have got carried away and forgotten to put the memory card back in the camera....
And PS - he wants to use PKTether, so he *has* to connect via USB.
05-14-2011, 02:22 AM #8
Senior Member

Location: Bristol, NY - Finger Lakes Region
Is this a new problem that you have just noticed since you have been connecting to your PC with a Kx for a long time? Not knowing more I would think that what you stated has always been the case.
You do know that if your cameras is in power save mode when you try to connect you will get
'Device Not Recognized' because Windows can not detect a USB device that is 'OFF'? Close the connect window on your PC-Give a tap to your camera shutter button to power on camera and Windows will auto-detect your camera same as it does with any other USB device.
Also in the K5 menus set 'Auto Power Off' to 'OFF' and see if this issue is resolved. Then you know to do the first thing I suggested when you have the 'Auto Power Off' feature set to some time length and your camera is in power save mode when you try to connect.
Good luck.
Last edited by jcp5; 05-14-2011 at 04:06 AM.
05-14-2011, 06:03 AM #9
Veteran Member


Location: Houston TX
Posts: 2,129
Originally posted by cats_five
And why is using a card reader faster than plugging the camera in? I've done both and not noticed a difference. I've also heard that a few folks who use a card reader have got carried away and forgotten to put the memory card back in the camera....
And PS - he wants to use PKTether, so he *has* to connect via USB.
One reason I've heard many times is that the USB connection on the camera (older models - don't know if this is still true) was prone to failure from repeated connection/disconnection. Other than that, for retrieving pictures I guess it's just personal preference. I've always used a card reader to avoid problems like the OP is having.
Of course, when you're trying to tether, that's a bit of a problem...
05-14-2011, 10:24 AM #10
Veteran Member

Location: NY
Originally posted by eaglem
It may pay to see if there are updated drivers for your USB ports and if so download and install them. I use Driver Detective which finds all the new drivers for my PC and believe me when I say updated drivers do make a difference.
Is there some major reason that you connect your cameras to the PC instead of using a Card Reader which is much faster?
I am wanting to use Pktether in order to remote control my camera when it's on my telescope, I would not use it for file transfer.
USB drivers are up to date.
Thanks
Terry
05-14-2011, 10:29 AM #11
Veteran Member

Location: NY
Originally posted by Highland
Is this a new problem that you have just noticed since you have been connecting to your PC with a Kx for a long time? Not knowing more I would think that what you stated has always been the case.
You do know that if your cameras is in power save mode when you try to connect you will get
'Device Not Recognized' because Windows can not detect a USB device that is 'OFF'? Close the connect window on your PC-Give a tap to your camera shutter button to power on camera and Windows will auto-detect your camera same as it does with any other USB device.
Also in the K5 menus set 'Auto Power Off' to 'OFF' and see if this issue is resolved. Then you know to do the first thing I suggested when you have the 'Auto Power Off' feature set to some time length and your camera is in power save mode when you try to connect.
Good luck.
That makes sense, I will try the power on feature to keep the camera 'alive'. Not used the USB connect before as I ue a built in card reader in both my desktop and latest laptop. So not sure if the KX has always had this issue. It is intermittent so it may be the power saving thing as you say.
Regards
Terry
05-14-2011, 11:06 AM #12
Veteran Member

Location: NY
I think I have discovered what the issue is. I think PK tether is causing the camera to hang, when it hangs I have been trying to get the laptop to recognize it but because it is not sending the right connection data the laptop is unable to sense what device it is. If I remove the battery from the camera and reset it then it is recognized right away.
This probably is a bug within PK tether, there are a few bugs that need to be dealt with, it's still fine software and it's good to have a way to control the camera remotely.
05-14-2011, 02:58 PM #13
Veteran Member


Location: Houston TX
Posts: 2,129
Originally posted by telfish
I think I have discovered what the issue is. I think PK tether is causing the camera to hang, when it hangs I have been trying to get the laptop to recognize it but because it is not sending the right connection data the laptop is unable to sense what device it is. If I remove the battery from the camera and reset it then it is recognized right away.
This probably is a bug within PK tether, there are a few bugs that need to be dealt with, it's still fine software and it's good to have a way to control the camera remotely.
I'm glad you're helping to sort it out. I don't need tethering right now, but may need it in the future. Since it doesn't look like Pentax is going to offer tethering, the next best thing is for users to get behind this developer and help make his software what we need. Good luck!
05-14-2011, 03:17 PM #14
Veteran Member

Location: NY
Originally posted by Highland
I did not know that PK tether was in use here so my post only applied to standard USB connect with the K5 type of use.
We know the K5 does not support tethering which means there is no tether feature to turn on in the camera which means removing the battery must give PK tether that one shot recognition that the camera has connected.
We also know the tethering software requires more then Windows USB auto-detect to work. I think you are dealing with a camera requirement and PK tether will tell you that and K5 does not have it.
I am just trying to give you some ideas here as I really don't know PK Tether requirements.
I would suggest you contact the makers of PK tether if they have a support path. They will likely tell you if your camera does not support tethering then the thing you do with the battery is as good as gets. You should hear that from them to be sure. Talk to someone that has a camera that supports tethering and you can verify that this feature has to be turned on in the camera menus to connect properly with PK tether as I think it would. That's all I got.

If windows (7 or XP) recognizes the camera (KX or K5) then PK tether also recognizes it and works fine, unfortunately there are a few bugs still in the program, it's currently a beta and has been a beta for some time. I am guessing the developer has limited time and incentive to complete it. I have donated to his paypal to encourage him and I recommend every user to do the same.
When Pk tether stops responding the camera hangs, nothing short of removing the battery will get the camera back from it's connection mode. That mode starts automatically when you plug the USB lead into a PC.
When you reset the camera it once again is recognized and you can re start PK tether. If you toggle the power switch you just get the device not recognized message.
So it's purely a PKtether issue, normal file transfer is fine.
I still wish Pentax would develop an official tethering program, It's not good for a semi pro camera not to have that facility.

«K-5 and Infrared | My K5 was firmare 1.01 and I updated to 1.03...now the playback is super delayed»

Tags - Make this thread easier to find by adding keywords to it!
camera, device, dslr, k-5, k-5 ii, k-5 iis, k5, pentax k-5

Similar Threads
ThreadThread StarterForumRepliesLast Post
Pentax K-x lens not recognized/others malfunctions.steezylisticTroubleshooting and Beginner Help1301-05-2012 08:23 PM
Sigma 10-20mm/4-5.6 not recognized by K-5lockheedPentax K-51410-31-2011 08:27 AM
Dowload devicePapouPentax Camera and Field Accessories405-17-2010 02:30 PM
K20D Not Recognized by Remote AssistanceLeeHollidayPentax SLR Lens Discussion408-25-2009 01:15 PM
Pentax-A 28-80 3.5-4.5 but f3.5 not recognized?imtheguyPentax SLR Lens Discussion808-10-2009 09:17 PM


Download Pentax Usb Devices Drivers

  • November 27, 2020 5.0.1

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    5.0.1

    Released

    November 27, 2020

    Type

    EXE

    Filesize

    7.5MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added support for DFG/HDMI converter.
    2. Added support for Windows 10 Device-Guard.
  • February 24, 2020 4.9.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.9.0

    Released

    February 24, 2020

    Type

    EXE

    Filesize

    7.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed Gamma not working.
    2. Fixed Polarization formats PPB1 320x240 creating an error on some CPUs.
  • January 31, 2020 4.8.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.8.0

    Released

    January 31, 2020

    Type

    EXE

    Filesize

    7.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Updated driver's FilterPackage to version with fix for saved Y800 image images being flipped
    2. Fixed Tonemapping not working after switching from YUY2 to RGB64 video format.
  • November 8, 2019 4.7.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.7.0

    Released

    November 8, 2019

    Type

    EXE

    Filesize

    7.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added support for polarization cameras.
    2. Fixed error on umcompressed Y800 AVI Capture.
  • August 22, 2019 4.6.2

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.6.2

    Released

    August 22, 2019

    Type

    EXE

    Filesize

    6.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fully reworked image transfer pipeline.
  • December 4, 2018 4.5.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.5.0

    Released

    December 4, 2018

    Type

    EXE

    Filesize

    6.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. General bugfixes.
  • November 14, 2018 4.4.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.4.0

    Released

    November 14, 2018

    Type

    EXE

    Filesize

    6.2MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Changed the way Directshow time stamps are generated.
    2. Fixed force_avg_time_per_frame not fully working for all programs.
  • September 13, 2018 4.3.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.3.0

    Released

    September 13, 2018

    Type

    EXE

    Filesize

    6.1MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added tone mapping for 8 bit video formats.
    2. Fixed Gamma and Saturation saving issue, e.g. Saturation being 0.
    3. Fixed an issue with respect to ffmpeg.
    4. Fixed hibernate and suspend behavior.
  • January 22, 2018 4.2.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.2.0

    Released

    January 22, 2018

    Type

    EXE

    Filesize

    6.1MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added Directshow driver property pages for several 33U properties.
    2. Fixed Contrast on YUY2/Y411
    3. Improved performance of Tonemapping
    4. Fixed very rare Bluescreen
  • October 17, 2017 4.1.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.1.0

    Released

    October 17, 2017

    Type

    EXE

    Filesize

    5.8MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Added support for 38U cameras.
    2. Faster Pause/Continue.
    3. Fixed some stability problems.
  • July 5, 2017 4.0.6

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.0.6

    Released

    July 5, 2017

    Type

    EXE

    Filesize

    5.9MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed tone mapping for some camera models.
  • May 2, 2017 4.0.4

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.0.4

    Released

    May 2, 2017

    Type

    EXE

    Filesize

    6MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Fixed an OpenCV compatibility issue.
    2. Enabled DMK J003 pattern fix.
  • February 21, 2017 4.0.2

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.0.2

    Released

    February 21, 2017

    Type

    EXE

    Filesize

    5.8MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Removed unnecessary properties.
  • February 9, 2017 4.0.1

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    4.0.1

    Released

    February 9, 2017

    Type

    EXE

    Filesize

    5.8MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. Complete redesign of driver architecture.
    2. Signature corrected for Windows 10 AU.
    3. Enhanced Tone Mapping.
  • August 8, 2016 3.1.0

    Device Driver for all 33U, 37U, 38U series, polarization USB cameras and the DFG/HDMI converter.

    Version

    3.1.0

    Released

    August 8, 2016

    Type

    ZIP

    Filesize

    2.4MB

    Requirements

    • Intel Core i3 or similar, 2 GB RAM
    • USB 3.0 controller
    • Graphics card with 24 or 32 bit
    • Windows 7 (32 & 64 bit), Windows 8 (32 & 64 bit), Windows 10 (32 & 64 bit)
    • DirectX 9.0c or higher

    Changelog

    1. First release