This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi All.
I bought a new LifecamStudio 2 days ago. I installed the camera, following the instructions of course. In the end of the installation, I could se my self in the Lifecam software window, so far no problems, the camera worked. Suddenly a popup message appeared, telling me that the firmware of the camera needed to be upgraded, so I pressed OK. The firmware upgrade started but was shortly aborted with an errormessage, saying the upgrade was not succesfull. I tryed to reinstall the firmware, but now it tells me hat I already have the most recent firmware installed. So the nproblem is now that, when I instert my camera into the USB port windows finds the camera, but as soon as I start any program the uses the camera it goes from a Lifecam Icon (in the hardware manager that is) to a unknown unit. The Lifecam studio software tells me that no camera is installed. I have installed the camera on other computers without any luck.
/Stefan
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Fixed it :)
In device manager underneath imaging devices I saw "Webcam" -- before the botched fw update it said "Microsoft LifeCam Studio" and had a diff driver. I rolled back the driver (or if that doesn't work you can force it to use the one inside program files \ lifecam) then re-installed lifecam -- my cam now works. Now -- what's the deal with this update utility and why's it changing what driver the camera uses?
I think that this kind of thing is why Apple stock is doing as well as it is . . I am dumbfounded that Microsoft leaves posted firmware which will destroy a new, fresh out of the box piece of hardware.
R.
If you are having a similar issue, contact Microsoft and get a case #. Call (866) 833-7088
Microsoft seems to think this is an isolated issue based on the so called 'customer support' that I've received. I get 'scripted' responses from a foreign employee. They are clueless. Ask to speak with someone in the USA.
I have already had a MS technician confirm that it is a Microsoft issue and was told it would be elevated to the proper department and I would receive email on a fix. It's been well over a month, Still waiting.......
I think if enough people call in and complain it will become obvious that there is a problem that is not getting dealt with. Keep calling and following up daily, the more noise MS gets on this, the better the chance of getting some resolve. MS will also call you back to follow up - getting nothing accomplished that way either, just repetitive chit chat. This is an MS forum with enough complaints on this issue for over 2 years, yet Microsoft clearly doesn't care.
Next step; We all go bang on BILL GATES DOOR !!
If you are having a similar issue, contact Microsoft and get a case #. Call (866) 833-7088
Microsoft seems to think this is an isolated issue based on the so called 'customer support' that I've received. I get 'scripted' responses from a foreign employee. They are clueless. Ask to speak with someone in the USA.
I have already had a MS technician confirm that it is a Microsoft issue and was told it would be elevated to the proper department and I would receive email on a fix. It's been well over a month, Still waiting.......
I think if enough people call in and complain it will become obvious that there is a problem that is not getting dealt with. Keep calling and following up daily, the more noise MS gets on this, the better the chance of getting some resolve. MS will also call you back to follow up - getting nothing accomplished that way either, just repetitive chit chat. This is an MS forum with enough complaints on this issue for over 2 years, yet Microsoft clearly doesn't care.
Next step; We all go bang on BILL GATES DOOR !!
It is already an older model of camera, so Microsoft is just waiting for this one to time out. If you read pack this thread actually goes back years. If they had the least interest in these customer concerns they would have taken down the 'upgrade' ages ago.
This explains why I never use MS more than is absolutely necessary to get specific tasks done.
R.
Hi all, I haven't been given an official sanction to reply but I have been following and I don't think I'll get in trouble for saying this.
Looks like the ball got dropped at some point with regards to the firmware update process. I worked with some people internally and the forced firmware update has been removed from Windows Update, which should prevent further issues.
If you've had a camera that's been bricked due to the firmware update, please call the number Maneki Neko had posted and open a case. I would suggest pointing the support tech to this thread and requesting a replacement camera, as there's no way to recover it from the end-user perspective.
I'll see if I can get some traction on tightening the loop on this process, but I probably shouldn't make promises until I get some official word.
Yeah, we're slow sometimes, but we're watching and we're trying to do the right thing.
