Reply
Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

[ Edited ]

hi everyone, 

 

I'm having WinXp Sp3 with MX 3200 logitech mouse and keyboard and is impossible to make the Logitech Unifying receiver to be detected. 4.80 version never had this problem - worked as a charm. I tried even the removal tool from logitech website, rebooted PC couple of times, 4.80 does not want to install as it says a newer version is detected. k, good, I install again latest 6 vers., installs sucessfully  and when I launch it, gets to the screen when it says now insert your unifying receiver and then click next. It never detects it and never get to click next. It's using some generic windows dirvers as basic functionality works, but not fully functional, as I cannot configure the zoom bottons of the mouse etc, as it does Not detect it to install the logitech drivers. I desperately need help. What are the steps to get this resolve once and for all? 

How do you remove the generic drivers from Windows, as it takes those prior detecting it - regardless of the USB port you try?

 

Thank you.

Regards, Pianist4Him.

Retired Logitech Employee / Moderator (Inactive)
Cintech
Posts: 3,154
Registered: ‎04-01-2011
0

Re: Logitech Unifying Receiver Not Detected

Hello Pianist4Him,

 

The MK320 Wireless Desktop is not packaged with a Unifying receiver. The MK320 uses the native USB drivers already present in your operating system. The MK320 will not be detected by SetPoint software or the Unifying connection utility no software is required. From your description, it seems that the MK320 is working as expected. If you are unhappy with the product please contact Logitech customer Care for your region. Please see: http://www.logitech.com/en-us/433/6232?softwareid=4338&osid=1&section=downloads

The Logitech® Connection Utility is only needed if you have replaced your receiver.

 

Best Regards,

.

 

Knowledgebase | Downloads + Get Parts | Contact Support | Manuals | Warranty | Rebate
If a reply adequately addresses your technical issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.
Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

sorry, my bad  I meant MX 3200 - which I know for certain it does require the setpoint software as I could configure the Zoom and custom buttons on the edge of the mouse, plus many monitoring tools as battery level would be displayed on your laptop.

 

That's exactly my issue - that windows starts installing the drivers by itself - some generic drivers and setpoint does Not detect that I introduced the receiver in the USB port.

 

Any solutions please?

It's so flat without the software and drivers from Logitech.

 

Thank you.

Retired Logitech Employee / Moderator (Inactive)
Cintech
Posts: 3,154
Registered: ‎04-01-2011
0

Re: Logitech Unifying Receiver Not Detected

Hello Pianist4Him,

 

From your description, it seems as if your are running the Unifying Connect utility. It also sounds like your MX 3200 is working, that means that the receiver is detected by the operating system. The MX3200 is not a Unifying device and the receiver for it will not show up in the Unifying Connect utility. Your issue sounds more like this: http://logitech-en-amr.custhelp.com/app/answers/detail/a_id/9165/~/my-mx-3200-cannot-be-customized-u...

Please post the M/N and P/N located on the bottom of the keyboard and inside battery compartment of the mouse.

 

Best Regards,

Knowledgebase | Downloads + Get Parts | Contact Support | Manuals | Warranty | Rebate
If a reply adequately addresses your technical issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.
Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

My mouse P/N is: 831803 - 0000 and thank you very much for the link - it seems like renaming that driver file to back after uninstalling using a tool which removes everything from registry completely, along with a restart, allowed me to install the 4.80 which I knew was working fine. I'm going to upgrade to 6 vers. after that.

 

Thank you for the quick replies - you have been helpful. :smileyhappy:

God bless,

 

Regards, Pianist4Him.

Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

Happy too soon... :smileysad:

 

Logs of the updater:

0.687: 2012/03/16 19:25:11.343 (local)
0.703: c:\3e8b7181ef8effe6e8595b19fad5e9\update\update.exe (version 6.3.4.0)
0.734: Hotfix started with following command line: /quiet
0.750: In Function GetBuildType, line 1170, RegQueryValueEx failed with error 0x2
0.797: C:\windows\system32\DRIVERS\wdf01000.sys is Present
0.844: FileVersion of C:\windows\system32\DRIVERS\wdf01000.sys is Greater Than 1.5.5600.0
0.844: Condition Check for Line 1 of PreRequisite returned FALSE
0.859: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
0.859: Wdf01005 Setup encountered an error: Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
0.875: ReadStringFromInf: UpdSpGetLineText failed: 0xe0000102
0.875: Setup cannot continue because one or more prerequisites required to install Wdf01005 failed. For More details check the Log File c:\windows\Wdf01005Inst.log
0.875: Update.exe extended error code = 0xf0f4
0.875: Update.exe return code was masked to 0x643 for MSI custom action compliance.

 

 

in the software when run, I have only Tools menu and i from Info which contains the software vers. update and about.

Trying updating directly.

 

App. Logs are:

 

116.218: SetupDiCallClassInstaller in CollectThirdPartyDriversFromDevice Failed with error: -536870387
121.843: SetupVerifyInfFile failed with error 0x490 for c:\windows\inf\oem15.inf of device {}\BLUETOOTHPORT\000
124.828: Failed to query DriverPath of {}\BTWDNDIS\1&30EE4AD&0&1000000020000 0x2
127.375: OEM file scan used 126282 ticks
127.406: AnalyzePhaseOne: used 126313 ticks
127.406: AnalyzeComponents: Hotpatch analysis disabled; skipping.
127.406: AnalyzeComponents: Hotpatching is disabled.
127.421: AnalyzePhaseTwo used 15 ticks
127.421: AnalyzePhaseThree used 0 ticks
127.421: AnalyzePhaseFive used 0 ticks
127.421: AnalyzePhaseSix used 0 ticks
127.421: AnalyzeComponents used 126328 ticks
127.421: Downloading 0 files
127.421: bPatchMode = FALSE
127.421: Inventory complete: ReturnStatus=0, 126328 ticks
127.421: Num Ticks for invent : 126328
127.421: Allocation size of drive C: is 4096 bytes, free space = 17598595072 bytes
127.421: Drive C: free 16783MB req: 7MB w/uninstall 0MB
127.421: CabinetBuild complete
127.421: Num Ticks for Cabinet build : 0
127.421: DynamicStrings section not defined or empty.
127.421: FileInUse:: Added to Filelist: c:\windows\wdf01005.cat
127.421: FileInUse:: Added to Filelist: c:\windows\system32\drivers\wdf01000.sys
127.687: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\wdf01005.cat
127.796: FileInUse:: PrintTasksUsingModule: No tasks found using c:\windows\system32\drivers\wdf01000.sys
128.859: LoadFileQueues: UpdSpGetSourceFileLocation for halmacpi.dll failed: 0xe0000102
129.375: PFE2: Not avoiding Per File Exceptions.
129.421: GetCatVersion: Failed to retrieve version information from C:\windows\system32\CatRoot\{}\Wdf01005.cat with error 0x80092004
129.421: GetCatVersion: Failed to retrieve version information from C:\windows\Wdf01005.cat with error 0x80092004
129.656: Copied file: C:\windows\system32\DRIVERS\wdf01000.sys
129.687: DoInstallation: Installing assemblies with source root path: c:\4293acc59968bd2bbf3342\
129.687: Num Ticks for Copying files : 2266
129.703: Num Ticks for Reg update and deleting 0 size files : 16
129.703: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is empty; nothing to do.
129.734: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

 

At least I know now which are the drivers files it uses.

Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

now, after trying couple of restarts and upgrade to 6.32, another error:

 

the file KHALMNPR.exe on logitech setpoint Driver disk is needed. Copy files from: C: program files common files logishrd cddrv2 

When click ok it cannot find the file, no matter the paths I tried.

 

Any help, any ideas. I'm close to give up and probably would be better to look to another vendor.

 

Thank you.

Regards, Pianist4Him.

Retired Logitech Employee / Moderator (Inactive)
Cintech
Posts: 3,154
Registered: ‎04-01-2011
0

Re: Logitech Unifying Receiver Not Detected

Hello Pianist4Him,

 

Since SetPoint 4.80 worked fine on your set up, I suggest removing SetPoint 6.32 and not updating it.

 

Best Regards,

Knowledgebase | Downloads + Get Parts | Contact Support | Manuals | Warranty | Rebate
If a reply adequately addresses your technical issue, please click on the "Accept as Solution" and "Give Kudos" button so this information can benefit other users via search.
Logi Browser
Pianist4Him
Posts: 7
Registered: ‎01-01-2012
0

Re: Logitech Unifying Receiver Not Detected

Hello, 

 

4.80 worked in a sense that the installation was completed, however, after running the systray Logitech software, I had only Tools menu and i from Info which contains the software vers. update and about. No section of settings at all, which means it still did not work properly - it did not detect properly the device. More over, now if I connect the logitech receiver, tries installing drivers for it and after the pop failing installing drivers window, today I got the BSOD and my PC restarted.

Any ideas you have from the logs I provided?

 

Can we get this escalated please, as I really want to use all the features of my mouse that used to be available when Unifying software was workng fine?

 

Thank you.

Regards, Pianist4Him.

MichaelKenward
Posts: 2,174
Topics: 15
Solutions: 103
Registered: ‎01-21-2007
0

Re: Logitech Unifying Receiver Not Detected

If you get nowhere here, you could try the official support channels.

 

Remember, this is a user-to-user forum, with only occasional input from Logitech's hired hands.

 

Use the "Contact Us" option in "Support". Depending on where you are, there may be an "email" option.

 

 

__________
MK
Just another customer.

M570, Cordless Trackball | Cordless Trackman Wheel | T650 Touchpad
K800, K360, K340 keyboards
QuickCam Pro 9000 | H600 headset
SetPoint Control Centre version: 6.52.74 | Driver version: 5.52.29
Windows 7 Home Premium 64-bit & 32-bit

If you find a solution to your problem, mark it as "solved". This assists people who are looking for help with their problems.