Showing 1 of 1136 conversations about:
View Full Discussion
I'm having problems with "Device not recognized" - even with installed driver.
It's listed as "Unknown device" with error "Windows has stopped this device because it has reported problems. (Code 43)".
Even on linux it doesn't work...
CEntrance support is so far unresponsive - after 2 months still waiting for a reply (to a different issue).
Firmware update tool comes out tommorow.
I've tested it and the new firmware fixes the USB recognition . Problem is that you need to find a port that doesn't complain first.
Found it, just one USB post that works!
Really strange issue...
Thanks a lot for the info, since I'm unable to send it back right now. Good thing all that's needed is a FW update. Is it going to be released here on on CEntrance website?
EDIT: It's still not working in Windows: "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
However it plays fine under Linux, at least it was not DOA.
Install windows updates and digital signature message will go away.
I'm surprised nobody has responded to the other issue. Please email info at CEntrance dot com. Probably email glitch. We usually reply within 24 hours.
My Windows machine is always offline, installing windows updates is both messy and risky considering the recently released telemetry KB's. Is there any workaround?
Hey, check out my posts on page 29 of the comments, might have the info you need :)
Edit: I get that you seem to be against windows updates for some personal reasons? You can always uninstall offending updates individually, you know ;) . If both KBs fail to update you are likely missing some prerequisite windows updates... Are you at least on the latest service pack for win7x64?
Sorry I struggle to relate to the anti-windows update stance nowadays as a sysadmin in a 99% windows environment... I find it fairly straightforward to research and choose to ignore (or rollback) individual updates (telemetry, windows 10 notifications, etc) while still staying safe and current. The KBs listed allow windows 7 to recognize a higher encryption for digital driver signing than previously recognized, and they likely rely on other incremental security patches that your OS is missing. (Although I'm not dual booting or running GRUB as a boot loader so I can't verify) Firmware updater might be failing for similar reasons (OS funtion and compatibility may be limited due to elective omission of unknown relevant patches)
Nope, KB3033929 is independent package, and it failed to install on all my Win7 machines, not just single one. Firmware update likely fails due to K32EnumProcesses call to kernel32 - this call is not supported by Win 5.1 kernel (XP) and triggers not valid Win32 application dialogue.
32-bit updater coming soon. It was a lower priority. So far we have one request (yours) and will be working on that. But if you have access to a VM or a mac, use that in the meantime. Seems like you know what you are doing. Linux will not be supported for firmware updates (not enough customers on Linux).
Hey asymcon, I fought with this for a few days, so I feel your pain... My affected Windows 7 PC didn't receive those KBs through Automatic Updates because it's on a domain using WSUS, and it looks like these updates got omitted during the normal update process. (home PC with Windows 7x64 was fine)
Are you using GRUB as a bootloader on all your Win7 machines? People's anecdotal info makes it seem like booting info win 7 via GRUB could trigger your symptom. In that scenario I'd set BIOS to boot directly to the Windows 7 x64 partition to install these updates, then you can revert back to your normal config though GRUB. If GRUB was implemented to replace the Windows bootloader instead of run on a separate drive, you could try re-installing the Windows bootloader using a Windows repair CD, installing the updates, and then reinstalling GRUB.
Are all the windows 7 machines you're referring to on a baseline level of at least SP1? Also, if they are all created from the same image it's not unsurprising they would have similar symptoms.
I would make sure that kb2949927, kb3033929, and kb3035131 are not in your list of Installed Updates. (kb2949927 was the original ,botched, then recalled, SHA-2 code signing update from MS, and if it's installed it might be causing problems as well.)
After you verify that I'd try re downloading and reinstalling kb3035131 first, then kb3033929... Once you're finally successful, it wouldn't hurt to make sure that all the relevant certificates are installed (to ensure you're not missing certs for some root or intermediary authorities)
Hope this helps in some way....
(Edited a few things, added GRUB info)
About rolling back telemetry KBs - it still leaves process called GWX.exe which still collects telemetry data and runs everytime OS is started.
I say don't update Windows OS, unless something doesn't work as it should. Setting updates to autopilot usually leave more stuff broken than fixed especially on music production PC (my case), which is very sensitive to software stability. It also inflates windows installation, as if it wasn't big enough already (17GB).
This folder is left after getting rid of those 4 KBs for Telemetry:
asymcon wrote: "I say don't update Windows OS, unless something doesn't work as it should."
Lots of the Windows updates are security patches that should get installed, even if you don't install the other updates. (Windows really "doesn't work as it should," except a user wouldn't necessarily know it unless they get hacked.)