Win7 will not connect to camera - device driver error 31

[slate_leeper]

Troubleshooting I've done:

First, using the camera and the same USB cable, I plugged it into an
XP Windows computer. Everything worked fine. As it used to do on my
Windows 7 (32 bit) computer. The Win-7 computer has not had any
changes other than updates to the Tax-Cut software plus whatever
Microsoft has done with automatic updates.

Next, using my Windows 7 computer:

1) Plug in camera to USB port (port works with other devices, also
tried two other ports)
2) Turn on camera
3) Pop-up message: Your device driver was not properly installed.
Click here for details.
Details box: "Please consult with your device
manufacturer...." MTP USB device
4) Using Windows device manager:
1) Right-click MTP USB device (which has a yellow
exclamation-point icon on it)
2) Select "update driver software"
Result: "The best driver software for your device is already
installed" MTP USB device
3) Right click again, select uninstall
4) Scan for hardware changes
Go back to #3 above, Pop-up message....

5) Right click MTP device
1) Select properties / driver
2) Click update driver, select automatically (defaults to
folder Windows/System32)
Result" Best device driver already installed...."

5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)

6) Roll back driver is grayed out.

The only thing I can see here that looks strange is the WUDFRd.sys
driver, which says win8 after it instead of win7.

Note that the camera is shown in Device Manager under "portable
devices." Also under this heading is the ScanDisc card reader, which
has the same problem and also used to work.


Help!


--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.

 

[ray carter]

Troubleshooting I've done:

First, using the camera and the same USB cable, I plugged it into an XP
Windows computer. Everything worked fine. As it used to do on my Windows
7 (32 bit) computer. The Win-7 computer has not had any changes other
than updates to the Tax-Cut software plus whatever Microsoft has done
with automatic updates.

Next, using my Windows 7 computer:

1) Plug in camera to USB port (port works with other devices, also tried
two other ports)
2) Turn on camera 3) Pop-up message: Your device driver was not properly
installed. Click here for details.
Details box: "Please consult with your device
manufacturer...." MTP USB device 4) Using Windows device manager:
1) Right-click MTP USB device (which has a yellow
exclamation-point icon on it)
2) Select "update driver software"
Result: "The best driver software for your device is already
installed" MTP USB device
3) Right click again, select uninstall 4) Scan for hardware changes
Go back to #3 above, Pop-up message....

5) Right click MTP device
1) Select properties / driver 2) Click update driver, select
automatically (defaults to
folder Windows/System32)
Result" Best device driver already installed...."

5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)

6) Roll back driver is grayed out.

The only thing I can see here that looks strange is the WUDFRd.sys
driver, which says win8 after it instead of win7.

Note that the camera is shown in Device Manager under "portable
devices." Also under this heading is the ScanDisc card reader, which has
the same problem and also used to work.


Help!

I don't understand why you'd want to connect the camera. An inexpensive
USB card reader will work on most every system - including MAC and Linux
- and save the camera batteries.

 

[Wolf K]

On 1/31/2013 1:20 PM, ray carter wrote:
[snip tale of woe from OP]

I don't understand why you'd want to connect the camera. An inexpensive
USB card reader will work on most every system - including MAC and Linux
- and save the camera batteries.

You connect the camera because that's what it's set up to do. On every
system. Also, repeatedly removing and reinserting flash cards can damage
the contacts. As for saving batteries: leaving the flash set on Auto,
and the "review" at the default 3 seconds, wastes a lot more power than
transferring pictures via USB cable.

That being said, I have no idea why OP's camera won't play nice with Win
7. Maybe it needs a firmware upgrade.

 

[Gene E. Bloch]

I don't understand why you'd want to connect the camera. An inexpensive
USB card reader will work on most every system - including MAC and Linux
- and save the camera batteries.

There are numerous reasons to connect a camera to a computer besides
reading a memory card.

For instance, some cameras can be controlled by a computer, while other
cameras are webcams and don't even have memory cards.

The OP gave us no information that I can find that would resolve those
questions.

OP: I noticed this in your post: "Please consult with your device
manufacturer". Why don't you do that, i.e., go to their site to see if
you can find drivers appropriate for your OS?

 

[Char Jackson]

Troubleshooting I've done:

First, using the camera and the same USB cable, I plugged it into an
XP Windows computer. Everything worked fine. As it used to do on my
Windows 7 (32 bit) computer. The Win-7 computer has not had any
changes other than updates to the Tax-Cut software plus whatever
Microsoft has done with automatic updates.

Next, using my Windows 7 computer:

1) Plug in camera to USB port (port works with other devices, also
tried two other ports)
2) Turn on camera
3) Pop-up message: Your device driver was not properly installed.
Click here for details.
Details box: "Please consult with your device
manufacturer...." MTP USB device
4) Using Windows device manager:
1) Right-click MTP USB device (which has a yellow
exclamation-point icon on it)
2) Select "update driver software"
Result: "The best driver software for your device is already
installed" MTP USB device
3) Right click again, select uninstall
4) Scan for hardware changes
Go back to #3 above, Pop-up message....

5) Right click MTP device
1) Select properties / driver
2) Click update driver, select automatically (defaults to
folder Windows/System32)
Result" Best device driver already installed...."

<SNIP>

In addition to the other responses:

I can't be of much help, but perhaps instead of choosing to automatically
find the best driver, (Step 5.2 above), which as you discovered is resulting
in loading a driver from your System32 folder, you might try manually
finding and installing a driver from the camera manufacturer's website. That
might give you a driver that's newer or older than what you have now, with
the point being that it's at least different from what you have now.

 

[Irwell]

<SNIP>

In addition to the other responses:

I can't be of much help, but perhaps instead of choosing to automatically
find the best driver, (Step 5.2 above), which as you discovered is resulting
in loading a driver from your System32 folder, you might try manually
finding and installing a driver from the camera manufacturer's website. That
might give you a driver that's newer or older than what you have now, with
the point being that it's at least different from what you have now.

Probably doing a System Restore to a date when everything
worked would rectify the situation.

 

[Char Jackson]

Probably doing a System Restore to a date when everything
worked would rectify the situation.

It might, but I've never been a fan of System Restore and in my opinion, SR
gets used far too often, usually for trivial things. When you do a System
Restore, you have no idea what all is being changed. It's a total crap
shoot, so I've always avoided it.

 

[Paul]

Troubleshooting I've done:

First, using the camera and the same USB cable, I plugged it into an
XP Windows computer. Everything worked fine. As it used to do on my
Windows 7 (32 bit) computer. The Win-7 computer has not had any
changes other than updates to the Tax-Cut software plus whatever
Microsoft has done with automatic updates.

Next, using my Windows 7 computer:

1) Plug in camera to USB port (port works with other devices, also
tried two other ports)
2) Turn on camera
3) Pop-up message: Your device driver was not properly installed.
Click here for details.
Details box: "Please consult with your device
manufacturer...." MTP USB device
4) Using Windows device manager:
1) Right-click MTP USB device (which has a yellow
exclamation-point icon on it)
2) Select "update driver software"
Result: "The best driver software for your device is already
installed" MTP USB device
3) Right click again, select uninstall
4) Scan for hardware changes
Go back to #3 above, Pop-up message....

5) Right click MTP device
1) Select properties / driver
2) Click update driver, select automatically (defaults to
folder Windows/System32)
Result" Best device driver already installed...."

5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)

6) Roll back driver is grayed out.

The only thing I can see here that looks strange is the WUDFRd.sys
driver, which says win8 after it instead of win7.

Note that the camera is shown in Device Manager under "portable
devices." Also under this heading is the ScanDisc card reader, which
has the same problem and also used to work.


Help!

At one time, updating a copy of Windows Media Player, was how a person
acquired a copy of the MTP (Media Transfer Protocol) driver. Surely,
a strange way to get a driver. On the later OSes, they should have
included such a driver in the baseline OS.

Delivering software that way, doesn't exactly make it easy to trace
the source of a problem. Drivers should be distributed as... drivers.
What a novel concept. Imagine, if say, that driver had its own entry
in Add/Remove.

This bothers me a tiny bit, because it seems to be a user mode driver
framework. And it's functionality might have to match the details of
the kernel it's being run on. So while on the one hand, I could wave
my hand and say "you got the latest and greatest", on the other hand,
the API in there might have to match your Windows 7 kernel. Like you,
this bothers me a tiny bit, and I don't know what to make of it.
You could find the file in question, do properties on it, and see if
any other detail is available to indicate it's some kind of universal
solution, rather than being intended as OS specific.

E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)

It could have come in with a Windows Media Player, but depending on
how such things install, there might not be enough "bread crumbs"
to figure it all out. Check your updates, for anything Windows Media Player
related.

Rolling back the OS would be one solution, but who knows how far
you'd have to go back.

Paul

 

[charlie]

There are numerous reasons to connect a camera to a computer besides
reading a memory card.

For instance, some cameras can be controlled by a computer, while other
cameras are webcams and don't even have memory cards.

The OP gave us no information that I can find that would resolve those
questions.

OP: I noticed this in your post: "Please consult with your device
manufacturer". Why don't you do that, i.e., go to their site to see if
you can find drivers appropriate for your OS?

For reasons unknown, some of the cameras have problems connecting via
USB. It's not an isolated problem, and has been going on for quite some
time. Sometimes uninstalling the camera software and divers, along with
the USB port and it's drivers, then doing a cold boot and reinstalling
the usb stuff, rebooting again, then installing the camera specific
software and drivers work. The is still the chicken and egg situation
with some, even with win 7. (Install the software and drivers, and plug
the camera in, or plug the camera in and hope that the software and
drivers install via the automated windows process.

One of my older cameras, an Olympus C8080, has three modes of operation
via USB. USB Storage, Remote Control, and a Test/Setup mode. Getting it
to work in all modes is difficult, even in XP.

 

[Rob]

Troubleshooting I've done:

First, using the camera and the same USB cable, I plugged it into an
XP Windows computer. Everything worked fine. As it used to do on my
Windows 7 (32 bit) computer. The Win-7 computer has not had any
changes other than updates to the Tax-Cut software plus whatever
Microsoft has done with automatic updates.

Next, using my Windows 7 computer:

1) Plug in camera to USB port (port works with other devices, also
tried two other ports)
2) Turn on camera
3) Pop-up message: Your device driver was not properly installed.
Click here for details.
Details box: "Please consult with your device
manufacturer...." MTP USB device
4) Using Windows device manager:
1) Right-click MTP USB device (which has a yellow
exclamation-point icon on it)
2) Select "update driver software"
Result: "The best driver software for your device is already
installed" MTP USB device
3) Right click again, select uninstall
4) Scan for hardware changes
Go back to #3 above, Pop-up message....

5) Right click MTP device
1) Select properties / driver
2) Click update driver, select automatically (defaults to
folder Windows/System32)
Result" Best device driver already installed...."

5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)

6) Roll back driver is grayed out.

The only thing I can see here that looks strange is the WUDFRd.sys
driver, which says win8 after it instead of win7.

Note that the camera is shown in Device Manager under "portable
devices." Also under this heading is the ScanDisc card reader, which
has the same problem and also used to work.


Help!

I would suggest that you load the drivers that came with the camera on
the cd -

first delete the yellow marked device from the device manager

Stick the CD in the slot which came with the camera.

Connect the camera turn it on and force the computer to find the device
driver on the CD.

You can have BTW some devices which MS say are ok and working but aren't
because MS can't supply drivers for each and every device they are only
generic. Like printers scanners etc.

 

[slate_leeper]

There are numerous reasons to connect a camera to a computer besides
reading a memory card.

For instance, some cameras can be controlled by a computer, while other
cameras are webcams and don't even have memory cards.

The OP gave us no information that I can find that would resolve those
questions.

OP: I noticed this in your post: "Please consult with your device
manufacturer". Why don't you do that, i.e., go to their site to see if
you can find drivers appropriate for your OS?

Been there, done that. No new drivers. In fact Canon specifically
specifies that no special drivers at all are needed with Windows 7.

RE: reading cards - the same error exists for the computer's bulit-in
card reader. Both are listed in Device Manager as "Portable Devices."
The card reader used to be listed as "Drive I:" but is now listed as
WPD File System Volume Driver, with the yellow exclamation point icon
on it. Since both devices are "WPD," and both stopped working at the
same time, and both give the same results when trying to update
drivers, I am assuming that the same solution would fix both (if we
can find one).

-dan z-



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.

 

[slate_leeper]

<SNIP>

In addition to the other responses:

I can't be of much help, but perhaps instead of choosing to automatically
find the best driver, (Step 5.2 above), which as you discovered is resulting
in loading a driver from your System32 folder, you might try manually
finding and installing a driver from the camera manufacturer's website. That
might give you a driver that's newer or older than what you have now, with
the point being that it's at least different from what you have now.

Another poster made the same suggestion. Canon states for this camera
no special drivers are needed when using Windows 7, and that they are
built in to standard Win7.



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.

 

[slate_leeper]

You could find the file in question, do properties on it, and see if
any other detail is available to indicate it's some kind of universal
solution, rather than being intended as OS specific.

E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)

It says created 07/25/12 and installed 12/10/12 (which is when I
installed Win7 Pro on the computer. It is for "Windows Driver
Foundation, user mode." There are no previous versions. All security
tabs allow read and execute. Only "trusted installer" can write or
modify.

It could have come in with a Windows Media Player, but depending on
how such things install, there might not be enough "bread crumbs"
to figure it all out. Check your updates, for anything Windows Media Player
related.

Rolling back the OS would be one solution, but who knows how far
you'd have to go back.

Paul

I have no restore point old enough. Besides, that would eliminate the
Tax-Cut download of my state program. I'm sure they would want me to
pay for it again,

-dan z-



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.

 

[Rob]

snip getting too long

Another poster made the same suggestion. Canon states for this camera
no special drivers are needed when using Windows 7, and that they are
built in to standard Win7.

What you may have to do is reset the USB ports.

MS have a Fixit solution on there site unsure which one it is to get but
have a look up problem solutions.

Google this - "microsoft W7 resetting usb ports" just to get started

or

http://preview.tinyurl.com/ab9yl3k

which is this page

https://www.google.com.au/search?q=...s=org.mozilla:en-US:official&client=firefox-a

 

[Jan Alter]

What about the idea of doing a system repair with the win 7 operating system
disk?

--
Jan Alter
(e-mail address removed)

I would suggest that you load the drivers that came with the camera on
the cd -

first delete the yellow marked device from the device manager

Stick the CD in the slot which came with the camera.

Connect the camera turn it on and force the computer to find the device
driver on the CD.

You can have BTW some devices which MS say are ok and working but aren't
because MS can't supply drivers for each and every device they are only
generic. Like printers scanners etc.

How about the idea of doing a system repair with the win 7 operating system
disk?
That may restore USB functionality without losing any data.
Of course, before trying this, I would make an image backup of the
drive.

 

[Wolf K]

On 1/31/2013 12:21 PM, slate_leeper wrote:
[...]

5) Driver details:
E:\Windows\system32\DRIVERS\UMDF\WpdMtpDr/dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\DRIVERS\winusb.sys
6.1.7601.17514 (win7sp_1rtm.101119-1850)
E:\Windows\system32\DRIVERS\WUDFRd.sys
6.2.9200.16384 (win8_rtm.120725-1247)
E:\Windows\system32\WpdMtp.dll
6.1.7600.16385 (win7_rtm.090713-1255)
E:\Windows\system32\WpdMtpUS.dll
6.1.7600. (win7_rtm.090713-1255)

[...]

????
I note:
a) WpdMtpUS.dll
b) WpdMtp.dll
They are not equivalent, as their names and version numbers
indicate.Which of these is supposed to be loaded for your camera? What
do the registry keys point to? Is there a key conflict? Are both drivers
loaded? Etc. There's some kind of conflict here, IMO.

I vote with the people who suggest uninstalling/reinstalling. Since
"reinstall" in W7 means letting W7 find the correct driver, this should
work. I'd delete all camera related keys first. W7 will create whatever
keys are needed when you reinstall. I'd also move the *.dlls to a safe
place to force W7 to find the correct one "on the web" during reinstall.
Alternatively, one could try them out one at a time.

Good luck.

 

[Paul]

It says created 07/25/12 and installed 12/10/12 (which is when I
installed Win7 Pro on the computer. It is for "Windows Driver
Foundation, user mode." There are no previous versions. All security
tabs allow read and execute. Only "trusted installer" can write or
modify.



I have no restore point old enough. Besides, that would eliminate the
Tax-Cut download of my state program. I'm sure they would want me to
pay for it again,

-dan z-

On my laptop, I don't generally install the optional Windows 7 updates.

What I found waiting in that (optional) section was:

KB2685811 Kernel Mode Driver Framework
KB2685813 User Mode Driver Framework

On the User Mode one ('13), on the KB webpage for that update, one
of the files listed is

http://support.microsoft.com/kb/2685813

wudfrd.sys 6.2.9200.16384

which by numbering, is a Windows 8 file, yet the framework
update is for OSes previous to Windows 8. So it looks like an
attempt to bring the other OSes up to the same framework design.
So that's an optional update listed in Windows update on my
Windows 7 laptop.

You could check your Windows Updates, see if both '11 and '13 are installed.
I don't know if the two updates are coupled together in some way, but
I listed both of them anyway so you'd know of their existence. The
Kernel mode portion would run in Ring0, the User portion in Ring3,
so they're separate portions of a software stack. A good design
might have the updates function independently (i.e. new API only
works, after both are installed), so there may not be any evidence
you have to do both at the same time.

And that's only important, if you think somehow that wudfrd.sys file
is involved in this puzzle.

Paul

 

[Gene E. Bloch]

Been there, done that. No new drivers. In fact Canon specifically
specifies that no special drivers at all are needed with Windows 7.

RE: reading cards - the same error exists for the computer's bulit-in
card reader. Both are listed in Device Manager as "Portable Devices."
The card reader used to be listed as "Drive I:" but is now listed as
WPD File System Volume Driver, with the yellow exclamation point icon
on it. Since both devices are "WPD," and both stopped working at the
same time, and both give the same results when trying to update
drivers, I am assuming that the same solution would fix both (if we
can find one).

-dan z-

OK, sorry for my assumptions. For one thing, what you wrote above makes
me think of a laptop. In any case, AFAIK, the built-in card readers are
also USB devices, but connected internally to a USB bus.

I have had problems with USB on two cases (literally, cases, i.e.,
boxes) where the cases' built-in USB ports, which plugged into the
motherboard headers via a captive cable, couldn't be made to work (it
was the same motherboard). In one case, I ended up adding a new USB2
port with its own cable to the front panel and that one worked OK. In
the other case, it was the front panel USB3 that was a problem. I
finally decided it was the motherboard's USB3 header and installed a
different kind of USB3connection using a PCI slot.

Maybe the above will point you into a direction that you haven't tried
(or at least, again, haven't mentioned).

 

[slate_leeper]

OK, sorry for my assumptions. For one thing, what you wrote above makes
me think of a laptop. In any case, AFAIK, the built-in card readers are
also USB devices, but connected internally to a USB bus.

I have had problems with USB on two cases (literally, cases, i.e.,
boxes) where the cases' built-in USB ports, which plugged into the
motherboard headers via a captive cable, couldn't be made to work (it
was the same motherboard). In one case, I ended up adding a new USB2
port with its own cable to the front panel and that one worked OK. In
the other case, it was the front panel USB3 that was a problem. I
finally decided it was the motherboard's USB3 header and installed a
different kind of USB3connection using a PCI slot.

Maybe the above will point you into a direction that you haven't tried
(or at least, again, haven't mentioned).

In the ASUS, both the card reader and the two front-panel USB ports
connect to the motherboard, the card reader through a different cable
to a different socket. There are two other USB ports on the back panel
(other than the ones with the track ball and keyboard devices plugged
in). I have tried all four of the free USB ports.

Also, since my last post I have reinstalled the AMD driver set, which
includes audio, video, USB, USB3 and PC-BUS. No improvement. Same
symptoms.

Thanks for your thoughts. Keep 'em coming. We'll figure this out yet.

-dan z-



--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.

 

[slate_leeper]

On my laptop, I don't generally install the optional Windows 7 updates.

What I found waiting in that (optional) section was:

KB2685811 Kernel Mode Driver Framework
KB2685813 User Mode Driver Framework

On the User Mode one ('13), on the KB webpage for that update, one
of the files listed is

http://support.microsoft.com/kb/2685813

wudfrd.sys 6.2.9200.16384

which by numbering, is a Windows 8 file, yet the framework
update is for OSes previous to Windows 8. So it looks like an
attempt to bring the other OSes up to the same framework design.
So that's an optional update listed in Windows update on my
Windows 7 laptop.

You could check your Windows Updates, see if both '11 and '13 are installed.
I don't know if the two updates are coupled together in some way, but
I listed both of them anyway so you'd know of their existence. The
Kernel mode portion would run in Ring0, the User portion in Ring3,
so they're separate portions of a software stack. A good design
might have the updates function independently (i.e. new API only
works, after both are installed), so there may not be any evidence
you have to do both at the same time.

And that's only important, if you think somehow that wudfrd.sys file
is involved in this puzzle.

Paul

In the list of updates is the Kernel Mode Driver Framework, but it
says it was installed in early December (that's when Win-7 Pro was
first installed on this machine). Probably not the problem, as the
camera connection worked fine until very recently.

The UMD Framework update I didn't see.




--
Protect your civil rights!
Let the politicians know how you feel.
Join or donate to the NRA today!
http://membership.nrahq.org/default.asp?campaignid=XR014887

Gun control is like trying to reduce drunk driving by making it tougher for sober people to own cars.