Other software and services have been updated.
If you use the flash drives for backup, then you don't need U3.
Are you familiar with Sysinternals? There's quite a learning curve, but yes you might pinpoint the issue.
What has been offered is fairly simple to test - that's where you'll get convincing information. But these are your decisions. Hope you find a solution, that's all I can think of right now.
The U3 Lauchpad has some special applications that are useful to me. I don't think it's causing the issue, but I would like to confirm that with something like Sysinternals.
I'm at the beginning of the learning curve on Sysinternals. I think it's a powerful tool. That's why I think it could pinpoint the issue. I've got a lot of reading to do before I can effectively use that tool on my own.
I'll remove the magicJack and see if I can still get the SanDisk USBs to not display properly in Disk Management. If I can duplicate the issue with the magicJack off the system, then I think that would confirm that the magicJack device is not causing the issue.
There was an unresolved bug in the magicJack software in Win 7 that I reported to magicJack tech support sometime ago and they were supposed to refer it to engineering. I started a thread on that issue, but no one responded. I contacted magicJack tech support yesterday to follow-up and they indicated that they had a major system update this past Tuesday that resolved a lot of issues. I checked the bug and it appears to be resolved.
What I noticed about the magicJack software in Win 7 was that it changed the Windows Driver Foundation - User-mode Driver Framework service startup from automatic to manual every time the magicJack device was removed and reinstalled, or just installed on the system with the system running. That issue appears to be resolved. When the Windows Driver Foundation service was in manual startup, I would get Event 219, Kernel-PnP error from a driver not loading on presumably the first attempt. If there were other USB devices attached, when the magicJack wasn't, the manual startup for that service would cause a similar error for that device. It seemed to cause the error one time for the first USB device attached to the system that it encountered. The only way to resolve this issue was to attach the magicJack device and let it load its software and then go into Services and manually change the Windows Driver Foundation service back to automatic start. It would stay that way until the magicJack device was removed and installed again. That issue now appears to be resolved; no more manually changing the service after each magicJack install.
Any other issues have been blamed on the magicJack device in the past should be duplicated now to confirm they're still valid now that the magicJack software system has had a major fix.
I've just removed the "free" Nero and Roxio applications that come with a DVD drive. These applications are the stripped down versions of the full product that have utilities for CD/DVD burning, label making, players, and other utilities. When I bought my DVD drives, Win 7 hadn't been released. I noticed I was getting a few Information posts in the Windows Log for the Applications that some component of these applications couldn't find a file or something, so I deleted the programs to resolve those issues.
Thanks for your help.
Regards
Quote